1. To Do List

This is a quick list of PATs to be built, along with PATS that have been built. It is manually maintained. It includes a list of category codes and a full database report of existing PATs. 

As lists are discovered in the SWEHBVD, they will be listed here as candidates for becoming a PAT. 

Asset NameLocationsPAT Name / Resolution

Category Codes

Ada Programming Practices for SafetyTopic 6.7 - Checklist for Ada Programming Practices

SftySp, CodePrac, 

Analysis of Requirements Changes

SWE-053 - Manage Requirements Changes

Tabs 3, 7.4


ReqAn, 
Analysis of test results

SWE-068 - Evaluate Test Results , Tab 3


TstAn, 
Assurance of models, simulations, analysis tools

SWE-070 - Models, Simulations, Tools , Tab 7.4


ModSim, Tool, 

Auto-generated Code

SWE-146 - Auto-generated Source Code , Tab 3


Impl, Plng, 
C Programming Practices for Safety

SWE-060 - Coding Software , Tab 3, 7.4,

Topic 6.5 - Checklist for C Programming Practices


SftySp, CodePrac, 
C++ Programming Practices for SafetyTopic 6.6 - Checklist for C++ Programming Practices
CodePrac, 
Change Evaluation

SWE-080 - Track and Evaluate Changes, tab 3


ChgMgmt, 

Choosing Off-the Shelf (OTS) Software

Programming Checklists, Topic 6.4, SWE-027

  1. This PAT deals with Coding Practices and could be cross-linked to: 
    1. SWE-027 - Use of Commercial, Government, and Legacy Software - DONE
    2. Topic 7.03 - Acquisition Guidance - DONE
  2. Added to Activities
    1. A.04 Software Design - DONE
PAT-024 - Checklist for Choosing Off-The Shelf SoftwareComLegSW, CodePrac, OTS, 
Configuration Items for Consideration

SWE-079 - Develop CM Plan, Tab 3


CM, 
Confirmation of Delivery ActivitiesSWE-077 - Deliver Software Products SWE-077, Tab 7
RelDel, 
Considerations for Identifying SW Causes in a General SW-Centric HA

SWE-205 - Determination of Safety-Critical Software, Tab 7.4


SftySp, Haz, 
Considerations for identifying SW Hazard CausesSWE-205 - Determination of Safety-Critical Software, Tab 7.4
SftySp, Haz, 
Considerations When Using Interrupts

Source Code Analysis, Tab 4.

  1. This PAT deals with Coding and could be cross-linked to: 
    1. SWE-060 - Coding Software - DONE
    2. Topic 8.56 - Source Code Quality Analysis - DONE
  2. Added to Activities
    1. A.05 Software Implementation - DONE

PAT-032 - Considerations When Using Interrupts

SftySp, Impl, Haz, 
Design Considerations

SWE-058 - Detailed Design, Tab 3, 7.4


DesAn, 
Preparing for a SARB Checklist

SWE-143, Tab 3, 7.4, 

Topic 8.55 - Software Design Analysis, tab 2.4

  1. This PAT deals with Coding Practices and could be cross-linked to: 
    1. SWE-143 - Software Architecture Review - DONE
    2. 8.55 - Software Design Analysis - DONE
  2. Added to Activities
    1. A.04 Software Design - DONE
PAT-023 - Preparing for a SARB ChecklistDesAn, SADesign, 
Software Architecture Review Board Checklist 

SWE-143, Tab 3, 7.4; Topic 8.16 - Software Design Analysis. Tab 2.4.2

  1. This PAT deals with Coding Practices and could be cross-linked to: 
    1. SWE-143 - Software Architecture Review - DONE
    2. Topic 8.55 - Software Design Analysis - DONE
  2. Added to Activities
    1. A.04 Software Design - DONE
PAT-029 - Software Architecture Review Board ChecklistDesAn, SADESIGN, 
SARB Review Checklist with Guidance

