< home >  last update  12-31-2020  LANDING -MAIN - FOR FAULT TOLERANT SYSTEMS (  DEVICES & SOFTWARE  )

  US Military Software Standards & Specifications  :: SOURCE https://en.wikipedia.org/wiki/ISO/IEC_12207 

  ISO/IEC 12207 >  https://www.iso.org/standard/63712.html

From Wikipedia, the free encyclopedia

ISO/IEC/IEEE 12207 Systems and software engineering – Software life cycle processes[1] is an international standard for software lifecycle processes. First introduced in 1995, it aims to be a primary standard that defines all the processes required for developing and maintaining software systems, including the outcomes and/or activities of each process.


Revision history

ISO/IEC/IEEE 12207:2017 is the newest version, published in November 2017.[1] The IEEE Computer Society joined directly with the International Organization for Standardization (ISO) in the editing process for this version.
 A significant change is that - it adopts a "process model" identical to the ISO/IEC/IEEE 15288:2015 process model (there is one name change, the 15288 "System Requirements Definition" process is renamed to the "System/Software Requirements Definition" process).
This harmonization of the two standards led to the removal of separate software development and software reuse processes, bringing the total number of 12207 processes from 43 down to the 30 processes defined in 15288.

It also caused changes to the quality management and quality assurance process activities and outcomes. Additionally, the definition of "audit" and related audit activities were updated.[2][3][4] Annex I of ISO/IEC/IEEE 12207:2017 provides a process mapping between the 2017 version and the previous version, including the primary process alignments between the two versions; this is intended to enable traceability and ease transition for users of the previous version.

Prior versions include:

IEEE versions[edit]

Prior to the IEEE Computer Society formally joining the editing process (becoming a major stakeholder) for the 2017 release, the IEEE maintained its own versions of ISO/IEC 12207, initially with modifications made jointly with the Electronic Industries Alliance (EIA).[10][11][12] 
 With the 2008 update came a "shared strategy of ISO/IEC JTC 1/SC 7 and the IEEE to harmonize their respective collections of standards," resulting in identical standards thereon, but with slightly different names.[12] Those IEEE versions included:

It's also worth noting that IEEE/EIA 12207 officially replaced MIL-STD-498 (released in December 1994[11]) for the development of DoD software systems on May 27, 1998.[9][11]

Processes not stages

The standard establishes a set of processes for managing the lifecycle of software. The standard "does not prescribe a specific software life cycle model, development methodology, method, modelling approach, or technique."[1].

Instead, the standard (as well as ISO/IEC/IEEE 15288) distinguishes between a "stage" and "process" as follows:

Stages (aka phases) are not the same as processes, and this standard only defines specific processes - it does not define any particular stages. Instead, the standard acknowledges that software life cycles vary, and may be divided into stages (also called phases) that represent major life cycle periods and give rise to primary decision gates. No particular set of stages is normative, but it does mention two examples:

The life cycle processes the standard defines are not aligned to any specific stage in a software life cycle. Indeed, the life cycle processes that involve planning, performance, and evaluation "should be considered for use at every stage". In practice, processes occur whenever they are needed within any stage.


ISO/IEC/IEEE 12207:2017 divides software life cycle processes into four main process groups: agreement, organizational project-enabling, technical management, and technical processes.[1][4] Under each of those four process groups are a variety of sub-categories, including the primary activities of acquisition and supply (agreement); configuration (technical management); and operation, maintenance, and disposal (technical).[1][16]

Agreement processes[edit]

Here ISO/IEC/IEEE 12207:2017 includes the acquisition and supply processes,[1][2][16] which are activities related to establishing an agreement between a supplier and acquirer. Acquisition covers all the activities involved in initiating a project. The acquisition phase can be divided into different activities and deliverables that are completed chronologically. During the supply phase a project management plan is developed. This plan contains information about the project such as different milestones that need to be reached.

Organizational project-enabling processes[edit]

Detailed here are life cycle model management, infrastructure management, portfolio managementhuman resource management, quality management, and knowledge management processes.[1][2][16] These processes help a business or organization enable, control, and support the system life cycle and related projects. Life cycle model management helps ensure acquisition and supply efforts are supported, while infrastructure and portfolio management supports business and project-specific initiatives during the entire system life cycle. The rest ensure the necessary resources and quality controls are in place to support the business' project and system endeavors. If an organization does not have an appropriate set of organizational processes, a project executed by the organization may apply those processes directly to the project instead.[1]

Technical management processes[edit]

ISO/IEC/IEEE 12207:2017 places eight different processes here:[1][2][16]

These processes deal with planning, assessment, and control of software and other projects during the life cycle, ensuring quality along the way.

Technical processes[edit]

