Your free source for specifications, standards, and handbooks
NASA - NPD PUBS
NPD 2820.1, NASA Software Policies
The following policies cover software created and acquired by or for NASA and also cover Government off-the-shelf (GOTS) software and commercial off-the-shelf (COTS) software when included in a NASA system. These policies shall be applied consistent with sound engineering and risk management practices as determined by cost, size, complexity, life span, risk, and consequences of failure. NASA policy regarding software management, engineering, and assurance is to accomplish the following: a. Manage, engineer, and assure software in accordance with common industry standards, processes, and best practices; document the use of standards, processes, and best practices; and tailor standards, processes, and best practices to the development or acquisition. b. Implement and integrate software engineering processes and practices with other system development and program/project processes and practices. Develop a plan for acquisition and life-cycle management of the software as part of the program/project plan. This plan should be developed prior to selection of the provider and should address, at a minimum, design tradeoff management, risk management, requirements management, software project planning, project tracking and oversight, software product engineering, subcontract management, configuration management, quality assurance, and peer review. c. Develop and maintain a total estimated software life-cycle cost and, where appropriate, perform tradeoff studies which address use of COTS and GOTS software versus created software to satisfy requirements before software is created or acquired. d. Demonstrate that the provider of software to be developed has proven organizational capabilities and experience to deliver quality software on time and within budget; require acceptable evidence of the entity`s software management, engineering, and assurance standards, processes, and practices to produce quality software. Examples of current acceptable evidence include an independent assessment of a software Capability Maturity Model (CMM) rating of 3 or above. The provider shall develop a plan to manage software throughout the program/project life cycle before the software requirements specification is complete and software design and coding takes place. The plan shall address items required in 1.b. e. Document software as to its form and function and verify that such software performs the functions claimed on the platform(s) for which it is
Ident. Num:
NASA NPD 2820.1
The following policies cover software created and acquired by or for NASA and also cover Government off-the-shelf (GOTS) software and commercial off-the-shelf (COTS) software when included in a NASA system. These policies shall be applied consistent with sound engineering and risk management practices as determined by cost, size, complexity, life span, risk, and consequences of failure. NASA policy regarding software management, engineering, and assurance is to accomplish the following: a. Manage, engineer, and assure software in accordance with common industry standards, processes, and best practices; document the use of standards, processes, and best practices; and tailor standards, processes, and best practices to the development or acquisition. b. Implement and integrate software engineering processes and practices with other system development and program/project processes and practices. Develop a plan for acquisition and life-cycle management of the software as part of the program/project plan. This plan should be developed prior to selection of the provider and should address, at a minimum, design tradeoff management, risk management, requirements management, software project planning, project tracking and oversight, software product engineering, subcontract management, configuration management, quality assurance, and peer review. c. Develop and maintain a total estimated software life-cycle cost and, where appropriate, perform tradeoff studies which address use of COTS and GOTS software versus created software to satisfy requirements before software is created or acquired. d. Demonstrate that the provider of software to be developed has proven organizational capabilities and experience to deliver quality software on time and within budget; require acceptable evidence of the entity`s software management, engineering, and assurance standards, processes, and practices to produce quality software. Examples of current acceptable evidence include an independent assessment of a software Capability Maturity Model (CMM) rating of 3 or above. The provider shall develop a plan to manage software throughout the program/project life cycle before the software requirements specification is complete and software design and coding takes place. The plan shall address items required in 1.b. e. Document software as to its form and function and verify that such software performs the functions claimed on the platform(s) for which it is
NPD 2820.1A, NASA Software Policies (Revalidated 5/29/04)
The following policies cover software created and acquired by or for NASA and also cover Government off-the-shelf (GOTS) software and commercial off-the-shelf (COTS) software when included in a NASA system. These policies shall be applied consistent with sound engineering and risk management practices as determined by cost, size, complexity, life span, risk, and consequences of failure.
Ident. Num:
NPD 2820.1A
Rev. Num:
A
The following policies cover software created and acquired by or for NASA and also cover Government off-the-shelf (GOTS) software and commercial off-the-shelf (COTS) software when included in a NASA system. These policies shall be applied consistent with sound engineering and risk management practices as determined by cost, size, complexity, life span, risk, and consequences of failure.
NPD 8070.6B, Technical Standards
NPD 8070.6B, Technical Standards. This NPD establishes NASA policy and organizational responsibilities for the development, management, and use of technical standards and associated products (specifications, guidelines, and handbooks) on NASA programs, projects, and functional activities.
Ident. Num:
NPD 8070.6
Rev. Num:
B
NPD 8070.6B, Technical Standards. This NPD establishes NASA policy and organizational responsibilities for the development, management, and use of technical standards and associated products (specifications, guidelines, and handbooks) on NASA programs, projects, and functional activities.
NPD 8710-3, NASA POLICY LIMITING ORBITAL DEBRIS GENERATION
NPD 8710-3, NASA POLICY LIMITING ORBITAL DEBRIS GENERATION. It is NASA policy to limit the generation of orbital debris (OD), consistent with mission requirements and cost effectiveness (Requirement 6025). To accomplish this policy, NASA will -a. Conduct formal OD assessments in accordance with NSS 1740.14, Guidelines and Assessment Procedures for Limiting Orbital Debris, on each space program/project to determine its potential to generate OD during nominal operations (Requirement 6001). b. Design for safe disposal of spacecraft and launch vehicles at end of mission in accordance with NSS 1740.14, Guidelines and Assessment Procedures for Limiting Orbital Debris, and JSC-27862, Postmission Disposal of Upper Stages (Requirement 6026). c. Provide timely notification to, and coordination with, other appropriate government entities concerning the proposed reentry of NASA spacecraft or their rocket bodies from Earth orbit (Requirement 6027). d. Promote the adoption of international policies, standards, and practices to minimize OD and its associated risks, and the exchange of information on OD research, modeling, and mitigation techniques in the international community (Requirement 6028).
Ident. Num:
NPD 8710-3
Rev. Num:
B
NPD 8710-3, NASA POLICY LIMITING ORBITAL DEBRIS GENERATION. It is NASA policy to limit the generation of orbital debris (OD), consistent with mission requirements and cost effectiveness (Requirement 6025). To accomplish this policy, NASA will -a. Conduct formal OD assessments in accordance with NSS 1740.14, Guidelines and Assessment Procedures for Limiting Orbital Debris, on each space program/project to determine its potential to generate OD during nominal operations (Requirement 6001). b. Design for safe disposal of spacecraft and launch vehicles at end of mission in accordance with NSS 1740.14, Guidelines and Assessment Procedures for Limiting Orbital Debris, and JSC-27862, Postmission Disposal of Upper Stages (Requirement 6026). c. Provide timely notification to, and coordination with, other appropriate government entities concerning the proposed reentry of NASA spacecraft or their rocket bodies from Earth orbit (Requirement 6027). d. Promote the adoption of international policies, standards, and practices to minimize OD and its associated risks, and the exchange of information on OD research, modeling, and mitigation techniques in the international community (Requirement 6028).
NPD 8730.2B, NASA PARTS POLICY
It is NASA policy to control risk and enhance reliability in NASA spaceflight and critical ground support systems, in part, by managing the selection, acquisition, traceability, testing, handling, packaging, storage, and application of NPD 8730.2B, NASA PARTS POLICY. Electrical, Electronic, and Electromechanical (EEE) parts; advanced packaging and interconnect systems; and mechanical parts (including fasteners, bearings, studs, pins, rings, shims, valves, springs, brackets, clamps, and spacers) (Requirement 10013).
Ident. Num:
NPD 8730.2
Rev. Num:
B
It is NASA policy to control risk and enhance reliability in NASA spaceflight and critical ground support systems, in part, by managing the selection, acquisition, traceability, testing, handling, packaging, storage, and application of NPD 8730.2B, NASA PARTS POLICY. Electrical, Electronic, and Electromechanical (EEE) parts; advanced packaging and interconnect systems; and mechanical parts (including fasteners, bearings, studs, pins, rings, shims, valves, springs, brackets, clamps, and spacers) (Requirement 10013).
