Operational Support Phase Checklist

– SDM Operational Support Phase Checklist Last Update: Yes No N/A Problem/Modification Identification SDM Reference Comments 1. A procedure exists for handling emergency changes  Problem/Modification Identification that cannot be implemented as part of a scheduled (10.1) release. 2. An identification number is assigned to the  Problem/Modification Identification modification. (10.1) 3. The modification is categorized as corrective,  Problem/Modification Identification adaptive, emergency, scheduled, or perfective (10.1) 4. The modification is analyzed to determine whether to  Problem/Modification Identification accept, reject or further evaluate. (10.1) 5. Software changes are assigned an initial priority  Problem/Modification Identification ranking as emergency, mandatory, required, or nice (10.1) to have. 6. Modification requests and process determinations  Problem/Modification Identification have been uniquely identified and placed into the (10.1) project folder. 7. A peer review has been conducted (as appropriate)  Problem/Modification Identification on problem/modification identification (10.1) 8. Metrics are recorded (e.g., number of requests, time  Problem/Modification Identification expended for problem validation) (10.1) Yes No N/A Analysis Phase SDM Reference Comments 1. A preliminary estimate of the modification  Analysis Stage (10.2) size/magnitude has been made.

2. The impact of the modification has been assessed.  Analysis Stage (10.2) 3. The Modification Requests are assigned to a block of  Analysis Stage (10.2) modifications scheduled for implementation. 4. The modifications are coordinated with other ongoing  Analysis Stage (10.2) maintenance tasks. 5. Once modifications are agreed to, firm requirements  Analysis Stage (10.2) have been defined.

6. Elements of the modification have been identified.  Analysis Stage (10.2)

SDM Operational Support Phase Checklist Page 1 of 7 – SDM Operational Support Phase Checklist Last Update:

7. Safety and security issues have been identified.  Analysis Stage (10.2) 8. A test and implementation strategy exist (includes  Analysis Stage (10.2) unit, integration and user-oriented functional tests). 9. The regression test requirements associated with the  Analysis Stage (10.2) testing levels have been identified. 10. When identifying the elements of the modification, all  Analysis Stage (10.2) outputs were examined, including: . A specification of the portion of the product to be modified . The interfaced affected . The user-noticeable changes expected . The relative degree and kind of experience required to make the change . The estimated time to complete the modification 11. The test cases used to establish the test baseline  Analysis Stage (10.2) was revalidated. 12. The relevant system documentation from the  Analysis Stage (10.2) configuration control process was retrieved. 13. The proposed changes and engineering analysis to  Analysis Stage (10.2) assess the technical and economic feasibility, and correctness are reviewed. 14. Consideration was given for the integration of the  Analysis Stage (10.2) proposed change within the existing software. 15. Verification of all appropriate analysis and project  Analysis Stage (10.2) documentation is updated, properly controlled and maintained in the project folder. 16. It has been verified that the changes and schedule  Analysis Stage (10.2) can support the proposed test strategy. 17. Resource estimates and schedules have been  Analysis Stage (10.2) reviewed and their accuracy verified. 18. A technical review to select the problem reports and  Analysis Stage (10.2) proposed enhancements to be implemented was conducted.

19. The detailed analysis report includes:  Analysis Stage (10.2) . The updated requirements (including the traceability list) . The test strategy . The Project Plan 20. At the completion of the analysis phase, a risk  Analysis Stage (10.2) analysis was performed. 21. A review was conducted and concurrence to proceed  Analysis Stage (10.2) to the design phase was given. Yes No N/A Design Phase SDM Reference Comments

1. Selected software modules have been identified.  Design Stage (10.3) 2. Software module documentation has been modified  Design Stage (10.3) (e.g., data and control flow diagrams, schematics). 3. Test cases, including safety and security issues have  Design Stage (10.3) been created for the new design.

4. Regression tests have been identified and created.  Design Stage (10.3) 5. Documentation update requirements have been  Design Stage (10.3) identified (system/user).

6. Modification list has been updated.  Design Stage (10.3) 7. Any known constraints and any possible actions  Design Stage (10.3) taken or recommended that mitigate risk have been documented.

8. The new design/requirement has been documented  Design Stage (10.3)

as an authorized change. 9. Inclusion of new design material, including safety and  Design Stage (10.3) security issues has been verified. 10. The appropriate test documentation has been  Design Stage (10.3) updated. 11. Traceability of the requirements to the design has  Design Stage (10.3) been completed.

