UNDER CONSTRUCTION

Note
Notes in this template provide guidance to authors on how the section if to be completed. Once the section is populated, the Note may be deleted. Notes are not intended to be left in the completed page.

4. Schedules

3.3 Software Schedules

SWE-016 - Software Schedule
SWE-018 - Software Activities Review
SWE-046 - Supplier Software Schedule

Tabsetup

0	1. Introduction
1	2. Initiation and Planning
2	3. Estination
3	4. Schedules
4	5. Training
5	6. Classification
6	Assurance and Safety
7	Coding
8	9. Cybersecurity
9	10. Scope
. Defining the Activity

Div

id	tabs-1

1. Introduction

Note
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).

Project Planning

Div

id	tabs-1

1. Introduction

Initiation and Planning activities occur at the beginning of a project.

A project may be for the creation of a new product, or the enhancement of an existing product. It may even involve the merging of capabilities from multiple products into a new, more capable product. It is always necessary to have an understanding of what the outcome of the project is. This is often called the High Level Requirements. These requirements set direction for the project. Once the direction is set, an early activity is the Make, Buy or Reuse decision.

Div

id	tabs-2

2

. Initiation and Planning

3.1 Software Life Cycle Planning

. 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

SWE-033 - Acquisition vs. Development Assessment

Excerpt Include

	SWEHBVD:SWE-033 - Acquisition vs. Development

Assessment

Assessment
	SWEHBVD:SWE-033 - Acquisition vs. Development Assessment
nopanel	true

Include Page

	SWE-033 - SA Task1
	SWE-033 - SA Task1

Include Page

	SWE-033 - SA Task2
	SWE-033 - SA Task2

Include Page

	SWE-033 - SA Task3
	SWE-033 - SA Task3

SWE-013 - Software Plans

Excerpt Include

	SWEHBVD:SWE-013 - Software Plans
	SWEHBVD:

SWE-013 - Software Plans
nopanel	true

Include Page

	SWE-013 - SA Task1
	SWE-013 - SA Task1

Include Page

	SWE-013 - SA Task2
	SWE-013 - SA Task2

SWE-024 - Plan Tracking

Excerpt Include

	SWEHBVD:SWE-024 - Plan Tracking
	SWEHBVD:SWE-024 - Plan Tracking
nopanel	true

Include Page

	SWE-024 - SA Task1
	SWE-024 - SA Task1

Include Page

	SWE-024 - SA Task2
	SWE-024 - SA Task2

Include Page

	SWE-024 - SA Task3
	SWE-024 - SA Task3

SWE-034 - Acceptance Criteria

Excerpt Include

	SWEHBVD:SWE-034 - Acceptance Criteria
	SWEHBVD:SWE-034 - Acceptance Criteria
nopanel	true

Include Page

	SWE-034 - SA Task1
	SWE-034 - SA Task1

SWE-036 - Software Process Determination

Excerpt Include

	SWEHBVD:SWE-036 - Software Process Determination
	SWEHBVD:SWE-036 - Software Process Determination
nopanel	true

Include Page

	SWE-036 - SA Task1
	SWE-036 - SA Task1

Include Page

	SWE-036 - SA Task2
	SWE-036 - SA Task2

SWE-037 - Software Milestones

Excerpt Include

	SWEHBVD:SWE-

039

037 - Software

Supplier Insight

Milestones
	SWEHBVD:SWE-

040

037 -

Access to Software Products

Software Milestones
nopanel	true

Include Page

	SWE-

042 - Source Code Electronic Access

037 - SA Task1
	SWE-

139 - Shall Statements

037 - SA Task1

Include Page

	SWE-

121

037 -

Document Tailored Requirements

SA Task2
	SWE-

125 - Requirements Compliance Matrix

037 - SA Task2

SWE-

027 - Use of Commercial, Government,
and Legacy Software

Div

id	tabs-3

3. Estimation

3.2 Software Cost Estimation

SWE-015 - Cost Estimation
SWE-151 - Cost Estimate Conditions
SWE-174 - Software Planning Parameters

Div

id	tabs-4

039 - Software Supplier Insight

Excerpt Include

	SWEHBVD:SWE-039 - Software Supplier Insight
	SWEHBVD:SWE-039 - Software Supplier Insight
nopanel	true

Include Page

	SWE-039 - SA Task1
	SWE-039 - SA Task1

Include Page

	SWE-039 - SA Task2
	SWE-039 - SA Task2

Include Page

	SWE-039 - SA Task3
	SWE-039 - SA Task3

Include Page

	SWE-039 - SA Task4
	SWE-039 - SA Task4

Include Page

	SWE-039 - SA Task5
	SWE-039 - SA Task5

Include Page

	SWE-039 - SA Task6
	SWE-039 - SA Task6

Include Page

	SWE-039 - SA Task7
	SWE-039 - SA Task7

Include Page

	SWE-039 - SA Task8
	SWE-039 - SA Task8

SWE-040 - Access to Software Products

Excerpt Include

	SWEHBVD:SWE-040 - Access to Software Products
	SWEHBVD:SWE-040 - Access to Software Products
nopanel	true

Include Page

	SWE-040 - SA Task1
	SWE-040 - SA Task1

SWE-042 - Source Code Electronic Access

Excerpt Include

	SWEHBVD:SWE-042 - Source Code Electronic Access
	SWEHBVD:SWE-042 - Source Code Electronic Access
nopanel	true

Include Page

	SWE-042 - SA Task1
	SWE-042 - SA Task1

SWE-139 - Shall Statements

Excerpt Include

	SWEHBVD:SWE-139 - Shall Statements
	SWEHBVD:SWE-139 - Shall Statements
nopanel	true

Include Page

	SWE-139 - SA Task1
	SWE-139 - SA Task1

