ISO IEC IEEE 24774-2021 Systems and software engineering — Life cycle management — Specification for process description

ISO IEC IEEE 24774-2021 Systems and software engineering — Life cycle management — Specification for process description. 3.11 process outcome observable result of the successful achievement of the process purpose (3.12) [SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.34] 3.12 process purpose high-level objective of performing the process (3.8) and the likely outcomes of effective implementation of the process [SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.35, modified — Note 1 to entry has been removed.] 3.13 process reference model model comprising definitions of processes (3.8) in a domain of application described in terms of process purpose (3.12) and outcomes, together with an architecture describing the relationships between the processes [SOURCE: ISO/IEC 33001:2015, 3.3.16] 3.14 process tailoring making, altering, or adapting a process (3.8) description for a particular end EXAMPLE A project tailors its defined process from the organization’s set of standard processes to meet the objectives, constraints, and environment of the project. 3.15 process view description of how a specified purpose and set of outcomes can be achieved by employing the activities (3.1) and tasks (3.20) of existing processes (3.8) [SOURCE: ISO/IEC/IEEE 15026-1:2019, 3.2.2, modified — “may” has been changed to “can”; note 1 to entry has been removed.] 3.16 product result of a process (3.8) [SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.36, modified — Note 1 to entry has been removed.] 3.17 stage period within the life cycle (3.4) of an entity that relates to the state of its description or realization [SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.58, modified — Notes 1 and 2 to entry have been removed.] 3.18 system combination of interacting elements organized to achieve one or more stated purposes [SOURCE: ISO/IEC/IEEE 15288:2015, 4.1.46, modified — Notes 1, 2 and 3 to entry have been removed.] 3.19 tailoring process (3.8) by which individual requirements in specifications, standards, and related documents are evaluated and made applicable to a specific project by selection, and in some exceptional cases, modification of existing or addition of new requirements Process descriptions may be used either to describe generic processes (for example “project management process”) or to describe a particular instance of a generic type (for example “project management process for project A”). For specific process descriptions, generic process descriptions may be instantiated with respect to roles or responsibilities, resources, required inputs and outputs, constraints and controls, and time. Annex A provides examples of process descriptions used to develop a process model. Annex B provides a technique for demonstration of process traceability between elements,...