Implementation of the product is initiated after all application testing has been successfully completed. This stage involves the activities required to install the software, databases, or data that comprise the product onto the hardware platform at the site(s) of operation. The activities associated with this stage should be performed each time the product is installed at a production site.
User training may be required to complete the implementation process. A description of the training necessary for developers, testers, users, and operations staff is provided in the Training Plan.
Input:
The following items provide input to this stage:
SEM Templates:
-
Conversion Plan
-
Installation Plan
-
Maintenance Plan
-
Training Plan
-
Transition Plan
PMM Templates:
-
Project Plan
-
Quality Management Plan
-
Security Plan
Other Inputs:
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 to accommodate the different sizes of information systems engineering efforts. The high-level activities are presented in the sections listed below.
9.1 Perform Installation Activities
9.2 Conduct Installation Tests
9.3 Transition to Operational Status
Touch Points:
The following touch points are involved in the Implementation Stage:
Contracts and Procurement
Security
Other
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 (final)
-
Maintenance Plan (final)
-
Transition Plan (final)
PMM Templates:
Other Outputs:
-
Converted data or system files
-
Installation Test materials
-
Operating documents
-
Operational software product
Review the Project Plan for accuracy and completeness of all Implementation 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 Implementation 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 forms that can be used for Stage Exits. This document is available on the MDIT SUITE website.
Complete
Implementation Stage
of the SEM
Printer Friendly
Text Version 
Email Page
