Iteration: Elaboration Iteration [n]
This iteration includes the activities to be performed during an iteration in the Elaboration Phase. The goal of the elaboration phase is to baseline the architecture of the system to provide a stable basis for the bulk of the design and implementation effort in the construction phase. The architecture evolves out of a consideration of the most significant requirements (those that have a great impact on the architecture of the system) and an assessment of risk. The stability of the architecture is evaluated through one or more architectural prototypes.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Relationships
Parent Activities
Description

In this depiction of a system development Elaboration iteration, the Analysis and Design workflow differs from the software development plan in the activities that are invoked - Define Candidate System Architecture, Analyze System Behavior and Refine System Architecture in which the system architecture (structure, process and locality) is refined, along with the Subsystem Vision, Subsystem Use-Case Model and Subsystem Supplementary Requirements.

Subsystem development is shown as a summary activity which runs in parallel with the system-level iteration: this should expand into a set of subactivities which replicate those under Software Development if the subproject is substantially software, or a set similar to those in the top-level Systems Engineering plan, if the the subsystem is itself a composite of hardware, software, and people.

Note that Implementation has been reduced to system integration, given that all construction takes place at the subsystem level. Details of Implementation, Test and Deployment, as they are affected for system development, are out of scope for this release of RUP for Systems Engineering.

Properties
Event-Driven
Multiple Occurrences
Ongoing
Optional
Planned
Repeatable