文档介绍：Sample Unified Process Artifacts and Timing (s-start; r-refine)
Discipline Artifact Incep. Elab. Const. Trans.
Iteration^ 11 T1..T2
Business Modeling Domain Model s
Requirements Use-Case Model s r
Vision a r
Supplementary Specification s r
Glossary s r
Design Design Model SW s s r r
Architecture Document Data s
Model
Implementation Implementation Model s r r
Project Managemen t SW Development Plan s r r r
Testing Test Model s r
Environment Development Case s r
Sample Unified Process Artifact Relationships
Domain Model
Sale Register ProductCatalog . . .
Captured-on
timeStamp 1 1 ... . . . . . .
domain concepts
Use-Case Model
: System
Process Sale : Cashier
make Process
1. Customer NewSale() Sale
system
arrives ... Cashier
events
2. Cashier enterItem
(id, quantity)
makes new ...
conceptual sale.
classes in 3. ...
the
domain Use Cases System Sequence Diagrams Use Case Diagrams
inspire the
names of
some
software use-case Design Model
classes in realization with
the design interaction : Register : ProductCatalog
diagrams
makeNewSale()
create()
: Sale
enterItem(id, quantity)
spec := getSpecification( id )
addLineItem( spec, quantity )
. . .
the design
Register classes
ProductCatalog discovered
... 1 while designing
1 ...
UCRs can be
makeNewSale()
getSpecification(...) : ProductSpecification summarized in
enterItem(...)
... class diagrams
...
General Responsibility Assignment Software Patterns (GRASI)
Pattern Description
Information A general principle of object design and responsibility assignment?
Expert Assign a responsibility to the information expert — the class that has the information necessary
to fulfill the responsibility.
Creator Who creates? (Note that Factory is mon alternate solution.)
Assign class B the responsibility to create an instance of class A if one of these is true: 1.
B contains A 4. B records A
2. B