Typically starts with a definition of 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
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:
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
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 - plans, schedules, estimates, etc.
Software Architecture
Software Design
Software Testing - plans and procedures
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.
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
Peer Review Findings
Life Cycle Planning
Software Architecture
Software Design
Software Testing
Configuration Management
Coding
1.4 Successor Activities
Note
Links to Activities which might be started or supported by this activity.
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
Div
id
tabs-2
2. Defining the Activity
Note
This tab contains the links to pages in the SWEHB or excerpts from the NASA-STD-8739.8B that are at the heart of the activity.
2.1 SWEs
Note
This section contains the links to SWE pages that form the heart of the activity. In the case of Software Assurance, copy in the task table from each of the tab 7.1 from appropriate SWEs.
Link to the SWE goes here
Excerpt include for the SWE goes here (Remove Surrounding Panel)
SWE
Requirement
SA Tasks
034
Excerpt Include
SWE-034 - Acceptance Criteria
SWE-034 - Acceptance Criteria
nopanel
true
Include Page
SITE:SWE-034 - SA Task1
SITE:SWE-034 - SA Task1
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 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.
Note
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
Div
id
tabs-3
3. Software Assurance
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
Software Assurance Tasks are included in many of the SWEs in this activity.
Note
For each of the SWEs in this activity (see tab 2 .1 SWEs) populate the table below with the SWE, Requirement, and SA Tasks.
The first column is for the SWE number
The second column is for the requirement - using the Excerpt Include macro to pull in the Excerpt from the SWE page (excerpt includes the text of the requirement)
The third column is for the SA Tasks using the Include Page macro - Each of the SA Tasks for a SWE are child pages under SITE:NASA-STD-8739.8B page
SWE-034 is used below only as an example of how to populate the table. The example below, using SWE-034, should be replaced by the actual SWEs in this activity.
