bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
Column
width33%
Panel
titleColorwhite
titleBGColorblue
titleChapter 1 Introduction

[SWE-001 - Effective Date]

[SWE-002 - Software Engineering Initiative]

[SWE-003 - Center Improvement Plans]

[SWE-004 - OCE Benchmarking]

[SWE-005 - Software Processes]

[SWE-006 - Agency Software Inventory] 

Panel
titleColorwhite
titleBGColorblue
titleChapter 2 - Software Management Requirements

 [SWE-013 - Software Plans]

[SWE-130 - Develop a Software Safety Plan]

[SWE-131 - Independent Verification and Validation|SWE-131 - Independent Verification and Validation Project Execution Plan] \\                    [Project Execution Plan|SWE-131 - Independent Verification and Validation Project Execution Plan]

[SWE-014 - Execute Planning]

[SWE-015 - Cost Estimation]

[SWE-016 - Software Schedule]

[SWE-017 - Project and Software Training]

[SWE-018 - Software Activities Review]

[SWE-019 - Software Life Cycle]

[SWE-020 - Software Classification]

[SWE-132 - Independent Software Classification|SWE-132 - Independent Software Classification Assessment] \\                    [Assessment|SWE-132 - Independent Software Classification Assessment]

[SWE-133 - Software Safety Determination]

[SWE-021 - Transition to a Higher Class]

[SWE-022 - Software Assurance]

[SWE-023 - Software Safety]

[SWE-134 - Safety Critical Software Requirements]

[SWE-024 - Plan Tracking]

[SWE-025 - Corrective Actions]

[SWE-026 - Commitment Change Agreements]

[SWE-027 - Use of Commercial, Government, and|SWE-027 - Use of Commercial, Government, and Legacy Software] \\                    [Legacy Software|SWE-027 - Use of Commercial, Government, and Legacy Software]

[SWE-028 - Verification Planning]

[SWE-029 - Validation Planning]

[SWE-030 - Verification Results]

[SWE-031 - Validation Results]

[SWE-032 - CMMI levels for Class A, B, and C|SWE-032 - CMMI levels for Class A, B, and C Software] \\                    [Software|SWE-032 - CMMI levels for Class A, B, and C Software]

[SWE-033 - Acquisition vs. Development|SWE-033 - Acquisition vs. Development Assessment] \\                    [Assessment|SWE-033 - Acquisition vs. Development Assessment]

[SWE-034 - Acceptance Criteria]

[SWE-035 - Supplier Selection]

[SWE-036 - Software Process Determination]

[SWE-037 - Software Milestones]

[SWE-038 - Acquisition Planning]

[SWE-039 - Software Supplier Insight]

[SWE-040 - Access to Software Products]

[SWE-041 - Open Source Software Notification]

[SWE-042 - Source Code Electronic Access]

[SWE-043 - Track Change Request]

[SWE-044 - Supplier Metric Data]

[SWE-045 - Project Participation in Audits]

[SWE-046 - Supplier Software Schedule]

[SWE-047 - Traceability Data]

[SWE-048 - Solicitation] 

Column
width34%
Panel
titleColorwhite
titleBGColorblue
titleChapter 3. Software Engineering (Life-Cycle) Requirements

[SWE-049 - Document Software Requirements]

[SWE-050 - Software Requirements]

[SWE-051 - Software Requirements Analysis]

[SWE-052 - Bidirectional Traceability Between Higher|SWE-052 - Bidirectional Traceability Between Higher Level Requirements and Software Requirements] \\                    [Level Requirements & Software Reqmts.|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-056 - Document Design]

[SWE-057 - Software Architecture]

[SWE-058 - Detailed Design]

[SWE-059 - Bidirectional Traceability Between Software|SWE-059 - Bidirectional Traceability Between Software Requirements and Software Design] \\                    [Requirements and Software 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|SWE-064 - Bidirectional Traceability Between Software Design and Software Code] \\                    [Design and Software Code|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-067 - Verify Implementation]

[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|SWE-072 - Bidirectional Traceability Between Software Test Procedures and Software Requirements] \\                    [Test Procedures and Software Requirements|SWE-072 - Bidirectional Traceability Between Software Test Procedures and Software Requirements]

[SWE-073 - Platform or Hi-Fidelity Simulations]

[SWE-074 - Document Maintenance Plan]

[SWE-075 - Plan Operations, Maintenance,|SWE-075 - Plan Operations, Maintenance, Retirement] \\                     [Retirement|SWE-075 - Plan Operations, Maintenance, Retirement]

