ISO/IEC 29110-5-6-4:2025

International
Standard
ISO/IEC
29110-5-6-4
First edition
Systems and software
2025-03
engineering — Life cycle profiles for
very small entities (VSEs) —
Part 5-6-4:
Systems engineering guidelines for
the generic Advanced profile
Reference number
© ISO/IEC 2025
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 at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2025 – All rights reserved
ii
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3  Terms and definitions . 1
4 Conventions and abbreviated terms . 5
4.1 General .5
4.2 Naming, diagramming and definition conventions .5
4.3 Notation used to document new processes, additions and modifications to the
processes of the Intermediate profile .6
4.4 Abbreviated terms .7
5 Systems thinking . 8
6 Overview . 8
7 Technical management (TM) process . 10
7.1 TM process purpose.10
7.2 TM process outcomes .10
7.3 TM roles involved .11
7.4 TM process description .11
7.4.1 TM diagram .11
7.4.2 TM activities . 12
8 Project management (PM) process . 19
8.1 PM process purpose .19
8.2 PM process outcomes .19
8.3 PM roles involved . 20
8.4 PM process description . 20
8.5 PM diagram. 20
8.5.1 PM activities .21
9  System definition and realization (SR) process .31
9.1 SR process purpose .31
9.2 SR process outcomes .31
9.3 SR roles involved .32
9.4 SR process description .32
9.4.1 SR diagram . .32
9.4.2 SR activities . 33
10 Acquisition management process (AM) .48
10.1 AM process purpose . 48
10.2 AM process outcome . 48
10.3 AM roles involved . . 48
10.4 AM process description . 48
10.4.1 AM diagram. 48
10.4.2 AM activities . 49
11 System transition and disposal process (SYTD) .52
11.1 SYTD process purpose .52
11.2 SYTD process outcomes .52
11.3 SYTD roles involved .52
11.4 SYTD process description.52
11.4.1 SYTD diagram .52
11.4.2 SYTD activities . 53
12 Roles .57

© ISO/IEC 2025 – All rights reserved
iii
13 Work product description .59
13.1 States of work products .59
13.2 Description of work products . 60
14 System tools .79
14.1 System tools overview . 79
14.2 Project management process. 79
14.3 System definition and realization process . 79
Annex A (informative) Systems engineering deployment packages .80
Bibliography .82

© ISO/IEC 2025 – 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).
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/IEC JTC 1, Information technology,
Subcommittee SC 7, Software and systems engineering.
A list of all parts in the ISO/IEC 29110 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.

