Phased Development
In classical phased development, the teams will finish and freeze specifications starting from the top level, for example, Stakeholder Requirements working down to the lower levels and to the right validation side of the V-Model like System Requirements will be finished based on the frozen content of the higher-level specifications. That process continues down through all specification level.
The goal of this phased approach is to:
• Support parallel working by starting work on the next phase (or version) of a high-level specification while the current phase in lower-level specifications is still being worked on.
• Preserve a consistent view on high-level specifications while work on lower-level specifications is being finalized.
• Establish a consistent view on a phase, even though the phase had been completed at different points in time on different specification level.
The following diagram shows how to implement a phased development approach with Working-Sets:
• Baselines are created for the stakeholder requirements once a specific state is reached.
• Working-Sets are created using the defined baselines of the stakeholder requirements.
• The Working-Set provides a consistent view and workspace to complete the phase.
• Unlike the approaches provided by other tools for phased development,Working-Sets allow working on multiple phases of the same specification level in parallel and then merge the results.
