2.12. How to Customize the Process? The UP Development Case
Are There Optional Artifacts or Practices in the UP?
Yes! Almost everything is optional. That said, some UP practices and principles are invariant, such as iterative and risk-driven development, and continuous verification of quality.However, a key insight into the UP is that all activities and artifacts (models, diagrams, documents, …) are optional well, maybe not the code!
Analogy The set of possible artifacts described in the UP should be viewed like a set of medicines in a pharmacy. Just as one does not indiscriminately take many medicines, but matches the choice to the ailment, likewise on a UP project, a team should select a small subset of artifacts that address its particular problems and needs. In general, focus on a small set of artifacts that demonstrate high practical value. |
Definition: What is the Development Case?
The choice of practices and UP artifacts for a project may be written up in a short document called the Development Case (an artifact in the Environment discipline). For example, Table 2.1 could be the Development Case for the "NextGen Project" case study explored in this book.
Discipline | Practice | Artifact | Incep. | Elab. | Const. | Trans. |
---|---|---|---|---|---|---|
Iteration | I1 | E1..En | C1..Cn | T1..T2 | ||
Business Modeling | agile modeling req. workshop | Domain Model | s | |||
Requirements | req. workshop vision box exercise dot voting | Use-Case Model | s | r | ||
Vision | s | r | ||||
Supplementary Specification | s | r | ||||
Glossary | s | r | ||||
Design | agile modeling test-driven dev. | Design Model | s | r | ||
SW Architecture Document | s | |||||
Data Model | s | r | ||||
Implementation | test-driven dev. pair programming continuous integration coding standards | … | ||||
Project Management | agile PM daily Scrum meeting | … | ||||
… |