Development Case: Implementation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Artifacts | How to use | Review Details | Tools Used/ Templates/ Examples | |||
| Incep | Elab | Const | Trans | |||
| Implementation Model | Could | Must | Must | Must | Formal- Internal |
Template- Implementation Model |
| Could | Must | Must | Must | Formal- Internal |
||
| Could | Must | Must | Must | Formal- Internal |
||
| Could | Must | Must | Must | Formal- Internal |
||
| Integration Build Plan | Could | Must | Must | Must | Formal- Internal |
Template: Integration Build Plan |
| Software Architecture Document (Implementation View) | Could | Must | Must | Must | Formal- External |
Template: Software Architecture Document |
None
None
None
Informal code reviews are performed.
When configuring the Implementation Discipline help can be found in:
You should also familiarize yourself with:
![]()
|