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 software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. This International Standard applies to the acquisition of software systems, products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of any system, whether performed internally or externally to an organization. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included. This International Standard also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project. The processes, activities and tasks of this International Standard may also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288, Systems and software engineering–System life cycle processes. In the context of this International Standard and ISO/IEC/IEEE 15288, it is recognized that there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system of interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this International Standard for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering-System life cycle processes, depends on the system of interest. Processes in both standards have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.
- Standard Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
- Status
- Active Standard
- PAR Approval
- 2013-05-10
- Superseding
- 12207-2008
- Board Approval
- 2017-09-28
- History
-
- Published:
- 2017-11-15
Additional Resources
- Downloads
- 12207-2017_downloads.zip
Working Group Details
- Society
- IEEE Computer Society
- Standard Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
- Working Group
-
WG_LCP - Working Group for Life Cycle Processes
- IEEE Program Manager
- Patricia Roder
Contact Patricia Roder - Working Group Chair
- Teresa Doran
Other Activities From This Working Group
Current projects that have been authorized by the IEEE SA Standards Board to develop a standard.
P15026-1
ISO/IEC/IEEE International Standard for Systems and software engineering--Systems and software assurance --Part 1:Concepts and vocabulary
This document defines assurance-related terms and establishes an organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to all parts of ISO/IEC/IEEE 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC/IEEE 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in the ISO/IEC/IEEE 15026 series.
P24748-10
ISO/IEC/IEEE Systems and software engineering-- Life cycle management--Part 10: Guidelines for systems engineering agility
This part of ISO/IEC/IEEE 24748 specifies strategic aspects supporting systems engineering agility, and provides guidelines for their selection and application. Strategic aspects included in this document are: adaptable modular architecture, iterative and incremental development, situational awareness and decision-making, common mission teaming, shared knowledge management, continual integration and test, and agile operations.
P24748-4
ISO/IEC/IEEE Draft International Standard - Systems and Software Engineering -- Life Cycle Management -- Part 4: Systems Engineering Management Planning
ISO/IEC/IEEE 15288, Systems and software engineering -- System life cycle processes, provides a common process framework covering the life cycle of human-made systems, from the conception of ideas through to the retirement of a system. It provides the processes for acquiring and supplying systems. In addition, this framework provides for the assessment and improvement of the life cycle processes. This common framework improves communication and cooperation among the parties that create, utilize, and manage modern systems in order that they can work in an integrated, coherent fashion. The acquisition or supply of a system is usually done within a project. A project prepares and implements the technical planning, resources and schedules necessary to guide the project toward accomplishment of its objectives and proper conclusion. The project's authorization and objectives are documented in an information item identified as a Systems Engineering Management Plan (SEMP). This document defines a SEMP as the key vehicle for representing a project's application of systems life cycle processes. In this document, the terms technical planning and systems engineering planning are used interchangeably to emphasize or differentiate technical contributions in the processes under discussion.
Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.
No Active Standards
These standards have been replaced with a revised version of the standard, or by a compilation of the original active standard and all its existing amendments, corrigenda, and errata.
No Superseded Standards
These standards have been removed from active status through a ballot where the standard is made inactive as a consensus decision of a balloting group.
No Inactive-Withdrawn Standards
These standards are removed from active status through an administrative process for standards that have not undergone a revision process within 10 years.
No Inactive-Reserved Standards