SWE-121 - Document Tailored Requirements

Excerpt Include

	SWEHBVD:SWE-121 - Document Tailored Requirements
	SWEHBVD:SWE-121 - Document Tailored Requirements
nopanel	true

Include Page

	SWE-121 - SA Task1
	SWE-121 - SA Task1

Include Page

	SWE-121 - SA Task2
	SWE-121 - SA Task2

SWE-125 - Requirements Compliance Matrix

Excerpt Include

	SWEHBVD:SWE-125 - Requirements Compliance Matrix
	SWEHBVD:SWE-125 - Requirements Compliance Matrix
nopanel	true

Include Page

	SWE-125 - SA Task1
	SWE-125 - SA Task1

Include Page

	SWE-125 - SA Task2
	SWE-125 - SA Task2

SWE-027 - Use of Commercial, Government, and Legacy Software

Excerpt Include

	SWEHBVD:SWE-027 - Use of Commercial, Government, and Legacy Software
	SWEHBVD:SWE-027 - Use of Commercial, Government, and Legacy Software
nopanel	true

Include Page

	SWE-027 - SA Task1
	SWE-027 - SA Task1

SWE-151 - Cost Estimate Conditions

Excerpt Include

	SWEHBVD:SWE-151 - Cost Estimate Conditions
	SWEHBVD:SWE-151 - Cost Estimate Conditions
nopanel	true

Include Page

	SWE-151 - SA Task1
	SWE-151 - SA Task1

SWE-016 - Software Schedule

Excerpt Include

	SWEHBVD:SWE-016 - Software Schedule
	SWEHBVD:SWE-016 - Software Schedule
nopanel	true

Include Page

	SWE-016 - SA Task2
	SWE-016 - SA Task2

SWE-046 - Supplier Software Schedule

Excerpt Include

	SWEHBVD:SWE-046 - Supplier Software Schedule
	SWEHBVD:SWE-046 - Supplier Software Schedule
nopanel	true

Include Page

	SWE-046 - SA Task1
	SWE-046 - SA Task1

SWE-020 - Software Classification

Excerpt Include

	SWEHBVD:SWE-020 - Software Classification
	SWEHBVD:SWE-020 - Software Classification
nopanel	true

Include Page

	SWE-020 - SA Task1
	SWE-020 - 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.

Software Assurance Plan
- Excerpt Include
  SWEHBVD:8.51 - Software Assurance Plan
  SWEHBVD:8.51 - Software Assurance Plan
  nopanel true

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-5

5. Training

3.4 Software Training

SWE-017 - Project and Software Training

Div

id	tabs-6

6. Classification

3.5 Software Classification Assessments

SWE-020 - Software Classification
SWE-176 - Software Records

3.9 Software Development Processes and Practices

SWE-032 - CMMI Levels for
Class A and B Software

Div

id	tabs-7

7. Assurance and Safety

3.6 Software Assurance and Software
Independent Verification & Validation

SWE-022 - Software Assurance
SWE-141 - Software Independent Verification
and Validation
SWE-131 - Independent Verification and
Validation Project Execution Plan
SWE-178 - IV&V Artifacts
SWE-179 - IV&V Submitted Issues and Risks

3.7 Safety-Critical Software

SWE-205 - Determination of Safety-
  Critical Software
SWE-023 - Software Safety-Critical
                   Requirements
SWE-134 - Safety Critical Software
                   Design Requirements
SWE-219 - Test Coverage for Safety
Critical Software Components
SWE-220 - Cyclomatic Complexity Values
for Safety Critical Software

Div

id	tabs-8

8. Coding Techniques

3.8 Automatic Generation of Software Source Code

SWE-146 - Auto-generated Source Code
SWE-206 - Auto-Generation Software Inputs

3.10 Software Reuse

SWE-147 - Specify Reusability Requirements
SWE-148 - Contribute to Agency
Software Catalog

Div

id	tabs-9

9. Cybersecurity

3.11 Software Cybersecurity

SWE-156 - Evaluate Systems for
                   Security Risks
SWE-154 - Identify Security Risks
SWE-157 - Protect Against
                   Unauthorized Access
SWE-159 - Verify and Validate Risk
                   Mitigations
SWE-207 - Secure Coding Standard
SWE-185 - Verification of Software Code
                   to Coding Standards
SWE-210 - Detection of Adversarial Actions

Div

id	tabs-10

10. Scope Management

3.12 Software Bi-Directional Traceability

SWE-052 - Bidirectional Traceability

Content

Space Tools

Versions Compared

Old Version 2

New Version Current

Key

UNDER CONSTRUCTION

4. Schedules

1. Introduction

1.1 Inputs

1.2 Predecessor Activities

1.3 Outputs

1.4 Successor Activities

1.5 Activity Repetition

1.6 Center Resources From SPAN

1. Introduction

2

. Defining the Activity

2.1 SWEs

3. Estimation

2.2 Topics and other Supporting Materials

2.3 Other Associated SWEs, Topics, etc.

5. Training

6. Classification

7. Assurance and Safety

8. Coding Techniques

9. Cybersecurity

10. Scope Management

Content

Space Tools

Page History

Versions Compared

Old Version 2

New Version Current

Key

UNDER CONSTRUCTION

1. Introduction

1.1 Inputs

1.2 Predecessor Activities

1.3 Outputs

1.4 Successor Activities

1.5 Activity Repetition

1.6 Center Resources From SPAN

1. Introduction

2

. Defining the Activity

2.1 SWEs

3. Estimation

4. Schedules

2.2 Topics and other Supporting Materials

2.3 Other Associated SWEs, Topics, etc.

5. Training

6. Classification

7. Assurance and Safety

8. Coding Techniques

9. Cybersecurity

10. Scope Management