SWE-143, Tab 3, 7.4; Topic 8.16 - Software Design Analysis. Tab 2.4.2

  1. This PAT deals with Architecture Practices and could be cross-linked to: 
    1. SWE-143 - Software Architecture Review - DONE
    2. Topic 8.55 - Software Design Analysis - DONE
  2. Added to Activities
    1. A.04 Software Design - DONE

PAT-030 - SARB Review Checklist with Guidance

DesAn, SADESIGN, 
Critical Design Analysis Checklist

Topic 8.16 - Software Design Analysis. Tab 2.4.3, Tab 3.4

  1. This PAT deals with Coding Practices and could be cross-linked to: 
    1. SWE-060 - Coding Software - DONE
    2. Topic 8.55 - Software Design Analysis - DONE
  2. Added to Activities
    1. A.04 Software Design - DONE
PAT-031 - Critical Design Analysis ChecklistDesAn, SADESIGN, 
Design Quality Attribute SpreadsheetTopic 7.07 - Software Architecture Description
DesAn, 
FORTRAN Programming Practices for SafetyTopic 6.8 - Checklist for Fortran Programming Practices
SftySp, CodePrac, 
General Good Programming Practices for SafetyTopic 6.10 - Checklist for General Good Programming Practices
SftySp, CodePrac, 
Generic (Non-Language Specific) Programming Practices for SafetyTopic 6.9 - Checklist for Generic (Non-Language-Specific) Programming Practices
SftySp, CodePrac, 
Hazard ReportsSWE-205 - Determination of Safety-Critical Software, Tab 7.4
SftySp, 
Maintenance, Operations, Retirement Planning

SWE-075 - Plan Operations, Maintenance, Retirement, Tab 3, (7.4 -Retirement)


MaOps, 
Functional Requirements ChecklistTopic 7.10 - Peer Review and Inspections Including Checklists, Tab 4,PAT-003 - Functional Requirements ChecklistReqAn, 
Safety Requirements Analysis ChecklistTopic 8.16 - SA Products- Software Requirements Analysis, tab 3,PAT-004 - Safety Requirements Analysis ChecklistReqAn, PRvw,
Software Component Design Analysis Checklist 

Other possible locations:


PAT-005 - Software Component Design Analysis Checklist DesAn,
Design Practices for Safety

Topic 6.1 - Design for Safety Checklist, Topic 8.55 - Software Design Analysis,

Other possible locations:

  • SWE-058 - Detailed Design  - DONE
  • SWE-205 - Determination of Safety-Critical Software  - DONE
  • 8.55 - Software Design Analysis - DONE
  • A.02 Software Assurance and Software Safety - DONE
  • A.04 Software Design - DONE
PAT-006 - Design Practices for Safety DesAn,
Checklist for General Software Safety Requirements

Topic 6.2 - Checklist for General Software Safety Requirements,

Other possible locations:

  • Topic 8.54 - Software Requirements Analysis, section 2, 
  • Topic 8.58 - Software Safety and Hazard Analysis, section 2,
  • SWE-051 - Software Requirements Analysis, section 3,
  • SWE-184 - Software-related Constraints and Assumptions , section 3
PAT-007 - Checklist for General Software Safety RequirementsReqAn, SftySp,
Safety Considerations for Design Peer Reviews Checklist

Software Design Analysis, tab 3.2,

Other possible locations:

  1. This PAT deals with Safety could be cross-linked to: 
    1. SWE-058 - Detailed Design - Tab 7.4 talks about Safety and Design
    2. 8.55 - Software Design Analysis - Topic calls out this PAT specifically
  2. Added to Activities
    1. A.02 Software Assurance and Software Safety
    2. A.04 Software Design
    3. A.10 Software Peer Reviews and Inspections
PAT-008 - Safety Considerations for Design Peer Reviews ChecklistPRvw, SftySp, DesAn,
Software Safety Process AuditTopic 8.17 - Software Safety Audit Checklists, tab 2Reserved - PAT-009 - Software Safety Process AuditAudCK, SftySp, ?
Software Safety Activities for Internal AuditTopic 8.17 - Software Safety Audit Checklists, tab 3

Reserved - PAT-010 - Software Safety Activities for Internal Audit

