bannerd

A. Introduction

B. Institutional Requirements

C. Project Software Requirements

D. Topics

E. Tools, References, and Terms

F. SPAN
(NASA Only)

Versions Compared

Old Version 3

changes.mady.by.user Haigh, Fred

Saved on

compared with

New Version Current

changes.mady.by.user Haigh, Fred

Saved on

Key

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

UNDER CONSTRUCTION

4. Schedules

3.3 Software Schedules

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

Tabsetup
10. Scope
01. Introduction
12. Initiation and Planning
23. Estination
34. Schedules
45. Training
56. Classification
6Assurance and Safety
7Coding
89. Cybersecurity
9
Defining the Activity
Div
idtabs-1

1. Introduction

Note

Typically starts with a quote from the NPR that helps define the activity. Additional descriptive material is meant to help define the activity but not be so detailed that it pulls in all of the guidance from the SWEs in the activity. 

Panel
borderColorblue
titleNPR 7150.2B para 3.1.1

Software life cycle planning covers the software aspects of a project from inception through retirement. The software life cycle planning is an organizing process that considers the software as a whole and provides the planning activities required to ensure a coordinated, well-engineered process for defining and implementing project activities. These processes, plans, and activities are coordinated within the project. At project conception, software needs for the project are analyzed, including acquisition, supply, development, operation, maintenance, retirement, decommissioning, and supporting activities and processes. The software effort is scoped, the development processes defined, measurements defined, and activities are documented in software planning documents.


1.1 Inputs

Note

List of some of the inputs from other activities that are necessary for the activity to begin. 

  • Documents and orders that initiate the Planning Activity
  • High level requirements that define the scope of the software product
  • Time and budget constraints that further define the scope of the project

1.2 Predecessor Activities

Note

List of some of the other activities that must be started (not necessarily completed) this activity to begin. 

The predecessor activities include planning, architecture and design activities from other projects and systems where the concept for the software product is defined. Examples include: 

  • New, or changed, hardware system that requires new software to monitor or control it.

1.3 Outputs

Note

List of some of the outputs or work products of the activity. These are typically used as inputs by the downstream activity. In some cases there is a supporting SWE associated with the work product. 

Outputs from Planning include a variety of documents, plans, and other work products that are used by downstream activities

Output Work ProductUsed by Downstream ActivitySupporting SWE or Topic
  • Project Plan
  • Monitor and Control
  • Software Requirements
  • Software Architecture
  • Software Design

1.4 Successor Activities

Note

Links to Activities which might be started or supported by this activity. 

  • Monitor and Control
  • Software Requirements
  • Software Architecture
  • Software Design

1.5 Repetition

Note

Describe what conditions determine if the activity needs to be repeated.

  • How much of the activity needs to be repeated
  • Frequency of repetition

Life Cycle Planning is done in the early stages of a Software Project. Other work may be started before the planning is actually completed. 

During the life of the project there may be multiple times when significant changes to things like requirements, budget, schedule, technology, which make re-planning necessary. Re-planning is covers the same areas of the original planning to make sure that all changes are accounted for in the new plans. Re-planning is done as often as necessary to keep the project under control. 


1.6 Center Resources From SPAN

Note

Add links to SPAN activity pages that are appropriate for this activity. Use links from the Activity section of the front page. SPAN

Several Centers Process Asset Libraries have materials related to this activity. Related Processes, templates, and other resources may be found in the following Activities in SPAN (available to NASA only). 


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. 

Div
idtabs-12
Div
idtabs-2

2. Defining the Activity

Note

This tab contains the links to pages in the SWEHB that are at the heart of the activity. 

Life Cycle Planning is a large activity that impacts the whole of the project. The SWEs listed below are included in the NPR 7150.2 under 3.1 Software Life Cycle Planning. 

  • Determinations are made regarding whether the software should be developed using related, existing software, secured by a separate acquisition from another supplier, or built from scratch. In some cases it may be a combination of all these approaches. 
  • Project plans are developed to account for all aspects of the development of the software. 
  • Plans for tracking the progress of the development project are put into place for use in the Monitor and Control activity. 
  • Acceptance Criteria are reviewed and made a part of the plan. These will be used together with Requirements to ensure that the right software is developed and delivered. 
  • The processes to be used in the development effort are selected and coordinated with the Requirement Mapping and Tailoring activity. 
  • Milestones are determined and planned into the project. These are coordinated in the Software Scheduling activity. 
  • Access to developed components is planned for and coordinated with the Configuration Management activity among others. 
  • Software Requirements are 

2.1 SWEs

Note

This section contains the links to SWE pages that form the heart of the activity. 

SWEs from NPR 7150.2D section

2. Initiation and Planning

3.1 Software Life Cycle Planning


                    
Div
idtabs-3

3. Estimation

3.2 Software Cost Estimation

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

Div
idtabs-4

SWEs from NPR 7150.2D section 3.4 Software Training

2.2 Topics and other Supporting Materials

Note

This section is for SWEHB pages, other than SWEs, that directly support the activity. This section contains Topics, document content pages, PATs, and other pages. 

2.3 Other Associated SWEs, Topics, etc.

Note

Includes other SWEHB pages that are indirectly associated with the activity. May include SWEs, Topics, document definition pages, PATs, etc. They may have been mentioned in the guidance of another page. 

Div
idtabs-5

5. Training

3.4 Software Training

SWE-017 - Project and Software Training

Div
idtabs-6

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

Div
idtabs-7

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

Div
idtabs-8

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

Div
idtabs-9

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

Div
idtabs-10

10. Scope Management

3.12 Software Bi-Directional Traceability

SWE-052 - Bidirectional Traceability 


Page Editor: Tim Crumbley
NASA Official: Tim Crumbley
Accessibility
NASA Software Engineering Handbook - A service of the NASA Office of the Chief Engineer
NASA Privacy Statement
______________________________________________________________________________