BS ISO IEC IEEE 24774-2021 pdf free download – Systems and software engineering — Life cycle management — Specification for process description.
Generally, several software or systems engineering processes are performed concurrently during a lifecycle stage.However, concurrent activities (e.g.installation and quality assurance inspections) are notnecessarily part of the same process, since their purpose, resources, methods, outputs, and outcomesare different.
Process descriptions may be used either to describe generic processes (for example “projectmanagement process”) or to describe a particular instance of a generic type (for example “projectmanagement process for project A”).For specific process descriptions, generic process descriptionsmay 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 developa process model.Annex B provides a technique for demonstration of process traceability betweenelements, using an example process from Annex A.
Processes are often combined to form a process model (framework of related processes).ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, for example, provide life cycle process reference modelsfor systems and software in which outcomes are defined and activities grouped for generic life cycleprocess description. Based on ISO/IEC/IEEE 15288:2015，Annex A and lSo/IEC/IEEE 12207:2017,Annex A, organizations or projects can apply process tailoring to suit the nature of the effort.
NOTE4 ISO/PAS 19450 specifies concepts，semantics,and syntax of Object-Process Methodology as amodelling paradigm and language for producing conceptual models at various extents of detail.
Various schemas for characterizing and evaluating process maturity, capability or quality are in use.These schemas typically distinguish between levels of process performance and involve processimprovement. Process levels can involve following the process repeatedly to successfully achieve itsoutcome or produce specified output, and automating and improving the process.The choice of detailsin the process description can be used to characterize the process description at a certain level ofprocess maturity, capability or quality.
NOTE5 ISO/IEC 33020 defines a process measurement framework for the assessment of process capability.
5.3 Process description – required elements
5.3.1General
A process description can include the elements as shown in Figure 2.The minimum required elementsfor a process description shall be the name, purpose, and outcomes. Optional elements, such as outputs,activities,and tasks, may be included in process descriptions.
The goals and objectives of performing a process shall be described by using the elements of name,purpose, and outcomes. These elements are used to describe intended results without the necessityof performing structural decomposition of the process. Processes defined using name, purpose, andoutcomes provide a common starting point for process implementation and process assessment.
NOTE ISO/IEC/IEEE 15288:2015, Figure D.1 and ISO/IEC/IEEE 12207:2017， Figure D.1 show a processconstruct. ISO/IEC/IEEE 24748-1:2018,Annex A also describes process elements.
To enable uniform description, 5.3.2 to 5.3.4 contain additional requirements for the process elements.
5.3.2 Process name
The name of a process description shall be stated as a short noun phrase that presents a descriptive heading for the process. The name identifies the principal concern of the process and distinguishes the process from other processes in the model. Because of the latter criterion, it may sometimes be necessary to tailor the name of a process. For example, one may have a “software architecture process” which is later refined as a “software detailed design process” or “data architecture process” or “interface architecture process.” Process names should end in the word process.BS ISO IEC IEEE 24774 pdf download.