iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO/IEC/IEEE 24748-5:2017

(Main)

Systems and software engineering — Life cycle management — Part 5: Software development planning

Systems and software engineering — Life cycle management — Part 5: Software development planning

ISO/IEC/IEEE 24748-5:2017 provides a common framework for planning and controlling the technical processes and activities to 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, develop, utilize, and manage modern software. ISO/IEC/IEEE 24748-5:2017: - specifies the required information items to be produced through the implementation of the required planning and control processes; - specifies the required content of the required information items; - gives guidelines for the format and content of the required and related information items; and - details the processes necessary to develop and implement a software plan. ISO/IEC/IEEE 24748-5:2017 is intended to provide guidance for parties involved in the planning of software engineering at all stages of the software life cycle. It is intended to provide a common framework for two-party and multi-party collaborations and can be applied where the parties are from the same organization. This document can also be used by a single party. ISO/IEC/IEEE 24748-5:2017 is applicable to: - those who use ISO/IEC/IEEE FDIS 12207 on projects dealing with software products and services related to those products; - those who are responsible for the technical management of the development of software systems; - organizations and individuals performing software development activities; and - organizations and individuals developing information items during the development of software.

Ingénierie des systèmes et du logiciel — Gestion du cycle de vie — Partie 5: Planification de développement de logiciel

General Information

Status
Published
Publication Date
18-Jul-2017
ICS
35.080 - Software
Technical Committee
ISO/IEC JTC 1/SC 7 - Software and systems engineering
Drafting Committee
ISO/IEC JTC 1/SC 7/WG 7 - Life cycle management
Current Stage
9093 - International Standard confirmed
Start Date
21-Dec-2022
Completion Date
19-Apr-2025
Ref Project

Relations

Consolidated By
ISO 8130-12:2019 - Coating powders — Part 12: Determination of compatibility
Effective Date
06-Jun-2022
ISO/IEC/IEEE 24748-5:2017 - Systems and software engineering -- Life cycle managementISO/IEC/IEEE 24748-5:2017 - Systems and software engineering -- Life cycle management
PreviousNext
Standard
ISO/IEC/IEEE 24748-5:2017 - Systems and software engineering -- Life cycle management
English language
40 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO/IEC/
STANDARD IEEE
24748-5
First edition
2017-06
Systems and software engineering —
Life cycle management —
Part 5:
Software development planning
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie —
Partie 5: Planification de développement de logiciel
Reference number
©
ISO/IEC 2017
©
IEEE 2017
© ISO/IEC 2017, Published in Switzerland
© IEEE 2017
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or
by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written
permission. Permission can be requested from either ISO or IEEE at the address below or ISO’s member body in the country of
the requester.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
Ch. de Blandonnet 8 • CP 401 3 Park Avenue, New York
CH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USA
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org stds.ipr@ieee.org
www.iso.org www.ieee.org
© ISO/IEC 2017 – All rights reserved
ii
© IEEE 2017 – All rights reserved

Contents
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
4 Abbreviations . 5
5 Conformance . 5
5.1 General . 5
5.2 Intended usage . 6
5.3 Conformance to processes . 6
5.4 Conformance to information item content . 6
5.5 Full conformance . 6
5.6 Tailored conformance . 7
6 Concepts . 7
6.1 General . 7
6.2 System concepts . 7
6.3 Life cycle concepts . 7
6.4 Process concepts . 8
6.5 Project concepts . 8
6.6 Information item concepts . 8
6.6.1 General . 8
6.6.2 Concept of Plans . 9
6.6.3 Software development plans . 9
6.7 Management concepts . 10
6.7.1 General . 10
6.7.2 Project management . 10
6.7.3 Technical management . 10
6.8 Software development model concepts . 10
6.8.1 General . 10
6.8.2 Once-Through software development model . 11
6.8.3 Evolutionary software development model . 11
6.8.4 Incremental software development model . 11
7 Software life cycle processes and software development planning . 12
7.1 General . 12
7.2 Agreement processes . 12
7.3 Organizational project-enabling processes . 12
7.4 Technical management processes . 13
7.5 Technical processes . 13
8 Software development planning . 13
9 Process Execution . 14
9.1 Overview . 14
9.2 Project planning process . 14
9.2.1 General . 14
9.2.2 Responsibility for planning . 14
9.2.3 Project scope . 15
9.2.4 Work Breakdown Structure . 16
iii
© ISO/IEC 2017 ‐ All rights reserved
© IEEE 2017 – All rights reserved

