[NASA Logo]

NASA Procedures and Guidelines

This Document is Obsolete and Is No Longer Used.
Check the NODIS Library to access the current version:
http://nodis3.gsfc.nasa.gov


NPR 7123.1
Eff. Date: March 13, 2006
Cancellation Date: March 26, 2007

Systems Engineering Procedural Requirements

| TOC | Change History | Preface | Prologue | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | ALL |


Appendix I. Additional Reading

The following documentsßwere used as reference materials in the development of this SE NPR. The documents are offered as informational sources and are not evoked in this SE NPR, though they may be referenced.

1.ß MIL-STD-499B (draft), SystemsßEngineering.

2.ß ISO/IEC 15288, SystemßLife CycleßProcesses.

3.ß ANSI/EIA 632, Processesßfor EngineeringßSystems.

EIA 632 is a commercial version that evolved from the never released, but fully developed 1994 Mil-Std 499B SystemsßEngineering. It was intended to provide a framework for developing and supporting universal SEßdiscipline for both defense and commercial environments. EIA 632 was intended to be a top-tier standard further defined to lower level tier standards that define specific practices. IEEE 1220 is a second-tier standard that implements EIA 632 by defining one way to practice systems engineering. ISO/IEC 15288 defines system life processesßfor the international set plus for any domainß(i.e., transportation, medical, commercial, et al.).

4.ß CMMI model.

The Capability Maturity Model½ (CMM) IntegrationSM (CMMI) in its present form is a collection of best practices for the "development and maintenance" of both "products and services." The model was developed by integrating practices from four different CMMs-the "source models:" the CMM for software, for systemsßengineering, for integrated product development (IPD), and for acquisition. Organizationsßcan use the model as a guide for improving their ability to develop (or maintain) products (and services) on time, within budget, and with desired quality. During the past decade, many organizations have used CMM and CMM-like concepts to bring order to their development processes. Additionally, it also provides these organizations the framework for enlarging the focus of process improvement to other areas that also affect product development-the discipline of systems engineering. During the past decade, new and effective concepts for organizing developmental work have surfaced and been adopted such as concurrent engineering or the use of integrated teams. Organizations using (or wishing to adopt these ideas) can also find support in the CMMI by using the model with integrated product and process development (IPPD) additions.

5.ß Defense Acquisition University SystemsßEngineeringßFundamentals. Defense Acquisition University Press, Ft. Belvoir, VA, December 2000.

6.ß International Council on Systems EngineeringßSystems Engineering Guide.

7.ß ISO/IEC 19760, A Guide for the Application of ISO/IEC 15288 (System Life Cycle Processes).

8. ISO/AS9100, "Quality Management Systems, Aerospace, Requirements.



| TOC | Change History | Preface | Prologue | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | ALL |
 
| NODIS Library | Program Formulation(7000s) | Search |

DISTRIBUTION:
NODIS


This Document is Obsolete and Is No Longer Used.
Check the NODIS Library to access the current version:
http://nodis3.gsfc.nasa.gov