UNDER CONSTRUCTION

Note
Notes in this template provide guidance to authors on how the section if to be completed. Once the section is populated, the Note may be deleted. Notes are not intended to be left in the completed page.

List of some of the inputs from other activities

Documents that are necessary for

the activity

Design to begin

.

:

Examples:

SRS - Software Requirements Specification - Requirements - These influence the design of the software
Architecture Documents- These influence 5.13 - SwDD - Software Design Description- Contains Architecture description - This influences the design of the software

1.2 Predecessor Activities

Tabsetup

0	1. Introduction
1	2. Defining the ActivitySoftware Engineering
2	3. Software Assurance

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.

Div

id	tabs-1

1. Introduction

Note

Panel

borderColor	blue
title	NPR 7150.2B para 4.3.1

Include Page

	2D-Para 4.3.1
	2D-Para 4.3.1

Software peer reviews and inspections are the in-process technical examination of work products by peers to find and eliminate defects early in the life cycle. Software peer reviews and inspections are performed following defined procedures covering the preparation for the review, the review itself is conducted, results are recorded, results are reported, and completion criteria is certified. When planning the composition of a software peer review or inspection team, consider including software testing, system testing, software assurance, software safety, software cybersecurity, and software IV&V personnel.

Panel

borderColor	black
borderWidth	2
title	Inputs, Outputs, and Predecessor Related Activities

Activity graphical representation of Inputs, Outputs, Predecessor and Successor Activities as appropriate. Not meant to be exhaustive, but representative of a typical project.

1.1 Inputs

Note

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

Examples:

Predecessor Activities are performed before Peer ReviewsDesign. These activities produce the work products that will be reviewed.
Life Cycle Planning - Design activities are included in the plan and schedules
Requirements Software Requirements - These influence the design of the software
Software Architecture - These influence the design of the software

1.3 Outputs

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

Output Work Product Used by Downstream Activity
Software Design Document
(SwDD - Software Design Description)
Implementation and Unit Testing
Preliminary at Preliminary Design Review
Baselined at Critical Design Review
Updated at Test Readiness Review
Software Interface Design Description document (see IDD - Interface Design Description)
Implementation and Unit Testing
Preliminary at Preliminary Design Review
Baselined at Critical Design Review
Updated at Test Readiness Review
Software User Manual (see SUM - Software User Manual)
Implementation and Unit Testing
Baselined at Operational Readiness Review

1.4 Successor

Activities NoteLinks to

Activities

which might be started or supported by this activity.

Implementation and Unit Testing - Implements the Design into one or more code modules.
Preliminary Design Review
Critical Design Review
Test Readiness Review
Operational Readiness Review

1.5 Activity Repetition

NoteDescribe what conditions determine if the activity needs to be repeated, such as re-planning after a change in requirements or schedule constraints.

How much of the activity needs to be repeated
Frequency of repetition
Design is always done once. Ideally it will It should be peer reviewed and analyzed by Software Assurance.
Design may be reviewed and re-analyzed as often as there are significant changes in architecture or requirements. For example,:
Technology changes to the architecture requires changes to the design
Customer changes to requirements require changes to the design

1.6 Center Resources From

SPAN NoteAdd 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).

Activity	Description
Design	Assets for use during product design

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

Software Engineering

2.1 SWEs

Div

id	tabs-2

2.

Defining the Activity

Note

Note
This section contains the links to SWE pages that form the heart of the activity. For each SWE, the related tasks from tab 4 are listed.

SWE-058 - Detailed Design with new tab 4

Expand

title	SWE-058 Tasking and Work Product Details

Link to SWE-058 - Copy of SWE-058 - Detailed Design with new tab 4

Class Applicability: A B C

SWE-058 Requirement

Excerpt Include

	Copy of SWE-058 - Detailed Design with new tab 4
	Copy of SWE-058 - Detailed Design with new tab 4
nopanel	true

Assess Design Readiness

Establish Coding Standards and Processes

Establish Project Specific Design Considerations

Establish Detailed Design Documentation and Progress Reviews

Establish Design Maintenance Processes and Mechanisms

Include Page

	SWE-058-ETask
	SWE-058-ETask

Include Page

	SWE-058-EWP
	SWE-058-EWP

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.

