1. Activity View of SWEHB

A.00 Activity View
- A.00.2 - History of Improvement Efforts
- A.01 Software Life Cycle Planning — Software Life Cycle Planning is a large activity. It includes a number of related sub-activities that are performed throughout the life of a development project.
- A.02 Software Assurance and Software Safety — The inclusion of content from NASA-STD-8739.8B adds breadth to the Handbook in Software Assurance and Safety areas.
  - A.02.01 Software Assurance and Software Safety
- A.03 Software Requirements — Requirements are the basis for a software product.
  - A.03.01 Software Requirements
- A.04 Software Design — The Software Design Activity includes both Architecture and Design aspects of the software. While they actually focus on different areas of the software development, they are very closely coupled. A change in one often requires a change in the other.
  - A.04.01 Software Design
- A.05 Software Implementation — Software Implementation is the building of code modules driven by the software requirements. It is shaped by the architecture and design considerations, and by the planning parameters including cost and schedule constraints.
  - A.05.01 Software Implementation
- A.06 Software Testing — Software testing is required to ensure that the software meets the agreed requirements and design. The application works as expected. The application doesn’t contain serious bugs, and the software meets its intended use as per user expectations.
  - A.06.01 Software Testing
- A.07 Software Release, Operations, Maintenance, and Retirement — Software operations, maintenance, and retirement activities are planned to provide a written or electronic file on how to operate the software, modify and retest the software and provide information on where to archive the software products, the software development environment, and software test environment products and tools.
- A.08 Software Configuration Management — Software Configuration Management planning encompasses the practices and procedures for administering source code, producing software development builds, controlling change, and managing software configurations for all of the software products, tools, data, and components produced by the project.
  - A.08.01 Software Configuration Management
- A.09 Software Risk Management — Risk Management is a continuous activity as stated in SWE-086 - Continuous Risk Management. The guidance in this requirement contains a basic process for conducting Risk Management.
  - A.09.01 Software Risk Management
- A.10 Software Peer Reviews and Inspections — Software peer reviews or inspections are performed to ensure product and process quality, add value, and reduce risk through expert knowledge infusion, confirmation of approach, identification of defects, and specific suggestions for product improvements.
  - A.10.01 Software Peer Reviews and Inspections
  - Work Products That Might Benefit From a Peer Review — Work Products that might benefit from a Peer Review are described in the table below:
- A.11 Software Measurements — Numerous years of experience on many NASA projects demonstrate the following three key reasons for software measurement activities: (1) to understand and model software engineering processes and products, (2) to aid in assessing the status of software projects, (3) to guide improvements in software engineering processes.
  - A.11.01 Software Measurements
- A.12 Software Non-conformance or Defect Management — To make sure that all software non-conformances are addressed. Managing and tracking non-conformances, software problem reports, or software issues are critical steps to ensuring that software defects are flagged and handled properly.
  - A.12.01 Software Non-conformance or Defect Management
- A.13 NASA Institutional Requirements — Institutional Requirements are grouped into several sub-activities.
Activity SWE 1.4 Sections
- SWE 1.3 A.01 — 1.3 Associated Activity
- SWE 1.3 A.02 — 1.3 Associated Activity
- SWE 1.3 A.07 — 1.3 Associated Activity
- SWE 1.3 A.13 — 1.3 Associated Activity
- SWE 1.4 A.01 — 1.4 Associated Activity
- SWE 1.4 A.02 — 1.4 Associated Activity
- SWE 1.4 A.03 — 1.4 Associated Activity
- SWE 1.4 A.04 — 1.4 Associated Activity
- SWE 1.4 A.05 — 1.4 Associated Activity
- SWE 1.4 A.06 — 1.4 Associated Activity
- SWE 1.4 A.07 — 1.4 Associated Activity
- SWE 1.4 A.08 — 1.4 Associated Activity
- SWE 1.4 A.09 — 1.4 Associated Activity
- SWE 1.4 A.10 — 1.4 Associated Activity
- SWE 1.4 A.11 — 1.4 Associated Activity
- SWE 1.4 A.12 — 1.4 Associated Activity
Activity Tools
B.00 Activity View - Sample content
Traceability of Subjects to SWEs and SM
Updates to SWEHB Pages

2. Launch Sequence

Steps in launching Activity View

2.1 Pre-launch

Item	Status
In all SWE and Topic pages in SWEHBVD that have a "Related Activity" section, add code to display the Activity section when the page contains the label "activity" All SWE pages All Topic pages	Done
Update all SWE pages with cross references to appropriate SWEs and Topics	Done
Update all Topic pages with cross references to appropriate SWEs and Topics	Done
Update all Activity pages with cross references to appropriate SWEs and Topics	In Progress
Update all PATs - Add PATs based on existing lists in SWEs and Topics - see PAT ToDo List	TBD
Prepare Blog entry to announce addition of Activity Pages

2.2 At Launch

Item

Status

Remove the "UNDER CONSTRUCTION" banner on all Activity pages

Add "activity" label to all SWE and Topic pages in SWEHBVD.

All SWE pages listed under page tree "SWE Pages"
All Topic pages listed under page tree "Topics Pages"

Tag blog entry with "swehb" label to display

Content

Space Tools

1. Activity View of SWEHB

2. Launch Sequence

2.1 Pre-launch

2.2 At Launch