bannerd

A. Introduction

B. Institutional Requirements

C. Project Software Requirements

D. Topics

E. Tools, References, and Terms

F. SPAN
(NASA Only)

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

UNDER CONSTRUCTION

This template, when complete, will be used to build out the SWEHB Activities. During development, its job is to take ideas and experiment with the layout of content. To do this will require many more tabs than will be needed wen the development job is done. 

A.00 Activity Content Template

1. Activity Overview

The major components of Planning are listed below along with a short description of what they contain. 


This section gives the user a top level view of the content of the activity. Subsections lay out the major pieces of work or concern in the Activity. For example, In the Planning Activity we could include estimation, schedule, training and classification as major components. 

1.1 Components of Planning 

In this example,

  • each SWE link has its requirement listed below the link (Excerpt-Include)
  • Each page in Supplementary Materials has its excerpt listed below the link (Excerpt-Include)

All SWEs and Topics already have excerpts. We would just need to be sure that the excerpt is suitable for the Activity as well as the other places where it is used. If we need a special description for the Activity, we could put that in a child page under the parent page and use the Include-Page macro to pull it in here. 

RequirementSupplementary Materials

3.1.2 The project manager shall assess options for software acquisition versus development.


3.1.3 The project manager shall develop, maintain, and execute software plans, including security plans, that cover the entire software life cycle and, as a minimum, address the requirements of this directive with approved tailoring.

3.1.5 The project manager shall define and document the acceptance criteria for the software. 


3.1.6 The project manager shall establish and maintain the software processes, software documentation plans, list of developed electronic products, deliverables, and list of tasks for the software development that are required for the project’s software developers, as well as the action required (e.g., approval, review) of the Government upon receipt of each of the deliverables.


3.1.7 The project manager shall define and document the milestones at which the software developer(s) progress will be reviewed and audited. 


3.1.8 The project manager shall require the software developer(s) to periodically report status and provide insight into software development and test activities; at a minimum, the software developer(s) will be required to allow the project manager and software assurance personnel to:

    1. Monitor product integration.
    2. Review the verification activities to ensure adequacy.
    3. Review trade studies and source data.
    4. Audit the software development processes and practices.
    5. Participate in software reviews and technical interchange meetings.


3.1.9 The project manager shall require the software developer(s) to provide NASA with software products, traceability, software change tracking information, and non-conformances in electronic format, including software development and management metrics.


3.1.10 The project manager shall require the software developer(s) to provide NASA with electronic access to the source code developed for the project in a modifiable format.


3.1.11 The project manager shall comply with the requirements in this NPR that are marked with an “X” in Appendix C consistent with their software classification.


Error rendering macro 'excerpt-include'

No link could be created for 'SWEHBVD:SWE-121 - Document Tailored Requirements'.


3.1.13 Each project manager with software components shall maintain a requirements mapping matrix or multiple requirements mapping matrices against requirements in this NPR, including those delegated to other parties or accomplished by contract vehicles or Space Act Agreements. 


Error rendering macro 'excerpt-include'

No link could be created for 'SWEHBVD:SWE-027 - Use of Commercial, Government, and Legacy Software'.



1.2 Components of Estimation

1.3 Components of Scheduling

1.4 Components of Training

1.5 Components of Classification


2. Requirements


3. Supplementary Guidance


  • No labels
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
______________________________________________________________________________