UNDER CONSTRUCTION
View this section on the website
See edit history of this section
Post feedback on this section
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.
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.
Activity graphical representation of Inputs, Outputs, and Predecessor Activities
1.1 Inputs
List of some of the inputs from other activities that are necessary for the activity to begin.
Examples:
- 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
- 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.
Examples:
Predecessor Activities are performed before Peer Reviews. These activities produce the work products that will be reviewed.
- Life Cycle Planning - plans, schedules, estimates, etc.
- Software Architecture
- Software Design
- Software Testing - plans and procedures
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.
Examples:
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.
| Output Work Product | Used by Downstream Activity | Supporting SWE or Topic |
|---|---|---|
| Peer Review Findings |
|
1.4 Repetition
Describe what conditions determine if the activity needs to be repeated.
- How much of the activity needs to be repeated
- Frequency of repetition
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.
- Link to the SWE goes here
- Excerpt include for the SWE goes here (Remove Surrounding Panel)
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.
- Link to the Topic or page goes here
- Excerpt include for the Topic or page goes here (Remove Surrounding Panel)
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.
- Include page for the PAT page goes here
