bannerd

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

UNDER CONSTRUCTION

Tabsetup
01. Introduction
12. Initiation and PlanningIndependent V&V
23. EstinationIV&V Planning
34. SchedulesIV&V Artifacts
45. Training
56. Classification
6Assurance and Safety
7Coding
89. Cybersecurity
910. Scope
IV&V Issues and Risks

2. Assurance

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. Safety

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

4. Schedules

3.3 Software Schedules

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

Div
idtabs-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
idtabs-2
Div
idtabs-3
Div
idtabs-4
Div
idtabs-5

5. Training

3.4 Software Training

SWE-017 - Project and Software Training

The software assurance and software safety activities provide a level of confidence that software is free from vulnerabilities, either intentionally designed into the software or accidentally inserted at any time during its life cycle, that the software functions in an intended manner, and that the software does not function in an unintended manner. The software assurance process is the planned and systematic set of activities that ensure the conformance of software life cycle processes and products to requirements, standards, and procedures.  Software assurance assures that the software and its related products meet their specified requirements, conform to standards and regulations, are consistent, complete, correct, safe, secure, and reliable as warranted for the system and operating environment, and satisfy customer needs. The objectives of software assurance and software safety activities include the following:

  1. Ensuring that the processes, procedures, and products used to produce and sustain the software conform to all specified requirements and standards that govern those processes, procedures, and products.
    • A set of activities that assess adherence to, and the adequacy of the software processes used to develop and modify software products.
    • A set of activities that define and assess the adequacy of software processes to provide evidence that establishes confidence that the software processes are appropriate for and produce software products of suitable quality for their intended purposes.
  2. Determining the degree of software quality obtained by the software products.
  3. Ensuring that the software systems are safe and that the software safety-critical requirements are followed.
  4. Ensuring that the software systems are secure.


1.1 Related Activities

  • SE-Initiation and Planning - Assurance activities are planned. They are dependent on a whole host of other project activities.  
  • SE-Estimation - Estimates are made and tracked for assurance activities. Assurance must be measured and controlled. 
  • SE-Schedules - Assurance Activities are scheduled and tracked to completion.  
  • SE-Training - Assurance tam members are trained in Assurance methods, the use of Assurance tools, and related subjects. 
  • SE-Scope Management - Requirements, defect management, change management, Non-conformance and Defect Management. 
  • SE-Testing - including V&V
  • SE-Operations, Maintenance and Retirement
  • SE-Configuration Mgmt - including code repository, builds, and releases 
  • Peer Reviews - including Assurance reviews
  • Measurements - related to Assurance

1.2 Related NPR 7150.2 SWEs

1.3 Related Topics and Process Assets


Div
idtabs-2

2. Independent V&V


2.1 Related NPR 7150.2 SWEs

2.2 Related Topics and Process Assets


Div
idtabs-3

3. IV&V Planning


3.1 Related NPR 7150.2 SWEs

3.2 Related Topics and Process Assets


Div
idtabs-4

4. IV&V Artifacts


4,1 Related NPR 7150.2 SWEs

4.2 Related Topics and Process Assets


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

5. IV&V Issues and Risks


5.1 Related NPR 7150.2 SWEs

Div
idtabs-6
Div
idtabs-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

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

5.2 Related Topics and Process Assets


Div
idtabs-6

6.

Div
idtabs-7

7.

Div
idtabs-8

8.

Coding Techniques3.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
idtabs-9

9

. Cybersecurity3

.

11 Software CybersecuritySWE-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
idtabs-10

10.

Scope Management

3.12 Software Bi-Directional Traceability

SWE-052 - Bidirectional Traceability