Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M7 -- UI Implementation
Requirements
- Now code the remainder of the graphical UI portion. All the M6 functionality should now be available through a user interface.
Comments
- Our GUI was designed very well from the start, at least "on paper." It should have been a great model for the system as defined by the requirements.
- The CCS, Retailer, and Supplier all worked separately as individual application models. Each model was coded up separately and worked as a separate entity very well.
- Sell policy was a terribly implemented set of classes from the start. We knew what we wanted but the code just did not happen. By the end we got everything working, but fighting Smalltalk the entire way.
- Linking the CCS, Retailer and Supplier together. We did not think to test them all together since they functioned so well separately. This was a costly mistake
- What We Would've Done Differently
- We would have gotten a jump on M7 while coding M6. There was no reason not to start the GUIs while coding up the other stuff. It makes testing a breeze and makes this milestone a lot easier, we heard from other teams. In retrospect, we would've started this a lot sooner.
Examples
- Look at all GUI code in the editor (GUI code is denoted by a sideways square symbol)
http://www.prism.gatech.edu/~fcatalano3/SupplyChain.st
Link to this Page