Capability Pattern: Construction Phase Iteration
This iteration template defines the activities (and associated roles and work products) performed in a typical iteration in the Construction phase.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Description

The architecture should be stable when the Construction phase starts, allowing the remaining requirements to be implemented on top of it. Another advantage of validating the architecture and eliminating as many risks as possible during Elaboration is that it provides more predictability in Construction, which allows the project manager to focus on team efficiency and cost reduction.

Functionality is continuously implemented, tested, and integrated, resulting in builds that are more and more complete and stable. You may deploy a beta or prerelease to a sampling of the intended audience at the end of Construction. Delivery of the actual release is the main focus of the next phase.

The following table summarizes the Construction phase objectives and what activities address each objective:

Construction phase objectives and activities

Phase objectives

Activities that address objectives

Iteratively develop a complete product that is ready to transition to the user community

Identify System Goals and Requirements

Develop Solution Increment

Test Solution

Minimize development costs and achieve some degree of parallelism

Plan and Manage Iteration

Develop Solution Increment

Test Solution

Properties
Event Driven
Multiple Occurrences
Ongoing
Optional
PlannedYes
RepeatableYes

This material is made available under the Creative Commons—Attribution-ShareAlike License v3.0.

© Copyright 2013, 2014 by Institute for Software & Systems Engineering, University of Augsburg
Contributors
Contact: Jan-Philipp Steghöfer
Impressum

Parts of this material is based on the Eclipse Process Framework Practice Library, distributed under the Eclipse Public License V1.0.