iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO/IEC/IEEE 24748-2:2024

(Main)

Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (system life cycle processes)

Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (system life cycle processes)

The proposed project is a revision of ISO/IEC/IEEE 24748-2:2018, Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (System life cycle processes). There are no scope changes. ISO/IEC/IEEE 24748-2 is a guideline for the application of ISO/IEC/IEEE 15288. It addresses system, life cycle, organizational, project, and process, concept application, principally through reference to ISO/IEC/IEEE 24748-1 and ISO/IEC/IEEE 15288. It gives guidance on applying ISO/IEC/IEEE 15288 from the aspects of strategy, planning, application in organizations, and application on projects. It also provides comparison of the differences between ISO/IEC/IEEE 15288 current revision and the prior version, ISO/IEC 15288:2015.

Ingénierie des systèmes et du logiciel — Gestion du cycle de vie — Partie 2: Lignes directrices pour l'application de l'ISO/IEC/IEEE 15288 (processus du cycle de vie du système)

General Information

Status
Published
Publication Date
14-Mar-2024
ICS
35.080 - Software
Technical Committee
ISO/IEC JTC 1/SC 7 - Software and systems engineering
Drafting Committee
ISO/IEC JTC 1/SC 7 - Software and systems engineering
Current Stage
6060 - International Standard published
Start Date
15-Mar-2024
Due Date
24-Jun-2025
Completion Date
15-Mar-2024
Ref Project

Relations

Revises
ISO/IEC/IEEE 24748-2:2018 - Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (System life cycle processes)
Effective Date
06-Jun-2022

Buy Standard

ISO/IEC/IEEE 24748-2:2024 - Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (system life cycle processes) Released:15. 03. 2024ISO/IEC/IEEE 24748-2:2024 - Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (system life cycle processes) Released:15. 03. 2024
PreviousNext
Standard
ISO/IEC/IEEE 24748-2:2024 - Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (system life cycle processes) Released:15. 03. 2024
English language
63 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


International
Standard
ISO/IEC/IEEE
24748-2
Second edition
Systems and software
2024-03
engineering — Life cycle
management —
Part 2:
Guidelines for the application of
ISO/IEC/IEEE 15288 (system life
cycle processes)
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie —
Partie 2: Lignes directrices pour l'application de l'ISO/IEC/IEEE
15288 (processus du cycle de vie du système)
Reference number © ISO/IEC 2024
© ISO/IEC 2024
© IEEE 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
respective address below or ISO’s member body in the country of the requester.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
CP 401 • Ch. de Blandonnet 8 3 Park Avenue, New York
CH-1214 Vernier, Geneva NY 10016-5997, USA
Phone: +41 22 749 01 11
Email: copyright@iso.org Email: stds.ipr@ieee.org
Website: www.iso.org Website: www.ieee.org
Published in Switzerland
© ISO/IEC 2024 – All rights reserved
© IEEE 2024 – All rights reserved
ii
Contents Page
Foreword .v
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Overview of ISO/IEC/IEEE 15288 . 1
4.1 General .1
4.2 Structure of ISO/IEC/IEEE 15288 .2
4.3 Context of ISO/IEC/IEEE 15288 .2
4.4 Comparison of ISO/IEC/IEEE 15288 to prior version .4
5 Application concepts . 5
6 Applying ISO/IEC/IEEE 15288. 5
6.1 Overview .5
6.2 Application strategy .5
6.2.1 Overview .5
6.2.2 Planning the application .7
6.2.3 Conduct pilot project(s) .7
6.2.4 Formalise the approach . .8
6.2.5 Institutionalise the approach .8
6.3 Application of system concepts .8
6.3.1 General .8
6.3.2 Systems .8
6.3.3 System structure .9
6.3.4 Structure in systems and projects .9
6.3.5 Interfacing, enabling and interoperating systems .9
6.4 Application of life cycle concepts .10
6.4.1 Overview .10
6.4.2 Decision gates .11
6.4.3 Application approaches . 12
6.5 Application of organizational concepts .17
6.5.1 Overview .17
6.5.2 Methods and tools .19
6.5.3 Considerations and techniques .19
6.5.4 Management commitment . 20
6.5.5 Uses of ISO/IEC/IEEE 15288 within an organization . 20
6.6 Application of project concepts . 20
6.7 Application of process concepts .21
6.7.1 General .21
6.7.2 Application of agreement processes (ISO/IEC/IEEE 15288:2023, 6.1) .21
6.7.3 Application of organizational project-enabling processes (ISO/IEC/IEEE
15288:2023, 6.2) .24
6.7.4 Application of technical management processes (ISO/IEC/IEEE 15288:2023, 6.3) . 25
6.7.5 Application of technical processes (ISO/IEC/IEEE 15288:2023, 6.4) .32
6.8 Application of conformance and adaptation concepts .47
6.8.1 Application of conformance concepts.47
6.8.2 Application of adaptation concepts .47
Annex A (informative) Summary of typical revised points in ISO/IEC/IEEE 15288:2023 from
ISO/IEC/IEEE 15288:2015 .50
Annex B (informative) Example for interfacing, enabling and interoperating systems .57
Annex C (informative) Model-based systems and software engineering (MBSSE) .59
Bibliography .62

