A. Introduction
B. Institutional Requirements
C. Project Software Requirements
D. Topics
E. Tools, References, and Terms
F. SPAN (NASA Only)
changes.mady.by.user Haigh, Fred
Saved on Mar 03, 2023
Saved on Mar 04, 2023
...
Benchmarking and Appraisals
3.9 Software Development Processes and Practices
SWE-004 - OCE Benchmarking
SWE-129 - OCE NPR Appraisals
SWE-209 - Benchmarking Software Assurance and Software Safety Capabilities
SWE-221 - OSMA NPR Appraisals
8.12 - Basics of Software Auditing
Licensing, Sharing and Reuse
Also see 3.10 Software Reuse
SWE-215 - Software License Rights
SWE-216 - Internal Software Sharing List
SWE-217 - List of All Contributors and Disclaimer Notice
SWE-214 - Internal Software Sharing and Reuse
SWE-218 - Contracting Officers
8.8 - COTS Software Safety Considerations
Measurements and Metrics
Also see 5.4 Software Measurements
SWE-091 - Establish and Maintain Measurement Repository
SWE-092 - Using Measurement Data
SWE-142 - Software Cost Repositories
7.14 - Implementing Measurement Requirements and Analysis for Projects
7.18 - Metrics - Software Metrics Report
SWE-002 - Software Engineering Initiative
SWE-208 - Advancing Software Assurance and Software Safety Practices
SWE-003 - Center Improvement Plans
SWE-005 - Software Processes
SWE-095 - Report Engineering Discipline Status
SWE-006 - Center Software Inventory
7.1 - History and Overview of the Software Process Improvement (SPI) Effort
SWE-098 - Agency Process Asset Library
SWE-144 - Software Engineering Process Assets
SWE-153 - ETA Define Document Content
Requirement Mapping, Tailoring, and Classification
Also see 3.5 Software Classification Assessments
SWE-152 - Review Requirements Mapping Matrices
SWE-212 - NASA-STD-8739 Mapping Matrices
SWE-223 - Tailoring IV&V project selections
SWE-140 - Comply with Requirements
SWE-126 - Tailoring Considerations
SWE-150 - Review Changes To Tailored Requirements
SWE-021 - Transition to a Higher Class
7.2 - Classification and Safety-Criticality
7.13 - Transitioning to a Higher Class
7.16 - Appendix C. Requirements Mapping and Compliance Matrix
Training
Also see 3.4 Software Training
SWE-100 - Software Training Funding
SWE-222 - Software Assurance Training
7.18 - Train - Software Training Plan
SWE-033 - Acquisition vs. Development Assessment SWE-013 - Software PlansSWE-024 - Plan Tracking SWE-034 - Acceptance CriteriaSWE-036 - Software Process DeterminationSWE-037 - Software MilestonesSWE-039 - Software Supplier InsightSWE-040 - Access to Software ProductsSWE-042 - Source Code Electronic AccessSWE-139 - Shall StatementsSWE-121 - Document Tailored RequirementsSWE-125 - Requirements Compliance MatrixSWE-027 - Use of Commercial, Government, and Legacy Software
7.3 - Acquisition Guidance
7.4 - Flow Down of NPR Requirements on Contracts and to Other Centers in Multi-Center Projects
7.5 - Work Breakdown Structures That Include Software
7.8 - Maturity of Life Cycle Products at Milestone Reviews
7.9 - Entrance and Exit Criteria
7.18 - SDP-SMP - Software Development - Management Plan
3.2 Software Cost Estimation
SWE-015 - Cost EstimationSWE-151 - Cost Estimate ConditionsSWE-174 - Software Planning Parameters
7.6 - Software Test Estimation and Testing Levels
3.3 Software Schedules
SWE-016 - Software ScheduleSWE-018 - Software Activities ReviewSWE-046 - Supplier Software Schedule
8.15 - SA Tasking Checklist Tool
3.4 Software Training
SWE-017 - Project and Software Training
3.5 Software Classification Assessments
SWE-205 - Determination of Safety- Critical Software SWE-023 - Software Safety-Critical Requirements SWE-134 - Safety-Critical Software Design RequirementsSWE-219 - Test Coverage for Safety Critical Software ComponentsSWE-220 - Cyclomatic Complexity Values for Safety-Critical Software
7.21 - Multi-condition Software Requirements
8.1 - Off Nominal Testing
8.4 - Additional Requirements Considerations for Use with Safety-Critical Software
8.5 - SW Failure Modes and Effects Analysis
8.7 - Software Fault Tree Analysis
8.9 - Software Safety Analysis
8.10 - Facility Software Safety Considerations
SWE-146 - Auto-generated Source Code SWE-206 - Auto-Generation Software Inputs
SWE-032 - CMMI Levels for Class A and B Software
7.7 - Software Architecture Description
7.18 - IDD - Interface Design Description
7.18 - SDD - Software Data Dictionary
7.18 - SUM - Software User Manual
7.18 - SwDD - Software Design Description
8.2 - Software Reliability
7.18 - VDD - Version Description Document
SWE-065 - Test Plan, Procedures, ReportsSWE-066 - Perform TestingSWE-187 - Control of Software Items
SWE-068 - Evaluate Test ResultsSWE-070 - Models, Simulations, ToolsSWE-071 - Update Test Plans and ProceduresSWE-073 - Platform or Hi-Fidelity SimulationsSWE-189 - Code Coverage MeasurementsSWE-190 - Verify Code CoverageSWE-191 - Software Regression TestingSWE-192 - Software Hazardous RequirementsSWE-193 - Acceptance Testing for Affected BehaviorSWE-211 - Testing Levels of Non-Custom Developed Software
7.15 - Relationship Between NPR 7150.2 and NASA-STD-7009
7.18 - STP - Software Test Plan
7.18 - STR - Software Test Report
7.18 - Test - Software Test Procedures
8.13 - Test Witnessing
7.18 - Maint - Software Maintenance Plan
7.18 - CR-PR - Software Change Request - Problem Report
7.18 - SCMP - Software Configuration Management Plan
7.19 - Software Risk Management Checklists
7.20 - Assessing - Meets the Intent
8.6 - IV&V Surveillance
7.10 - Peer Review and Inspections Including Checklists
7.18 - Inspect - Software Inspection, Peer Reviews, Inspections
8.3 - Organizational Goals of Software Assurance Metrics
SWE-201 - Software Non-ConformancesSWE-202 - Software Severity LevelsSWE-203 - Mandatory Assessments for Non-ConformancesSWE-204 - Process Assessments
7.11 - SWE History
7.12 - Retired
7.17 - 7150.2D Appendices (Definitions, References, etc.)
8.14 - SA Tasking for NPR 7150.2B
Other Activities for consideration: