July 2001
Intermediate to advanced
656 pages
15h 51m
English
As in the prior use case chapter, Table 7.1 summarizes a sample of artifacts and their timing. All requirements artifacts are started in inception, and primarily worked on through elaboration.
| Discipline | Artifact | Incep. | Elab. | Const. | Trans. |
|---|---|---|---|---|---|
| IterationÜ | I1 | E1..En | C1..Cn | T1..T2 | |
| Business Modeling | Domain Model | s | |||
| Requirements | Use-Case Model | s | r | ||
| Vision | s | r | |||
| Supplementary Specification | s | r | |||
| Glossary | s | r | |||
| Design | Design Model | s | r | ||
| SW Architecture Document | s | ||||
| Data Model | s | r | |||
| Implementation | Implementation Model | s | r | r | |
| Project Management | SW Development Plan | s | r | r | r |
| Testing | Test Model | s | r | ||
| Environment | Development Case | s | r |
It should not be the case that these requirements artifacts ...
Read now
Unlock full access