Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M5 - Application Design (OOA)
M5 Detailed Requirements
M5 Requirements:
- Architecture/Trust Boundaries
- Application/Utility Class Identification
- Updated CRC Cards (updated version loaded into M3 swiki page)
- Updated Scenarios
- UML Class Diagram
- UML Sequence Diagrams (based on a scenario)
- User Interface Screen Prototypes
- Contract
- Exception Handling Strategy
Layered System Architecture
Trust Boundaries
A bit messy because so many classes were connected to many more
UML Class Diagram:
Overview of Class Diagram:
Details of Class Diagram:
User Interface Screen Prototypes
Scenarios used in UML Sequence Diagrams
Scenario 1:
A new company, NewbsRUs, has just entered the market as a supplier. They sell 2 products: CoolItem1 and CoolItem2. They wish to be involved in the supply chain, so the CCS administrator is contacted. He/She then adds NewbsRUs as a new Supplier. NewbsRUs must now enter their inventory details, by adding their 2 products into their inventory and setting the correct amounts and prices for each item.
Scenario 2:
A new company, Whits Store, has just entered the market as a retailer (POS Location). They are looking to sell DVDs and CDs. They contact the CCS administrator so that they can be included in the Supply Chain system and be in contact with some suppliers. The CCS administrator adds Whits Store as a new POS Location. The inventory specialists now send orders to Supplier A, Supplier B, Supplier C, Supply X and Supply Y.
UML Sequence Diagrams
Contracts
Error/Exception Handling Strategy
Link to this Page