| 5.4-1-1 Ensure system, segment, and element-level requirements definition and management processes include software representation |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure contractor and Government software personnel participate in defining, recording, and managing the system, segment, and element-level requirements. Ensure contractor and Government software personnel participate in defining and recording system, segment, and element-wide requirements decisions. Ensure contractor and Government software personnel participate in system, segment, and element-level requirements reviews. Ensure key decisions made during the system, segment, and element-level requirements development process are documented.
|
NA
|
NA
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-2 Ensure system, segment, and element-level requirements are properly allocated to software |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure contractor and Government software personnel participate in the allocation of system, segment, and element-level requirements to software. Ensure system, segment, and element-level requirements are properly allocated to software and that trade studies are performed to properly allocate performance requirements to hardware and software. Ensure the results of trade studies are documented and communicated to software personnel. Ensure the requirements allocations to hardware and software are documented in the appropriate requirements specifications and reviewed by relevant stakeholders.
|
NA
|
System Requirements Document; System Requirements Allocation Matrix; System/Segment Specification (SSS)
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-3 Ensure the system, segment, and element-level requirements specifications include software-related requirements |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure system, segment, and element-level requirements specifications, including interface specifications include software-related requirements such as specialty engineering requirements that will be implemented in software. Ensure technical performance measures and key performance parameters that will impact software are defined. Ensure system, segment, and element-level dependability requirements include software. Note that dependability includes reliability, maintainability, availability, and safety. Ensure system, segment, and element-level quality attribute requirements include software.
|
NA
|
System Requirements Document; System Requirements Allocation Matrix; System/Segment Specification (SSS)
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-4 Ensure the software requirements are correct, complete, consistent, feasible, and clearly and unambiguously stated |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure software requirements are validated against user intent, including review by relevant stakeholders. Ensure software requirements correctly include all functional, performance, and non-functional requirements. Non-functional requirements include quality attributes, safety, and security. Ensure the contractor documents all analyses, models, simulations, and trade study decisions that are used in the process of software requirements definition. Ensure the associated reports and conclusions are clear and unambiguous and are reviewed by relevant stakeholders. Perform independent validation of key software requirements as appropriate.
|
NA
|
System/Segment Specification (SSS)
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-5 Ensure bi-directional traceability exists between software requirements and higher-level requirements, between software requirements and the system operational concept |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure bi-directional traceability between the software requirements and their parent requirements are documented via the use of a verification cross-reference matrix or equivalent method. Ensure bi-directional traceability between the software requirements and the operational concept, scenarios, and use cases are documented as appropriate and reviewed. It is especially important that the bi-directional traceability continued to be maintained up-to-date if an iterative life cycle model is used.
|
NA
|
System/Segment Specification (SSS); System Requirements Allocation Matrix; System CONOPS
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-6 Ensure the software requirements include appropriate software specialty engineering, fault management, functional performance, and information assurance requirements |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure software dependability and security requirements cover program needs. Note that software dependability includes reliability, maintainability, availability, and safety. Ensure software fault management requirements cover program needs. Ensure appropriate human machine interface (HMI) requirements are defined. Ensure appropriate software performance requirements with allocations based on analyses are defined. Ensure software-related information assurance/cyber security and software safety requirements are defined. Ensure the software requirements clearly identify and fully define operational modes (normal mode, graceful degradation, safe mode, or other contingency modes). Ensure the software requirements include failure detection, containment, diagnosis, recovery and reporting requirements, including which mechanisms will be automated and what classes of failures will be covered (for example, are only single-event failures handled). Ensure that capabilities for operator monitoring and control are defined. Ensure that timing requirements defined for both steady state and recovery -- in particular, isolation, recovery and repair durations (average and maximum) have been identified and allocated. Ensure that computing resource requirement margins account for anticipated error and recovery rates.
|
NA
|
System/Segment Specification (SSS)
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; SMC-S-013, Reliability Program for Space Systems, 13 June 2008 (also published as TOR-2007(8583)-6889 under same title) or equivalent
|
| 5.4-1-7 Ensure software requirements are documented in software requirements specifications and interface specifications that comply with the data item descriptions and all contract requirements |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure software requirements are formally inspected in product evaluations and peer reviews, formal requirements reviews, and joint technical reviews as defined in the program's Systems Engineering Management Plan (SEMP) and Software Development Plan (SDP).
|
NA
|
Configuration Item (Hardware, Software and Firmware) Requirements Specifications; Interface Requirement Specification (IRS)
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-8 Ensure the software requirements definition and management process is complete, correct, effective, and meets all contract requirements |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure contractor software personnel are trained in the program's defined software processes, including all subcontractor personnel with software responsibility. Ensure software requirements personnel have adequate resources to perform the requirements definition and management tasks. Ensure the software requirements definition process incorporates operational concepts, scenarios, and use cases as applicable. Ensure the software requirements definition and management process requires software requirements to be validated via analysis, modeling, or simulation. Ensure the software requirements definition and management process is monitored, controlled, periodically reviewed, and evaluated for adherence.
|
NA
|
NA
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-9 Ensure software requirements definition and management includes specification and application of applicable standards |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure software requirements definition includes specification of applicable software standards, practices, and conventions, both Government and contractor. These standards may include programming practices, human-system interface, backwards compatibility, network protocols, and product interoperability. Ensure, in addition to the system, segment, and element-level requirements allocated to software, additional requirements are derived from software standards, specifications, and practices.
|
NA
|
Software Quality Assurance (SQA) Plan
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-10 Ensure software requirements definition and management tools and methods are effective and appropriate |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure the program's defined software requirements definition and management process requires the use of a requirements management tool and includes configuration management and bi-directional traceability. Ensure the tools supporting the software requirements definition processes are applicable to the methods and techniques documented in the processes and Software Development plan. Ensure analysis, modeling, and simulation tools are available for use in validating the software requirements. Ensure program software personnel are adequately trained in the use of the tools, including all subcontractors with software development responsibility. Ensure the tools are being used effectively across all program software development personnel at all locations. Note that the Government may choose to install the same requirements management tool used by the contractor for easy access to current requirements status.
|
NA
|
Software Quality Assurance (SQA) Plan
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-11 Ensure independent software requirements analyses are executed and documented |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure software requirements validation is performed to be sure the right system is being built. Ensure higher level requirements allocation to software is complete. Ensure, via analysis, that computer resource margins are adequate. Ensure the independent software analysis activities result in a clear and unambiguous evaluation of the contractor's analytical studies, models and simulations, and trade studies that are used in the process of software requirements definition. Ensure the results of these independent software analyses are documented and kept up to date.
|
NA
|
NA
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|
| 5.4-1-12 Ensure computer software resource analyses have been performed and margin budgets are adequate to meet program needs |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure initial computer software resource utilization analyses (e.g., processor throughput, memory, storage, and bandwidth) are performed for all software items. Ensure initial computer software resource utilization budgets are allocated to software items and are consistent with margin requirements. Ensure, if multiple software items share processor resources, allocations made total no more than 100% of the budget. Independent software analyses for key resource requirements may be performed.
|
NA
|
NA
|
TOR-2004(3909)-3537 SW Development Standard for Space Systems; TOR-2011(8591)-20 Space Segment SW Readiness Assessment; CMMI for Development, Version 1.3. Technical Report CMU/SEI-2010-TR-033, Pittsburgh: Carnegie Mellon University, 2010
|