AudCK, SftySp, ?
Objective Evidence Confirmations Checklist

Topic 8.16, Objective Evidence, Tab 3

  1. This PAT deals with Coding Practices and could be cross-linked to: 
    1. See Related SWEs
    2. See Related SM
  2. Added to Activities
    1. See Related Activities 

PAT-033 - TASKS NEEDING OBJECTIVE EVIDENCE



AudCK
ISO 27001-2013 Audit ChecklistTopic 8.16 - SA Products, 5.2.2?Reserved - PAT-011 - ISO 27001-2013 Audit ChecklistAudCK, SftySp, ?
Detection of Adversarial Actions

SWE-210, tab 3

  1. This PAT deals with Safety could be cross-linked to: 
    1. SWE-210 - Detection of Adversarial Actions - Tab 3 - DONE
    2. SWE-154 - Identify Security Risks
    3. SWE-157 - Protect Against Unauthorized Access
    4. Topic 8.04 - Additional Requirements Considerations for Use with Safety-Critical Software
  2. Added to Activities
    1. A.01 Software Life Cycle Planning - A.01.08 Cybersecurity
PAT-012 - Detection of Adversarial Actions - Retired
Software Requirements Checklist

Topic 7.10, tab 4.1,

  1. This PAT deals with Safety could be cross-linked to: 
    1. Topic 7.10 - Peer Review and Inspections Including Checklists - DONE
    2. Topic 8.54 - Software Requirements Analysis
    3. SWE-050 - Software Requirements
    4. SWE-051 - Software Requirements Analysis
  2. Added to Activities
    1. A.03 Software Requirements
    2. A.10 Software Peer Reviews and Inspections
PAT-013 - Software Requirements ChecklistPRvw, ReqAn,
Architecture Design Checklist

Topic 7.10, tab 4.3,

  1. This PAT deals with Safety could be cross-linked to: 
    1. SWE-057 - Software Architecture
    2. Topic 8.55 - Software Design Analysis
  2. Added to Activities
    1. A.04 Software Design
    2. A.10 Software Peer Reviews and Inspections
PAT-014 - Architecture Design ChecklistPRvw, ReqAn,
Detailed Design Checklist

Topic 7.10, tab 4.4,

  1. This PAT deals with Safety could be cross-linked to: 
    1. SWE-058 - Detailed Design - DONE
    2. Topic 8.55 - Software Design Analysis - DONE
  2. Added to Activities
    1. A.04 Software Design
    2. A.10 Software Peer Reviews and Inspections
PAT-015 - Detailed Design ChecklistPRvw, ReqAn,
Functional Design Checklist

Topic 7.10, tab 4.5,

  1. This PAT deals with Safety could be cross-linked to: 
    1. SWE-058 - Detailed Design
    2. Topic 8.55 - Software Design Analysis
  2. Added to Activities
    1. A.04 Software Design
    2. A.10 Software Peer Reviews and Inspections
PAT-016 - Functional Design ChecklistPRvw, ReqAn,
C Code Inspection Checklist

Topic 7.10, tab 4.6,

  1. This PAT deals with Safety could be cross-linked to: 
    1. SWE-060 - Coding Software - in tab 3
    2. Topic 8.56 - Source Code Quality Analysis - in tab 3
    3. Topic 7.10 - Peer Review and Inspections Including Checklists - DONE
  2. Added to Activities
    1. A.05 Software Implementation- DONE 
    2. A.10 Software Peer Reviews and Inspections - DONE
PAT-017 - C Code Inspection ChecklistPRvw,
Test Plan Checklist

Topic 7.10, tab 4.7,

  1. This PAT deals with testing and could be cross-linked to: 
    1. SWE-065 - Test Plan, Procedures, Reports - tab 3
    2. Topic 8.57 - Testing Analysis  - tab 2
    3. Topic 7.10 - Peer Review and Inspections Including Checklists - DONE
  2. Added to Activities
    1. A.06 Software Testing - DONE
    2. A.10 Software Peer Reviews and Inspections - DONE
