• There are no items in your cart
We noticed you’re not on the correct regional site. Switch to our AMERICAS site for the best experience.
Dismiss alert

NASA STD 8719.13B : 2004

Superseded

Superseded

A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.

View Superseded by
superseded

A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.

**DUPLICATE RECORD**

Superseded date

23-07-2013

Published date

01-01-2004

1 SCOPE
  1.1 Purpose
  1.2 Applicability
  1.3 Assumptions
  1.4 Guide to this Standard
       1.4.1 Requirements
       1.4.2 Software Safety Personnel
       1.4.3 Plans and Documents
2 RELATED DOCUMENTATION
  2.1 Applicable Documents
       2.1.1 Government documents
       2.1.2 Non-government documents
  2.2 Reference Documents
       2.2.1 Government documents
       2.2.2 Non-government documents
3 DEFINITIONS AND ACRONYMS
  3.1 Definitions used in this Standard
  3.2 Acronyms used in this Standard
4 SAFETY-CRITICAL SOFTWARE DETERMINATION
  4.1 Determination Process
  4.2 Software as Part of System Safety Analysis
5 SOFTWARE SAFETY MANAGEMENT
  5.1 Organization and Responsibilities
       5.1.1 Center Safety and Mission Assurance
             Organization
       5.1.2 Program/Project/Facility Management
             Responsibilities
       5.1.3 Software Safety Personnel
       5.1.4 Other Personnel Responsibilities
  5.2 Software Safety Planning
  5.3 Personnel Qualifications and Training
  5.4 Resources
  5.5 Software Life Cycles
  5.6 Documentation Requirements
  5.7 Traceability
  5.8 Discrepancy and Problem Reporting and Tracking
  5.9 Software Configuration Management Activities
  5.10 Software Assurance Activities
  5.11 Tool Support and Approval
  5.12 Off-the-shelf Software (COTS/GOTS/OTS)
  5.13 Contract Management
  5.14 Certification Process
  5.15 Waivers/Deviations
  5.16 Security
6 SOFTWARE DEVELOPMENT AND SAFETY ANALYSES
  6.1 Software Safety Requirements and Analysis
  6.2 Software Design and Safety Analysis
  6.3 Software Implementation and Safety Analysis
  6.4 Software Test and Safety Analysis
7 OPERATIONAL USE OF THE SOFTWARE
Appendix A. Example - Tailoring Activities to Implement
            Standard
Appendix B. Requirements Compliance Matrix

Describes the software safety activities, data, and documentation necessary for the acquisition or development of software in a safety-critical system.

DevelopmentNote
This is a duplicate record, which will be removed from the database after three months. (05/2013)
DocumentType
Standard
PublisherName
National Aeronautics and Space Administration
Status
Superseded
SupersededBy

NASA STD 8709.22 : 2010 SAFETY AND MISSION ASSURANCE ACRONYMS, ABBREVIATIONS, AND DEFINITIONS
NASA KSC STD E 0001 : 2008 DESIGN OF ELECTRICAL CONTROL AND MONITORING SYSTEMS, EQUIPMENT (GSE), AND PANELS, STANDARD FOR
NASA STD 8719.24 : 2011 NASA EXPENDABLE LAUNCH VEHICLE PAYLOAD SAFETY REQUIREMENTS
NASA-STD-8739.8A : 2020 SOFTWARE ASSURANCE AND SOFTWARE SAFETY STANDARD
NASA STD 8739.8 : 2004 SOFTWARE ASSURANCE STANDARD

RTCA DO 178 : C2011 SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEMS AND EQUIPMENT CERTIFICATION
IEEE 610.12-1990 IEEE Standard Glossary of Software Engineering Terminology
ISO 8402:1994 Quality management and quality assurance — Vocabulary
NASA GB 8719.13 : 0 NASA SOFTWARE SAFETY GUIDEBOOK
IEEE 12207.0-1996 IEEE/EIA Standard - Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology -- Software Life Cycle Processes
NASA STD 8739.8 : 2004 SOFTWARE ASSURANCE STANDARD

View more information
Sorry this product is not available in your region.

Access your standards online with a subscription

Features

  • Simple online access to standards, technical information and regulations.

  • Critical updates of standards and customisable alerts and notifications.

  • Multi-user online standards collection: secure, flexible and cost effective.