In this stage, components are integrated and tested to determine whether the product meets predetermined functionality, performance, quality, interface, and security requirements. Once the product is fully integrated, system testing is conducted to validate that the product will operate in its intended environment, satisfies all user requirements, and is supported with complete and accurate operating documentation. User Acceptance Testing (UAT) follows System Testing, and solicits feedback from users to make any final adjustments to the programming before releasing the product for implementation.

Input:  

The following items provide input to this stage.

SEM Templates:

• Conversion Plan
• Installation Plan
• Maintenance Plan
• Requirements Specification
• Requirements Traceability Matrix
• Test Plan
• Integration testing (component to component)
• Performance testing (load, stress, etc.)
• System testing (end to end)
• User acceptance testing (UAT)
• Test Reports
• Integration test reports
• Performance test report
• System test reports
• User Acceptance test reports
• Transition Plan
• Training Plan

PMM Templates:

• Project Plan
• Quality Management Plan
• Security Plan

Other Inputs:

• Development Baselines
• Operating Documentation
• Users Manual
• Developer's Reference Manual
• Project Test File
• Software Modules

High-Level Activities:  

The remainder of this chapter is divided into sections that describe 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.

8.1        Conduct Integration Testing

8.2        Conduct System Testing

8.3        Conduct User Acceptance Testing

Touch Points:  

The following touch points are involved in Testing Stage:

Contracts and Procurement

• Contract Liaison involvement if contract issues arise

E-Michigan

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

Infrastructure Services

• Infrastructure Specialist involvement as documented in the Infrastructure Services Request (ISR)

Security

• Include application testing for security controls

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:

• Error Reporting and Tracking Checklist (final)
• Integration and System Testing Checklist (final)
• Pre-acceptance Checklist (final)
• Testing Package Checklist (final)
• User Acceptance Checklist (final)
• Conversion Plan (revised, if needed)
• Installation Plan (final)
• Maintenance Plan (revised)
• Requirements Traceability Matrix (final)
• Test Reports (final)
• Integration test reports
• Performance test report
• System test reports
• User Acceptance test reports
• Training Plan (final)
• Transition Plan (revised)

PMM Templates:

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

Other Outputs:

• Operating Documents (final)
• Users Manual
• Developer's Reference Manual

Review the Project Plan for accuracy and completeness of all Testing 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 Testing 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 Testing Stage of the SEM