9.2.5 Project estimation . 16
9.2.6 Relationship management . 18
9.2.7 Risk Management . 19
9.2.8 Configuration management . 19
9.2.9 Information management . 19
9.2.10 Quality Assurance . 19
9.3 Project and software measurement . 19
9.3.1 Measurement overview . 19
9.3.2 Project measures . 20
9.3.3 Software measures . 20
9.4 Project assessment and control . 21
9.4.1 Overview . 21
9.4.2 General guidance . 21
9.4.3 Project assessment and control process . 23
9.5 Decision management . 25
10 Information items: Technical plans . 26
10.1 Software Development Plan related to other plans . 26
10.2 Content of the Software Development Plan . 27
10.2.1 Content Overview . 27
10.2.2 Detailed content of the SDP . 27
Annex A (informative) Generic content for a plan . 30
Annex B (informative) Sample Software Development Plan outline . 31
Annex C (informative) Application of related standards . 35
Bibliography . 37
iv
© ISO/IEC 2017 ‐ All rights reserved
© IEEE 2017 – All rights reserved

Foreword
Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC
participate in the development of International Standards through technical committees established by the
respective organization to deal with particular fields of technical activity. ISO and IEC technical committees
collaborate in fields of mutual interest. Other international organizations, governmental and nongovernmental, in
liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have
established a joint technical committee, ISO/IEC JTC 1.

IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees
of the IEEE Standards Association (IEEE‐SA) Standards Board. The IEEE develops its standards through a
consensus development process, approved by the American National Standards Institute, which brings together
volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not
necessarily members of the Institute and serve without compensation. While the IEEE administers the process
and establishes rules to promote fairness in the consensus d
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

ISO
ISO/IEC 29110-3-2:2018/Amd 1:2025(Amendment)
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 3-2: Conformity certification scheme — Amendment 1: Removal of requirement for 3-year recertification
  • Standard
    1 page
    English language
    sale 15% off
  • Draft
    1 page
    English language
    sale 15% off
  • Draft
    1 page
    English language
    sale 15% off
ISO
ISO/IEC TS 19770-10:2025(Main)
Information technology — IT asset management — Part 10: Guidance for implementing ITAM

This document covers the following information technology asset management (ITAM) system processes: a) management system processes for the overall system of IT asset management (not described in ISO/IEC 19770-1 in detail), which are specified in this document for comprehensive coverage and consistency of explanations; these include: — understanding the external context and shareholder needs (7.1, 7.2 and 10.2); — leadership, policy and organization (10.3); — establishing and maintaining the management system (10.4); — planning and risk management (10.5); — support (including resources, competence, awareness, and communication – 10.6); — executing functional and life cycle processes (10.7); — performance evaluation and improvement (10.8); b) functional management processes for IT assets (not described in ISO/IEC 19770-1 in detail), which are cross-cutting processes that integrate with life-cycle processes for IT assets and which are shared with most IT management system standards, though sometimes slightly differently grouped; these include: — change management (11.2; also required by ISO/IEC 19770-1); — data management; — license management; — security management; — relationship and contract management; — financial management; — service level management; — other risk management; c) life cycle management processes for IT assets as specified in ISO/IEC 19770-1, which are grouped and named slightly differently by different methodologies; these include: — specification; — development; — acquisition; — release; — deployment; — operation; — retirement. This document is applicable to all ITAM implementations. This document can be applied to all types of IT assets and by all types and sizes of organizations.

  • Technical specification
    144 pages
    English language
    sale 15% off
ISO
ISO/IEC 20582:2025(Main)
Software and systems engineering — Capabilities of build and deployment tools

This document defines the requirements for capabilities of build and deployment tools to support and automate building, packaging, and deploying work. This document is intended for use in evaluating and selecting build and deployment tools according to the procedures defined in ISO/IEC 20741. This document is applicable to different development methodologies and approaches (e.g. Waterfall, Agile, or DevOps).

  • Standard
    32 pages
    English language
    sale 15% off
ISO
ISO/IEC TS 33060:2025(Main)
Information technology — Process assessment — Process assessment model for system life cycle processes

This document defines a process assessment model for system life cycle processes, conformant with the requirements of ISO/IEC 33004, for use in performing a conformant assessment in accordance with the requirements of ISO/IEC 33002.

  • Technical specification
    65 pages
    English language
    sale 15% off
ISO
ISO/IEC TS 33062:2025(Main)
Information technology — Process assessment — Process assessment model for quantitative processes to support higher levels of process capability in ISO/IEC 33020

