|
This section contains guidance, rationale, and lists of useful resources and tools related to each and every one of the requirements in NPR 7150.2B in Chapters 3, 4, and 5. You can use the table below to link to the full text of all requirements and to the guidance on each. |
PROJECT SOFTWARE REQUIREMENTS (CHAPTER 3, 4, & 5)SWE-013 - Software Plans
SWE-024 - Plan Tracking
SWE-015 - Cost Estimation
SWE-151 - Cost Estimate Conditions
SWE-016 - Software Schedule
SWE-018 - Software Activities Review
SWE-017 - Project and Software Training
SWE-020 - Software Classification
SWE-021 - Transition to a Higher Class
SWE-160 - Safety Critical Classification
SWE-022 - Software Assurance
SWE-141 - Software Independent Verification
and Validation
SWE-131 - Independent Verification and
Validation Project Execution Plan
SWE-023 - Software Safety
SWE-134 - Safety Critical Software
Requirements
SWE-146 - Auto-generated Source Code
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-034 - Acceptance Criteria
SWE-036 - Software Process Determination
SWE-037 - Software Milestones
SWE-039 - Software Supplier Insight
SWE-040 - Access to Software Products
SWE-042 - Source Code Electronic Access
SWE-045 - Project Participation in Audits
SWE-046 - Supplier Software Schedule
SWE-147 - Specify Reusability Requirements
SWE-148 - Contribute to Agency
Software Catalog
SWE-154 - Identify Security Risks
SWE-155 - Implement Risk Mitigations
SWE-156 - Evaluate Systems for
Security Risks
SWE-157 - Protect Against
Unauthorized Access
SWE-158 - Evaluate Software for
Security Vulnerabilities
SWE-159 - Verify and Validate Risk
Mitigations
Renew your license to continue
Your evaluation license of Visibility for Confluence expired. Please use the Buy button to purchase a new license.
SWE-050 - Software Requirements
SWE-051 - Software Requirements Analysis
SWE-052 - Bidirectional Traceability
Between Higher Level
Requirements and Software
Requirements
SWE-053 - Manage Requirements Changes
SWE-054 - Corrective Action for
Inconsistencies
SWE-055 - Requirements Validation
SWE-057 - Software Architecture
SWE-143 - Software Architecture Review
SWE-058 - Detailed Design
SWE-059 - Bidirectional Traceability
Between Software
Requirements and
Software Design
SWE-060 - Coding Software
SWE-061 - Coding Standards
SWE-135 - Static Analysis
SWE-062 - Unit Test
SWE-063 - Release Version Description
SWE-064 - Bidirectional Traceability
Between Software
Design and Software Code
SWE-136 - Software Tool Accreditation
SWE-065 - Test Plan, Procedures, Reports
SWE-066 - Perform Testing
SWE-068 - Evaluate Test Results
SWE-069 - Document Defects and Track
SWE-070 - Models, Simulations, Tools
SWE-071 - Update Test Plans and
Procedures
SWE-072 - Bidirectional Traceability
Between Software
Test Procedures and
Software Requirements
SWE-073 - Platform or Hi-Fidelity
Simulations
SWE-075 - Plan Operations, Maintenance,
Retirement
SWE-077 - Deliver Software Products
Renew your license to continue
Your evaluation license of Visibility for Confluence expired. Please use the Buy button to purchase a new license.
SWE-079 - Develop CM Plan
SWE-080 - Track and Evaluate Changes
SWE-081 - Identify Software CM Items
SWE-082 - Authorizing Changes
SWE-083 - Status Accounting
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-090 - Management and Technical
Measurements
SWE-093 - Analysis of Measurement Data
SWE-094 - Reporting of Measurement
Analysis
