Project “CashSales”
Sep 14, 2005 5:41:55 PM
Package Summary
<default>
data_management
problem_domain The Problem Domain diagram is where business-level classes reside.
Requirements This top-level requirements diagram is used to help readers walk through the various requirements artifacts available for review.
Requirements.analysis This is the initial analysis model.
server
user_interface
util
Package Diagram Summary
<default>
analysis This is the initial analysis model.
data_management
problem_domain The Problem Domain diagram is where business-level classes reside.
Requirements This top-level requirements diagram is used to help readers walk through the various requirements artifacts available for review.
server
user_interface
util
Class Diagram Summary
Architecture View This diagram is designed to highlight the overall simple architecture of:
Object View The Object Diagram can help unwind what the state of the system might look like in a specific scenario.
OpenFirst This diagram is used to show new users how to navigate through the Cash Sales example.
System Overview This logical diagram walks you through the architectural views.
Use-Case Diagram Summary
Make A Sale This use case documents the requirements for how the system needs to make a sale.
Product Scanning Details This is the next level of information for a higher-level use case.
Component Diagram Summary
Component The Component Diagram can be used to help lay out the various parts of the system; their components, and the inerfaces that are supported and used.
Sequence Diagram Summary
Generated From Code This sequence diagram was generated automatically by Together based on existing source code.
Initializing GUI from PD
Persistent Save
Product Scan This sequence diagram illustrates how a product is scanned and priced.
Total of Sale
Collaboration Diagram Summary
Collaboration
Robustness Diagram Summary
Robustness Diagram A sample robustness diagram.
ER Diagram Summary
CashSales ERD Here is the schema for the Cash Sales system.