Hello. Sign In
Standards Store

EIA 12207.0

2015 Edition, July 2015

Complete Document

Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology Software Life Cycle Processes

Includes all amendments and changes through Stabilization Notice (No longer revised / updated) , July 2015

Detail Summary

Active, Most Current

Additional Comments:
Price (USD)
Single User
In Stock
Add to Cart

Product Details:

  • Revision: 2015 Edition, July 2015
  • Published Date: July 2015
  • Status: Active, Most Current
  • Document Language: English
  • Published By: SAE International (SAE)
  • Page Count: 87
  • ANSI Approved: No
  • DoD Adopted: No

Description / Abstract:


This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes the software portion of firmware.

This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.

Field of application

This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, and maintenance of software products, and to the software portion of firmware, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.

NOTE-The processes used during the software life cycle need to be compatible with the processes used during the system life cycle.

This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. This International Standard may be used by a single party as self-imposed tasks.

This International Standard is not intended for off-the-shelf software products unless incorporated into a deliverable product.

This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.

Tailoring of the International Standard

This International Standard contains a set of processes, activities, and tasks designed to be tailored in respect of software projects. The tailoring process is deletion of non-applicable processes, activities, and tasks.

NOTEÑAddition of unique or special processes, activities, and tasks may be provided in the contract.


Compliance with this International Standard is defined as the performance of all the processes, activities, and tasks selected from this International Standard in the Tailoring Process (annex A) for the software project. The performance of a process or an activity is complete when all its required tasks are performed in accordance with the pre-established criteria and the requirements specified in the contract as applicable.

Any organization (for example, national, industrial association, company) imposing this International Standard, as a condition of trade, is responsible for specifying and making public the minimum set of required processes, activities, and tasks, which constitute suppliers' compliance with this International Standard.


This International Standard describes the architecture of the software life cycle processes but does not specify the details of how to implement or perform the activities and tasks included in the processes.

This International Standard is not intended to prescribe the name, format, or explicit content of the documentation to be produced. This International Standard may require development of documents of similar class or type; various plans are an example. This International Standard, however, does not imply that such documents be developed or packaged separately or combined in some fashion. These decisions are left to the user of this International Standard.

This International Standard does not prescribe a specific life cycle model or software development method. The parties of this International Standard are responsible for selecting a life cycle model for the software project and mapping the processes, activities, and tasks in this International Standard onto that model. The parties are also responsible for selecting and applying the software development methods and for performing the activities and tasks suitable for the software project.

This International Standard is not intended to be in conflict with any organization's policies, standards or procedures that are already in place. However, any conflict needs to be resolved and any overriding conditions and situations need to be cited in writing as exceptions to the application of this International Standard.

Throughout this International Standard, "shall" is used to express a provision that is binding between two or more parties, "will" to express a declaration of purpose or intent by one party, "should" to express a recommendation among other possibilities, and "may" to indicate a course of action permissible within the limits of this International Standard.

In this International Standard, there are a number of lists for tasks; none of these is presumed to be exhaustiveÑthey are intended as examples.
AIA/NAS Aerospace Standards