• SWEHBVA - Healthcheck
• SWEHBVB - Healthcheck
• SWEHBVC - Healthcheck
• SWEHBVD - Healthcheck

It can be viewed by anyone. Each of the tabs tests a specific part of the software. The content in the tab explains what is being tested and displays what the viewer will see when there is an error, The content also explains what a "good" test looks like. In some cases the viewer must click on a link to exercise the software being tested and ensure proper functioning. 

2.1 Tabs And Tests

The following tabs are available in the SWEHBVD version of Healthcheck: 

1. TABSETUP - tests the "tabsetup" User Macro. This is the macro that displays content like a tabbed set of cards. If you see the tabs, the macro is working properly. 
   1. This page shows where all the "tabsetup" macros are found: tabsetup (1465)
2. Panel & Note - This tab displays several styles of panels, warning, and notes used in SWEHB. All come from Confluence Basic Macros. 
   1. This page shows where all the Panel macros are found: panel (1898)
   2. This page shows where all the Warning macros are found: warning (14)
   3. This page shows where all the Note macros are found: note (717)
   4. This page shows where all the Info macros are found: info (199)
3. SWEREF Macro - tests the SWERF and SWERFN macros. Clicking on the ¹²³  link should take the viewer to the Resources tab. This tests the functionality of the SWERFN macro. 
   1. This page shows where all the SWEREFN macros are found: swerefn (633)
4. Resources - REFSTABLE Macro - This contains a report that comes from the Reporting plugin. It reports on data contained in the References Table which is built using the Scaffolding Plugin. A list of selected references demonstrates the proper working of these plugins. 
5. Other - Displays the functioning of 3 Applicability Macros. 
6. TOC - Displays the table of contents macro for the Healthcheck page. 
7. Show If - shows the working of the Show-If macro. parts of the tab will not be displayed unless the viewer is an editor. 
8. Gliffy - displays a Gliffy flow chart diagram if the Gliffy plugin is working. 
9. Expand - This tab displays a working example of the Expand macro. All come from Confluence Expand Macros. 
   1. This page shows where all the expand macros are found: expand (493)

2.2 Daily Healthcheck

Each day, the SWEHB Maintainer is responsible for running Healthcheck and other tests to assess the operation of the whole SWEHB system. The links below are used to check on the system. 

• https://swehb.nasa.gov - This goes to the default SWEHB version. Currently this is the SWEHBVD home page - Book A. Introduction. 
• https://swehb-staging-pri.msfc.nasa.gov - This goes to the Staging SWEHB version. Normally this is the same as SWEHBVD Production home page - Book A. Introduction. 
• https://swehb.nasa.gov/display/SAEHB/Book+A.+Introduction - This goes to the Production SAEHB version for Software Assurance.
• https://swehb.nasa.gov/pages/reorderpages.action?key=SWEHBVD - This is the Pagetree for the Production SWEHBVD
• https://swehb.nasa.gov/display/SWEHBVD/Healthcheck - This is the Healthcheck for version SWEHBVD on Production.
• https://swehb-staging-pri.msfc.nasa.gov/display/SWEHBVD/Healthcheck - This is the Healthcheck for version SWEHBVD on Staging.
• https://swehb.nasa.gov/collector/pages.action?key=SWEHBVD - displays SWEHBVD pages with recent action. Check to see that only valid editors are making changes. 
• https://swehb.nasa.gov/collector/pages.action?key=SWEHBVC - displays SWEHBVC pages with recent action. Check to see that only valid editors are making changes. 
• https://swehb.nasa.gov/collector/pages.action?key=SWEHBVB - displays SWEHBVB pages with recent action. Check to see that only valid editors are making changes. 
• https://swehb.nasa.gov/collector/pages.action?key=SITE - displays SITE pages with recent action. Check to see that only valid editors are making changes. 
• https://swehb.nasa.gov/collector/pages.action?key=7150 - displays 7150 pages with recent action. Check to see that only valid editors are making changes. 
• https://swehb.nasa.gov/display/SWEHBVD/SPAN+Access - tests the SPAN link. Should take you to SPAN in NEN. 
  • Make sure SPAN is available
  • Open all Center Libraries in new tabs to make sure they are available. See Documentation of SPAN for more information. 
• https://swehb-staging-pri.msfc.nasa.gov/collector/pages.action?key=MSH7009B - displays MSH7009B pages with recent action. Check to see that only valid editors are making changes. 
• https://swehb-staging-pri.msfc.nasa.gov/collector/pages.action?key=MSHSITE - displays MSHSITE pages with recent action. Check to see that only valid editors are making changes. 

If there are any error messages or unexpected results, investigate and fix. Some fixes may require help from IT group. 

When certain documents are used in the SWEHB, it is convenient to have a copy of the document in the Document Archive. When it is brought into the Archive it is decomposed into pieces that can be used in many places in the SWEHB. Usually, pieces are used in many pages throughout the a SWEHB version. It is easier to maintain document integrity by pulling in a piece with an Include-Page macro than to manually copy and paste it from the parent document. 

The process of copying a document into the Archive and disassembling it is described below. 

