Invalid license: Your evaluation license of Refined expired.
bannerd

A. Introduction

B. Institutional Requirements

C. Project Software Requirements

D. Topics

E. Tools, References, and Terms

F. SPAN
(NASA Only)

UNDER CONSTRUCTION

Activity - Software Peer Reviews and Inspections - Combined
This page contains macros or features from a plugin which requires a valid license.

You will need to contact your administrator.

1. Introduction

Typically starts with a quote from the NPR that helps define the activity. Additional descriptive material is meant to help define the activity but not be so detailed that it pulls in all of the guidance from the SWEs in the activity. 

NPR 7150.2B para 5.3.1

Software peer reviews and inspections are the in-process technical examination of work products by peers to find and eliminate defects early in the life cycle. Software peer reviews and inspections are performed following defined procedures covering the preparation for the review, the review itself is conducted, results are recorded, results are reported, and completion criteria is certified. When planning the composition of a software peer review or inspection team, consider including software testing, system testing, software assurance, software safety, software cybersecurity, and software IV&V personnel.

Peer Reviews are unique in the sense that they must be accounted for in the Software Development Plan, as well as used to improve the quality of that plan. 

Examples of Some Documents Going Through Peer Review 

1.1 Inputs

List of some of the inputs from other activities that are necessary for the activity to begin. 

  • Planning - Peer Reviews are planned activities. They appear in the plans and schedules for the project
  • Requirements - These are the things that are Peer Reviewed
  • Architecture Items - These are the things that are Peer Reviewed
  • Design items - These are the things that are Peer Reviewed
  • Source Code - These are the things that are Peer Reviewed
  • Test Plans and Procedures - These are the things that are Peer Reviewed

1.2 Predecessor Activities

List of some of the other activities that must be started (not necessarily completed) this activity to begin. 

Predecessor Activities are performed before Peer Reviews. These activities produce the work products that will be reviewed. 

  • Life Cycle Planning - Peer Reviews are planned activities. They are also used to review and improve all types of plans. 
  • Software Requirements -  Creating the things that are Peer Reviewed
  • Software Architecture Items - Creating the things that are Peer Reviewed
  • Software Design items - Creating the things that are Peer Reviewed
  • Implementation and Unit Testing - Source Code for Peer Review
  • Test Plans and Procedures - Creating the things that are Peer Reviewed

1.3 Outputs

List of some of the outputs or work products of the activity. These are typically used as inputs by the downstream activity. In some cases there is a supporting SWE associated with the work product. 

In the case of Peer Reviews, outputs cycle back to the activity that provided the inputs so that improvements to the work products can be made. The activities that initiated the Peer Review, receive the findings from Peer Reviews, Those activities then use those findings to to fix defects and implement improvements uncovered in the reviews. The improved work products are then used by downstream activities as the project proceeds. 

Output Work ProductUsed by Downstream Activity
  • Peer Review Findings
  • Life Cycle Planning
  • Software Architecture 
  • Software Design
  • Software Testing
  • Configuration Management
  • Coding


1.4 Successor Activities

Links to Activities which might be started or supported by this activity. 

  • Life Cycle Planning
  • Software Requirements
  • Software Architecture 
  • Software Design
  • Software Testing
  • Configuration Management
  • Implementation and Unit Testing - Coding

1.5 Repetition

Describe what conditions determine if the activity needs to be repeated.

  • How much of the activity needs to be repeated
  • Frequency of repetition

Peer Reviews are planned activities and may be repeated as needed throughout the life cycle.

  • As Software Requirements, budgets, schedules, and technology changes are factored into the project, additional Peer Reviews of affected work products may be desirable.  

1.6 Center Resources From SPAN

Add links to SPAN activity pages that are appropriate for this activity. Use links from the Activity section of the front page. SPAN

Several Centers Process Asset Libraries have materials related to this activity. Related Processes, templates, and other resources may be found in the following Activities in SPAN (available to NASA only). 

2. Defining the Activity

This tab contains the links to pages in the SWEHB that are at the heart of the activity. 

2.1 SWEs

