1、 IEEE Standard Adoption of ISO/IEC 15026-2:2011 Systems and Software EngineeringSystems and Software Assurance Part 2: Assurance Case 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. iv Copyright 2011 IEEE. All rights reserved. Introduction This introduction is not part of IEEE Std 15026-2-2011, IEEE StandardAdoption of ISO/IEC 15026-2:2011, Systems and Software EngineeringSystems and Software AssurancePart 2: Assurance Case. The IEEE Software and Sys
3、tems 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 relevant standard from t
4、he 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 15026-2:2011. References to some ISO/IEC standards should be considered as references to t
5、he 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 16085:2006 is identical to ISO/IEC 16085:2006 IEEE Std 15026-1-2011 is identical to ISO/IEC TR 15026-1:2010 It should be noted that IEEE is c
6、urrently processing a standard that will be identical to the following ISO/IEC standard: ISO/IEC/IEEE 15289 will be identical to ISO/IEC 15289 when the former is approved. It should also be noted that IEEE is currently planning adoptions of the other parts of the 15026 series, namely, ISO/IEC 15026-
7、3 and ISO/IEC 15026-4, after they are published as ISO/IEC standards. It should further be noted that IEEE is currently planning to adopt ISO/IEC 25010:2011. Notice to users Laws and regulations Users of these documents should consult all applicable laws and regulations. Compliance with the provisio
8、ns of this standard does not imply compliance to any applicable 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 complia
9、nce with applicable laws, and these documents may not be construed 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-regulat
10、ion, standardization, and the promotion of engineering practices 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. v Copyright 2011 IEEE. All rights reserved. Updating of IEEE
11、 documents Users of IEEE standards should be aware that these documents may be superseded at any 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
12、edition of the document together with any amendments, corrigenda, or errata then in effect. In order 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 Standards Association web site a
13、t http:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit the IEEE-SA web site at http:/standards.ieee.org. Errata Errata, if any, for this and all ot
14、her standards can be accessed at the following URL: http:/standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata periodically. Interpretations Current interpretations for this and all other standards can be accessed at the following URL: http:/standards.ieee
15、.org/findstds/interps/index.html. Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in co
16、nnection therewith. The IEEE is not responsible for identifying Essential Patent 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
17、a Letter of Assurance, if any, or in any licensing agreements are reasonable 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 informa
18、tion may be obtained from the IEEE Standards Association. vi Copyright 2011 IEEE. All rights reserved. Participants At the time this standard was submitted to the IEEE-SA Standards Board for approval, the Life Cycle Processes Working Group had the following membership: James W. Moore, IEEE Computer
19、Society Liaison to ISO/IEC JTC 1/SC 7 The following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. Ed Addario Edward Addy Johann Amsenga H. Stephen Berger Juris Borzovs Pieter Botman Lyle Bullock Juan Carreon S
20、ue Carroll Keith Chow Paul Croll Geoffrey Darnton David Deighton Sourav Dutta Andrew Fieldsend David Friscia David Fuschi Ignacio Marin Garcia Lewis Gray Ron Greenthaler Randall Groves Jon Hagar John Harauz Mark Henley Richard Hilliard Werner Hoelzl Glenn Hoffman Robert Holibaugh Bernard Homes Peter
21、 Hung Atsushi Ito Cheryl Jones Piotr Karocki Dwayne Knirk Thomas Kurihara Susan Land J. Dennis Lawrence David Leciston Daniel Lindberg Greg Luri Faramarz Maghsoodlou Wayne W. Manges L. Tajerian Martinez Edward McCall Kathryn Moland James Moore Michael S. Newman Mirko Palazzo William Petit Ulrich Poh
22、l Iulian Profir Gerald Radack Annette Reilly Robert Robinson Randall Safier Bartien Sayogo Robert Schaaf Maud Schlich Richard Schrenker Stephen Schwarm Gil Shultz Carl Singer James Sivak Luca Spotorno Friedrich Stallinger Thomas Starai Elena Strange Walter Struppler Marcy Stutzman Anusheel Tandon Th
23、eodore Urbanowicz David Walden Paul Work Oren Yuen Janusz Zalewski Wenhao Zhu vii Copyright 2011 IEEE. All rights reserved. When the IEEE-SA Standards Board approved this standard on 10 September 2011, it had the following membership: Richard H. Hulett, Chair John Kulick, Vice Chair Robert Grow, Pas
24、t Chair Judith Gorman, Secretary Masayuki Ariyoshi William Bartley Ted Burse Clint Chaplin Wael Diab Jean-Philippe Faure Alex Gelman Paul Houz Jim Hughes Joseph L. Koepfinger* David Law Thomas Lee Hung Ling Oleg Logvinov Ted Olsen Gary Robinson Jon Rosdahl Sam Sciacca Mike Seavey Curtis Siller Phil
25、Winston Howard Wolfman Don Wright*Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Satish Aggarwal, NRC Representative Richard DeBlasio, DOE Representative Michael Janezic, NIST Representative Catherine Berger IEEE Standards Project Editor Malia Zaman IEEE
26、Standards Program Manager, Technical Program Development 1 Copyright 2011 IEEE. All rights reserved. IEEE Standard Adoption of ISO/IEC 15026-2:2011 Systems and Software EngineeringSystems and Software AssurancePart 2: Assurance Case IMPORTANT NOTICE: This standard is not intended to ensure safety, s
27、ecurity, health, or environmental protection. Implementers of the standard are responsible for determining appropriate safety, security, environmental, and health practices or regulatory requirements. This IEEE document is made available for use subject to important notices and legal disclaimers. Th
28、ese 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:/standards.ieee.org/IPR/disclaimers
29、.html. Reference numberISO/IEC 15026-2:2011(E)ISO/IEC 2011INTERNATIONALSTANDARDISO/IEC15026-2First edition2011-02-15Systems and software engineering Systems and software assurance Part 2: Assurance case Ingnierie du logiciel et des systmes Assurance du logiciel et des systmes Partie 2: Cas dassuranc
30、e ISO/IEC 15026-2:2011(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed butshall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. I
31、n 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 file can be found
32、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 Secretariat at the ad
33、dress given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2011 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 writing from eith
34、er ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 g120 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 2011 All rights reserved ISO/IEC 15026
35、-2:2011(E) ISO/IEC 2011 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 2 Conformance .1 3 Normative references1 4 Terms and definitions .1 5 Use of this part of ISO/IEC 15026.1 6 Structure and contents of an assurance case .2 6.1 General .2 6.2 Overall structure3 6.3 Claims
36、.5 6.3.1 Form of claim .5 6.3.2 Claim contents.5 6.3.3 Coverage of conditions.5 6.3.4 Justification of the choice of top-level claims .5 6.4 Arguments6 6.4.1 Argument characteristics .6 6.4.2 Justification of arguments method of reasoning6 6.5 Evidence.6 6.5.1 Evidence contents.6 6.5.2 Associated in
37、formation.6 6.5.3 Associated assumptions 6 6.6 Assumptions7 6.6.1 Form of Assumption .7 6.6.2 Assumption contents7 6.6.3 Associated evidence.7 6.7 Justifications .7 6.8 Combining assurance cases7 7 Required outcomes of using Part 2 assurance case.7 7.1 Outcomes .7 7.2 Mapping to this part of ISO/IEC
38、 15026 8 Bibliography9 ISO/IEC 15026-2:2011(E) iv ISO/IEC 2011 All rights reservedForeword 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 I
39、SO or IEC participate in the development of International Standards through 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 organizatio
40、ns, governmental and non-governmental, in liaison with ISO and IEC, also take 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 Direc
41、tives, Part 2. The main task of the joint technical committee is to prepare 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
42、 national bodies casting a vote. 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 15026-2 was prepared by Joint Technical Committee IS
43、O/IEC JTC 1, Information technology,Subcommittee SC 7, Software and systems engineering.ISO/IEC 15026 consists of the following parts, under the general title Systems and software engineering Systems and software assurance:g127 Part 1: Concepts and vocabulary Technical Report g127 Part 2: Assurance
44、caseSystem integrity levels and assurance in the life cycle will form the subjects of future parts. ISO/IEC 15026-2:2011(E) ISO/IEC 2011 All rights reserved vIntroduction The purpose of this part of ISO/IEC 15026 is to ensure the existence of types of assurance case content and restrictions on assur
45、ance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases. Existing standards addressing different application areas and topics related to assurance cas
46、es might use differing terminology and concepts when addressing common themes. This part of ISO/IEC 15026 is based on experience drawn from these many specialized standards and guidelines. It is applicable to any property of a system or product. NOTE It is intended that ISO/IEC TR 15026-1 will be tr
47、ansformed into an International Standard. In addition to concepts and terminology, ISO/IEC TR 15026-1 provides background and a list of related standards that could be useful in understanding and using this part of ISO/IEC 15026. Assurance cases are generally developed to support claims in areas suc
48、h as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R transition, operations, and maintenance documentation; training; operator and user aids;
49、 data collection capabilities; and services included in or accompanying the system or product. Knowledge of these limitations allows avoidance and recognition of violations of relevant assumptions or the conditions related to the top-level claims. NOTE 4 The text often refers to a single assurance case or to a single top-level claim; however, a system or product may have multiple assurance cases, and an assurance case may have multiple top
