bannerd

A. Introduction

B. Institutional Requirements

C. Project Software Requirements

D. Topics

E. Tools, References, and Terms

F. SPAN
(NASA Only)
Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

Version 1 Next »

Last used in rev NPR 7150.2C

RevSWE Statement
A

4.3.3 The project shall, for each planned software peer review/inspections:

      a. Use a checklist to evaluate the work products.
      b. Use established readiness and completion criteria.
      c. Track actions identified in the reviews until they are resolved.
      d. Identify required participants.

Difference between A and B

Reworded with same intent

B

5.3.3 The project manager shall, for each planned software peer review or software inspection:

    1. Use a checklist or formal reading technique (e.g., perspective based reading) to evaluate the work products.
    2. Use established readiness and completion criteria.
    3. Track actions identified in the reviews until they are resolved.
    4. Identify required participants.
Difference between B and C

No change

C

5.3.3 The project manager shall, for each planned software peer review or software inspection:

    1. Use a checklist or formal reading technique (e.g., perspective based reading) to evaluate the work products.
    2. Use established readiness and completion criteria.
    3. Track actions identified in the reviews until they are resolved.
    4. Identify the required participants.



  • No labels
Page Editor: Tim Crumbley
NASA Official: Tim Crumbley
NASA Software Engineering Handbook - A service of the NASA Office of the Chief Engineer
NASA Privacy Statement
______________________________________________________________________________