Page History
This is a working page to build the list of activities and the SWEs and topics that define them.
The table below was built from the activity descriptions in NPR 7150.2D chapters 3 thru 5. These are highlighted in yellow.
Additional activities were derived from chapter 2 and are highlighted blue below as the first 7 activities. These chapter 2 activities were then copied into the activities highlighted in yellow where they seemed most likely to belong.
Distribution Of SWEs Into Activities
- All SWEs in NPR 7150.2D are represented in an activity in the yellow group. SWEs that come from chapter 2 represent things that are done at the Institutional level to enable projects to perform a SWE at the project level. In a sense, they are enabling SWEs.
Distribution Of Topics And PATs Into Activities
- All topics are represented in at least one activity.
- Some topics are associated with multiple SWEs and may appear in more than one activity. For example, topic 8.5 - SW Failure Modes and Effects Analysis deals with design as well as has safety related considerations as well. It appears in both the 3.7 Safety-Critical Software and 4.3 Software Design activities.
- All PATs are represented in at least one activity. Some PATs may appear in multiple activities depending on the same criteria as topics.
Topics That Don't Fit Into Activities
- There are a few topics that don't fit into the activity scheme. They are listed in the next to last row in the red highlight.
Activities That Are Not Represented In This Model
- There are a few topics that are not represented in this activity model. They are listed in the last row in the green highlight. If we want this activity model to match more closely with the way projects do their work, it may be necessary to add these activities into the model and move the appropriate SWEs, Topics, PATs, etc. into them.
Additional Considerations Moving Forward
- 3.8 Automatic Generation of Software Source Code content might be better to put into the activity 4.3 Software Design or 4.4 Software Implementation
- 3.12 Software Bi-Directional Traceability has only one SWE and no other topics or other materials associated with it. It may be more appropriate to put this SWE under 4.1 Software Requirements
- 4.2 Software Architecture and 4.3 Software Design might be better to consider as a single activity.
Benchmarking and Appraisals
3.9 Software Development
Processes and Practices
Licensing, Sharing and Reuse
Also see 3.10 Software Reuse
Measurements and Metrics
Also see 5.4 Software Measurements
7.1 - History and Overview of the Software Process Improvement (SPI) Effort
Requirement Mapping, Tailoring,
and Classification
Also see 3.5 Software Classification
Assessments
Training
Also see 3.4 Software Training
SWE-033 - Acquisition vs. Development
Assessment
SWE-013 - Software Plans
SWE-024 - Plan Tracking
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-139 - Shall Statements
SWE-121 - Document Tailored Requirements
SWE-125 - Requirements Compliance Matrix
SWE-027 - Use of Commercial, Government,
and Legacy Software
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
8.16 - Software Assurance Plan
PAT-024 - Checklist for Choosing Off-The Shelf Software
PAT-025 - Checklist for Choosing a Real Time Operating System (RTOS)
3.2 Software Cost Estimation
3.3 Software Schedules
7.5 - Work Breakdown Structures That Include Software
7.8 - Maturity of Life Cycle Products at Milestone Reviews
3.4 Software Training
3.5 Software Classification
Assessments
7.2 - Classification and Safety-Criticality
7.13 - Transitioning to a Higher Class
7.16 - Appendix C. Requirements Mapping and Compliance Matrix
and Software Independent
Verification & Validation
8.16 - Software Assurance Plan
8.16 - IV&V Project Execution Plan
7.21 - Multi-condition Software Requirements
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.8 - COTS Software Safety Considerations
8.9 - Software Safety Analysis
8.10 - Facility Software Safety Considerations
8.15 - SA Tasking Checklist Tool
8.16 - Software Safety and Hazard Analysis
8.17 - Software Safety Audit Checklists
8.19 - Dead / Dormant Code and Safety-Critical Software
8.20 - Safety Specific Activities in Each Phase
6.1 - Design for Safety Checklist
6.2 - Checklist for General Software Safety Requirements
6.11 - Examples of Programming Practices for Exception Handling
Software Safety and Design Principles
PAT-004 - Safety Requirements Analysis Checklist
PAT-006 - Design Practices for Safety
PAT-007 - Checklist for General Software Safety Requirements
PAT-008 - Safety Considerations for Design Peer Reviews Checklist
Software Source Code
Processes and Practices
8.12 - Basics of Software Auditing
8.16 - Audit Reports
SWE-148 - Contribute to Agency
Software Catalog - Performance
- Performance Measures SWEs from Ch 2 - Institutional Requirements |
Volatility Metrics
7.14 - Implementing Measurement Requirements and Analysis for Projects 7.18 - Metrics - Software Metrics Report | |
| 5.5 Software Non-conformance or Defect Management |
| 7.18 - CR-PR - Software Change Request - Problem Report | ||
| Other SWEHB pages that don't fit into the "activity" model | 7.12 - Retired 7.15 - Relationship Between NPR 7150.2 and NASA-STD-7009 | |
Other Activities for consideration:
|


