Tabsetup

0	1. Introduction
1	2. Software Development Activity
2	3. Software Assurance Activity

Div

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

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 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
List of some of the inputs from other activities that are necessary for the activity to begin.

Examples:

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

1.2 Predecessor Activities

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 Design. These activities produce the work products that will be reviewed.

Life Cycle Planning - Design activities are included in the plan and schedules
Software Requirements - These influence the design of the software
Software Architecture - These influence the design of the software

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.

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

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

Note

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

Note
Add links to SPAN activity pages that are appropriate for this activity. Use links from the Activity section of the front page. SPAN All of the links to SPAN activities are provided. Delete the ones that do not apply

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

Preliminary at PDR - 7.9 - Entrance and Exit Criteria (tab 7)

Baselined at CDR - 7.9 - Entrance and Exit Criteria (tab 8)

Updated at TRR - 7.9 - Entrance and Exit Criteria (tab 11)

IDD - Interface Design Description

Preliminary at PDR - 7.9 - Entrance and Exit Criteria (tab 7)

Baselined at CDR - 7.9 - Entrance and Exit Criteria (tab 8)

Updated at TRR - 7.9 - Entrance and Exit Criteria (tab 11)

SUM - Software User Manual

Baselined at ORR - 7.9 - Entrance and Exit Criteria (tab 13)

Div

id	tabs-2

2. Software Development Activity

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. For each SWE, the related tasks from tab 4 are listed.

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

Expand

title	SWE-058 Tasking and Work Product Details

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

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

Work ProductsSwDD - Software Design Description

excerpt-

Include Page

SWEHBVD:SwDD - Software Design Description

nopanel

true

Excerpt Include

SWEHBVD:IDD - Interface Design Description

nopanel

true

Excerpt Include

SWEHBVD:SUM - Software User Manual

nopanel

true

SWE-058-ETask
SWE-058-ETask
Include Page
SWE-058-EWP
SWE-058-EWP

Software Development Process - which includes details on the Design Process to be followed.

List of design components including when they are expected to be available - as input to Development Schedule

List of methods, tools, standards, and guidelines for your project.

List of training and experience required by team members to perform the design and development work.

....

Metrics

# of architectural issues, found in peer reviews, identified vs. number closed.

# of design issues, from peer reviews, found versus the number of design issues resolved.

# of requirement issues (Open, Closed) over time.

# of non-conformances identified found versus resolved.

# of software work product Non-Conformances identified versus closed.

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, PATs, and other relevant pages.

2.2.1 Topics

6.3 - Checklist for Choosing a Real Time Operating System (RTOS)
- Excerpt Include
  SWEHBVD:6.3 - Checklist for Choosing a Real Time Operating System (RTOS)
  SWEHBVD:6.3 - Checklist for Choosing a Real Time Operating System (RTOS)
  nopanel true
6.4 - Checklist for Choosing Off-The Shelf Software (OTS)
- Excerpt Include
  SWEHBVD:6.4 - Checklist for Choosing Off-The Shelf Software (OTS)
  SWEHBVD:6.4 - Checklist for Choosing Off-The Shelf Software (OTS)
  nopanel true

2.2.2 Supporting Materials

Software Design Principles
- Excerpt Include
  SWEHBVD:Software Design Principles
  SWEHBVD:Software Design Principles
  nopanel true
- Include Page
  SWEHBVD:Principles Table
  SWEHBVD:Principles Table

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. This section may be removed if there is no content for it.

Div

id	tabs-3

3. Software Assurance Activity

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.

3.1.1 - Copy of SWE-058 - Detailed Design with new tab 4

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

Software Assurance Products

Software Design Analysis
Results of software assurance design analysis, including assessments in Tasks 1, 2, and 3.
List of any identified design risks and issues.

Metrics
1. # of architectural issues identified vs. number closed.
2. # of design issues found versus the number of design issues resolved.
3. # of safety-related requirement issues (Open, Closed) over time.
4. # of safety-related non-conformances identified by life cycle phase over time.
5. # of software work product Non-Conformances identified by life cycle phase over time

3.2 Topics and Other Supporting Materials

3.2.1 Topics

Topic 8.16 - Software Design Analysis
- Excerpt Include
  SWEHBVD:Software Design Analysis
  SWEHBVD:Software Design Analysis
  nopanel true
  - SA Tasks for SWEs
    - 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

3.2.2 Process Asset Templates

PAT-021 - SADESIGN Checklist
- Excerpt Include
  PAT-021 - SADESIGN Checklist
  PAT-021 - SADESIGN Checklist
  nopanel true
PAT-023 - Preparing for a SARB Checklist
- Excerpt Include
  PAT-023 - Preparing for a SARB Checklist
  PAT-023 - Preparing for a SARB Checklist
  nopanel true
PAT-031 - Critical Design Analysis Checklist
- Excerpt Include
  PAT-031 - Critical Design Analysis Checklist
  PAT-031 - Critical Design Analysis Checklist
  nopanel true
PAT-008 - Safety Considerations for Design Peer Reviews Checklist
- Excerpt Include
  PAT-008 - Safety Considerations for Design Peer Reviews Checklist
  PAT-008 - Safety Considerations for Design Peer Reviews Checklist
  nopanel true
PAT-020 - Examples of Interface Problems
- Excerpt Include
  PAT-020 - Examples of Interface Problems
  PAT-020 - Examples of Interface Problems
  nopanel true

3.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. This section may be removed if there is no content for it.

Content

Space Tools

Versions Compared

Old Version 27

New Version 28

Key

1. Introduction

1.1 Inputs

1.2 Predecessor Activities

1.3 Outputs

1.4 Successor Activities

1.5 Activity Repetition

1.6 Center Resources From SPAN

2. Software Development Activity

2.1 SWEs

2.2 Topics and other Supporting Materials

2.2.1 Topics

2.2.2 Supporting Materials

2.3 Other Associated SWEs, Topics, etc.

3. Software Assurance Activity

3.1 Software Assurance Tasks from SWEs

3.1.1 - Copy of SWE-058 - Detailed Design with new tab 4

3.2 Topics and Other Supporting Materials

3.2.1 Topics

3.2.2 Process Asset Templates

3.3 Other Associated SWEs, Topics, etc.

Content

Space Tools

Page History

Versions Compared

Old Version 27

New Version 28

Key

1. Introduction

1.1 Inputs

1.2 Predecessor Activities

1.3 Outputs

1.4 Successor Activities

1.5 Activity Repetition

1.6 Center Resources From SPAN

2. Software Development Activity

2.1 SWEs

2.2 Topics and other Supporting Materials

2.2.1 Topics

2.2.2 Supporting Materials

2.3 Other Associated SWEs, Topics, etc.

3. Software Assurance Activity

3.1 Software Assurance Tasks from SWEs

3.1.1 - Copy of SWE-058 - Detailed Design with new tab 4

3.2 Topics and Other Supporting Materials

3.2.1 Topics

3.2.2 Process Asset Templates

3.3 Other Associated SWEs, Topics, etc.