© ISO/IEC 2025 – All rights reserved
v
Introduction
0.1 Introduction to the ISO/IEC 29110 series
Very small entities (VSEs) around the world are creating valuable products and services. For the purpose of
ISO/IEC 29110 series, a VSE is an enterprise, organization (e.g. government agency, non-profit organization),
department or project having up to 25 people. Many VSEs develop and/or maintain systems and software
components used in those systems, either as independent products or incorporated in the larger systems.
Due to this a recognition of VSEs as suppliers of high-quality products is required.
VSEs around the world are creating valuable products and services. According to the World Bank, small
and medium-sized enterprises (SMEs) account for about 90 % of enterprises worldwide. According to the
Organisation for Economic Co-operation and Development (OECD), SMEs represent 99 % of all businesses
and generate about 60 % of employment. Almost one person out of three is employed in a micro firm with less
than 10 employees. The European Union reports that micro firms, with fewer than 10 persons, account for
93,5 % of all enterprises and small firms, with 10 to 49 employees, account for 5,5 % of all enterprises. The
challenge facing OECD governments is to provide a business environment that supports the competitiveness
of this large heterogeneous business population and that promotes a vibrant entrepreneurial culture.
From studies and surveys conducted, it is clear that the majority of International Standards do not address
the needs of VSEs. Implementation of and conformity with these standards is difficult, if not impossible.
Consequently, VSEs have no, or very limited, ways to be recognized as entities that produce quality systems/
system elements including software in their domain. Therefore, VSEs are excluded from some economic
activities.
It has been found that VSEs find it difficult to relate International Standards to their business needs and to
justify the effort required to apply standards to their business practices. Most VSEs can neither afford the
resources, in terms of the number of employees, expertise, budget and time, nor do they see a net benefit in
establishing over-complex systems or software life cycle processes. To address some of these difficulties,
a set of guidelines has been developed based on a set of VSE characteristics. The guidelines are based on
subsets of appropriate standards processes, activities, tasks, and outcomes, referred to as Profiles. The
purpose of a profile is to define a subset of International Standards relevant to the VSEs' context; for example,
processes, activities, tasks, and outcomes of ISO/IEC/IEEE 12207 for software; and processes, activities,
tasks, and outcomes of ISO/IEC/IEEE 15288 for systems; and information products (documentation) of
ISO/IEC/IEEE 15289 for software and systems.
VSEs can achieve recognition through implementing a profile and by being audited against the specifications
of the ISO/IEC 29110 series.
The ISO/IEC 29110 series can be applied at any phase of system or software development within a life cycle.
This series is intended to be used by VSEs that do not have experience or expertise in adapting/tailoring
ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288 standards to the needs of a specific project. VSEs that have
expertise in adapting/tailoring ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288 are encouraged to use those
standards instead of ISO/IEC 29110.
The ISO/IEC 29110 series is intended to be used with any life cycle such as waterfall, iterative, incremental,
evolutionary or agile.
Systems, in the context of the ISO/IEC 29110 series, are typically composed of hardware and software
components.
The ISO/IEC 29110 series, targeted by audience, has been developed to improve system or software and/
or service quality, and process performance. Figure 1 describes the ISO/IEC 29110 series and positions the
parts within the framework of reference.

© ISO/IEC 2025 – All rights reserved
vi
Figure 1 — The ISO/IEC 29110 series
ISO/IEC 29110-1-1 introduces processes, life cycle and standardization concepts, the taxonomy (catalogue) of
ISO/IEC 29110 profiles and the ISO/IEC 29110 series. ISO/IEC 29110-1-1 also introduces the characteristics
and needs of a VSE, and clarifies the rationale for specific profiles, documents, standards and guidelines.
ISO/IEC 29110-1-2 defines the terms common to the ISO/IEC 29110 series. ISO/IEC 29110-1-1 and
ISO/IEC 29110-1-2 are targeted at VSEs and their customers, assessors, standards producers, tool vendors
and methodology vendors.
ISO/IEC 29110-2 introduces the concepts for systems and software engineering profiles for VSEs. It
establishes the logic behind the definition and application of profiles. For standardized profiles, it specifies
the elements common to all profiles (structure, requirements, conformity, and assessment). For domain-
specific profiles (profiles that are not standardized and developed outside of the ISO process), it provides
general guidance adapted from the definition of standardized profiles. ISO/IEC 29110-2 is targeted at profile
producers, tool vendors and methodology vendors.
ISO/IEC 29110-3 defines certification schemes, assessment guidelines and compliance requirements for
process capability assessment, conformity assessments, and self-assessments for process improvements.
ISO/IEC 29110-3 also contains information that can be useful to developers of certification and assessment
methods and developers of certification and assessment tools. ISO/IEC 29110-3 is addressed to people
who have direct involvement with the assessment process, for example, the auditor, certification and
accreditation bodies and the sponsor of the audit, who need guidance on ensuring that the requirements
for performing an audit have been met. ISO/IEC 29110-3 is targeted at VSEs and their customers, assessors,
accreditation bodies.
ISO/IEC 29110-4 provides the specifications for all generic profiles of the generic profile group that are based
on subsets of appropriate standards elements. ISO/IEC 29110-4 is targeted at VSEs, customers, standards
producers, tool vendors and methodology vendors.
ISO/IEC 29110-5 provides a management, engineering and service delivery guidelines for profiles of the
generic profile group. ISO/IEC 29110-5 is targeted at VSEs and their customers.

