Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
Milestone 9-Design Twist
Finally, the time had come for the final m9 project. With two experienced web developers on the team, we figured the m9 design twist would be a "piece of cake". We could not have been so wrong. In the beginning, we were optimistic and determined create a mind blowing, amazing web site so that even the professor would be speechless. Instead, we ended up spending countless nights burning the midnight oil trying to figure out how to link dynamically link smalltalk into the static html and totally forgot the fancy stuff. I say our efforts payed off really well because I am 100% sure that our project is still the best in the class. :)
Login Page
Our login page uses basic session vars and a text database. Our validating script looks through the text containing user names and passwords to match with the input text. If it finds a match, the script then creates session vars to keep the user logged in at all times. Without session vars, the user cannot view any other pages.
Here is an example of our session var code:
session at: 'loggedin' put: userName.]. (For logging in)
session at: 'loggedin' ifAbsent:[ some code here]. (For checking to see if a user is logged in)
session removeKey: 'loggedin'. (For logging out)
CCS Page
When a user successfully logs in, they are automatically redirected to the CCS page. Because our group did not fully read the m9 instructions, we thought that we had to have nearly all of the functionality on m7 also on m9. That is why we have Add/Remove/View functions on both POS and Suppliers when we only needed a couple functions on the POS. We have the CCS initially start out with a default POS and Supplier. Users can also modify whatever they want to and save and load their modifications on this page.
Supplier Page
In the Supplier page, the user can add or remove items for a specific supplier. Since each supplier page had to be unique for different suppliers, we passed supplier names as query strings to make this happen. This way, no more than one supplier will have the same item. This is how a typical supplier URL looks like: http://teamvelociraptorsrus.com/supplier.ssp?name=Dunder+Miflin+Warehouse&Submit=Add+Item
Pos Page
Our POS page looks almost exactly like the Supplier Page except for one difference. The POS page has a "Order Item" button instead of a "Add Item" button. The Order Item Button opens a popup that displays the POS' inventory and a list of all items that all suppliers contain. The Pos is able to choose from the supplier list and add the item to itself. Once the item is added, the main POS window is updated too. Again, we use query strings to pass the POS name so that each POS inventory can be unique.
Site Map, Flow Chart, Wire Frame
We were required to include these for m9:
Although we spent so much time and effort on stuff that we did not need to do, we are glad that we did it anyways. After struggling to get all the html, javascript and query string to work together without problems, we had fully functioning web application online. To make our web app even more amazing, one of our web developers added in css style sheets and a background template that makes our website look very professional in my opinion. ^_^
THE END
Link to this Page