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.
Panel
borderColor
black
borderWidth
2
title
Inputs, Outputs, and Related Activities
Activity graphical representation of Inputs, Outputs, Predecessor and Successor Activities as appropriate. Not meant to be exhaustive, but representative of a typical project.
1.1 Inputs
ExamplesDocuments that are necessary for Design to begin:
Implementation and Unit Testing - Implements the Design into one or more code modules.
Preliminary Design Review
Critical Design Review
Test Readiness Review
Operational Readiness Review
1.5 Activity Repetition
Design is always done once. It should be peer reviewed and analyzed by Software Assurance.
Design may be reviewed and re-analyzed as often as there are significant changes in architecture or requirements. For example:
Technology changes to the architecture requires changes to the design
Customer changes to requirements require changes to the design
1.6 Center Resources From 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).