© ISO/IEC 2025 – All rights reserved
vii
ISO/IEC 29110-6 provides the specifications for specific profiles that are based on subsets of appropriate
standards elements. ISO/IEC 29110-6 is targeted at VSEs, customers, standards producers, tool vendors and
methodology vendors.
ISO/IEC 29110-7 provides a guideline for each profile of the specific profile group. ISO/IEC 29110-7 is
targeted at VSEs and their customers.
If a new profile is needed, ISO/IEC 29110-4, ISO/IEC 29110-6, ISO/IEC 29110-7 or ISO/IEC 29110-5, or all, can
be developed with minimal impact to existing documents.
These guidelines are oriented towards the management of more than one project in parallel with more than
one work team.
0.2 Introduction to this document
This document has been developed using the management and engineering guidelines from the systems
engineering Intermediate profile. Elements were added or modified (e.g. process, task, work product, role) to
support VSEs involved in the development of more than one project in parallel with more than one work team.
This document is intended to be used with any process, technique and method that enhances the VSE’s
stakeholder satisfaction and productivity.
The Advanced profile is the fourth profile of a four-profile systems engineering roadmap (i.e. Entry, Basic,
Intermediate and Advanced).
The outcomes and tasks are guidance, not requirements, for purposes of process assessment.
This document applies for the development of non-safety critical systems.
Using this document, a VSE can obtain benefits in the following aspects:
— systematic system definition and realization process is followed, that satisfies the acquirer needs and
helps ensure quality work processes are followed;
— management and monitoring of more than one project in parallel with more than one work team;
— reuse of existing system components (e.g. code and document) in new projects;
— continuous measurement and evaluation of projects;
— continuous evaluation and improvement processes;
— continuous sustainability and growth;
— support to customers in the disposal of a current system and installation of a new system.
Once the system, developed by a VSE, has been accepted by their customers, the VSE can provide after
delivery services by referring to ISO/IEC 29110-5-3.
To use this document, the VSE should ensure the following entry conditions:
— project needs and expectations are documented;
— feasibility of the project was performed;
— project team, including project manager and system engineer, assigned;
— goods, services and infrastructure to start the project are available.
In the context of systems engineering, that is the system definition and realization (SR) process, the group
that is part of the VSE responsible for developing software elements that are part of the system, should
use the management and engineering guidelines of the software engineering Advanced profile (ISO/
IEC TR 29110-5-1-4).
© ISO/IEC 2025 – All rights reserved
viii
To use this document, a VSE should be familiar with or have implemented ISO/IEC TR 29110-5-6-3, the
systems engineering Intermediate profile, for their system development projects.

© ISO/IEC 2025 – All rights reserved
ix
International Standard ISO/IEC 29110-5-6-4:2025(en)
Systems and software engineering — Life cycle profiles for
very small entities (VSEs) —
Part 5-6-4:
Systems engineering guidelines for the generic Advanced profile
1 Scope
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.
2 Normative references
This document has no normative references.
3  Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
Advanced profile
profile (3.14) targeted at VSEs which want to sustain and grow as a system (3.19) and/or software
development organization
[SOURCE: ISO/IEC 29110-1-2:2024, 3.3, modified — "competitive system" has been changed to "system".]
3.2
agreement
mutual acknowledgement of terms and conditions under which a working relationship is conducted
EXAMPLE Contract, memorandum of agreement.
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.4]