The technical processes of ISO/IEC/IEEE 12207:2017 encompass 14 different processes,[1][2][16] some of which came from the old software-specific processes that were phased out from the 2008 version.[2]

The full list includes:[1][2][16]

These processes involve technical activities and personnel (information technology, troubleshooters, software specialists, etc.) during pre-, post- and during operation. The analysis and definition processes early on set the stage for how software and projects are implemented. Additional processes of integration, verification, transition, and validation help ensure quality and readiness. The operation and maintenance phases occur simultaneously, with the operation phase consisting of activities like assisting users in working with the implemented software product, and the maintenance phase consisting of maintenance tasks to keep the product up and running. The disposal process describes how the system/project will be retired and cleaned up, if necessary.[1]


Clause 4 describes the document's intended use and conformance requirements. It is expected that particular projects "may not need to use all of the processes provided by this document." In practice, conforming to this standard normally involves selecting and declaring the set of suitable processes. This can be done through either "full conformance" or "tailored conformance".

"Full conformance" can be claimed in one of two ways. "Full conformance to tasks" can be claimed if all requirements of the declared processes' activities and tasks are met. "Full conformance to outcomes" can be claimed if all required outcomes of the declared processes are met. The latter permits more variation.

"Tailored conformance" may be declared when specific clauses are selected or modified through the tailoring process also defined in the document.

See also[edit]


  1. Jump up to:a b c d e f g h i j k l "ISO/IEC/IEEE 12207:2017"Standards catalogue. International Organization for Standardization. November 2017. Retrieved 21 June 2018.
  2. Jump up to:a b c d e f g Reilly, A. (27 June 2017). "New or Improved! Software Engineering Standards for Quality". American Society for Quality. Retrieved 21 June 2018.
  3. ^ Bach, C. (12 December 2017). "ISO/IEC 12207 Updated and Renumbered as ISO/IEC/IEEE 12207"Standards Forum. Document Center, Inc. Retrieved 22 June 2018.
  4. Jump up to:a b Reilly, A. (March 2018). "INCITS/SSE - Software and Systems Engineering Annual Report - April 2017 to March 2018" (PDF). INCITS. Retrieved 22 June 2018. The cornerstone standards of ISO/IEC JTC 1/SC 7, ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015, have recently completed revision to reflect a unified model set of acquisition, organizational, technical management, and technical processes for systems and software.
  5. ^ "ISO/IEC 12207:2008"Standards catalogue. International Organization for Standardization. February 2008. Retrieved 21 June2018.
  6. ^ "ISO/IEC 12207:1995/Amd 2:2004"Standards catalogue. International Organization for Standardization. November 2004. Retrieved 21 June 2018.
  7. ^ "ISO/IEC 12207:1995/Amd 1:2002"Standards catalogue. International Organization for Standardization. May 2002. Retrieved 21 June 2018.
  8. ^ "ISO/IEC 12207:1995"Standards catalogue. International Organization for Standardization. July 1995. Retrieved 21 June 2018.
  9. Jump up to:a b "Overview of IEEE/EIA 12207: Standard for Information Technology". SSC San Diego Process Asset Library. 30 July 1998. Archived from the original on 30 December 2008. Retrieved 22 June2018.
  10. Jump up to:a b "IEEE 12207.0-1996 - Standard for Information Technology - Software Life Cycle Processes". IEEE Standards Association. March 1998. Retrieved 22 June 2018.
  11. Jump up to:a b c "ISO/IEC 12207:2008, IEEE Std 12207-2008 Systems and Software Engineering — Software Life Cycle Processes" (PDF). SemanticScholar.org. 7 December 2009. Retrieved 22 June 2018.
  12. Jump up to:a b "1SO/IEC 12207:2008(en) Systems and software engineering — Software life cycle processes: IEEE Introduction"Online Browsing Platform. International Organization for Standardization. February 2008. Retrieved 22 June 2018.
  13. ^ "IEEE Std. 12207-2008 - Systems and software engineering -- Software life cycle processes". IEEE Standards Association. January 2008. Retrieved 22 June 2018.
  14. ^ "IEEE 12207.2-1997 - Guide for Information Technology - Software Life Cycle Processes - Implementation Considerations". IEEE Standards Association. April 1998. Retrieved 22 June 2018.
  15. ^ "IEEE 12207.1-1997 - Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data". IEEE Standards Association. April 1998. Retrieved 22 June 2018.
  16. Jump up to:a b c d e f Peñalvo, F.J.; Holgado, A.G. (2017). "Proceso: Ingeniería de Software I" (PDF). Universidad de Salamanca. p. 39. Retrieved 21 June 2018.

ISO standards by standard number


List of International Electrotechnical Commission standards


IEEE standards


Navigation menu