Package Diagram “analysis”
Requirements.analysis
This is the initial analysis model.
Alias:
Initial Analysis Model
Stereotype:
problem domain
Note1:
This represents a "back of the envelope" scribble session to map out a rough analysis model. This model was eventually turned into the current problem domain (PD) object model. To get traceability, the PD classes are linked back to these original analysis-level classes. Also, these classes are similarly linked forward to the PD classes! You can do as much linking as needed.
Diagram Node Summary
Class: Most stores have cashiers that operate the cash registers.
Class: Stores sell products, which have a price.
Class: A sale is a simple transaction with a sense of who (Cashier), what (SaleDetails), and when (timestamp).
Class: The "many" side of the sale transaction.
Diagram Node Detail
Class "Cashier"
Most stores have cashiers that operate the cash registers.
Stereotype:
role
See Also:  Class Documentation

Class "Product"
Stores sell products, which have a price.
Stereotype:
description
See Also:  Class Documentation
All Outgoing Links
Hyperlink
to Class ProductDesc (in Package Diagram problem_domain)

Class "Sale"
A sale is a simple transaction with a sense of who (Cashier), what (SaleDetails), and when (timestamp).
Stereotype:
moment-interval
See Also:  Class Documentation
All Outgoing Links
Association
to Class Cashier
Attribute:
lnkCashier
Supplier Cardinality:
1
Client Cardinality:
1..*
Composition
to Class SaleDetail
Supplier Cardinality:
1..*
Client Cardinality:
1
Hyperlink
to Class CashSale (in Package Diagram problem_domain)

Class "SaleDetail"
The "many" side of the sale transaction.
Stereotype:
mi-detail
See Also:  Class Documentation
All Outgoing Links
Association
to Class Product
Attribute:
lnkProduct
Supplier Cardinality:
1
Client Cardinality:
1..*
Hyperlink
to Class CashSaleDetail (in Package Diagram problem_domain)