ISO/IEC/IEEE 24748 provides unified and consolidated guidance on the life cycle management of systems and software. This document focuses on the processes required for successful planning and management of the project's software development effort and for development of the software development plan (SDP) as a vehicle for representing a project's application of software life cycle processes. The SDP is a top level technical planning document for a project which addresses technical management processes established by three principal sources (the project's contract, applicable organizational and technical management processes, and the software development project team) as necessary to successfully accomplish the software development related tasks of the project.
- Standard Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
- Status
- Active Standard
- PAR Approval
- 2013-05-10
- Board Approval
- 2017-05-18
- History
-
- ANSI Approved:
- 2018-11-26
- Published:
- 2017-06-23
Additional Resources
- Downloads
- 24748-5-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
- Christian Orlando
Contact Christian Orlando - 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.
P24748-3
ISO/IEC/IEEE International Standard – Systems and software engineering – Life cycle management – Part 3: Guidelines for the application of ISO/IEC/IEEE 12207 (software life cycle processes)
This document is a guideline for the application of ISO/IEC/IEEE 12207. This document establishes guidance for implementing a common framework for software life cycle processes, with well-defined terminology that can be referenced by the software industry. This document provides guidance on defining, controlling and improving software life cycle processes within an organization or a project. This document recommends methods and approaches suitable for a variety of life cycle models. The guidance emphasizes the importance of establishing a strategy, planning, and the involvement of stakeholders with the ultimate goal of achieving customer satisfaction.
P24748-5
Systems and software engineering – Life cycle management – Part 5: Software engineering technical management
This document provides a common framework for planning and controlling the technical processes and activities to develop, produce and sustain software products. The complete life cycle is covered by this document, from idea conception to the retirement of a software product. The framework described by this document provides for best practices in communication and cooperation among parties that plan for developing, utilizing, and managing modern software.
Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.
12207-2026
ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes
This document establishes a common process framework for describing the full life cycle of software systems from conception through retirement. It applies to the acquisition or development of software products and services whether performed internally or externally to an organization. Those aspects of software system definition needed to provide the context for software products and services are included. The document also supports the definition, control, assessment, and improvement of these processes. These processes can be applied concurrently, iteratively, and recursively to a software system and its elements throughout the life cycle of a software system. Users of the document can apply the processes and terminology to construct a suitable life cycle model, composed of stages that use selected processes. The process purposes and outcomes in ISO/IEC/IEEE 15288:2023 (systems life cycle processes) and this document are fully aligned so that one may select appropriate activities from either document for use in systems with substantial software content.
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