© ISO/IEC 2025 – All rights reserved
3.3
acquirer
stakeholder (3.18) that acquires or procures a product or service from a supplier
Note 1 to entry: Other terms commonly used for an acquirer are buyer, customer, owner, purchaser or internal/
organizational sponsor.
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.1]
3.4
Basic profile
profile (3.14) targeted at VSEs developing a single product by a single work team
[SOURCE: ISO/IEC 29110-1-2: 2024, 3.18]
3.5
business objective
strategy designed by senior management to ensure an organization's continued existence and enhance its
profitability, market share, and other factors influencing the organization's success
[SOURCE: ISO/IEC/IEEE 24765:2017, 3.444]
3.6
conditional process
process that may be mandatory under some specified conditions, may be optional under other specified
conditions, and may be out of scope or not applicable under other specified conditions
Note 1 to entry: These are to be observed if the specified conditions apply.
[SOURCE: ISO/IEC TR 29110-5-1-3:2017, 3.3]
3.7
critical system
product that is essential to the operation of a business or organization, whose sustained failure would result
in significant business impacts e.g. loss of revenue or loss of reputation
3.8
disposed system
system (3.19) that has been transformed (i.e. state change) by applying the disposal process
Note 1 to entry: A systems approach considers the total system and the total life cycle of the system. This includes all
aspects of the system throughout its life until the day users (3.24) depose of the system and the external enterprises
complete the handling of the disposed system products.
3.9
enabling system
system (3.19) that supports a system-of-interest during its life cycle stages but does not necessarily
contribute directly to its function during operation
EXAMPLE Production-enabling system, which is required when a system-of-interest enters the production stage.
Note 1 to entry: Each enabling system has a life cycle of its own. This document is applicable to each enabling system
when, in its own right, it is treated as a system-of-interest.
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.15]
3.10
Entry profile
profile (3.14) targeted at start-up VSEs (i.e. VSEs who started their operation less than 3 years) and/or at
VSEs working on small projects (e.g. project size of less than 6 person-months)
[SOURCE: ISO/IEC 29110-1-2:2024, 3.42]

© ISO/IEC 2025 – All rights reserved
3.11
generic profile group
profile (3.14) group applicable to VSEs (very small entities) that do not develop critical systems (3.7) or
software products
[SOURCE: ISO/IEC 29110-1-2:2024, 3.45]
3.12
Intermediate profile
profile (3.14) targeted at VSEs involved in the development of more than one project in parallel with more
than one work team
[SOURCE: ISO/IEC 29110-1-2:2024, 3.51]
3.13
operator
individual or organization that performs the operations of a system (3.19)
Note 1 to entry: The role of operator and the role of user (3.24) can be vested, simultaneously or sequentially, in the
same individual or organization.
Note 2 to entry: An individual operator combined with knowledge, skills and procedures can be considered as an
element of the system.
Note 3 to entry: An operator may perform operations on a system that is operated, or of a system that is operated,
depending on whether or not operating instructions are placed within the system boundary.
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.24]
3.14
profile
subset of appropriate standards’ processes and their outcomes, activities and tasks combined to accomplish
a particular function
Note 1 to entry: The base standards used to develop profiles for VSEs are ISO/IEC/IEEE 12207, ISO/IEC/IEEE 15288
and ISO/IEC/IEEE 15289.
3.15
process purpose
high-level objective of performing the process and the likely outcomes of effective implementation of the process
[SOURCE: ISO/IEC/IEEE 24774:2021, 3.12]
3.16
process outcome
observable result of the successful achievement of the process purpose (3.15)
[SOURCE: ISO/IEC/IEEE 24774:2021, 3.11]
3.17
small and medium enterprise
SME
enterprise which employs fewer than 250 persons
[SOURCE: ISO/IEC 29110-1-2:2024, 3.92]
3.18
stakeholder
individual or organization having a right, share, claim, or interest in a system (3.19) or in its possession of
characteristics that meet their needs and expectations
[SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.59, modified — EXAMPLE and note 1 to entry have been removed.]

