






Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M3 -- Team Domain Design
Requirements
- Create team page and indicate your team members
- 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.
- Meet with assigned TA to discuss your design and get corrections.
Comments
- Brainstorming is fun and a good team-building exercise
- Filtering is easy to do and generally helps every feel involved
- The scenarios were not too difficult to come up with and everyone was able to participate. This was an easy way to divide up the work for this milestone
- The CRC cards are not just "intuitive," you really need to know what to look for when writing them
- Deciding stereotypes for some CRC cards is harder than you may think, and lead to an argument or two. Get a firm grasp on the stereotypes before starting the part.
- What we would've done differently
- Borrowed the CRC card book from Bob before hand. It really would have been a time saver in the end (not that this was a very time-intensive milestone)
Examples
Brainstormed Classes:
- Supplier
- Order
- EmergencyOrder
- Bob
- SupplyAppModel
- Retailer
- ItemPriceReport
- EmergencyOrderReport
- SupplierQuantityReport
- Item
- Invoice
- Purchase
- Marketer
- Policy
- Buyer
- Backorder
- Buyer Agent
- RetailerAppModel
- Company
- Supply Agent
- Lot
- Fish
- LotInventory
- CCS
- CCSAppModel
- Inventory
Filtered Classes:
- Supplier
- Order
- Retailer
- Item
- Invoice
- Buyer Agent
- Supply Agent
- Lot
- CCS
- Inventory
Scenarios:

CRC Cards:


Link to this Page