IEEE 24774-2012 en Guide-Adoption of ISO IEC TR 24774 2010 Systems and Software Engineering-Life Cycle Management-Guidelines for Process Description (IEEE Compu.pdf

《IEEE 24774-2012 en Guide-Adoption of ISO IEC TR 24774 2010 Systems and Software Engineering-Life Cycle Management-Guidelines for Process Description (IEEE Compu.pdf》由会员分享，可在线阅读，更多相关《IEEE 24774-2012 en Guide-Adoption of ISO IEC TR 24774 2010 Systems and Software Engineering-Life Cycle Management-Guidelines for Process Description (IEEE Compu.pdf（34页珍藏版）》请在麦多课文档分享上搜索。

1、 IEEE Guide Adoption of ISO/IEC TR 24774:2010 Systems and Software Engineering Life Cycle ManagementGuidelines for Process Description Sponsored by the Software +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the

2、 Copyright Clearance Center. Copyright 2012 IEEE. All rights reserved. ivNotice to users Laws and regulations Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not imply compliance to any applicabl

3、e regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be const

4、rued as doing so. Copyrights This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practic

5、es and methods. By making this document available for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this document. Updating of IEEE documents Users of IEEE Standards documents should be aware that these documents may be superseded at any

6、 time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In o

7、rder to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE-SA Website at http:/standards.ieee.org/index.html or contact the IEEE at the address listed previously. For more information abo

8、ut the IEEE Standards Association or the IEEE standards development process, visit the IEEE-SA Website at http:/standards.ieee.org/index.html. Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/findstds/errata/index.html. Users are

9、encouraged to check this URL for errata periodically. Interpretations Current interpretations can be accessed at the following URL: http:/standards.ieee.org/findstds/interps/ index.html. Copyright 2012 IEEE. All rights reserved. vPatents Attention is called to the possibility that implementation of

10、this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has filed a statement of assuranc

11、e via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website http:/standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without compensation or under reas

12、onable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applicants desiring to obtain such licenses. Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not responsible for identifying Essential Pa

13、tent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonabl

14、e or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. Copyright 2012 IE

15、EE. All rights reserved. viParticipants At the time this guide was completed, the Life Cycle Processes Working Group had the following membership: James W. Moore, IEEE Computer Society Liaison to ISO/IEC JTC 1/SC 7 The following members of the individual balloting committee voted on this guide. Ball

16、oters may have voted for approval, disapproval, or abstention. Michael Adams Ed Addario Johann Amsenga Chris Bagge Charles Barest Juris Borzovs Pieter Botman Susan Burgess Sue Carroll Lawrence Catchpole Keith Chow Kenneth Costello Paul Croll Geoffrey Darnton Ronald Dean Thomas Dineen Sourav Dutta An

17、drew Fieldsend David Friscia David Fuschi Gregg Giesler Randall Groves John Harauz Mark Henley Rutger A. Heunks Werner Hoelzl Glenn Hoffman Robert Holibaugh Peter Hung Noriyuki Ikeuchi Atsushi Ito Mark Jaeger Cheryl Jones Piotr Karocki Yuri Khersonsky Fanny Klett Dwayne Knirk Thomas Kurihara Susan L

18、and J. Dennis Lawrence David Leciston Daniel Lindberg Wayne W. Manges Edward McCall William Milam Kathryn Moland James W. Moore Michael S. Newman Mark Paulk William Petit Annette Reilly Garry Roedler Keith Roseberry Terence Rout Sergio Santos Bartien Sayogo Robert Schaaf Maud Schlich David Schultz S

19、tephen Schwarm Gil Shultz Carl Singer James Sivak Kapil Sood Luca Spotorno Friedrich Stallinger Thomas Starai Walter Struppler Gerald Stueve Marcy Stutzman Thomas Tullia John Vergis David Walden Charlene Walrad John Walz Stephen Webb Jian Yu Oren Yuen Janusz Zalewski Daidi Zhong Copyright 2012 IEEE.

20、 All rights reserved. viiWhen the IEEE-SA Standards Board approved this guide on 29 March 2012, it had the following membership: Richard H. Hulett, Chair John Kulick, Vice Chair Robert M. Grow, Past Chair Judith Gorman, Secretary Satish Aggarwal Masayuki Ariyoshi Peter Balma William Bartley Ted Burs

21、e Clint Chaplin Wael Diab Jean-Philippe Faure Alexander Gelman Paul Houz Jim Hughes Young Kyun Kim Joseph L. Koepfinger* David J. Law Thomas Lee Hung Ling Oleg Logvinov Ted Olsen Gary Robinson Jon Walter Rosdahl Mike Seavey Yatin Trivedi Phil Winston Yu Yuan * Member Emeritus Also included are the f

22、ollowing nonvoting IEEE-SA Standards Board liaisons: Richard DeBlasio, DOE Representative Michael Janezic, NIST Representative Catherine Berger IEEE Senior Standards Program Manager, Document Development Malia Zaman IEEE Standards Program Manager, Technical Program Development Jodi Haasz IEEE Senior

23、 Program Manager, International Standards Programs Copyright 2012 IEEE. All rights reserved. viiiIntroduction This introduction is not part of IEEE Std 24774-2012, IEEE GuideAdoption of ISO/IEC TR 24474:2010, Systems and Software EngineeringLife Cycle ManagementGuidelines for Process Description. Th

24、e IEEE Software and Systems Engineering Standards Committee (S2ESC) has undertaken a long-term program to harmonize its standards with those of ISO/IEC JTC 1/SC 7, the international standards committee for software and systems engineering. In areas of overlap, one organization sometimes adopts the r

25、elevant standard from the other organization, or the two organizations cooperate to produce a single joint standard. In this case, S2ESC has chosen to adopt a relevant document from SC 7. This IEEE standard is an adoption of ISO/IEC TR 24774:2010. References to some ISO/IEC standards should be consi

26、dered as references to the identical IEEE standard: ISO/IEC/IEEE 12207:2008 is identical to ISO/IEC 12207:2008 ISO/IEC/IEEE 15288:2008 is identical to ISO/IEC 15288:2008 ISO/IEC/IEEE 15289:2011 is identical to ISO/IEC 15289:2011 IEEE 15939:2008 is the identical adoption of ISO/IEC 15939:2007 ISO/IEC

27、/IEEE 16085:2006 is identical to ISO/IEC 16085:2006 IEEE 1471:2007 is the identical source of ISO/IEC 42010:2007Copyright 2012 IEEE. All rights reserved. ixContents of IEEE adoption of ISO/IEC TR 24474:2010 (E) ISO/IEC TR 24474:2010 . 1 Copyright 2012 IEEE. All rights reserved. 1IEEE Guide Adoption

28、of ISO/IEC TR 24474:2010 Systems and Software EngineeringLife Cycle ManagementGuidelines for Process Description IMPORTANT NOTICE: IEEE Standards documents are not intended to ensure safety, health, or environmental protection, or ensure against interference with or from other devices or networks. I

29、mplementers of IEEE Standards documents are responsible for determining and complying with all appropriate safety, security, environmental, health, and interference protection practices and all applicable laws and regulations. This IEEE document is made available for use subject to important notices

30、 and legal disclaimers. These notices and disclaimers appear in all publications containing this document and may be found under the heading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.” They can also be obtained on request from IEEE or viewed at http:/standard

31、s.ieee.org/IPR/disclaimers.html. Reference numberISO/IEC TR 24774:2010(E)ISO/IEC 2010TECHNICAL REPORTISO/IECTR24774Second edition2010-09-15Systems and software engineering Life cycle management Guidelines for process description Ingnierie du logiciel et des systmes Gestion du cycle de vie Lignes dir

32、ectrices pour la description 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 installe

33、d 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 Adobe Systems Incorporated. Details of the software products

34、 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 unlikely event that a problem relating to it is found, plea

35、se inform the Central Secretariat 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 microfi

36、lm, 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 v 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/IE

37、C 2010 All rights reserved ISO/IEC TR 24774:2010(E) ISO/IEC 2010 All rights reserved iiiContents PageForeword ivIntroduction.v1 Scope12 Terms and definitions .13 Characterizing the elements.33.1 Introduction33.2 The title element 43.3 The purpose element 43.4 The outcomes element53.5 The activities

38、element .73.6 The task element .73.7 The information item element 83.8 Use of notes .94 Using process views.94.1 Introduction94.2 The process view concept94.3 Process viewpoint.104.4 Process view10Annex A (informative) Example process description11A.1 Introduction11A.2 Disposal process.11A.2.1 Purpo

39、se 11A.2.2 Outcomes .11A.2.3 Activities and tasks .11Annex B (informative) Example process view .13B.1 Introduction13B.2 Specialty engineering process view13B.2.1 Purpose 13B.2.2 Outcomes .13B.2.3 Processes, activities and tasks .14Bibliography15ISO/IEC TR 24774:2010(E) iv ISO/IEC 2010 All rights re

40、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

41、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

42、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

43、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

44、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

45、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

46、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

47、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

48、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 F

49、or 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 input to the next. A number of international, national and industry standards describe process reference models. The process description