Page 4 of 56. Showing 559 results (0.02 seconds)
Copy of 5.09 - SRS - Software Requirements Specification
2D-Topic Page Message Content updates needed on this page: To be renamed to "5.09 - SRS - Software Requirements Specification" Fix References report Topic rewritten using AI inputs - CLS - Return to 7.18 - Documentation Guidance 1. Minimum Recommended Content Minimum recommended content for the Software Req5.10 - Freds - Alt - STP - Software Test Plan
2D-Topic Page Message Content updates needed on this page: To be renamed to "5.10 - STP - Software Test Plan" Content from AI has been added to this topic and the topic has been reorganized accordingly. Tabs were changed and added to align with the Recommended Content organization. In tab 1 item "k. Qualificat5.10 - STP - Software Test Plan
2D-Topic Page Message Content updates needed on this page: Renamed to "5.10 - STP - Software Test Plan" Content from AI was added to this topic and the topic has been reorganized accordingly. - 5/12/2025 Tabs were reorganized and new ones added to align with the Recommended Content organization. In tab 1 itemSWE-068 - Evaluate Test Results
2D-SWE Page Message 1. Requirements 4.5.5 The project manager shall evaluate test results and record the evaluation. 1.1 Notes NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this requirement. 1.2 History SWE-068 History 1.3 Applicability Across Classes 1.4 Related ActSWE-051 - Software Requirements Analysis
Requirements Analysis - Analyze requirements to ensure that they are necessary and sufficient - SP3.3 "In light of the operational concept and scenarios, the requirements for one level of the product hierarchy are analyzed to determine whether they are necessary and sufficient to meet the objectives of higher levels ofR002 - Incomplete Implementation Of Static Code Analysis Results
3 3 1. Risk Static code analysis is the process of analyzing source code without executing it, enabling the identification of potential defects, vulnerabilities, and adherence to coding standards early in the software development lifecycle. In NASA projects, static analysis plays a critical role inR001 - Incomplete Code Peer Reviews
3 3 1. Risk Code peer review is a critical quality assurance process that ensures the correctness, reliability, maintainability, and compliance of software to engineering and safety standards. In NASA's software projects, peer review plays an integral role in identifying and resolving issues relatedSWE-053 - Manage Requirements Changes
3.5. Management Practices - Control how requirements are introduced, changed, and removed. "The average project experiences about a twenty-five percent change in requirements after the requirements have been defined for the first system release, which causes at least a twenty-five percent schedule slip. Several studiesSWE-184 - Software-related Constraints and Assumptions
2D-SWE Page Message Content updates needed on this page: Update Guidance Update Software Assurance Added link to 8.01 - 1 place 1. Requirements 4.1.4 The project manager shall include software related safety constraints, controls, mitigations, and assumptions between the hardware, operator, and software in theSWE-052 - Bidirectional Traceability
2D-SWE Page Message 1. Requirements 3.12.1 The project manager shall perform, record, and maintain bi-directional traceability between the following software elements: Bi-directional Traceability Class A, B, and C Class D Class F Higher-level requirements to the software requirements X