SwDD - Software Design Description Excerpt IncludeSWEHBVD:SwDD - Software Design DescriptionSWEHBVD:SwDD - Software Design DescriptionnopaneltrueIDD - Interface Design Description Excerpt IncludeSWEHBVD:IDD - Interface Design DescriptionSWEHBVD:IDD - Interface Design DescriptionnopaneltrueSUM - Software User Manual Excerpt IncludeSWEHBVD:SUM - Software User ManualSWEHBVD:SUM - Software User ManualnopaneltrueSoftware Design Principles Excerpt IncludeSWEHBVD:Software Design PrinciplesSWEHBVD:Software Design Principlesnopaneltrue Include PageSWEHBVD:Principles TableSWEHBVD:Principles Table6.3 - Checklist for Choosing a Real Time Operating System (RTOS) Excerpt Include

2.2.1 Topics

Expand

title	SWE-058 Topics

Include Page

	SWE-058-ETopics
	SWE-058-ETopics

2.2.2 Supporting Materials

Expand

title	SWE-058 Supporting Materials

Include Page

	SWE-058-ESupport
	SWE-058-ESupport

2.3 Other Associated SWEs, Topics, etc.

SWEHBVD:6.3 - Checklist for Choosing a Real Time Operating System (RTOS)SWEHBVD:6.3 - Checklist for Choosing a Real Time Operating System (RTOS)nopaneltrue6.4 - Checklist for Choosing Off-The Shelf Software (OTS) Excerpt IncludeSWEHBVD:6.4 - Checklist for Choosing Off-The Shelf Software (OTS)SWEHBVD:6.4 - Checklist for Choosing Off-The Shelf Software (OTS)nopaneltrue

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.

Include page for the PAT page goes here

PAT-023 - Preparing for a SARB Checklist
3.2.2 Process Asset Templates
Div
id tabs-3
3. Software Assurance
Software Assurance is integral to the performance of all Software Development activities. It includes Process Monitoring as well as Process Analysis.
Process Monitoring - addresses the question, "Is the development team following their processes and producing the expected work products?"
Process Analysis - addresses the question, "Are there better ways of performing the processes that would result in the early discovery of defects?"
3.1 Software Assurance Tasks from SWEs
Software Assurance Tasks are included in tab 7 of the SWEs in this activity. .
SWE-058 - Detailed Design with new tab 4
Expand
title SWE-058 SA Tasking and Work Product Details
Link to SWE-058 - Copy of SWE-058 - Detailed Design with new tab 4

Tasking from tab 7
From
SWE-058 Requirement
Excerpt Include
Copy of SWE-058 - Detailed Design with new tab 4
Copy of SWE-058 - Detailed Design with new tab 4
nopanel true
Tasking From
Panel
borderColor blue
title
NASA-STD-8739.8B
Include Page
SWE-058 - SA Task1
SWE-058 - SA Task1
Include Page
SWE-058 - SA Task2
SWE-058 - SA Task2
Include Page
SWE-058 - SA Task3
SWE-058 - SA Task3
Include Page
SWE-058 - SA Task4
SWE-058 - SA Task4
Include Page
SWE-058 - SA Task5
SWE-058 - SA Task5
SA Work Products
Include Page
SWE-058-SAWP
SWE-058-SAWP
3.2 Topics and
other
Other Supporting Materials
3.2.1 Topics
Topic 8.16 - 8.55 - Software Design Analysis
Excerpt Include
SWEHBVD:8.55 - Software Design Analysis
SWEHBVD:8.55 - Software Design Analysis
nopanel true
Expand
SA Tasks for SWEs
title SA Tasking from Topic 8.16 - Software Design Analysis
SWE-034 - Acceptance Criteria
Include Page
SWE-034 - SA Task1
SWE-034 - SA Task1
SWE-134 - Safety-Critical Software Design Requirements
Include Page
SWE-134 - SA Task1
SWE-134 - SA Task1
Include Page
SWE-134 - SA Task4
SWE-134 - SA Task4
Include Page
SWE-134 - SA Task5
SWE-134 - SA Task5
Include Page
SWE-134 - SA Task6
SWE-134 - SA Task6
SWE-057 - Software Architecture
Include Page
SWE-057 - SA Task1
SWE-057 - SA Task1
Include Page
SWE-057 - SA Task2
SWE-057 - SA Task2
SWE-143 - Software Architecture Review
Include Page
SWE-143 - SA Task1
SWE-143 - SA Task1
SWE-080 - Track and Evaluate Changes
Include Page
SWE-080 - SA Task1
SWE-080 - SA Task1
SWE-081 - Identify Software CM Items
Include Page
SWE-081 - SA Task2
SWE-081 - SA Task2
SWE-203 - Mandatory Assessments for Non-Conformances
Include Page
SWE-203 - SA Task2
SWE-203 - SA Task2
PAT-021 - SADESIGN Checklist
Excerpt Include
PAT-021 - SADESIGN Checklist PAT-021 - SADESIGN Checklist
nopanel true
Include Page
Design Analysis Process Asset Templates
Design Analysis Process Asset Templates

