| 2.1.6-3-1 Ensure the contractor's technical reviews meet all contract requirements and include software |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure review of the contractor's plans for technical reviews, including system requirements review, system design review, preliminary design review, software requirements and architecture review, critical design review, test readiness review, and other technical reviews to ensure that software criteria are included. Ensure that technical reviews comply with the Technical Reviews and Audits standard for software topics, including the entry and exit criteria. Ensure that all entry and exit requirements are met. Ensure that action items are taken, assigned to responsible engineers, and tracked to closure. Document all findings.
|
NA
|
NA
|
TOR-2007(8583)-6414 Technical Reviews and Audits for Systems, Equipment and Computer Software, Volume 1; TOR-2007(8583)-6414 Technical Reviews and Audits for Systems, Equipment and Computer Software, Volume 2
|
| 2.1.6-3-2 Ensure the contractor's program management effectiveness by performing independent modeling of the program management processes |
Phase 0 |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure independent modeling of the contractor's program management processes is performed to validate plans, to assess performance, or to identify process improvements when the processes fail to perform effectively. Independent modeling can be performed using static analysis, dynamic analysis, and other analysis techniques. Static analysis includes analysis of reported metrics. Dynamic analysis uses system dynamics modeling and contractor data to model program cost, schedule, and quality and to suggest changes to improve process performance. Document all findings.
|
NA
|
NA
|
CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 2.1.6-3-3 Ensure the contractor is performing in accordance with the program's defined processes by performing independent process appraisals |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure review of the contractor's performance to the program's defined processes. As stipulated in the contract, this may be accomplished by the contractor's quality organization in process audits, by a process appraisal performed by the contractor's organizational process group, or by program office personnel. It may also be performed independently by a Government process appraisal. The process appraisal should be conducted in accordance with the Software Engineering Institute's Standard CMMI Appraisal Method for Process Improvement (SCAMPI) and should be performed for the contractor's entire team, including all subcontractors with software responsibility. Ensure that findings and weaknesses from the process appraisal are addressed in a process improvement plan. Ensure that the contractor's performance to the process improvement plan is tracked to closure. Document all findings.
|
NA
|
NA
|
Standard CMMI Appraisal Method for Process Improvement (SCAMPI) A, Version 1.3: Method Definition Document. Software Engineering Institute. June 2, 2011
|
| 2.1.6-3-4 Ensure software readiness assessments are performed at identified milestones in the program |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure independent software readiness assessments are performed at identified milestones in the program, in accordance with the guidance in the Space Segment Software Readiness Assessment TOR. Ensure entry and exit criteria are defined for the readiness assessments. Ensure software is not promoted from one phase of the software development life cycle to the next based simply on schedule, but based on the demonstrated maturity of the software product. Ensure software readiness assessments include the software developed by all subcontractors. Document all findings.
|
NA
|
NA
|
TOR-2011(8591)-20, Space Segment Software Readiness Assessment
|
| 2.1.6-3-5 Ensure contractor installation and transition to operations planning is evaluated |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure assessment of contractor plans and procedures for installation of software at operational sites and transition to operations adequately describe the approach, methods, and resources required to install the software, maintain configuration management control, perform installation tests, and integrate with ongoing site activities. Ensure that local site acceptance, security, and other requirements are addressed. Verify that the plans and procedures are complete, feasible, and consistent.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter; TOR-2004(3909)-3537, Rev B, Software Development Standard for Space System)
|
| 2.1.6-3-6 Ensure the contractor transition to maintenance planning is evaluated |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure assessment of contractor plans and procedures adequately describes the approach, methods, and resources required to deliver the software and its required maintenance documentation to the maintenance organization, transition configuration management control, and provide a smooth transition to post-development maintenance. Verify that the plans and procedures are complete, feasible, and consistent. Ensure that plans are in place for robust software development and test environments at the maintenance site, and that these environments will continue to be maintained after launch to support anomaly resolution and changes to software including ground, on orbit software and operational flight constants.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter; TOR-2004(3909)-3537, Rev B, Software Development Standard for Space System)
|