BS ISO IEC IEEE 24774 pdf free download

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 life cycle stage. However, concurrent activities (e.g. installation and quality assurance inspections) are not necessarily part of the same process, since their purpose, resources, methods, outputs, and outcomes are different. 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, 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 models for systems and software in which outcomes are defined and activities grouped for generic life cycle process description. Based on ISO/IEC/IEEE 15288:2015, Annex A and ISO/IEC/IEEE 12207:2017, Annex A, organizations or projects can apply process tailoring to suit the nature of the effort. NOTE 4 ISO/PAS 19450 specifies concepts, semantics, and syntax of Object-Process Methodology as a modelling 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 process improvement. Process levels can involve following the process repeatedly to successfully achieve its outcome or produce specified output, and automating and improving the process. The choice of details in the process description can be used to characterize the process description at a certain level of process maturity, capability or quality. NOTE 5 ISO/IEC 33020 defines a process measurement framework for the assessment of process capability. 5.3 Process description – required elements 5.3.1 General A process description can include the elements as shown in Figure 2. The minimum required elements for 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 necessity of performing structural decomposition of the process. Processes defined using name, purpose, and outcomes 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 process construct. ISO/IEC/IEEE 24748-1:2018, Annex A also describes 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. Wordy noun-verb or verb-noun phrases can get confused with process activities and often represent an attempt to summarize the purpose or process so that the name can stand for the purpose. A descriptive noun phrase – the name of the process – is more useful. The intent is to give a name, not a summary. NOTE Although the term “process name” is preferred and used throughout this document, “process title” is an acceptable alternative. 5.3.3 Process purpose The purpose element of the process shall be stated as one or more related high-level goals for performing the process. In cases where processes seem to overlap, the purpose element should be used to characterize the scope or bounds of the process. Whenever possible, the purpose element should be succinctly captured in a single sentence. Summarizing the activities or outcomes of the process in the purpose statement should be avoided. Use of the conjunction “and” to connect multiple clauses should be avoided as it would indicate that the description is being written as an aggregation of marginally related outcomes rather than as a statement of a single purpose. The purpose element shall begin with the words, “The purpose of the xxx process is… “. The phrase, “in order to” may be useful in recording the objective of the process. Further explanations of the purpose of a process can be placed in informative text or notes.BS ISO IEC IEEE 24774 pdf download.