3.3 Other Associated SWEs, Topics, etc.

Excerpt IncludePAT-023 - Preparing for a SARB ChecklistPAT-023 - Preparing for a SARB ChecklistPAT-031 - Critical Design Analysis Checklist Excerpt IncludePAT-031 - Critical Design Analysis ChecklistPAT-031 - Critical Design Analysis ChecklistPAT-008 - Safety Considerations for Design Peer Reviews Checklist Excerpt IncludePAT-008 - Safety Considerations for Design Peer Reviews ChecklistPAT-008 - Safety Considerations for Design Peer Reviews ChecklistPAT-020 - Examples of Interface Problems Excerpt IncludePAT-020 - Examples of Interface ProblemsPAT-020 - Examples of Interface Problems

Content

Space Tools

Versions Compared

Old Version 8

New Version Current

Key

UNDER CONSTRUCTION

1.2 Predecessor Activities

1. Introduction

1.1 Inputs

1.3 Outputs

1.4 Successor

Activities

Implementation and Unit Testing - Implements the Design into one or more code modules.
Preliminary Design Review
Critical Design Review
Test Readiness Review
Operational Readiness Review

1.5 Activity Repetition

1.6 Center Resources From

SPAN

Software Engineering

2.1 SWEs

2.

SWE-058 - Detailed Design with new tab 4

Link to SWE-058 - Copy of SWE-058 - Detailed Design with new tab 4

SWE-058 Requirement

2.2 Topics and other Supporting Materials

2.2.1 Topics

2.2.2 Supporting Materials

2.3 Other Associated SWEs, Topics, etc.

2.3 Other Associated SWEs, Topics, etc.

3. Software Assurance

3.1 Software Assurance Tasks from SWEs

SWE-058 - Detailed Design with new tab 4

Link to SWE-058 - Copy of SWE-058 - Detailed Design with new tab 4

SWE-058 Requirement

Tasking From

NASA-STD-8739.8B

SA Work Products

3.2 Topics and

Other Supporting Materials

3.2.1 Topics

3.3 Other Associated SWEs, Topics, etc.

Output Work Product	Used by Downstream Activity
Software Design Document (SwDD - Software Design Description)	Implementation and Unit Testing Preliminary at Preliminary Design Review Baselined at Critical Design Review Updated at Test Readiness Review
Software Interface Design Description document (see IDD - Interface Design Description)	Implementation and Unit Testing Preliminary at Preliminary Design Review Baselined at Critical Design Review Updated at Test Readiness Review
Software User Manual (see SUM - Software User Manual)	Implementation and Unit Testing Baselined at Operational Readiness Review

Content

Space Tools

Page History

Versions Compared

Old Version 8

New Version Current

Key

UNDER CONSTRUCTION

1. Introduction

1.1 Inputs

1.2 Predecessor Activities

1.3 Outputs

1.4 Successor

Activities

Implementation and Unit Testing - Implements the Design into one or more code modules. Preliminary Design ReviewCritical Design ReviewTest Readiness ReviewOperational Readiness Review

1.5 Activity Repetition

1.6 Center Resources From

SPAN

2.

Software Engineering

2.1 SWEs

SWE-058 - Detailed Design with new tab 4

Link to SWE-058 - Copy of SWE-058 - Detailed Design with new tab 4

SWE-058 Requirement

2.2 Topics and other Supporting Materials

2.2.1 Topics

2.2.2 Supporting Materials

2.3 Other Associated SWEs, Topics, etc.

2.3 Other Associated SWEs, Topics, etc.

3. Software Assurance

3.1 Software Assurance Tasks from SWEs

SWE-058 - Detailed Design with new tab 4

Link to SWE-058 - Copy of SWE-058 - Detailed Design with new tab 4

SWE-058 Requirement

Tasking From

NASA-STD-8739.8B

SA Work Products

3.2 Topics and

Other Supporting Materials

3.2.1 Topics

3.3 Other Associated SWEs, Topics, etc.

Implementation and Unit Testing - Implements the Design into one or more code modules.
Preliminary Design Review
Critical Design Review
Test Readiness Review
Operational Readiness Review