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.
Panel
borderColor
blue
title
NPR 7150.2B para 4.3.1
Include Page
2D-Para 4.3.1
2D-Para 4.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.
Panel
borderColor
black
borderWidth
2
title
Inputs, Outputs, and Predecessor 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
Note
List of some of the inputs from other activities that are necessary for the activity to begin.
Examples:
Requirements - These influence the design of the software
Architecture Documents- These influence the design of the software
1.2 Predecessor Activities
Note
List of some of the other activities that must be started (not necessarily completed) so that this activity may begin.
Examples:
Predecessor Activities are performed before Peer Reviews. These activities produce the work products that will be reviewed.
Life Cycle Planning - Design activities are included in the plan and schedules
Software Requirements - These influence the design of the software
Software Architecture - These influence the design of the software
1.3 Outputs
Note
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.
Links to Activities which might be started or supported by this activity.
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
Note
Describe what conditions determine if the activity needs to be repeated, such as re-planning after a change in requirements or schedule constraints.
How much of the activity needs to be repeated
Frequency of 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
Note
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).
Software Development Process - which includes details on the Design Process to be followed.
List of design components including when they are expected to be available - as input to Development Schedule
List of methods, tools, standards, and guidelines for your project.
List of training and experience required by team members to perform the design and development work.
....
Metrics
# of architectural issues, found in peer reviews, identified vs. number closed.
# of design issues, from peer reviews, found versus the number of design issues resolved.
# of requirement issues (Open, Closed) over time.
# of non-conformances identified found versus resolved.
# of software work product Non-Conformances identified versus closed.
2.2 Topics and other Supporting Materials
Note
This section is for SWEHB pages, other than SWEs, that directly support the activity. This section contains Topics, document structure pages, PATs, and other relevant pages.
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.
Div
id
tabs-3
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.
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.
