| NASA Software Management, Assurance, and Engineering Policy |
NASA NMI 2410.10B
MANAGEMENT Effective Date April 20, 1993
INSTRUCTION Expiration Date April 20, 1997
Responsible Office: QE/Technical Standards Division
1. PURPOSE
This Instruction sets forth NASA policy and responsibilities for implementing
software management, assurance, and engineering requirements.
2. APPLICABILITY AND SCOPE
This Instruction applies to NASA Headquarters and Field Installations for all
software developed for, or acquired by, NASA after the effective date of this
Instruction. This Instruction also shall apply to existing software if it is
deemed beneficial to a project by either the responsible Program Associate
Administrator or the Director of the implementing Field Installation.
3. POLICY
All software acquisition and development at NASA shall be managed to ensure that
the software satisfies its intended use and that the software is developed using
sound engineering and assurance practices and procedures.
a. Software acquisition and development shall be managed, engineered, and
assured in accordance with NASA and other applicable standards.
b. A software classification scheme shall be developed based on the
combined factors of cost, size, complexity, lifespan, risk, and
consequences of failure. For each class there shall be allocated a
corresponding set of minimum requirements for software management,
assurance, and engineering activities.
c. The classification scheme must contain a class in which is contained all
complex, high profile NASA projects, specifically including flight
projects. For this class, each project shall be required to produce a
software management plan according to the contents specified in
NASA-STD-2100-91, "NASA Software Documentation Standards."
April 20, 1993 NMI 2410.10B
d. For the class of complex, high profile projects, the software management
plan will be developed within 9 months after project plan approval. The
software management plan shall be reviewed by a committee of peers.
e. In order to promote efficient use of software resources, the
classification scheme shall also contain a class for which there shall
be minimal Center requirements for management, assurance, and/or
engineering activities.
4. RESPONSIBILITIES
a. The Associate Administrator for Management Systems and Facilities, as
the NASA-designated senior official, in accordance with Public Law
96-511 (44 U.S.C. 3501), as amended (The Paperwork Reduction Act of
l980), is accountable for the following:
(1) Software acquisitions subject to Public Law 89-306 (40 U.S.C. 759), as
amended (The Brooks Act of 1955).
(2) Establishing NASAwide policies and procedures to implement the software
management provisions of the Federal Information Resources Management
Regulation (FIRMR) and any terms of delegations of procurement authority
for software.
(3) Reviewing software acquisitions at NASA Field Installations to ensure
compliance with the terms and conditions contained in delegations of
procurement authority and to ensure compliance with the software
management provisions of the FIRMR.
b. The Associate Administrator for Safety and Mission Quality is
responsible for the following:
(1) Reviewing, for the purpose of promoting quality and uniformity, the
software classification scheme and related management, assurance,
engineering, and documentation requirements established by each Field
Installation.
(2) Conducting NASA's programs for software management, assurance, and
engineering to focus on software activities to support operational
success of NASA programs and projects.
(3) Appointing up to three members to the Peer Review Committee that reviews
the software management plan for NASA's complex, high profile projects.
*c. The Associate Administrator for Procurement is responsible for
developing procurement policies and practices and compliance procedures
consistent with the procurement-related aspects of this Instruction.
*Changed by this revision.
d. Officials-in-Charge of Headquarters Program and Functional Offices are
responsible for the following:
(1) Ensuring that appropriate planning has been undertaken in accordance
with NASA policy, standards, and guidelines.
(2) Resolving differences in classification schemes for multicenter
programs.
(3) Ensuring that sufficient resources have been allocated and scheduled to
implement the software management, assurance, and engineering
requirements.
e. Field Installation Directors charged with software acquisition or
development and NASA Officials-in-Charge of Headquarters Offices charged
with software acquisition or development directly from Headquarters are
responsible for the following:
(1) Establishing and implementing a software classification scheme.
(2) Establishing policy and procedures for classifying software developed or
acquired.
(3) Establishing minimum software management, assurance, engineering, and
documentation requirements for each class of software.
(4) Establishing policies and procedures for software management, assurance,
and engineering requirements.
(5) Appointing members to the Peer Review Committee that reviews the
software management plan for NASA's complex, high profile projects.
(6) Reviewing Peer Review Committee findings.
(7) Establishing requirements to ensure that NASA contractors comply with
the software management, assurance, and engineering requirements.
5. CANCELLATION
NMI 2410.10A dated December 12, 1991.
(signed by)
Administrator
DISTRIBUTION:
SDL 1
|