Unified Process model - kubapeter/portfolio GitHub Wiki
The Unified Process model is a [parallel process model]] of [[software development]]. Its basic structure has sequential [phases within a repeatable cycle. Within most of the Unified Process model’s phases, work happens in small iterations until the phase is considered complete, i. e. when a milestone, a specific and identifiable point in a project, is reached.
The model allows for tasks done in one phase to also occur in another. So, a requirements task or activity can happen throughout all the phases instead of in just one.
Phases
The Unified Process model has four phases, with each phase having a distinct aim.
- Inception phase - goals:
- creation of basic use cases
- definition of the project’s scope
- definition of the potential project risks
- Elaboration phase - goals:
- create design models and prototypes of the product
- refine requirements conceived earlier
- address risks
- Construction phase - goals:
- develop full use cases
- Transition phase - goals:
- gathering analysing user feedback
The iterations circle around phases 2, 3 and 4. Phase 1 happens only once. Iterations also happen within phases; for example, the elaboration phase may lead to several iterations of design before the work product is ready for the construction phase.
Phases and prototypes
- In the inception phase an illustrative prototype can be produced.
- Subsequent phases could build on this illustrative prototype with either an incremental or an evolutionary prototype approach