ISO/IEC TR 24774:2010 pdf – Systems and software engineering — Life cycle management — Guidelines for process description.
1 Scope This Technical Report provides guidelines for the description of processes by identifying descriptive elements and rules for their formulation. It characterizes the following elements of process description: ⎯ Title; ⎯ Purpose; ⎯ Outcomes; ⎯ Activities; ⎯ Tasks; ⎯ Information items. In addition process views are described. It does not describe how processes are composed or otherwise aggregated into larger frameworks or architectures. 2 Terms and definitions For the purposes of this document, the following terms and definitions apply. 2.1 activity set of cohesive tasks of a process [ISO/IEC 15288:2008] 2.2 information item separately identifiable body of information that is produced and stored for human use during a system or software life cycle [ISO/IEC 15289:2006] 2.3 life cycle evolution of a system, product, service, project or other human-made entity from conception through retirement [ISO/IEC 15288:2008]
2.4 life cycle model framework of processes and activities concerned with the life cycle that may be organized into stages, which also acts as a common reference for communication and understanding [ISO/IEC 15288:2008] 2.5 process set of interrelated or interacting activities which transforms inputs into outputs [ISO 9000:2005] 2.6 process purpose high level objective of performing the process and the likely outcomes of effective implementation of the process NOTE The implementation of the process should provide tangible benefits to the stakeholders. [ISO/IEC 12207:2008] 2.7 process outcome observable result of the successful achievement of the process purpose [ISO/IEC 12207:2008] 2.8 product result of a process [ISO 9000:2005] 2.9 system combination of interacting elements organized to achieve one or more stated purposes [ISO/IEC 15288:2008] 2.10 task requirement, recommendation, or permissible action, intended to contribute to the achievement of one or more outcomes of a process [ISO/IEC 15288:2008] 2.11 view representation of a whole system from the perspective of a related set of concerns [ISO/IEC 42010:2007, IEEE Std 1471-2000] NOTE In standards being developed in ISO/IEC JTC 1/SC 7, the “system” (system of processes) referenced in the definition is the collection of system and software life cycle processes provided by ISO/IEC 15288 and ISO/IEC 12207. 2.12 viewpoint specification of the conventions for constructing and using a view [ISO/IEC 42010:2007, IEEE Std 1471-2000]
NOTE 1 A viewpoint is a pattern or template from which to develop individual views by establishing the purposes and audiences for a view, and the techniques for its creation and analysis. NOTE 2 For a detailed explanation of view and viewpoint and how they can be defined and used, see ISO/IEC 42010, Recommended practice for architectural description of software-intensive systems. 3 Characterizing the elements 3.1 Introduction To enable uniform description additional characterization of the elements is helpful. The remainder of this Technical Report provides that characterization. This Technical Report describes the following process elements: ⎯ The title is a descriptive heading for a process; ⎯ The purpose describes the goal of performing the process; ⎯ The outcomes express the observable results expected from the successful performance of the process; ⎯ The activities are a list of actions that may be used to achieve the outcomes. Each activity may be further elaborated as a grouping of related lower level actions; ⎯ The tasks are specific actions that may be performed to achieve an activity. Multiple related tasks are often grouped within an activity; ⎯ The information items are separately identifiable bodies of information produced and stored for human use during a system or software life cycle. To prevent confusion and to encourage consistency the use of alternative terms for these elements is strongly discouraged. Figure 1 is a UML representation, adapted from Figure C.1 of ISO/IEC 15288:2008, depicting the relationships among the elements of a process as discussed in this International Technical Report. NOTE A process view has the same component entities. Annex A presents an example of a process described using the guidelines in this Technical Report.