Develop and build detailed designs and IT solutions to the requirements identified in the Define Phase.  Based on the architectural design from the Define Phase, the detailed design is developed and documented, and system components are built and integrated.  Product support documentation is also developed in the Construct Phase.  Unit and integration testing is performed as the product components are built and groups of components are integrated into subsystems.  Design components are mapped to requirements to ensure that all requirements are incorporated into the designs of the system and its components. 


Planning and preparation for work to be performed in subsequent phases of the project and for transitioning the system to an ongoing operational organization are performed.  Plans for system testing and user acceptance testing are created.  


The Construct phase is divided into the Detailed Design and Build sub-phases.  A supplier has primary responsibility for the activities in the Construct phase, emphasizing the Outsourced Model.

 The Detailed Design is developed based on the requirements and architectural design from the Define phase.  The preparation of the development environment is completed early in this sub-phase to allow for coding, configuring, unit and integration testing of individual system components to begin during this sub-phase.

 During the Build sub-phase, the team or supplier(s) continues in performing the technical activities of developing and integrating the system components. This approach facilitates iterative development of the solution.  The System Test Plan, system documentation, operations and support plans are also completed during this sub-phase.  The test environment is prepared for system and user acceptance testing.

 Throughout the Construct phase, the Program and Project is responsible for change management and the planning of the user acceptance test, in addition to on-going reviews of Supplier progress.  The Construct phase finishes with a Construct Tollgate, which provides a Go/No-Go decision for the project to continue.

Entrance Criteria:

  • System Design Document baseline communicated to Development Team
  • Approved Specifications for System Documentation delivered to Development Team
  • Standards Bill of Materials baseline communicated to Develop Team
  • Development Team oriented on organizational data and standards enabling the development team to follow the standards for building the system
  • Operations and Support Manager oriented on the Application and/or System

Exit Criteria:

  • Requirements Traceability Matrix updated with references to Unit Test Cases and Integration Test Cases
  • System packaged with unit tested source code, Unit Test Cases, Build Procedures and updated Requirements Traceability Matrix.

Process and Procedures:

Tailoring Guidelines:

  • None

Process Verification Record(s):

  • Completed System Delivery Checklist
    • Stored By: Project Manager
  • Correspondence over e-mail clarifying the requirements, architecture and design.
    • Stored By: Project Manager
  • Updated RTM with references to Unit Test Cases and Integration Test Cases
    • Stored By: Project Manager


  • None


  • None