12. Outputs for the Design Phase maintained in the  Design Stage (10.3) project folder include: . Revised modification list . Updated design baseline . Updated test plans . Revised detailed analysis . Verified requirements . Updated Project Plan . Documented constraints and risks 13. Structured Walkthroughs, In-Phase Assessments,  Design Stage (10.3) and Phase Exits for the design phase have been conducted as appropriate. Yes No N/A Development Phase SDM Reference Comments 1. Code changes have been implemented and unit  Development Phase (10.4) tested. 2. After coding and unit test, the modified software has  Development Phase (10.4) been integrated with the system, at appropriate intervals, and integration and regression tests refined and performed. 3. Risk analysis and review have been performed  Development Phase (10.4) periodically during the Development Phase.

4. A Test Readiness Review has been conducted.  Development Phase (10.4) 5. All effects (e.g., functional, performance, usability) of  Development Phase (10.4) the modification have been assessed and noted. A return to coding and unit testing is made to remove any unacceptable impacts. 6. Metrics/measurement data have been used to  Development Phase (10.4) quantify risk analysis. 7. Unit and integration testing was performed and  Development Phase (10.4) maintained in the project folder 8. Test documentation (test plans, test cases, and test  Development Phase (10.4) procedures) are either updated or created.

9. Risks are identified, documented and resolved during  Development Phase (10.4) the software and readiness reviews. 10. Software is placed under software configuration  Development Phase (10.4) management control. 11. Training and technical documentation has been  Development Phase (10.4) updated. 12. Traceability of the design to the code has been  Development Phase (10.4) verified. 13. Outputs for the Development Phase maintained in  Development Phase (10.4) the project folder include: . Updated software . Updated design documentation . Updated test documentation . Updated user documentation . Updated training material . Statement of risk and impact to users . Test Readiness Review report 14. Structured Walkthroughs, In-Phase Assessments,  Development Phase (10.4) and Phase Exits for the development phase have been conducted as appropriate. Yes No N/A System Test Phase SDM Reference Comments 1. System tests were conducted on a fully integrated  System Test Phase (10.5) system and included: . System functional testing . Interface testing . Regression testing . A Test Readiness review to assess preparedness for acceptance testing 2. Results conducted before the Test Readiness review,  System Test Phase (10.5) were not used as part of the system test. 3. The status of the activities was reported to the  System Test Phase (10.5) appropriate reviewers before proceeding to acceptance testing.

4. Outputs for the System Test Phase for software  System Test Phase (10.5) maintenance maintained in the project folder include:

. Tested and fully integrate system . Test report . Test Readiness Review report . Updated Project Plan 5. Structured Walkthroughs, In-Phase Assessments,  System Test Phase (10.5) and Phase Exits for the system test phase have been conducted as appropriate. Yes No N/A Acceptance Phase SDM Reference Comments 1. Acceptance tests have been performed at the  Acceptance Phase (10.6) functional level 2. Interoperability testing (validating any input and  Acceptance Phase (10.6) output interfaces) was performed.

3. Regression testing was performed  Acceptance Phase (10.6) 4. A Functional Configuration Audit (FCA) was  Acceptance Phase (10.6) conducted. 5. Results of the FCA are reported to ensure all  Acceptance Phase (10.6) functionality is present in the system. 6. Confirmation is obtained from the change authority  Acceptance Phase (10.6) indicating the change has been successfully completed. 7. A new system baseline has been established and  Acceptance Phase (10.6) documented. 8. The acceptance test items (i.e., software units,  Acceptance Phase (10.6) documentation) have been placed under software configuration management control. 9. Outputs for the Acceptance Phase maintained in the  Acceptance Phase (10.6) project folder include: . New system baseline . Functional Configuration Audit (FCA) Report . Acceptance Test Report . Updated Project Plan . Update modification request log

10. Structured Walkthroughs, In-Phase Assessments,  Acceptance Phase (10.6) and Phase Exits for the acceptance phase have been conducted as appropriate. Yes No N/A Delivery Phase SDM Reference Comments

11. The User Community has been notified.  Delivery Phase (10.7) 12. An archival version of the system has been created  Delivery Phase (10.7) for backup. 13. Installation and training has been performed at the  Delivery Phase (10.7) user facility. 14. Access has been provided to the system materials for  Delivery Phase (10.7) users 15. The version description document (VDD) has been  Delivery Phase (10.7) completed and placed under configuration management.

16. A Physical Configuration Audit has been performed.  Delivery Phase (10.7) 17. Structured Walkthroughs, In-Phase Assessments,  Delivery Phase (10.7) and Phase Exits for the delivery phase have been conducted as appropriate.

18. All documentation is maintained in the project folder.  Delivery Phase (10.7)

SDM Operational Support Phase Checklist Page 7 of 7