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 37

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


Note

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


Tabsetup
01. Introduction
12. Software Development ActivityEngineering
23. Software Assurance Activity
List of some of the inputs from other activities

Documents that are necessary for

the activity

Design to begin

. 

Examples: 

1.2 Predecessor Activities

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

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 ProductUsed by Downstream Activity
  • Implementation and Unit Testing
  • Preliminary at Preliminary Design Review
  • Baselined at Critical Design Review
  • Updated at Test Readiness Review
  • Implementation and Unit Testing
  • Preliminary at Preliminary Design Review
  • Baselined at Critical Design Review
  • Updated at Test Readiness Review
  • 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). 

    ActivityDescription

    Design

    		Assets for use during product design
    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

    Div
    idtabs-2

    2. Software

    Development Activity

    Engineering

    Note

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

    2.1 SWEs

    Note
    Expand
    titleSWE-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
    nopaneltrue

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

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

    2.2 Topics and other Supporting Materials

    NoteThis 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

    Expand
    titleSWE-058 Topics

    Include Page
    SWE-058-TopicsETopics
    SWE-058-TopicsETopics

    2.2.2 Supporting Materials

    Expand
    titleSWE-058 Supporting Materials

    Include Page
    SWE-058-SupportESupport
    SWE-058-SupportESupport

    2.3 Other Associated SWEs, Topics, etc.

    NoteIncludes 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

    .

     


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

    3.3 Other Associated SWEs, Topics, etc.

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

    SWE-058 - Detailed Design with new tab 4

    Expand
    titleSWE-058 SA Tasking and Work Product Details

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

    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
    nopaneltrue

    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

    SA Work Products

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

    Include Page
    SWE-058-SAWP
    SWE-058-SAWP

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

    3.2 Topics and Other Supporting Materials

    3.2.1 Topics

    Expand
    SA Tasks for SWEs
    titleSA Tasking from Topic 8.16 - Software Design Analysis

    3.2.2 Process Asset Templates

    PAT-021 - SADESIGN Checklist

    excerpt-

    Include Page

    		PAT-021 - SADESIGN ChecklistPAT-021 - SADESIGN Checklist
    nopaneltrue
    Excerpt Include
    PAT-023 - Preparing for a SARB ChecklistPAT-023 - Preparing for a SARB Checklist
    nopaneltrue
    Excerpt Include
    PAT-031 - Critical Design Analysis ChecklistPAT-031 - Critical Design Analysis Checklist
    nopaneltrue
    Excerpt Include
    PAT-008 - Safety Considerations for Design Peer Reviews ChecklistPAT-008 - Safety Considerations for Design Peer Reviews Checklist
    nopaneltrue
    Excerpt Include
    PAT-020 - Examples of Interface ProblemsPAT-020 - Examples of Interface Problems
    nopaneltrue
    Note
    Design Analysis Process Asset Templates
    Design Analysis Process Asset Templates

    3.3 Other Associated SWEs, Topics, etc.





    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
    ______________________________________________________________________________