This document defines a process assessment model for quantitative processes, conforming to the requirements of ISO/IEC 33004, for use in performing a process assessment in accordance with the requirements of ISO/IEC 33002.

  • Technical specification
    18 pages
    English language
    sale 15% off
ISO
ISO/IEC 29110-5-6-4:2025(Main)
Systems and software engineering — Life cycle profiles for very small entities (VSEs) — Part 5-6-4: Systems engineering guidelines for the generic Advanced profile

This document describes processes targeted at VSEs that want to sustain and grow as an independent competitive system development organization. This document provides management and engineering guidelines for the systems engineering Advanced profile of the generic profile group. This document is applicable to VSEs that do not develop critical systems and have little or no experience with systems engineering (SE) process planning and implementation using the ISO/IEC/IEEE 15288. This document is also applicable to VSEs which are familiar with the management and engineering guidelines of the systems engineering Intermediate profile (ISO/IEC TR 29110 5-6-3) for their system development projects and are involved in the development of more than one project in parallel with more than one work team.

  • Standard
    83 pages
    English language
    sale 15% off
ISO
ISO/IEC 29110-5-1-1:2025(Main)
Systems and software engineering — Life cycle profiles for very small entities (VSEs) — Part 5-1-1: Software engineering guidelines for the generic Entry profile

This document provides the management and engineering guidelines to the software Entry profile specified in ISO/IEC 29110-4-1 through project management and software implementation processes. This document applies to VSEs that do not develop safety-critical software. This document applies for software development projects, which can fulfil an external or internal agreement. This document applies to start-up VSEs (e.g. VSEs that started their operation less than three years ago) and/or VSEs working on small projects (e.g. projects with a size of less than six person-months).

  • Standard
    36 pages
    English language
    sale 15% off
ISO
ISO/IEC 29110-5-1-2:2025(Main)
Systems and software engineering — Life cycle profiles for very small entities (VSEs) — Part 5-1-2: Software engineering guidelines for the generic Basic profile

This document provides management and engineering guidelines to the software Basic profile specified in ISO/IEC 29110-4-1 through project management and software implementation processes. This document applies to VSEs that do not develop safety-critical software. This document applies for software development projects, which can fulfil an external or internal agreement. This document is applicable to VSEs developing a single product by a single work team.

  • Standard
    93 pages
    English language
    sale 15% off
ISO
ISO/IEC/IEEE 32430:2025(Main)
Software engineering — Software non-functional size measurement

This document defines a method for measuring the non-functional size of the software. It complements ISO/IEC 20926:2009, which defines a method for measuring the functional size of the software. This document also describes the complementarity of functional and non-functional sizes, so that deriving the sizes from the functional and the non-functional requirements does not result in duplication in the distinct functional and non-functional sizes. In general, there are many types of non-functional requirements. Moreover, non-functional requirements and their classification evolve over time as the technology advances. This document does not intend to define the type of NFR for a given context. Users can choose ISO 25010 or any other standard for the definition of NFR. It is assumed that users size the NFR based on the definitions they use. This document covers a subset of non-functional requirements. It is expected that, with time, the state of the art can improve and that potential future versions of this document can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that can be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional sizes would then correspond to the total size necessary to bring the software into existence. Estimating the cost, effort and duration of the implementation of the NFR is outside the scope of this document.

  • Standard
    71 pages
    English language
    sale 15% off
ISO
ISO/IEC/IEEE 29119-5:2024(Main)
Software and systems engineering — Software testing — Part 5: Keyword-driven testing

This document defines an efficient and consistent solution for keyword-driven testing by: — giving an introduction to keyword-driven testing; — providing a reference approach to implement keyword-driven testing; — defining requirements on frameworks for keyword-driven testing to enable testers to share their work items, such as test cases, test data, keywords, or complete test specifications; — defining requirements for tools that support keyword-driven testing; these requirements are applicable to any tool that supports the keyword-driven approach (e.g. test automation, test design and test management tools); — defining interfaces and a common data exchange format to ensure that tools from different vendors can exchange their data (e.g. test cases, test data and test results); — defining levels of hierarchical keywords, and advising use of hierarchical keywords; this includes describing specific types of keywords (e.g. keywords for navigation or for checking a value) and when to use "flat" structured keywords; — providing an initial list of example generic technical (low-level) keywords, such as "inputData" or "checkValue"; these keywords can be used to specify test cases on a technical level and can be combined to create business-level keywords as required. This document is applicable to all those who want to create keyword-driven test specifications, create corresponding frameworks, or build test automation based on keywords.

  • Standard
    55 pages
    English language
    sale 15% off