3.1 Selecting a Document to Archive

Only those documents that are static and have many pieces that will be quoted in the SWEHB in many places should be Archived. 

• Static means the document is in it's final, released form. It would not be very productive to archive many draft documents and then have to update all the places where the pieces are used throughout a SWEHB Version.  
• "many pieces" means there are lots of small items in a document that will be quoted in SWEHB pages. For example, NPR 7150.2 has several paragraphs that are used in other pages of the SWEHB. NASA-STD-8729.8B has many requirements and SA Tasks that are included in pages throughout the SWEHBVD version. 

The documents that are currently in the Document Archive include: 

• NASA-STD-8719.29 — NASA Technical Standard 8719.29, Approved: 2023-12-11 Basline - NASA Technical Requirements for Human-Rating. Full text of this NPR as taken from NODIS. Assembled from component pieces beneath this page. 
• NASA-STD-8739.8A — NASA Technical Standard 8739.8A - Approved 2020-06-10 - SOFTWARE ASSURANCE AND SOFTWARE SAFETY STANDARD. Full text of this NPR as taken from NODIS. Assembled from component pieces beneath this page. 
• NASA-STD-8739.8B — NASA Technical Standard 8739.8B - Approved 2004-27-08 - SOFTWARE ASSURANCE AND SOFTWARE SAFETY STANDARD. Full text of this NPR as taken from NODIS. Assembled from component pieces beneath this page. 
• NPR 7150.2C — NASA Procedural Requirements NPR 7150.2C - Approved 2019-08-02 - NASA Software Engineering Requirements. Full text of this NPR as taken from NODIS. Assembled from component pieces beneath this page. 
• NPR 7150.2D — NASA Procedural Requirements NPR 7150.2D - Approved 2022-03-08 - NASA Software Engineering Requirements. Full text of this NPR as taken from NODIS. Assembled from component pieces beneath this page. 

3.2 Disassembly and Reassembly of a Document

To replicate a document accurately, it will take some editing time. The process below should be done to a level that will yield usable document components. Breaking down a document too much will just be a waste of time if the pieces are never used elsewhere. 

In this example, the NPR 7150.2D is used. 

3.2.1 Top Level Document Container

The top level document container is a child page of Document Archive.

• It may be constructed by opening the Archive page and selecting the "Create Content" icon. This will force the new page to be created in the proper location in the pagetree. 
• Use the document ID as a page title - in this case, "NPR 7150.2D" was used
• Add an Excerpt at the top of the page and put in it the full ID of the document, Approved date, Title, and a comment regarding where the text comes from and how it is assembled. See the example below: 
  • NASA Procedural Requirements NPR 7150.2D - Approved 2022-03-08 - NASA Software Engineering Requirements. Full text of this NPR as taken from NODIS. Assembled from component pieces beneath this page. 
• From the source document, copy the full text and paste it into the new container. 
• Save your work 
• Check to see that:
  • the document is located under the Document Archive
  • the document is properly named (page title)
  • the excerpt for the new document appears on the Document Archive page
  • the document contains the copy of content from the original document 

3.2.2 Document Cleanup

This is the most time consuming part of adding a document to the archive. The document must be reformatted in Confluence to look like what it did in the source (usually NODIS, PDF or other server format).

In the example below, the cleanup of NPR 7150.2D is discussed. 

• At the top of the document page there is a 2 column table with the document name and other data about the document. 
• The Subject line is formatted in header 1 style
• Responsible Office is formatted in header 2 style
• Table of Contents is formatted in header 3 style
• Preface and its subheadings are all in paragraph style
• Chapter 1 is formatted in header 4 style

Moving down to the Preface styles like Header 1, 2, and 3 are used as appropriate to replicate the styles used in the original document. Where Notes are used in the original document, the Note macro is used to contain the note. Where there are diagrams and images, these may have been converted to attachments by Confluence. These will be reformatted later. 

Continue reformatting to the end of the document. 

Save and test the document to see that everything has been reformatted and looks close to the original source document. Fix formatting issues as much as you can at this point. 

3.2.3 Create Child Pages For Reusable Selections 

It will be necessary to go through the document and identify the pieces that will be used in other pages of the SWEHB. For each of those reusable pieces, they will need to be copied into child pages under the document page in the pagetree. They also need to be named so they are easy to find. Finally, the text in the document is replaced with an "Include Page" macro.  

3.2.3.1 Text Selection

The next section in the example that is considered a reusable portion of text is the paragraph "P.2 Applicability b". It is a piece of text that is referred to be other SWEHB pages. It needs to be pulled out into a child page and included in the document. 

• a child page under NPR 7150.2D was created and named 2D-P.2 APPLICABILITY b 
• The title of the child page is "2D-P.2 APPLICABILITY b" with
  • the prefix "2D" indicating the NPR 7150.2D origin, 
  • the name "P.2 APPLICABILITY b" indicating the source in the document where the content is taken
  • the content is the paragraph formatted so that when it is displayed in the NPR 7150.2D document it will look properly formatted (not like it was cut and pasted in). 
