1、 Collection of SANS standards in electronic format (PDF) 1. Copyright This standard is available to staff members of companies that have subscribed to the complete collection of SANS standards in accordance with a formal copyright agreement. This document may reside on a CENTRAL FILE SERVER or INTRA
2、NET SYSTEM only. Unless specific permission has been granted, this document MAY NOT be sent or given to staff members from other companies or organizations. Doing so would constitute a VIOLATION of SABS copyright rules. 2. Indemnity The South African Bureau of Standards accepts no liability for any
3、damage whatsoever than may result from the use of this material or the information contain therein, irrespective of the cause and quantum thereof. ISBN 978-0-626-21380-0 SANS 24774:2008Edition 1ISO/IEC TR 24774:2007Edition 1SOUTH AFRICAN NATIONAL STANDARD Software and systems engineering Life cycle
4、management Guidelines for process description This national standard is the identical implementation of ISO/IEC TR 24774:2007 and is adopted with the permission of the International Organization for Standardization and the International Electrotechnical Commission. Published by Standards South Afric
5、a 1 dr lategan road groenkloof private bag x191 pretoria 0001 tel: 012 428 7911 fax: 012 344 1568 international code + 27 12 www.stansa.co.za Standards South Africa SANS 24774:2008 Edition 1 ISO/IEC TR 24774:2007 Edition 1 Table of changes Change No. Date Scope National foreword This South African s
6、tandard was approved by National Committee StanSA SC 71C, Information technology ICT systems and software engineering, in accordance with procedures of Standards South Africa, in compliance with annex 3 of the WTO/TBT agreement. This SANS document was published in May 2008. Reference numberISO/IEC T
7、R 24774:2007(E)ISO/IEC 2007TECHNICAL REPORT ISO/IECTR24774First edition2007-09-01Software and systems engineering Life cycle management Guidelines for process description Ingnierie du logiciel et des systmes Gestion du cycle de vie Lignes directrices pour la description des procds SANS 24774:2008Thi
8、s s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 24774:2007(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 t
9、he typefaces which are embedded are licensed to and installed on the computer performing 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
10、Adobe Systems Incorporated. Details of the software products used to create this PDF 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
11、 unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2007 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
12、electronic or mechanical, including photocopying and microfilm, without permission in 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 copyright
13、iso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2007 All rights reservedSANS 24774:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 24774:2007(E) ISO/IEC 2007 All rights reserved iiiForeword ISO (the International Or
14、ganization 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 technical committees established by the
15、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 take part in the work. In the field of info
16、rmation 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 International Standards. Draft Internati
17、onal 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 technical committee may propose the publica
18、tion 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 for any other reason there is the future b
19、ut 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). Technical Reports of types 1 and 2 are su
20、bject 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 useful. Attention is drawn to the possibil
21、ity 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 3, was prepared by Joint Technical Committee ISO/IEC JTC 1, Information t
22、echnology, Subcommittee SC 7, Software and systems engineering. SANS 24774:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 24774:2007(E) iv ISO/IEC 2007 All rights reservedIntroduction A number of international, national and in
23、dustry 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 processes. Uniform description of processes across process referen
24、ce 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 appropriate forms of process description and apply them in a consist
25、ent 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 prescription. The guidelines in this Technical Report can be appli
26、ed to any process model developed for any purpose. They have been made publicly available as a Technical Report with the intention of establishing a uniform description of processes across all process models, from all sources, for all purposes. SANS 24774:2008This s tandard may only be used and prin
27、ted by approved subscription and freemailing clients of the SABS .TECHNICAL REPORT ISO/IEC TR 24774:2007(E) ISO/IEC 2007 All rights reserved 1Software and systems engineering Life cycle management Guidelines for process description 1 Scope This Technical Report provides guidelines for the descriptio
28、n of processes by identifying descriptive attributes and rules for their formulation. It characterizes the following attributes of process description: title; purpose; outcomes; activities; tasks. This Technical Report does not describe how processes are composed or otherwise aggregated into larger
29、frameworks or architectures. NOTE Future work may set out rules for guiding standards developers in formulating the definition, scope, granularity, decomposition, scale and number of processes. The intended audience for this Technical Report is the editors, working group members, reviewers and other
30、 participants in the development of process standards and technical reports. It is intended that they will select the process description attributes suitable for their project from those described in this Technical Report. It is further intended that, having selected the appropriate attributes, read
31、ers of this Technical Report will apply them in a manner consistent with the guidance provided by this Technical Report. 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
32、interest groups, professional standards, researchers and process assessors. These process models may be for the purpose of process definition, implementation or assessment. 2 Background Within the International Standards arena, the definition of life cycle processes for systems and software falls wi
33、thin the scope of ISO/IEC JTC 1/SC 7/WG 7. The existing International Standards in this area are ISO/IEC 12207, Information technology Software life cycle processes, and ISO/IEC 15288, Systems engineering System life cycle processes. Other International Standards, such as ISO/IEC 15939, Systems and
34、software engineering Measurement process, and ISO/IEC 16085, Systems and software engineering Life cycle processes Risk management, provide further characterization of a single life cycle process by elaborating the process attributes and levying specific requirements on the execution of the process.
35、 The decomposition is described by use of the activity attribute. When instantiated for an organization or project, other details 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
36、 Standard in this area is ISO/IEC 15504-2, Information technology Process assessment Part 2: Performing an assessment. ISO/IEC 15504-2 provides requirements for assessing capability of SANS 24774:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the
37、SABS .ISO/IEC TR 24774:2007(E) 2 ISO/IEC 2007 All rights reservedprocesses defined in external process models; processes may 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 stat
38、ed in ISO/IEC 15504-2. NOTE 1 In addition to the attributes described in this Technical Report, ISO/IEC 15504 defines and uses the attribute Work Product. A work product is an artefact associated with the execution of a process (ISO 9000). There are four generic product categories as follows: servic
39、es (e.g. operation); software (e.g. computer program, documents, information, contents); hardware (e.g. computer, device); processed materials. NOTE 2 In addition to the attributes described in this Technical Report, ISO/IEC 15504 defines and uses the attribute Assessment Indicator. An assessment in
40、dicator is a source of objective evidence used to support an assessors judgement in rating process attributes. Examples include work products, practices and resources. ISO/IEC JTC 1/SC 7/WG 19 covers the fields of Open Distributed Processing and Modelling Languages. The International Standards devel
41、oped in that working group provide notations that may be useful in detailed process description for other purposes. The goals and objectives of performing a process can be described by using the attributes of title, purpose and outcomes. These attributes are used to describe intended results without
42、 the necessity of performing structural decomposition of the process. Processes defined using title, purpose and outcomes provide a common starting point for process implementation and process assessment. Not all attributes need to be treated in all standards. Some standards will treat only process
43、title, purpose and outcomes, leaving the activities for further elaboration by other standards. 3 Characterizing the attributes 3.1 Introduction To enable uniform description additional characterization of the attributes is helpful. The remainder of this Technical Report provides that characterizati
44、on. The process attributes to be used by International Standards developed by SC 7 are as follows. The title conveys the scope of the process as a whole. The purpose describes the goal of performing the process. The outcomes express the observable results expected from the successful performance of
45、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 with
46、in an activity. 3.2 The title attribute The title of a process is a short noun phrase intended to summarize the scope of the process, identify the principal concern of the process, and distinguish it from other processes within the scope of a process model. Because of the latter criterion, it may so
47、metimes be necessary to change the title of a process. For example, one might have a “software design process” which is later renamed as a “software detailed design process” to distinguish it from a newly-invented “software architectural design process”. NOTE Process descriptions may be used both to
48、 describe generic objects of a particular type (for example “design screen layout”), and to describe a particular instance of a generic type (for example “design layout of screen a”). For a process model or a standard the type description is sufficient, but in other cases (for example project planni
49、ng) generic process types are instantiated with respect to resources and time. When both generic types and particular instances are described, in order to differentiate between the two a typographical convention may be adopted (for example the title of the specific instance may be set in italic font). SANS 24774:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 24774:2007(E) ISO/IEC 2007 All rights reserved 33.3 The purpose at
