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 5

changes.mady.by.user Haigh, Fred

Saved on

compared with

New Version 6

changes.mady.by.user Haigh, Fred

Saved on

Key

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

...

4.

Tabsetup
01. Introduction
12. Initiation and Planning
23. Estination
34. Schedules
45. Training
56. Classification
6Assurance and Safety
7Coding
89. Cybersecurity
910. Scope
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

Requirements

Architecture and Design


Div
idtabs-2

2. Defining the Activity

Div
idtabs-3

3.

Div
idtabs-4
Div
idtabs-5

5.

Div
idtabs-6

6.

Note

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


2.1 SWEs

Note

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

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-7

7.

Div
idtabs-8

8.

Div
idtabs-9

9.

Div
idtabs-10
10.

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
______________________________________________________________________________