© ISO/IEC 2025 – All rights reserved
3.19
system
arrangement of parts or elements that together exhibit a stated behaviour or meaning that the individual
constituents do not
Note 1 to entry: A system is sometimes considered as a product or as the services it provides.
Note 2 to entry: In practice, the interpretation of its meaning is frequently clarified by the use of an associative noun,
e.g. aircraft system. Alternatively, the word "system" is substituted simply by a context-dependent synonym, e.g.,
aircraft, though this potentially obscures a system principles perspective.
Note 3 to entry: A complete system includes all of the associated equipment, facilities, material, computer programs,
firmware, technical documentation, services and personnel required for operations and support to the degree
necessary for self-sufficient use in its intended environment.
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.46]
3.20
systems engineering management plan
SEMP
top level technical plan for managing the systems (3.19) engineering effort which defines how the technical
aspects of the project will be organized, structured, and conducted and how the systems engineering
processes will be controlled to provide a product that satisfies stakeholder (3.18) requirements
[SOURCE: ISO/IEC/IEEE 24748-4:2016, 4.14]
3.21
system-of-interest
SOI
system (3.19) whose life cycle is under consideration
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.48]
3.22
system structure
decomposition of a system-of-interest (3.21) into a set of interacting systems (3.19) and system elements
Note 1 to entry: The system structure is described in a system breakdown structure (SBS).
3.23
trade-off
decision-making actions that select from various requirements and alternative solutions on the basis of net
benefit to the stakeholders (3.18)
3.24
user
individual or group that interacts with a system (3.19) or benefits from a system during its utilization
Note 1 to entry: The role of user and the role of operator (3.13) are sometimes vested, simultaneously or sequentially,
in the same individual or organization.
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.53]
3.25
work breakdown structure
WBS
deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish
the project objectives and create the required deliverables
Note 1 to entry: The WBS can be an output or an input.
[SOURCE: ISO/IEC/IEEE 26511:2018, 3.1.42, modified — The abbreviated term and note 1 to entry have
been added.]
© ISO/IEC 2025 – All rights reserved
4 Conventions and abbreviated terms
4.1 General
Conventions for naming, diagramming, describing and defining profiles are defined in ISO/IEC 29110-2-1.
4.2  Naming, diagramming and definition conventions
The following process structure description and notation are used to describe the processes:
Process name – process identifier, followed by its abbreviation in parentheses “( )”.
Process purpose – the high-level objectives and results expected of the effective implementation of the
process. The implementation of the process should provide tangible benefits to the stakeholders.
Process outcomes - the process outcomes are identified by the abbreviation of the process name, followed by
the letter “O” and a consecutive number, for example PM.O1, SR.O2.
Input work products – work products required to perform the process and its corresponding source, which
can be another process or an external entity to the project, such as the acquirer. Input work products are
identified by the abbreviation of the process name.
Output work products – work products generated by the process and its corresponding destination, which
can be another process or an external entity to the project, such as an acquirer. Output work products are
identified by the abbreviation of the process name.
Internal work products – work products generated (i.e. output work product) and consumed (i.e. input work
product) by the process. Internal work products are identified by the abbreviation of the process name. An
internal work product is not reviewed or approved by the customer.
All work products’ names begin with capital letters. Some work products have one or more states attached
to the work product name surrounded by square brackets “[ ]” and separated by”,”. The work product state
may change during the process execution. See Clause 13 for the alphabetical listing of the work products, its
descriptions, possible states and the source of the work product. The source can be another process or an
external entity to the project, such as the acquirer.
Roles involved – names and abbreviation of the functions to be performed by project team members. Several
roles may be performed by a single person and one role may be assumed by several persons. Roles are
assigned to project participants based on the characteristics of the project. The role list is identified by the
abbreviation of the process name and shown as a two-column table. See Clause 12 for the alphabetical list of
the roles and required competencies description.
Diagram – graphical representation of the processes. The large round-edged rectangles indicate process
or activities, and the smaller square-edged rectangles indicate the work products. The directional or
bidirectional thick arrows indicate the major flow of information between processes or activities. The thin
directional arrows indicate the input or output work products. The notation used in the diagrams does not
imply the use of any specific process life cycle.
Activity – a set of cohesive tasks. A task is a requirement, recommendation, or permissible action, intended
to contribute to the achievement of one or more outcomes of a process. A process activity is the first level
of process workflow decomposition and the second one is a task. Activities are identified by process name
abbreviation followed by consecutive number and the activity name.
Activity description – each activity description is identified by the activity name and the list of related
outcomes surrounded by parenthesis “( )”. For example, PM.01 project planning (contributes to PM.O1,
PM.O5, PM.O6, and PM.O7) means that the activity PM.01 project planning contributes to the achievement
of the listed outcomes: PM.O1, PM.O5, PM.O6 and PM.O7. The activity description begins with the task
summary and is followed by the task descriptions table.

