Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M6 - Domain Implementation (Main coding)
M6 is the main Domain implementation assignment for our final project.
We started out by planning out our design based on our UML diagrams. I highly recommend that you plan your design well ahead of time.
Our group divided up the work by giving each person a group of classes to design and implement.
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.
Criteria Breakdown:
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
Remember to do your best to get as much done as possible for the milestones. If you make a valid effort to complete this milestone, you may demo missing functionality later in the class without penalty.
Be sure to have the abilility to demo functionality to the TA. We do not code read for credit. You only get credit for features that are executing either from SUnit tests (preferred) or from a gui mockup.
CRUD = Create, Read, Update, Delete
Our first demo score and evaluation was as follows. However we were able to make up points in the final demo by having the functionality in the GUI.
Point of Sale Functionality Each POS has inventory of items............5/5
Inventory items are correctly accounted for including the concept of lot numbers.......10/10
Auto reordering functions properly..................................................7/7
Sell Policies are correctly handled ......................................................................7/7
Central Coordination System Functionality CRUD POS ............................................................7/7
CRUD Suppliers..............................7/7
Load and Save Simulation data .............................0/10
Route orders and invoices correctly.................................................7/7
Supplier Functionality Maintains inventory of items...............................5/5
Ensures each Lot of items has same price ..................5/5
Fills orders and send invoices .......................10/10
General Requirements SUnit Tests ...........................................................................3/10
Good Smalltalk comments, code and style....................................9/10
Link to this Page