Preventing events “…that could not only hurt someone, but hurt someone you know and … could have a dramatic consequence on all of us “ SO’K Mission Success Starts With Safety "Mission success stands on the foundation of our unwavering commitment to safety" Administrator Sean O'Keefe January 2003 Office of Safety and Mission Assurance Standards Status Engineering Standards Working Group Glenn Research Center 5 – 6 October 2004 Wil Harkins Office of Safety and Mission Assurance (1)

Mission Success Starts With Safety 2 Agenda Standards Updates and Changes Overall Requirements Documents Changes – NASA Internal Rules Review – OSMA Implementation of Rules Review and impact on OSMA Standards Safety and Mission Assurance Requirements Tracking System (SMARTS)

Mission Success Starts With Safety 3 Standards Updates and Changes NASA-Standard , Software Assurance – Released July 2004 – Replaces NASA-STD – This standard provides: Minimum required software assurance procedures for software life cycle The acquirer and provider requirements for software engineering activities Basic procedures for establishing, operating, and maintaining a software assurance program Specific requirements for overall software assurance and its disciplines of software quality, software reliability, software safety, software verification and validation, and independent verification and validation – Roll-out in conjunction with release of NPR 7150 Draft 1, Software Engineering Requirements planned for Fall 2004 – Establishing a compliance transition period through 2008 for this document.

Mission Success Starts With Safety 4 Standards Updates and Changes NASA-Guidebook , Software Safety Guidebook – Released March 2004 – Replaces NASA-GB – Companion document to NASA-Standard , Software Safety – This standard (guidebook) provides: An overview of general software safety and software engineering practices The means to scope and tailor the software safety and software engineering activities Analyses, methods and guidance for application during each phase of the software life cycle Development approaches, safety analyses, and testing methodologies that lead to improved safety in software

Mission Success Starts With Safety 5 Standards Updates and Changes NASA-Standard B, Software Safety – Released July 2004, Change 1 released July 2004 – This standard provides: Requirements to implement a systematic approach to software safety as an integral part of the overall system safety program, software development, and software assurance processes Descriptions of the activities necessary to ensure that safety is designed into software and maintained throughout the software and system lifecycle – Roll-out in conjunction with release of NPR 7150 Draft 1, Software Engineering Requirements planned for Fall 2004 – Establishing a compliance transition period through 2008 for this document.

Mission Success Starts With Safety 6 NASA Internal Rules Review Initiated December 2003 at HQ, extended to Centers July 2004 Covers all Internal Requirements Documents – Major emphasis has been on Directives – Standards also included within scope “All” Agency Directives have been updated to contain only requirements, no guidance

Mission Success Starts With Safety 7 NASA Internal Rules Review Internal Rules Review Team working to establish an “overarching” requirements NPD – Establish basic requirements for all internal requirements documents (Directives, Standards, Plans, Manuals, Work Instructions, Agreements) All NASA internal requirements documents must: (1) Support the fulfillment of NASA’s vision, mission, or external mandates. (2) Be developed and controlled by a documented process. (3) Be clearly labeled as a requirement. (4) Be made available to the people who use them. (5) Be verified for compliance. (6) Be current. – Establish precedence among document types

Mission Success Starts With Safety 8 OSMA Implementation of Rules Review and impact on OSMA Standards NASA Administrator through Internal Rules Review has mandated that guidance cannot appear in Directives – As OSMA updates directives expect that some “old” guidance material will now migrate to NASA Standards (Guidebooks) Internal Rules Review is considering requirements that would eliminate system requirements from Directives – As OSMA updates directives, we will probably move system requirements out of directives into standards. As part of restructuring OSMA directives, we will probably attempt to remove roles and responsibilities from NASA- Standards and incorporate these into appropriate directives. OSMA is tracking individual directives requirements using SMARTS – will be adding individual NASA-Standards requirements to SMARTS as well

Mission Success Starts With Safety 9 SMARTS is being implemented to make it easier to understand, track, and implement NASA’s SMA requirements. SMARTS is an internet-based information system designed to: – Collect all SMA requirements at the Agency and Center levels and from appropriate sources external to NASA – Provide a means to filter, collect, search, and sort requirements across document types into “personalized virtual” documents to meet specific needs Whole documents/Partial Documents Requirements lists Compliance Verification Documentation – Support the data associated with the verification of compliance to SMA requirements – Trace links to SMA requirements to improve effectiveness and limit duplication of requirements What is the Safety and Mission Assurance Requirements Tracking System (SMARTS)?

Mission Success Starts With Safety documents: – 18 NPDs – 14 NPRs – OSMA Functional Leadership Plan – 3 NASA-STDs – 4 Presidential Decision Directives – 1 Executive Order – NASA FAR Supplement SMA sections – 29 CFR What is Currently in SMARTS?

Mission Success Starts With Safety 11 How much of the document is in SMARTS (at a minimum)? – SMA Owned documents: The entire requirements sections of the document, preface, core chapters and appendix titles. Requirements contained in appendices are also included. – Non-SMA owned NASA documents contain: SMA portions of core document and SMA appendix titles. – Non-NASA documents: SMA portions and unclassified excerpts. All paragraph text is stored exactly as stored in NODIS (or other master library) except: – ‘Tags’ have been added to the beginning of subsection paragraphs so that requirements read as a whole thought. For example, ‘tags’ like: “The ____ shall –” have been added to bulleted lists so the data is more readable than the standalone bullet. – Some documents captured early in the process use “AA/SMA” and “EAA” abbreviations when the master document may have the text spelled out. – SMARTS Requirement ID Numbers may appear within SMARTS before they appear in the Master Library (NODIS, etc). What is Currently in SMARTS?

Mission Success Starts With Safety 12 What Functionality is currently in SMARTS? Filter, Search, Sort on SMA Requirements to develop ‘virtual’ SMA requirements documents. Create Requirement Lists Printout: – Whole or parts of single documents, – ‘Virtual’ documents, and requirements lists – Compliance Verification Responsibility Matrices and Audit Assessment Reports (which can be ‘tailored’ with sorts/searches)

Mission Success Starts With Safety 13 Sample Actor Report

Mission Success Starts With Safety 14 Sample Compliance Verification Report