© ISO/IEC 2024 – All rights reserved
© IEEE 2024 – All rights reserved
iii
IEEE notices and abstract .64

© ISO/IEC 2024 – All rights reserved
© IEEE 2024 – All rights reserved
iv
Foreword
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 non-governmental, in liaison with ISO and IEC, also take part in the work.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/
IEC Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
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 development process,
the IEEE does not independently evaluate, test or verify the accuracy of any of the information contained in
its standards.
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/JTC 1, Information technology, Subcommittee
SC 7, Software and systems engineering, in cooperation with the IEEE Computer Society Systems and Software
Engineering Standards Committee, under the Partner Standards Development Organization cooperation
agreement between ISO and IEEE.
This second edition cancels and replaces the first edition (ISO/IEC/IEEE 24748-2:2018), whi
...

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 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-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 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/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
ISO
ISO/IEC TS 25052-2:2024(Main)
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE): cloud services — Part 2: Quality measurement

This document defines quality measures for quantitatively evaluating cloud services quality in terms of characteristics and sub-characteristics defined in ISO/IEC TS 25052-1 and is intended to be used together with ISO/IEC TS 25052-1. This document contains the following: — a basic set of quality measures for each characteristic and sub-characteristics; — an explanation of how to apply quality measures to cloud services. Since the quality model defined in ISO/IEC TS 25052-1 is the extension to the existing quality models defined in ISO/IEC 25010 to ISO/IEC 25019, it can be used with the product quality model, IT service quality model, data quality model, and quality-in-use model according to evaluation purposes. For the same reason, the quality measures defined in this document can also be used with the quality measures for software ICT products, IT services, data, and quality-in-use. As there are several cloud service categories, this document focuses on the quality model of SaaS (software as a service). This document does not address PaaS (platform as a service) and IaaS (infrastructure as a service).

  • Technical specification
    18 pages
    English language
    sale 15% off
ISO
ISO/IEC/IEEE 41062:2024(Main)
Software engineering — Life cycle processes — Software acquisition

This document describes a set of useful activities, tasks, methods, and practices that acquirers of software and related services from unrelated (external) suppliers can apply to help ensure an efficient and effective acquisition of software or software services. These practices can be applied in competitive and in sole source procurements, regardless of the type, size, complexity, and cost of the acquisition. The document can be applied to software that runs on any computer system regardless of its size, complexity, or criticality. The software supply chain can include integration of off-the-shelf (OTS), custom, software as a service (SaaS), or open-source software. Software services can include software development and sustainment (maintenance), integration, verification (testing) and operation. Security and safety are included as attributes to be considered during the acquisition. However, specific requirements for acquisition of information assurance (security), safety, and cloud services are not included.

  • Standard
    81 pages
    English language
    sale 15% off
ISO
ISO/IEC TR 33022:2024(Main)
Information technology — Process assessment — Application of ISO/IEC/IEEE 12207 processes to the ISO/IEC 33020 process capability measurement scale

This document provides a specification for associating the life cycle processes of ISO/IEC/IEEE 12207 with the process attribute outcomes of ISO/IEC 33020 with the intent of demonstrating support for levels 1 to 3 of the process capability measurement scale defined in ISO/IEC 33020.

  • Technical report
    107 pages
    English language
    sale 15% off
ISO
ISO/IEC TR 33023:2024(Main)
Information technology — Process assessment — Application of ISO/IEC TS 33073 processes to the ISO/IEC 33020 process capability measurement scale

This document provides a specification for associating the processes of ISO/IEC TS 33073 with the process attribute outcomes of ISO/IEC 33020 with the intent of demonstrating support for levels 1 to 3 of the process capability measurement scale defined in ISO/IEC 33020.

  • Technical report
    68 pages
    English language
    sale 15% off