[SWE-076 - Implement Operations, Maintenance,|SWE-076 - Implement Operations, Maintenance, and Retirement Activities] \\                    [and Retirement Activities|SWE-076 - Implement Operations, Maintenance, and Retirement Activities]

[SWE-077 - Deliver Software Products]

[SWE-078 - As-built Documentation] 

Panel
titleColorwhite
titleBGColorblue
titleChapter 4. Supporting Software Life-Cycle Requirements

 [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|SWE-087 - Software Peer Reviews and Inspections for Requirements, Test Plans, Design, and Code] \\                    [for Requirements, Test Plans,|SWE-087 - Software Peer Reviews and Inspections for Requirements, Test Plans, Design, and Code] \\                    [Design, and Code|SWE-087 - Software Peer Reviews and Inspections for Requirements, Test Plans, Design, and Code]

[SWE-137 - Software Peer Reviews and Inspections -|SWE-137 - Software Peer Reviews and Inspections - Peer Reviews and Inspections of Software Plans] \\                    [Peer Reviews and Inspections of|SWE-137 - Software Peer Reviews and Inspections - Peer Reviews and Inspections of Software Plans] \\                    [Software Plans|SWE-137 - Software Peer Reviews and Inspections - Peer Reviews and Inspections of Software Plans]

[SWE-088 - Software Peer Reviews and Inspections -|SWE-088 - Software Peer Reviews and Inspections - Checklist Criteria and Tracking] \\                    [Checklist Criteria and Tracking|SWE-088 - Software Peer Reviews and Inspections - Checklist Criteria and Tracking]

[SWE-089 - Software Peer Reviews and Inspections -|SWE-089 - Software Peer Reviews and Inspections - Basic Measurements] \\                    [Basic Measurements|SWE-089 - Software Peer Reviews and Inspections - Basic Measurements]

[SWE-090 - Measurement Objectives]

[SWE-091 - Measurement Selection]

[SWE-092 - Measurement Collection and Storage]

[SWE-093 - Analysis of Measurement Data]

[SWE-094 - Reporting of Measurement Analysis]

[SWE-095 - Directorate Measurement System]

[SWE-096 - Directorate Measurement Objectives]

[SWE-098 - Agency PAL]

[SWE-099 - Center PAL Reviews]

[SWE-100 - Software Training Funding]

[SWE-101 - Center SW Training Plans|] 

Column
width33%
Panel
titleColorwhite
titleBGColorblue
titleChapter 5. Software Documentation Requirements

[SWE-102 - SW Development-Management Plan]
[SWE-103 - Software CM Plan]
[SWE-104 - Software Test Plan]
[SWE-105 - Software Maintenance Plan]
[SWE-106 - Software Assurance Plan]
[SWE-107 - SW Training Plan Contents]
[SWE-108 - Center SW Improvement Plan]
[SWE-138 - Software Safety Plan Contents]
[SWE-109 - Software Requirements Specification]
[SWE-110 - Software Data Dictionary]
[SWE-111 - Software Design Description]
[SWE-112 - Interface Design Description]
[SWE-113 - SW Change Request_Problem Report]
[SWE-114 - Software Test Procedures]
[SWE-115 - Software User Manual]
[SWE-116 - Software Version Description]
[SWE-117 - Software Metrics Report]
[SWE-118 - Software Test Report]
[SWE-119 - Software Documentation Reqmts. -|SWE-119 - Software Documentation Requirements - Software Inspection, Peer Reviews, Inspections] \\                    [Software Inspection, Peer Reviews,|SWE-119 - Software Documentation Requirements - Software Inspection, Peer Reviews, Inspections] \\                    [Inspections|SWE-119 - Software Documentation Requirements - Software Inspection, Peer Reviews, Inspections] 

Panel
titleColorwhite
titleBGColorblue
titleChapter 6. Tailoring, Engineering Technical Authority, and Compliance Measurement

[SWE-120 - General Exclusion from Requirements]
[SWE-121 - Document Alternate Requirements]
[SWE-122 - Technical Authority Appointment]
[SWE-124 - ETA OCE Compliance]
[SWE-125 - Requirements Compliance Matrix]
[SWE-126 - Waiver and Deviation Considerations]
[SWE-139 - Shall Statements]
[SWE-140 - Partial Center (P(Center)) Requirements]
[SWE-127 - P (Center) OCE Concurrence]
[SWE-128 - Technical Authority Records]
[SWE-129 - OCE NPR Appraisals]  

Div