bannerd

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

Compare with Current View Page History

« Previous Version 11 Next »

UNDER CONSTRUCTION

Peer Review Activity

1. Introduction

(From 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.

1.1 Inputs

  • Requirements
  • Planning
  • Architecture Items
  • Design items

1.2 Predecessor Activities

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

  • Life Cycle Planning
  • Software Architecture 
  • Software Design
  • Software Testing

1.3 Outputs

The activities that initiated the Peer Review, receive the findings from Peer Reviews, and then use those findings to to fix defects and implement improvements uncovered in the reviews. 

Output Work ProductUsed by Downstream ActivitySupporting SWE or Topic
Peer Review Findings
  • Configuration Management
  • Coding



2. Defining the Activity

2.1 SWEs

2.2 Topics and other Supporting Materials

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. 

Click on a link to download a usable copy of the template. 



3.


4.


5.


  • No labels