The activities in this stage result in the transformation of the system design into the first complete executable representation of the product. If required, the source code or COTS "glue" code, including suitable comments, is generated using the approved program specifications. The source code is then grouped into processable units and all high-level language units are compiled into object code. Unit testing is performed to determine if the code satisfies the program specifications and is complete, logical, and error free.

The operating documentation is also produced. The operating documentation is required for installing, operating, and supporting the product through its lifecycle.

Input:

The following items provide input to this stage.

SEM Templates:

• Conversion Plan
• Functional Design Document
• Maintenance Plan
• Requirements Specification
• Requirements Traceability Matrix
• System Design Document
• Test Plan
• Test Reports

PMM Templates:

• Project Plan
• Quality Management Plan
• Security Plan

Other Inputs:

• Data Dictionary

High-Level Activities:  

The remainder of this chapter is divided into sections that describe the specific high-level activities performed during this stage. These activities represent the minimum requirements for a large information systems engineering effort. Notes are provided, as applicable, to assist in customizing these lifecycle stage requirements.

The high-level activities are presented in the sections listed below.

7.1        Establish Development Environment

7.2        Develop Programs

7.3        Conduct Unit Testing

7.4        Establish Development Baselines

7.5        Plan Transition to Operational Status

7.6        Generate Operating Documentation

7.7        Develop Training Plan

7.8        Develop Installation Plan

Touch Points:  

The following touch points are involved in Construction Stage:

Contracts and Procurement

• Contract Liaison involvement if contract issues arise

E-Michigan

• Continue to work with E-Michigan's webmaster, as appropriate, to ensure ADA compliance and Michigan.gov look and feel standards

Infrastructure Services

• Infrastructure Specialist involvement in establishing hosting environments

Security

• Finalize Network and Data Flow diagrams

Output:            

Several work products are produced during this stage. The work products listed below are the minimum requirements for a large project. Deviations in the content and delivery of these work products are determined by the size and complexity of the project. Explanations of the work products are provided under the applicable activities described in the remainder of this chapter.

SEM Templates:

• Conversion Plan (revised)
• Installation Plan (initial)
• Maintenance Plan (revised)
• Requirements Traceability Matrix (revised)
• Test Plan (final)
• Test Reports (revised)
• Training Checklist (final)
• Training Plan (initial)
• Transition Plan (initial)

PMM Templates:

• Project Plan (revised)
• Security Plan (revised)

Other outputs:

• Development baselines
• Operating Documentation
• Users Manual
• Developer's Reference Manual
• Project Test File
• System units and modules

Review the Project Plan for accuracy and completeness of all Construction Stage activities and make any changes needed to update the information.

Review Process:         

Quality reviews are necessary during this stage to validate the product and associated work products. The activities that are appropriate for quality reviews are identified in this chapter and Chapter 2.0, Lifecycle Model. The time and resources needed to conduct the quality reviews should be reflected in the project resources, schedule, and work breakdown structure.

Structured Walkthrough (SWT)

Requirements for a peer review or a more formal structured walkthrough are documented under Review Process at the end of each Task, Subtask, or Activity section in this stage. The State of Michigan guide titled Structured Walkthrough Process Guide provides a procedure and sample forms that can be used for SWTs. This document is available on the MDIT SUITE website.

Stage Exit

Schedule a Stage Exit as the last activity of the Construction Stage to enable the project approvers to review project deliverables and provide a concur/non-concur position to the project manager. The State of Michigan guide titled Stage Exit Process Guide provides a procedure and sample report form that can be used for stage exits. This document is available on the MDIT SUITE website.

Complete Construction Stage Chapter of the SEM