© ISO/IEC 2025 – All rights reserved
Task description - Each task description begins with an active verb (e.g. assign, test) and is followed by
an object (e.g. review the project plan). The task description doesn’t impose any technique or method to
perform it. The selection of the techniques or methods is left to the VSE or project team.
Tasks description tables contain four columns corresponding to:
— Role – the abbreviation of roles involved in the task execution.
— Task – description of the task to be performed. Each task is identified by activity ID and consecutive
number, for example PM.01.01, PM.01.02, and so on. A few numbered items are added to provide additional
information intended to assist the understanding or use of tasks.
— Input work products – work products needed to execute the task.
— Output work products – work products created or modified by the execution of the task.
NOTE 1 A conditional task is executed if its associated work product (e.g. software user documentation) is required
by the customer and listed in the delivery instructions. A conditional task statement is preceded with this text: " x)
Conditional task". A work product associated to a conditional task is identified as an ‘optional’ work product.
Organizational repository – list of work products to be saved in organizational repository; the configuration
management strategy should be applied to some of them.
NOTE 2 Tables used in process description are for presentation purpose only. The tables are not prescribing a
waterfall approach.
NOTE 3 The term ‘Advanced’ is using a capital ‘A’ to indicate an ISO/IEC 29110 profile (e.g. Advanced profile) while
the term ‘advanced’ is used when referring to something modern and highly developed.
4.3  Notation used to document new processes, additions and modifications to the processes
of the Intermediate profile
The Advanced profile has been designed to build upon the processes of the Intermediate profile such that,
when moving from the Intermediate profile to the Advanced profile, a VSE should only add to its existing
Intermediate profile processes the new processes (e.g., outcomes, activities, tasks, roles and work products)
described in this document.
Since, in the Advanced profile, there are additions and modifications to the Intermediate profile processes,
this document has been written such that it will be easy for a VSE to identify these additions and
modifications. The project management (PM) and system definition and realization (SR) processes, of the
Intermediate profile, have been complemented with additional outcomes, tasks and work products in a
context where a VSE is conducting more than one project in parallel with more than one work team. The
following notation is used to highlight the addition/deletion/modification to the Intermediate profile:
— added text:
— is underlined;
— except for the added new processes of the Advanced profile;
— deleted/modified text is struck out.
The Advanced profile has one new process that is not in the Intermediate profile: system transition and
disposal process (SYTD).
The purpose of the system transition and disposal process is to move the system, in an orderly and planned
manner, into the operational status. In this way, the system is functional and operable in the operational
environment of the customer to end the existence of a system element or system for a specified intended
use. At this time, the customer can appropriately handle, replace, or retire elements, by properly attending
to critical disposal needs (e.g. per an agreement, per organizational policy, or for environmental, safety,
security aspects).
© ISO/IEC 2025 – All rights reserved
The SYTD process is a conditional process. It is executed if a VSE is required, in the agreement (e.g. statement
of work), to install and/or dispose of a system at the customer operational environment. If this is the case,
this process is included in the scope of an audit or an assessment.
To facilitate the identification of additional abbreviations, roles and work products of the SYTD process
of the Advanced profile, these items are underlined. To facilitate reading, the SYTD process has not been
underlined.
The Advanced profile terminology has been aligned with ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 15289. The
following terms of old standards have been replaced with the new terms:
— “Statement of work”, “agreement” and “contract” have been replaced with “agreement”;
— work products are identified with a unique code WP.XX where XX is a sequential number in Clause 10.
These codes have not been used in the descriptions of activities and tasks to facilitate readability.
4.4 Abbreviated terms
ACQ acquirer
AM acquisition management
CUS customer
DES designer
DEV developper
PO purchase order
PM project management
PJM project manager
PROM proposal manager
SBS system breakdown structure
SDD system design document
SEMP systems engineering management plan
SMART specific, measurable, accepted, realistic and traced
SR system definition and realization
STK stakeholder
SUP supplier
SW software
SYS systems engineer
SYTD system transition and disposal
TM technical management
TCM technical manager
© ISO/IEC 2025 – All rights reserved
TPM technical performance management
VSE very small entity
V&V verification and validation
V&VE verification and validation engineer
WP work product
WT work team
5 Systems thinking
The traditional approach to solve a problem is called artisan. This approach focuses on dividing a problem
into s
...