• replace the text in the document with an Include-Page macro pointing to the child page so that the document is complete. 

3.2.3.2 Table Selection

This example shows how a small tabular piece of information is converted into a child page. 

• a child page under NPR 7150.2D was created and named 2D-P.2 Fig 1 
• The title of the child page is "2D-P.2 Fig 1" with
  • the prefix "2D" indicating the NPR 7150.2D origin, 
  • the name "P.2 Fig 1" indicating the source in the document where the content is taken
  • the content is a table format listing software classifications it was built from a Panel macro with text added and formatted to look like the original document. 
• replace the text in the document with an Include-Page macro pointing to the child page so that the document is complete. 

3.2.3.3 Larger Table Selection

This example shows how a large table of information is converted into a child page. 

• a child page under NPR 7150.2D was created and named 2D Requirements Mapping Matrix 
• The title of the child page is "2D Requirements Mapping Matrix" with
  • the prefix "2D" indicating the NPR 7150.2D origin, 
  • the name "Requirements Mapping Matrix" indicating the source in the document where the content is taken
  • the content is a table format listing sections of the document, corresponding SWE numbers, Requirement Text, Technical Authority, ..."
• replace the text in the document with an Include-Page macro pointing to the child page so that the document is complete. 

The content replicates the table found in the original document. It uses header styles to display headers appropriately. 

3.2.3.4 Diagrams and Images

When a diagram or image is pasted from a source document, Confluence will automatically build an attachment and upload it to the document. If this diagram or image needs to be used as a child page, it will need to be added as an attachment to the child page, pulled into the child page, and then formatted in the child page before it can be used properly. 

3.2.4 Test Reassembled Document

Once all of the child pages are built and the text is replaced with the appropriate Include Page,

• The whole document must be compared to the original document to ensure that no parts are missing.
• Check to see that child pages appear in the proper locations. 
• Check to see that child pages are properly formatted to look like the originals. 

The same Include Page macros that brought child pages into the document will also be used to put those child pages into other SWEHB pages as necessary. 

3.3 Using A Piece Of A Document In A SWEHB Page

When you need to display a piece of a archived document in a SWEHB page, Use an "Include-Page" macro. 

For example, the NASA software Classification structure is a list of Classes of software taken from paragraph 2, Figure 1 of the NPR 7150.2D document. That table is in the 2D-P.2 Fig 1 child page under NPR 7150.2D in the Document Archive. It is shown in the note box below. 

The include page macro that was used to fill the note panel above is shown in the note panel below:

Release Process - Branch and Merge

Major updates and new pages should be done using the SWEHBDOC Branch and Merge Process. This will keep the new content away from the general population of Handbook users during the development process and give reviewers access to see and make comments before the content is released. The process below may be used during the review period and certainly at the time of the general release of the content to the general area of the Handbook. 

1. Review each watch email to identify changes.
2. Use the checklist in tab 1 of SWEHBDOC Content Style and Consistency to identify changes that need to be corrected. 
3. For each change requiring correction, edit the page and make the necessary correction. 
4. Save and review the page to ensure that all corrections were made properly. Fix any problems found. 
5. Discard watch emails once they have been reviewed and corrections are verified. 
6. Major updates or new pages should have a blog post prepared and published announcing the release of the update or new page. See SWEHBDOC Blogs In SWEHB for details on building and publishing Blog posts in SWEHB. 

Creating New Pages or Updating Pages - Checklist

When preparing either a New Page of just updating an existing page. The "Checklist for New SWEHB Page" should be copied and used to track all the actions necessary for the page. Using this checklist will help ensure that all the steps for the page are completed and nothing is missed. 

The "Checklist for SWEHB Page" should be stored under the page that it is used for. Example: be for the new Topic page "8.28 - Preparing and Evaluating Commercial Services Contracts" the checklist would be under it in the hierarchy and named: "Checklist for 8.28". The checklist would be used and updated to track the steps to create the new 8.28 page. Once the page is published and the blog posted, the checklist remains under the parent until a significant update is made to the page. When an update is necessary, a new update checklist is created to replace the new page checklist. 

• Checklist for New SWEHB Page
• Checklist for Updated SWEHB Page

As new versions of the NPR are released, new SWEHB versions are built and released. Each new release of the SWEHB is contained in its own space on the Confluence Server. At a high level, as each SWEHB version is built the following maintenance is performed on the new space:

This page is being built as the SWEHBVE space is being constructed. It contains a checklist of things that have been done and things that need to be done to bring the new SWEHB online. 

A Development page for the new version is being created in parallel with this new version. The development page is Dev Area For New Version Of SWEHB - SWEHBVE. It will be referenced in the checklist as necessary. 

10.1 New Versions of the SWEHBVE and NPR 7150.2E

As the new NPR is created, SWEs and Topics may be added or removed. Updates to pages in SWEHBVD will continue. The copying of most pages to SWEHBVE will be done late in September 2025 to ensure that duplicate work (updating to synchronize SWEHBVD and SWEHBVE) can be minimized.  

10.2 Checklist For Construction And Launch Of New SWEHBVE