bannerd

A. Introduction

B. Institutional Requirements

C. Project Software Requirements

D. Topics

E. Tools, References, and Terms

F. SPAN
(NASA Only)

Versions Compared

Old Version 3

changes.mady.by.user Haigh, Fred

Saved on

compared with

New Version 4

changes.mady.by.user Haigh, Fred

Saved on

Key

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

...

"Project Tasks are recommended for projects where this SWE is applicable. They are derived from the requirement and guidance . Suggestions for performing completing the tasks and producing the suggested recommended work products are based on the guidance in tab 3."

...

Panel

4.1 Tasking for Software Development

Guidance for each task is available in tab 3. 

  1. Assess Design Readiness 
  2. Establish Coding Standards and Processes
  3. Establish Project Specific Design Considerations
  4. Establish Detailed Design Documentation and Progress Reviews
  5. Establish Design Maintenance Processes and Mechanisms

4.2 Software Development Work Products

  1. Software Development Process - which includes details on the Design Process to be followed. 
  2. List of design components including when they are expected to be available - as input to Development Schedule
  3. List of methods, tools, standards, and guidelines for your project. 
  4. List of training and experience required by team members to perform the design and development work. 

4.3 Metrics

Suggested metrics are listed below. Items in bold are strongly recommended for implementation in order to provide benefit for tracking and assessing completion of the work. 

  • # of architectural issues identified vs. number closed.
  • # of design issues found versus the number of design issues resolved.
  • # of requirement issues (Open, Closed) over time.
  • # of non-conformances identified by life cycle phase over time.
  • # of software work product Non-Conformances identified by life cycle phase over time


This tasking was derived using

...

6.4 Assembling the Combined Activity from Tasks

Looking at the Development Tasks above, it is clear that there is not a one to one correspondence between Development Tasks and Assurance Tasks. The table below demonstrates this: 

Development TaskAssurance Task
  1. Assess Design Readiness 
  2. Establish Coding Standards and Processes
  3. Establish Project Specific Design Considerations
  4. Establish Detailed Design Documentation and Progress Reviews
  5. Establish Design Maintenance Processes and Mechanisms

Include Page
SWE-058 - SA Task1
SWE-058 - SA Task1

Include Page
SWE-058 - SA Task2
SWE-058 - SA Task2

Include Page
SWE-058 - SA Task3
SWE-058 - SA Task3

Include Page
SWE-058 - SA Task4
SWE-058 - SA Task4

Include Page
SWE-058 - SA Task5
SWE-058 - SA Task5



Page Editor: Tim Crumbley
NASA Official: Tim Crumbley
Accessibility
NASA Software Engineering Handbook - A service of the NASA Office of the Chief Engineer
NASA Privacy Statement
______________________________________________________________________________