Purpose

The purpose of this Standard is to provide an integrated set of fundamental processes to aid a developer in the engineering or reengineering of a system.

Use of this Standard is intended to help developers

a) establish and evolve a complete and consistent set of requirements that will enable delivery of feasible and cost-effective system solutions;

b) satisfy requirements within cost, schedule, and risk constraints;

c) provide a system, or any portion of a system, that satisfies stakeholders over the life of the products that make up the system.

NOTE - The term product is used in this standard to mean: a physical item, such as a satellite (end product), or any of its component parts (end products); a software item such as a stand-alone application to run within an existing system (end product); or a document such as a plan, or a service such as test, training, or maintenance support, or equipment such as a simulator (enabling products).

d) provide for the safe and/or cost-effective disposal or retirement of a system.

Coverage

This Standard defines processes for engineering a system, as shown in Figure 1.2. These have been organized into five groups.

Intended applications

This Standard is intended to be applicable to the engineering or the reengineering of

a) commercial or non-commercial systems, or portions thereof;

b) any system, small or large, simple or complex, software-intensive or not, precedented or unprecedented;

c) systems containing products made up of hardware, software, firmware, personnel, facilities, data, materials, services, techniques, or processes (or combinations thereof);

d) a new system or a legacy system, or portions thereof.

NOTE - The specific tasks and implementation methods for applying the processes required by this Standard can vary, for example, between commercial and government projects, or between customer-involved and internally developed projects. The fundamental processes, however, are the same in all cases.

The requirements of this Standard, or a designated subset, are intended to be applied by establishing enterprise policies and procedures that define the requirements for project implementation of the adopted processes of this Standard. The application of this Standard with respect to enterprises and projects is shown in Figure 1.3.

Limitations

This Standard does not specify the details of "how to" implement process requirements for engineering a system. Nor does it specify the methods or tools a developer would use to implement the process requirements. It is intended that the developer select or define methods and tools that are applicable to the development, and that are consistent with enterprise policies and procedures.

This Standard does not prescribe the name, format, content, structure, or medium of documentation.

Customers who purchased TECHAMERICA EIA-632
also purchased

• IEEE 1220 : Standard for Application and Management of the Systems Engineering Process-IEEE Computer Society Document
• TECHAMERICA EIA-649-B : Configuration Management Standard
• BSI BS ISO/IEC 15288 : Systems engineering System life cycle processes

See More Documents