PAT-018 - Test Plan Checklist

PRvw, (TstDoc)

Test Procedure Checklist

Topic 7.10, tab 4.8,

  1. This PAT deals with Testing and could be cross-linked to: 
    1. SWE-065 - Test Plan, Procedures, Reports - tab 3.2
    2. Topic 8.57 - Testing Analysis - Tab 3.2 - DONE
    3. Topic 7.10 - Peer Review and Inspections Including Checklists - DONE
    4. Topic 5.14 - Test - Software Test Procedures - tab 3.5 - DONE
  2. Added to Activities
    1. A.06 Software Testing - DONE
    2. A.10 Software Peer Reviews and Inspections - DONE
PAT-019 - Test Procedure ChecklistPRvw, (TstDoc)
Test Review Checklist for Test Leads 

SWE-066, tab 3.3,

Will also be in 8.16, Testing Analysis, TBD tab


  1. This PAT deals with Testing Practices and could be cross-linked to: 
    1. SWE-066 - Perform Testing - DONE
    2. 8.57 - Testing Analysis - DONE
  2. Added to Activities
    1. A.06 Software Testing - DONE
PAT-026 - Test Review Checklist For Test Leads(TstDoc), SATest, 
Examples of Interface Problems

Topic 8.16 - SA Products, Software Design Analysis, tab 3.3, Item 6,

  1. This PAT deals with Testing and could be cross-linked to: 
    1. SWE-058 - Detailed Design - tab 3.4
    2. Topic 5.02 - IDD - Interface Design Description - tab 3.1
  2. Added to Activities
    1. A.04 Software Design - DONE
PAT-020 - Examples of Interface ProblemsDesAn,
SADESIGN Checklist

Topic 8.16 - SA Products- Software Design Analysis, tab 2,

  1. This PAT deals with Testing and could be cross-linked to: 
    1. SWE-058 - Detailed Design - tab 3.4
    2. Topic 5.13 - SwDD - Software Design Description - Tab 3.4
    3. Topic 8.55 - Software Design Analysis - tab 2.1 - DONE
  2. Added to Activities
    1. A.04 Software Design - DONE
PAT-021 - SADESIGN ChecklistSADESIGN, DesAn,
Programming Practices Checklist

Topic 8.16 - SA Products- Source Code Quality Analysis, tab 2.2,

  1. This PAT deals with Coding Practices and could be cross-linked to: 
    1. SWE-061 - Coding Standards - DONE
    2. SWE-185 - Secure Coding Standards Verification - DONE
    3. Topic 8.56 - Source Code Quality Analysis - tab 2.2 - DONE
  2. Added to Activities
    1. A.05 Software Implementation - DONE
PAT-022 - Programming Practices ChecklistCodePrac,
Peer Review Best PracticesSWE-087 - Software Peer Reviews and Inspections for Requirements, Plans, Design, Code, and Test Procedures, Tab 3

PRvw,

Potential Software Hazard CausesTopic 8.21 - Software Hazard Causes, Tab 1
SftySp, Haz, 
Release Package ActivitiesSWE-085 - Release Management, Tab 3
RelDel, 
Requirements Contents ChecklistTopic 8.16 - SA Products: Software Req. Analysis, tab 2
(WrtReq)
Requirements Development/AssessmentSWE-050 - Software Requirements SWE-050, Tab 7.4
ReqAn, 
Requirements Development/Assessment (SRS contents)SWE-050 - Software Requirements, Tab 7.4
ReqAn, 
Requirements Editorial ChecklistTopic 8.16 - SA Products: Software Req. Analysis, tab 2
EdConv, 
Requirements Quality ChecklistTopic 8.16 - SA Products: Software Req. Analysis, tab 2
ReqAn, 
SA Non-Conformance ActivitiesSWE-201 - Software Non-Conformances, Tab 7.4
NonCon, 
SAANALYSIS (Requirements Analysis Checklist)

SWE-050 - Software Requirements, tab 7.4,

