1. Introduction

Initiation and Planning activities occur at the beginning of a project.

A project may be for the creation of a new product, or the enhancement of an existing product. It may even involve the merging of capabilities from multiple products into a new, more capable product. It is always necessary to have an understanding of what the outcome of the project is. This is often called the High Level Requirements. These requirements set direction for the project.  Once the direction is set, an early activity is the Make, Buy or Reuse decision. 

2. Initiation and Planning

3.1 Software Life Cycle Planning

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

3. Estimation

3.2 Software Cost Estimation

SWE-015 - Cost Estimation
SWE-151 - Cost Estimate Conditions
SWE-174 - Software Planning Parameters

4. Schedules

3.3 Software Schedules

SWE-016 - Software Schedule
SWE-018 - Software Activities Review
SWE-046 - Supplier Software Schedule

5. Training

3.4 Software Training

SWE-017 - Project and Software Training

6. Classification

3.5 Software Classification Assessments

SWE-020 - Software Classification 
SWE-176 - Software Records 

3.9 Software Development Processes and Practices

SWE-032 - CMMI Levels for
                   Class A and B Software

7. Assurance and Safety 

3.6 Software Assurance and Software
Independent Verification & Validation

SWE-022 - Software Assurance
SWE-141 - Software Independent Verification
                   and Validation
SWE-131 - Independent Verification and
                   Validation Project Execution Plan
SWE-178 - IV&V Artifacts
SWE-179 - IV&V Submitted Issues and Risks

3.7 Safety-Critical Software

SWE-205 - Determination of Safety-
                  Critical Software 
SWE-023 - Software Safety-Critical
                   Requirements 
SWE-134 - Safety Critical Software
                   Design Requirements
SWE-219 - Test Coverage for Safety
                   Critical Software Components
SWE-220 - Cyclomatic Complexity Values
                   for Safety Critical Software

8. Coding Techniques

3.8 Automatic Generation of Software Source Code

SWE-146 - Auto-generated Source Code 
SWE-206 - Auto-Generation Software Inputs

3.10 Software Reuse

SWE-147 - Specify Reusability Requirements
SWE-148 - Contribute to Agency
                   Software Catalog

9. Cybersecurity

3.11 Software Cybersecurity

SWE-156 - Evaluate Systems for
                   Security Risks
SWE-154 - Identify Security Risks
SWE-157 - Protect Against
                   Unauthorized Access
SWE-159 - Verify and Validate Risk
                   Mitigations 
SWE-207 - Secure Coding Standard
SWE-185 - Verification of Software Code
                   to Coding Standards
SWE-210 - Detection of Adversarial Actions

10. Scope Management

3.12 Software Bi-Directional Traceability

SWE-052 - Bidirectional Traceability