Delivery Process: OpenUP/Basic Lifecycle | |
 |
Aimed to support small projects, this delivery process for iterative software development is based on risk management, driven by use cases and architecture centric. Development is based on iterations, use-case scenarios driven. Up-front thinking is invested on doing design and architecture, but capturing design and architectural decisions in visual models is optional. |
|
Work Product Breakdown
Prefix | Breakdown Element | Model Info | Entry State | Exit State |
| | Output | | |
| | Optional Input,Output | | |
| | Optional Input,Output | | |
| | Output | | |
| | Optional Input,Output | | |
| | Mandatory Input,Output | | |
| | Output | | |
| | Mandatory Input,Optional Input,Output | | |
| | Mandatory Input,Output | | |
| | Optional Input,Output | | |
| | Optional Input,Output | | |
| | Mandatory Input,Output | | |
| | Mandatory Input,Optional Input,Output | | |
| | Output | | |
| | Optional Input | | |
| | Mandatory Input,Output | | |
| | Mandatory Input,Output | | |
| | Mandatory Input,Optional Input,Output | | |
| | Mandatory Input,Output | | |
|