SWE-051 - Software Requirements Analysis, Tab 7.4, Topic 8.54 - Software Requirements Analysis, tab 2

  1. This PAT deals with Requirements Practices and could be cross-linked to: 
    1. SWE-050 - Software Requirements - DONE 
    2. SWE-051 - Software Requirements Analysis - DONE
    3. Topic 8.54 - Software Requirements Analysis - DONE
  2. Added to Activities
    1. A.03 Software Requirements - DONE
PAT-034 - SA Requirements Analysis ChecklistReqAn, 
Selection of Commercial & Legacy SWSWE-027 - Use of Commercial, Government, and Legacy Software, Tab 3.5
ComLegSW
Selection of Real Time Operating System (RTOS)

SWE-027 - Use of Commercial, Government, and Legacy Software, Tab 3.1, Programming Checklists, 
Topic 6.3 - Checklist for Choosing a Real Time Operating System (RTOS)

  1. This PAT deals with Coding Practices and could be cross-linked to: 
    1. SWE-027 - Use of Commercial, Government, and Legacy Software - DONE
    2. Topic 6.3 - Checklist for Choosing a Real Time Operating System (RTOS) - DONE
  2. Added to Activities
    1. A.01 Software Life Cycle Planning - DONE
PAT-025 - Checklist for Choosing a Real Time Operating System (RTOS)ComLegSW, CodePrac, Plng, ComSW, OTS
Software Component Safety Design ChecklistSoftware  Design Analysis, Tab 3
DesAn, SftySp, 
Software Safety-Specific Activities in Each PhaseTopic 8.20 - Safety Specific Activities in Each Phase, Tab 1
SftySp, 
Test Documentation ChangesSWE-065 - Test Plan, Procedures, Reports
TstDoc, 
Test Practices (incl. safety)SWE-066 - Perform Testing, Tab 3,
TstAn, 
Unit test guidanceSWE-186 - Unit Test Repeatability, Tabs 3, 7.4 Repeated in SWE-062
TstDoc, 
Updates to Test DocumentsSWE-071 - Update Test Plans and Procedures, Tabs, 3, 7.4
TstAn, 
Risk Management in Planning PhaseTopic 7.19 - Software Risk Management Checklists, tab 2
RskMgmt, 
Risk Management in Requirements  PhaseTopic 7.19 - Software Risk Management Checklists, tab 3
RskMgmt, 
Risk Management in Design PhaseTopic 7.19 - Software Risk Management Checklists, tab 4
RskMgmt, 
Risk Management in Implementation PhaseTopic 7.19 - Software Risk Management Checklists, tab 5
RskMgmt, 
Risk Management in Test PhaseTopic 7.19 - Software Risk Management Checklists, tab 6
RskMgmt, 
Risk Management in Release PhaseTopic 7.19 - Software Risk Management Checklists, tab 7
RskMgmt, 
Risk Management in Ops and Maint PhaseTopic 7.19 - Software Risk Management Checklists, tab 8
RskMgmt, 
Risk Management Other Software RisksTopic 7.19 - Software Risk Management Checklists, tab 9
RskMgmt, 
Requirements Mapping and Compliance Matrix - Appendix C.

Topic 7.16 

  1. This PAT deals with Coding Practices and could be cross-linked to: 
    1. SWE-125 - Requirements Compliance Matrix - DONE
    2. Topic 7.16 - Appendix C. Requirements Mapping and Compliance Matrix - DONE
  2. Added to Activities
    1. A.01 Software Life Cycle Planning - tab 07 - Classification, Tailoring and Waivers  - DONE

PAT-028 - NPR 7150.2D Compliance Matrix

ReqAn, 
Additional Requirements Considerations for Use with Safety-Critical SoftwareTopic 8.04 - Additional Requirements Considerations for Use with Safety-Critical Software, steps 3 & 4
SftySp, 
SFMEA Components WorksheetTopic 8.05 - SW Failure Modes and Effects Analysis, tab 10.2
Tool, 
SFMEA WorksheetTopic 8.05 - SW Failure Modes and Effects Analysis, tab 10.1
Tool, 
SFMEA Data TableTopic 8.05 - SW Failure Modes and Effects Analysis, tab 10.3
Tool, 
SFMEA Events TableTopic 8.05 - SW Failure Modes and Effects Analysis, tab 10.4
Tool, 
SARP SA Tasking Checklist Tool.xlsmTopic 8.15 - SA Tasking Checklist Tool, tab 1 - attachment
SATask,
Tasks Needing Objective EvidenceObjective Evidence, tab 3

