This was my CSCE Capstone project: Should Cost Analysis. It was a fairly simple design to find commodity prices and break down products into commodities so that people could figure out how much a fair price for an object would be.
I'm not going to discuss the grade we got for it or the class itself. I think that my group did a good job, and from what I can tell most of them are doing well now; I'm happy about that. But given my health problems during the semester, I don't think that I, personally, did as much as I could have. And I would like to do more work on it, expand it, create an interface that'll work with multiple databases and multiple commodity APIs and such. I want to make it secure, which I know will require a full redesign. I want to make the code cleaner and easier to read if you're coming into it blind, and part of that will be disconnecting it from the CSS we generated for it via a third-party site. (The site's formatting looked fine, but it's going to be a good way to learn more about CSS, if nothing else.)
I already have some of the work done; one of the first things I wanted to do was switch any remaining Postgres-only pg_connect logic to the more generic PDO type. I know that pg_connect probably has better performance if you know you're going to be working with Postgres, but other users might prefer other databases. The big thing about PDO is that you can use MySQL or SQLi or whatever type you want to use and still be able to connect to the database without making a big effort to edit the code.
My fork for the project is here. I have finished some unrelated projects and have more time to work on it now, so I'm hoping to finish the PDO swap soon, and to start on a few more of the project objectives that I have already added.