Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M3 - Team Domain Design (CRC Cards/Scenarios)
Requirements:
- A brainstormed list of Domain classes
- A list of candidate classes after filtering
- A set of CRC cards for the candidate classes. Cards should be filled out on both sides (role stereotypes and responsibilities/purpose). These should real index cards, not a word document.
- A set of scenarios that cover typical uses of system and exercise the CRC Cards. The number of scenarios is left to you, but they should cover the major uses of the system.
Brainstormed Classes:
Filtered Classes:
- POS Location (sell policy is method of location)
- Inventory
- Item
- Order (from POS and then to supplier)
- Central Coordination System (CCS)
- Invoice (from supplier to POS)
- Supplier
- Backorder (extra credit)
- Report
CRC Cards
Scenarios
1. When item in Inventory = reorderPoint (out of stock)
Send message to POS Location to order more. Then POS Location will send an Order to CCS.
Then CCS sends/processes Order to Supplier. Then Supplier will send the items back to POS Location.
2. When item in Inventory = reorderPoint (out of stock) and no suppliers have items.
Send message to POS Location to order more. Then POS Location will send an Order to CCS.
Then CCS sends/processes Order to Supplier. Then Supplier will then make a BackOrder object to wait for new items.
3. You/CCS UI wants a report of emergency orders.
CCS UI calls the Report class that it wants an Emergancy order.
Report retrieves from CCS the data of normal and emergancy orders.
Report makes it into a graph and sends that report to CCS UI.
CCS UI displays the graph.
4. Supplier Receives Order and Creates Invoice
The Supplier receives an order from the CCS. It creates an invoice and
adds each of the items (setting the price, quantity and lot number).
Then it sends the invoice to the CCS which passes it along to the POS
Location that placed the order.
Link to this Page