bannerd

A. Introduction

B. Institutional Requirements

C. Project Software Requirements

D. Topics

E. Tools, References, and Terms

F. SPAN
(NASA Only)

SWE-015 - Last used in rev NPR 7150.2D

RevSWE Statement
A

2.2.3 The project shall establish, document, and maintain at least one software cost estimate and associated cost parameter(s) that satisfies the following conditions:

    1. Covers the entire software life cycle.
    2. Is based on selected project attributes (e.g., assessment of the size, functionality, complexity, criticality, and risk of the software processes and products).
    3. Is based on the cost implications of the technology to be used and the required maturation of that technology.
Difference between A and B

Further defines that Class A and B software over $2M need 2 cost estimates, others only need 1 estimate. Removed the conditions that need to be satisfied.


B

3.2.1 The project manager shall establish, document, and maintain two cost estimates and associated cost parameters for all software class A and B projects that have an estimated project cost of $2 million dollars or more or one software cost estimate and associated cost parameter(s) for other software projects.

Difference between B and C

Made requirement more explicit; Added requirement for the use of a "model" and deleted the requirement for Class E to develop a cost estimate.

C

3.2.1 To better estimate the cost of development, the project manager shall establish, document, and maintain:

    1. Two cost estimate models and associated cost parameters for all Class A and B software projects that have an estimated project cost of $2 million or more.
    2. One software cost estimate model and associated cost parameter(s) for all Class A and Class B software projects that have an estimated project cost of less than $2 million.
    3. One software cost estimate model and associated cost parameter(s) for all C and D software projects.
    4. One software cost estimate model and associated cost parameter(s) for all Class F software projects.

Difference between C and DClarification - added the word Class in front of C & D in item c.
D

3.2.1 To better estimate the cost of development, the project manager shall establish, document, and maintain:

    1. Two cost estimate models and associated cost parameters for all Class A and B software projects that have an estimated project cost of $2 million or more.
    2. One software cost estimate model and associated cost parameter(s) for all Class A and Class B software projects that have an estimated project cost of less than $2 million.
    3. One software cost estimate model and associated cost parameter(s) for all Class C and Class D software projects.
    4. One software cost estimate model and associated cost parameter(s) for all Class F software projects.



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