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 1

changes.mady.by.user Haigh, Fred Douglas. (HQ-KA000)[PEROT]

Saved on

compared with

New Version 2

changes.mady.by.user Haigh, Fred Douglas. (HQ-KA000)[PEROT]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: fix name
Excerpt

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

Excerpt Include
SWEHBVC:SWE-088 - Software Peer Reviews and Inspections - Checklist Criteria and Tracking
SWEHBVC:SWE-088 - Software Peer Reviews and Inspections - Checklist Criteria and Tracking
nopaneltrue



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
______________________________________________________________________________