Security Plan contentSoftware Assurance Plan, tab 1Not a NASA document
TEST REVIEW CHECKLIST FOR REVIEW TEAMS

SWE-066 - Perform Testing, tab 7.4.1, 

  1. This PAT deals with Testing Practices and could be cross-linked to: 
    1. SWE-066 - Perform Testing - tab 7.4.1 - DONE
    2. Topic 8.57 - Testing Analysis - tab 4 - DONE
  2. Added to Activities
    1. A.06 Software Testing - DONE
PAT-027 - Test Review Checklist For Review Teams(TstDoc)
Checklist for Auditing the Risk Management ProcessSWE-086 - Continuous Risk Management, tab 7.4.1
RskMgmt

Other PAT Items


#ItemDescriptionCheck / Fix Status
1Uniform naming of Screenshots: SS1, SS2, etc.Affects all PATsDone 10/17/2022 
2

Uniform naming of PATs in panels: 

  • include PAT number in panel title
Affects all PATsDone 10/17/2022 
3

Build checklist for PATS: 

  • Building a new PAT
  • Updating a PAT
  • Building new PAT reports
  • Building new Category reports

Applies to all PATs

Building a new PAT

Update a PAT Checklist

Done 10/17/2022 

2. Category Codes

This is a list of the Category codes currently in use. Links take you to a report of PATs having the category code.

To edit this list go to PAT Categories. 

6/20 - From Fred - I added a few additional category suggestions below based on the descriptions I found in the PAT Categories page. Additionally, I put the codes up in the ToDo list so I can add them to the PAT Database entry once it is created. You may find that more categories are needed, also, more codes may be needed. Just add them in red text and I'll take the necessary action when the PATs are created. 


Additional Potential Categories - Add new suggested Category Reports in red text below


3. PAT Database

Full PAT Database. 

4. Reorganization Items

To Do list of ideas for reorganization of SWEHBVD. 

Item NumberDescriptionActions

Comments

1Deploy Advanced Tables Macro to long tables

To Do: 

Implemented Sticky Headers on some pages. SWEHBDOC Sticky Headers

2Complete deployment of Activities



5. Consistency Items


#VariantsPreferred / Corrected WordsCheck / Fix Status

life cycle, lifecycle, life-cycle

life cycle

FDH - 224 pages done 7/21/2022


safety critical, safety-critical

safety-critical

FDH - 213 pages done 7/26/2022


non-conformance, nonconformance

non-conformance

FDH - 134 pages done 7/26/2022


top level, top-level

top-level

FDH - 24 pages done 7/26/2022


flowed-down, flowed down

Flow down

FDH - 71 pages done 7/27/2022


Software Assurance Plan, SA Plan, SAP

Ask Tim



NPR 2810.1 Security of Information Technology

NPR 2810.1 Security of Information and Information Systems

FDH - 10 pages 7/27/2022


NIST SP 800-40 Creating a Patch and Vulnerability Management Program

NIST SP 800-40  Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology

FDH - SWEREF-337 added 8/8/2022

changed in NASA-STD-8739.8B


IEEE Standard Measures of the Software Aspects of Dependability, 8 November 2005

IEEE Standard Dictionary of Measures of the Software Aspects of Dependability, 8 November 2005

Added SWEREF-367 - 

Not be changed in NASA-STD-8739.8B


CMMI-Dev 2.0, CMMI-Dev 1.3

  • SWE-032 contains 1.3 in Notes

CMMI-Dev 2.0 (for current version of Handbook only)

FDH - 1 page
8/8/2022

Adapted from SWEHBDOC Consistency of Language.