This section contains the links to SWE pages that form the heart of the activity. 

  • Copy of SWE-087 - Software Peer Reviews and Inspections for Requirements, Plans, Design, Code, and Test Procedures
    • 5.3.2 The project manager shall perform and report the results of software peer reviews or software inspections for: 

      a. Software requirements.
      b. Software plans, including cybersecurity.
      c. Any design items that the project identified for software peer review or software inspections according to the software development plans.
      d. Software code as defined in the software and or project plans.
      e. Software test procedures.

    • Establishes the Peer Review Process to be used in the project
    • Tasks
      1. Identify specific documents for Peer Review
      2. Ensure that time for performing reviews is in the Plan and Schedule
      3. Identify Peer Review Process that will be followed for each Review
    • Work Products
      1. List of documents for Peer Review
      2. Plan and Schedule showing time allocation for Reviews
  • Copy of SWE-088 - Software Peer Reviews and Inspections - Checklist Criteria and Tracking
    • 5.3.3 The project manager shall, for each planned software peer review or software inspection:

      a. Use a checklist or formal reading technique (e.g., perspective-based reading) 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 the required participants.

    • Establishes individual Peer Review content for each of the documents to be reviewed
    • Tasks
      1. Prepare the Checklist for the Review
      2. Establish the Entrance and Exit Criteria for the Review
      3. Prepare Action Items and Plan for Their Resolution
      4. Select Participants for the Review
    • Work Products
      1. Review Checklist
      2. Entrance and Exit Criteria for the Review
      3. Action Items Tracking Mechanism
      4. Participants List for the Review
  • Copy of SWE-089 - Software Peer Reviews and Inspections - Basic Measurements
    • 5.3.4 The project manager shall, for each planned software peer review or software inspection, record necessary measurements. 
    • Establishes Metrics for the Process as well as the individual reviews
    • Tasks
      1. Establish in the Peer Review Process, metrics that will be obtained for all Peer Reviews
      2. Establish in the individual reviews of documents, metrics that are unique to the document being reviewed (if any) 
    • Work Products
      1. Tailored Peer Review Process with General Metrics for all reviews section 
      2. Specific additional metrics for the document(s) being reviewed

2.2 Topics and other Supporting Materials

This section is for SWEHB pages, other than SWEs, that directly support the activity. This section contains Topics, document content pages, PATs, and other pages. 

2.2.1 Topics

2.2.2 Supporting Materials

Peer Reviews Assets Process Asset Templates

Click on a link to download a usable copy of the template. (PRvw)       2/12/2025 - 9 items

Renew your license to continue

Your evaluation license has expired. Contact your administrator to renew your Reporting for Confluence license.



2.3 Other Associated SWEs, Topics, etc.

Includes other SWEHB pages that are indirectly associated with the activity. May include SWEs, Topics, document definition pages, PATs, etc. They may have been mentioned in the guidance of another page. 

3. Software Assurance Activity

Software Assurance is integral to the performance of all Software Development activities. It includes Process Monitoring as well as Process Analysis. 

  • Process Monitoring - addresses the question, "Is the development team following their processes and producing the expected work products?"
  • Process Analysis - addresses the question, "Are there better ways of performing the processes that would result in the early discovery of defects?"

3.1 Software Assurance Tasks from SWEs

Software Assurance Tasks are included in tab 7 of the SWEs in this activity. 

3.1.1 - Copy of SWE-087 - Software Peer Reviews and Inspections for Requirements, Plans, Design, Code, and Test Procedures

    • Tasking From NASA-STD-8739.8B

      • 1. Confirm that software peer reviews are performed and reported on for project activities. 

      • 2. Confirm that the project addresses the accepted software peer review findings.

      • 3. Perform peer reviews on software assurance and software safety plans.

      • 4. Confirm that the source code satisfies the conditions in the NPR 7150.2 requirement SWE-134, "a" through "l," based upon the software functionality for the applicable safety-critical requirements at each code inspection/review.

    • Software Assurance Products
      • SA peer review records (Including findings for  software assurance and software safety plans.)

3.1.2  -  Copy of SWE-088 - Software Peer Reviews and Inspections - Checklist Criteria and Tracking

    • Tasking From NASA-STD-8739.8B

      • 1. Confirm that the project meets the NPR 7150.2 criteria in "a" through "d" for each software peer review.

      • 2. Confirm that the project resolves the actions identified from the software peer reviews.

      • 3. Perform audits on the peer-review process.

    • Software Assurance Products
      • Peer Review Process Audit Report (SA audit results and findings on software peer-review process).

3.1.3 - Copy of SWE-089 - Software Peer Reviews and Inspections - Basic Measurements

    • Tasking From NASA-STD-8739.8B

      • 1. Confirm that the project records the software peer reviews and results of software inspection measurements.
    • Software Assurance Products
      • None at this time

3.2 Topics and Other Supporting Materials

3.2.1 Topics

3.2.2 Process Asset Templates

Peer Reviews Assets Process Asset Templates

Click on a link to download a usable copy of the template. (PRvw)       2/12/2025 - 9 items

Renew your license to continue

Your evaluation license has expired. Contact your administrator to renew your Reporting for Confluence license.



3.3 Other Associated SWEs, Topics, etc.

Includes other SWEHB pages that are indirectly associated with the activity. May include SWEs, Topics, document definition pages, PATs, etc. They may have been mentioned in the guidance of another page. This section may be removed if there is no content for it. 

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