- SWE-013 - Software Plans
- SWE-015 - Cost Estimation
- SWE-016 - Software Schedule
- SWE-017 - Project and Software Training
- SWE-018 - Software Activities Review
- SWE-020 - Software Classification
- SWE-022 - Software Assurance
- SWE-023 - Software Safety-Critical Requirements
- SWE-024 - Plan Tracking
- SWE-027 - Use of Commercial, Government, and Legacy Software
- SWE-032 - CMMI Levels for Class A and B Software
- SWE-033 - Acquisition vs. Development Assessment
- SWE-036 - Software Process Determination
- SWE-037 - Software Milestones
- SWE-039 - Software Supplier Insight
- SWE-046 - Supplier Software Schedule
- SWE-050 - Software Requirements
- SWE-051 - Software Requirements Analysis
- SWE-052 - Bidirectional Traceability
- SWE-053 - Manage Requirements Changes
- SWE-054 - Corrective Action for Inconsistencies
- SWE-055 - Requirements Validation
- SWE-057 - Software Architecture
- SWE-058 - Detailed Design
- SWE-060 - Coding Software
- SWE-061 - Coding Standards
- SWE-062 - Unit Test
- SWE-063 - Release Version Description
- SWE-065 - Test Plan, Procedures, Reports
- SWE-066 - Perform Testing
- SWE-068 - Evaluate Test Results
- SWE-070 - Models, Simulations, Tools
- SWE-071 - Update Test Plans and Procedures
- SWE-073 - Platform or Hi-Fidelity Simulations
- SWE-075 - Plan Operations, Maintenance, Retirement
- SWE-077 - Deliver Software Products
- SWE-079 - Develop CM Plan
- SWE-080 - Track and Evaluate Changes
- SWE-081 - Identify Software CM Items
- SWE-082 - Authorizing Changes
- SWE-084 - Configuration Audits
- SWE-085 - Release Management
- SWE-086 - Continuous Risk Management
- SWE-087 - Software Peer Reviews and Inspections for Requirements, Plans, Design, Code, and Test Procedures
- SWE-088 - Software Peer Reviews and Inspections - Checklist Criteria and Tracking
- SWE-089 - Software Peer Reviews and Inspections - Basic Measurements
- SWE-093 - Analysis of Measurement Data
- SWE-121 - Document Tailored Requirements
- SWE-125 - Requirements Compliance Matrix
- SWE-134 - Safety-Critical Software Design Requirements
- SWE-135 - Static Analysis
- SWE-136 - Software Tool Accreditation
- SWE-139 - Shall Statements
- SWE-143 - Software Architecture Review
- SWE-146 - Auto-generated Source Code
- SWE-147 - Specify Reusability Requirements
- SWE-148 - Contribute to Agency Software Catalog
- SWE-151 - Cost Estimate Conditions
- SWE-154 - Identify Security Risks
- SWE-156 - Evaluate Systems for Security Risks
- SWE-157 - Protect Against Unauthorized Access
- SWE-159 - Verify and Validate Risk Mitigations
- SWE-174 - Software Planning Parameters
- SWE-176 - Software Records
- SWE-179 - IV&V Submitted Issues and Risks
- SWE-184 - Software-related Constraints and Assumptions
- SWE-185 - Secure Coding Standards Verification
- SWE-185 - Secure Coding Standards Verification
- SWE-186 - Unit Test Repeatability
- SWE-187 - Control of Software Items
- SWE-189 - Code Coverage Measurements
- SWE-190 - Verify Code Coverage
- SWE-191 - Software Regression Testing
- SWE-192 - Software Hazardous Requirements
- SWE-194 - Delivery Requirements Verification
- SWE-195 - Software Maintenance Phase
- SWE-199 - Performance Measures
- SWE-200 - Software Requirements Volatility Metrics
- SWE-201 - Software Non-Conformances
- SWE-202 - Software Severity Levels
- SWE-203 - Mandatory Assessments for Non-Conformances
- SWE-204 - Process Assessments
- SWE-205 - Determination of Safety-Critical Software
- SWE-207 - Secure Coding Practices
- SWE-210 - Detection of Adversarial Actions
- SWE-211 - Test Levels of Non-Custom Developed Software
- SWE-219 - Code Coverage for Safety Critical Software
NASA Software Engineering Handbook - A service of the NASA Office of the Chief Engineer
NASA Privacy Statement
______________________________________________________________________________
NASA Privacy Statement
______________________________________________________________________________
