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.
Planning of Software Assurance activities in a Software Development Project are done in a collaborative fashion along with the Software Development team. It includes cost estimates and schedules.
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
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.
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
SA Plan
SA Auditing
SA SW Requirements Analysis
SA SW Source Code Analysis
SA SW Testing Analysis
SA Reporting
SA Design Analysis
SA Safety and Hazard Anaysis
1.4 Successor Activities
Note
Links to Activities which might be started or supported by this activity.
SA Auditing
SA SW Requirements Analysis
SA SW Source Code Analysis
SA SW Testing Analysis
SA Reporting
SA Design Analysis
SA Safety and Hazard Anaysis
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
This activity is done in the early stages of a Software Project. Other work may be started before the planning is actually completed.
During the life of the project there may be multiple times when significant changes to things like requirements, budget, schedule, technology, which make re-planning necessary. Re-planning is covers the same areas of the original planning to make sure that all changes are accounted for in the new plans. Re-planning is done as often as necessary to keep the project under control.
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).
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)
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.
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.
