bannerd

A. Introduction

B. Institutional Requirements

C. Project Software Requirements

D. Topics

E. Tools, References, and Terms

F. SPAN
(NASA Only)

SWE-146 - Last used in rev NPR 7150.2D

RevSWE Statement
A


Difference between A and B

NEW

B

3.8.1 The project manager shall define the approach to the automatic generation of software source code including:

    1. Validation and verification of auto-generation tools.
    2. Configuration management of the auto-generations tools and associated data.
    3. Identification of the allowable scope for the use of auto-generated software.
    4. Verification and validation of auto-generated source code.
    5. Monitoring the actual use of auto-generated source code compared to the planned use.
    6. Policies and procedures for making manual changes to auto-generated source code.
    7. Configuration management of the input to the auto-generation tool, the output of the auto-generation tool, and modifications made to the output of the auto-generation tools.
Difference between B and CIn item c, changed "Identification" to "Description".
Also, added requirement to include the limits of the auto-generated software.
In item d., made the requirement more specific by adding "using the same software standards and processes as hand-generated code".
C

3.8.1 The project manager shall define the approach to the automatic generation of software source code including:

    1. Validation and verification of auto-generation tools.
    2. Configuration management of the auto-generation tools and associated data.
    3. Description of the limits and the allowable scope for the use of the auto-generated software.
    4. Verification and validation of auto-generated source code using the same software standards and processes as hand-generated code.
    5. Monitoring the actual use of auto-generated source code compared to the planned use.
    6. Policies and procedures for making manual changes to auto-generated source code.
    7. Configuration management of the input to the auto-generation tool, the output of the auto-generation tool, and modifications made to the output of the auto-generation tools.

Difference between C and DNo change
D

3.8.1 The project manager shall define the approach to the automatic generation of software source code including: 

a. Validation and verification of auto-generation tools.
b. Configuration management of the auto-generation tools and associated data.
c. Description of the limits and the allowable scope for the use of the auto-generated software.
d. Verification and validation of auto-generated source code using the same software standards and processes as hand-generated code.
e. Monitoring the actual use of auto-generated source code compared to the planned use.
f. Policies and procedures for making manual changes to auto-generated source code.
g. Configuration management of the input to the auto-generation tool, the output of the auto-generation tool, and modifications made to the output of the auto-generation tools.



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