Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
Team Shiny Milestone 6
Team Shiny
Milestone 6
Team Shiny Project Description
M6 Requirements
-Implement Domain Objects
-Create SUnit tests to unit test your core Domain Objects (you do not need to write tests for trivial
accessor/modifier methods or for gui-specific methods)
The TA's will not type anything in the workspace except XXXAppModel open. Or TestRunner open. You have to
have code written for them to test your application. At the TA's discression, you may demo your application.
This demo may occur after the due date. You may demo the latest version of your code at the demo (i.e. you may
demo code written after due date), however you must submit your st file on t-square by the deadline to get full
credit on the milestone.
Tips
Did you enjoy all the neat design tools you saw in M5? It was perfect in theory. Excellent.
We threw it all out.
As it turns out, theory is only theory. During the actual coding phase for our project, we discovered that
our design was impractical in the worst way.
The main issue was that we took everything too literally during M5. For example, we assumed that the Supplier
class would only be responsible for creating items and other duties listed specifically in the project description.
However, in reality, we realized that we had not planned a way for Supplier to communicate with the CCS and vice versa.
Similarly, we had no way planned for the POS to communicate with the other two systems. Furthermore, we did not
even consider a way for POS to sell its items, only how it would receive items and send orders.
Ultimately, we did not plan beyond the specific requirements listed in the assignment. We did not put any
thought into how we would actually implement those requirements.
Code
Unit Tests
Grading Ruberic
Point of Sale Functionality
-Each POS has inventory of items............05
-Inventory items are correctly accounted for including the concept of lot numbers.......10
-Auto reordering functions properly..................................................07
-Sell Policies are correctly handled ............................................................07
Central Coordination System Functionality
-CRUD POS ............................................................07
-CRUD Suppliers...................................................07
-Load and Save Simulation data .................................10
-Route orders and invoices correctly....................................07
Supplier Functionality
-Maintains inventory of items...............................05
-Ensures each Lot of items has same price ..................05
-Fills orders and send invoices .......................10
General Requirements
-SUnit Tests ...........................................................................10
-Good Smalltalk comments, code and style....................................10
Team Shiny Milestone 7
Team Shiny
Links to this Page