1、 Reference number ISO/IEC TR 24774:2010(E) ISO/IEC 2010TECHNICAL REPORT ISO/IEC TR 24774 Second edition 2010-09-15Systems and software engineering Life cycle management Guidelines for process description Ingnierie du logiciel et des systmes Gestion du cycle de vie Lignes directrices pour la descript
2、ion des processus ISO/IEC TR 24774:2010(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer perform
3、ing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF
4、file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Sec
5、retariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2010 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in
6、 writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2010 All rights reservedI
7、SO/IEC TR 24774:2010(E) ISO/IEC 2010 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 2 Terms and definitions .1 3 Characterizing the elements.3 3.1 Introduction3 3.2 The title element 4 3.3 The purpose element 4 3.4 The outcomes element5 3.5 The activities element .7 3.6 The
8、 task element .7 3.7 The information item element 8 3.8 Use of notes .9 4 Using process views.9 4.1 Introduction9 4.2 The process view concept9 4.3 Process viewpoint.10 4.4 Process view10 Annex A (informative) Example process description11 A.1 Introduction11 A.2 Disposal process.11 A.2.1 Purpose11 A
9、.2.2 Outcomes.11 A.2.3 Activities and tasks .11 Annex B (informative) Example process view .13 B.1 Introduction13 B.2 Specialty engineering process view13 B.2.1 Purpose13 B.2.2 Outcomes.13 B.2.3 Processes, activities and tasks .14 Bibliography15 ISO/IEC TR 24774:2010(E) iv ISO/IEC 2010 All rights re
10、servedForeword 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
11、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 tak
12、e part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare
13、International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. In exceptional circumstances, the joint tec
14、hnical committee may propose the publication of a Technical Report of one of the following types: type 1, when the required support cannot be obtained for the publication of an International Standard, despite repeated efforts; type 2, when the subject is still under technical development or where fo
15、r any other reason there is the future but not immediate possibility of an agreement on an International Standard; type 3, when the joint technical committee has collected data of a different kind from that which is normally published as an International Standard (“state of the art”, for example). T
16、echnical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether they can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or us
17、eful. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC TR 24774, which is a Technical Report of type 1/2/3, was prepared by Joint Tech
18、nical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering. This second edition cancels and replaces the first edition (ISO/IEC TR 24774:2007), which has been technically revised. ISO/IEC TR 24774:2010(E) ISO/IEC 2010 All rights reserved vIntroduction
19、For an organization to function effectively, it has to determine and manage numerous linked activities. An activity or set of activities using resources, and managed in order to enable the transformation of inputs into outputs, can be considered a process. Often the output from one process forms the
20、 input to the next. A number of international, national and industry standards describe process reference models. The process descriptions used in such models vary in format, content and level of prescription. The purpose of this Technical Report is to encourage uniformity in the description of proc
21、esses. Uniform description of processes across process reference models allows the combination of processes from different reference models, eases the development of new models and facilitates comparison of models. In order for future standards and revisions of current standards to select the approp
22、riate forms of process description and apply them in a consistent fashion, it is desirable to develop a common characterization of all of these forms of process description. This Technical Report presents guidelines for the description of processes in terms of their format, content and level of pres
23、cription. Within the International Standards arena the definition of life cycle processes for systems and software falls within the scope of ISO/IEC JTC 1/SC 7/WG 7. The existing International Standards in this area are ISO/IEC 12207, Software life cycle processes, and ISO/IEC 15288, System life cyc
24、le processes. The information items associated with these process definitions are given in ISO/IEC 15289, Content of systems and software life cycle process information products (Documentation). Other International Standards, such as ISO/IEC 15939, Measurement process, and ISO/IEC 16085, Risk manage
25、ment, provide further characterization of a single life cycle process by elaborating the process elements and levying specific requirements on the execution of the process. The decomposition is described by use of the activity element. When instantiated for an organization or project, other details
26、are added (entrance/exit criteria, actors, artefacts). The assessment of process capability falls within the scope of ISO/IEC JTC 1/SC 7/WG 10. The existing International Standard in this area is ISO/IEC 15504-2, Process assessment Performing an assessment. It provides requirements for assessing the
27、 capability of processes defined in external process models; processes can be assessed providing there is a description of them in terms of Title, Purpose, and Outcomes and the description satisfies the criteria for a “process reference model” as stated in ISO/IEC 15504-2. In addition to the element
28、s described in this Technical Report, ISO/IEC 15504 defines and uses the element Assessment Indicator. An assessment indicator is a source of objective evidence used to support an assessors judgement in rating process elements. Examples include work products, practices and resources. ISO/IEC JTC 1/S
29、C 7/WG 19 covers the fields of Open Distributed Processing and Modelling Languages. The International Standards developed in that working group provide notations that might be useful in detailed process description for other purposes. The guidelines in this Technical Report are those applied in ISO/
30、IEC JTC 1/SC 7. They align with those used in ISO/TC 176 (the committee responsible for ISO 9001). The guidelines can be applied to any process model developed for any purpose. The guidelines have been made publicly available as a Technical Report with the intention of establishing a uniform descrip
31、tion of processes across all process models, from all sources, for all purposes. The intended audience for this Technical Report is the editors, working group members, reviewers and other participants in the development of process standards and technical reports. It is intended that they will select
32、 the process description elements suitable for their project from those described in this Technical Report. It is further intended that, having selected the appropriate elements, users of this Technical Report will apply them in a manner consistent with the guidance provided by this Technical Report
33、. This Technical Report is also intended for use by all parties that define process models, for example other international standards groups, national standards, sector or special interest groups, professional standards groups, researchers, process assessors. These process models can be for the purp
34、ose of process definition, implementation or assessment. TECHNICAL REPORT ISO/IEC TR 24774:2010(E) ISO/IEC 2010 All rights reserved 1Systems and software engineering Life cycle management Guidelines for process description 1 Scope This Technical Report provides guidelines for the description of proc
35、esses 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 other
36、wise 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 p
37、roduced 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 ISO/IEC TR 24774:2010(E) 2 ISO/IEC 2010 All rights reserved2.4 l
38、ife 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 o
39、utputs 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 re
40、sult 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,
41、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“
42、(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 ISO/IEC TR 24774:2010
43、(E) ISO/IEC 2010 All rights reserved 3NOTE 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 b
44、e 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 provide
45、s 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; Th
46、e 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;
47、 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 representati
48、on, 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 Tec
49、hnical Report. ISO/IEC TR 24774:2010(E) 4 ISO/IEC 2010 All rights reservedProcess Name, Purpose, Outcome(s) Activity Name Task 1 11 0* 1* 0* Information item 1 0* NameFigure 1 UML representation of the component entities of a process Not all elements need to be treated in all standards. Some standards will treat only process Title, Purpose, and Outcomes, for example, leaving the activities for further elaboration by other standards. The goals and objectives of performing a proces
