1、 IEEE Standard Adoption of ISO/IEC 15026-1Systems and Software EngineeringSystems and Software AssurancePart 1: Concepts and Vocabulary Sponsored by the Software and Systems Engineering Standards Committee IEEE 3 Park Avenue New York, NY 10016-5997 USA IEEE Computer Society IEEE Std 15026-1-2014 IEE
2、E Std 15026-1-2014 IEEE Standard Adoption of ISO/IEC 15026-1Systems and Software EngineeringSystems and Software AssurancePart 1: Concepts and Vocabulary Sponsor Software and Systems Engineering Standards Committee of the IEEE Computer Society Approved 3 November 2014 IEEE-SA Standards Board Abstrac
3、t: Assurance-related terms are defined and an organized set of concepts and relationships to establish a basis for shared understanding across user communities for assurance are established in this adoption of ISO/IEC 15026-1. It provides information to users of the other parts of this International
4、 Standard including the combined use of multiple parts. The essential concept introduced by ISO/IEC 15026 is the statement of claims in an assurance case and the support of those claims through argumentation and evidence. These claims are in the context of assurance for properties of systems and sof
5、tware within life cycle processes for the system or software product. Assurance for a service being operated and managed on an ongoing basis is not covered in this International Standard. Keywords: adoption, assurance, assurance case, claim, IEEE 15026-1, integrity level, life cycle processes, relia
6、bility, software assurance, software engineering, system assurance, systems engineering The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2014 by The Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published
7、 4 November 2014. Printed in the United States of America. IEEE is a registered trademark in the U.S. Patent fitness for a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness of material. In addition, IEEE disclaims any and all conditions relating to
8、: results; and workmanlike effort. IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.” Use of an IEEE standard is wholly voluntary. The existence of an IEEE standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and s
9、ervices related to the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. In publishing and making its standar
10、ds available, IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity nor is IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon his or her own ind
11、ependent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE standard. IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR C
12、ONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
13、WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE. Translations The IEEE consensus development process involves the review of documents in English only. In the event that an IEEE
14、standard is translated, only the English version published by IEEE should be considered the approved IEEE standard. Official statements A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered or inferred to be the o
15、fficial position of IEEE or any of its committees and shall not be considered to be, or be relied upon as, a formal position of IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be co
16、nsidered the personal views of that individual rather than the formal position of IEEE. Comments on standards Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of membership affiliation with IEEE. However, IEEE does not provide consulting information
17、 or advice pertaining to IEEE Standards documents. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is important that any responses to comments
18、 and questions also receive the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to comments or questions except in those cases where the matter has previously been addresse
19、d. For the same reason, IEEE does not respond to interpretation requests. Any person who would like to participate in revisions to an IEEE standard is welcome to join the relevant IEEE working group. Comments on standards should be submitted to the following address: Secretary, IEEE-SA Standards Boa
20、rd 445 Hoes Lane Piscataway, NJ 08854 USA 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 applicable regulatory requirements. Implementers of the
21、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 construed as doing so. Copyrights IEEE draft and app
22、roved standards are copyrighted by IEEE under U.S. and international copyright laws. They are made available by IEEE and are adopted 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,
23、 and the promotion of engineering practices and methods. By making these documents available for use and adoption by public authorities and private users, IEEE does not waive any rights in copyright to the documents. Photocopies Subject to payment of the appropriate fee, IEEE will grant users a limi
24、ted, non-exclusive license to photocopy portions of any individual standard for company or organizational internal use or individual, non-commercial use only. To arrange for payment of licensing fees, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923
25、USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. Updating of IEEE Standards documents Users of IEEE Standards documents should be aware that these documents may be superseded a
26、t 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 edition of the document together with any amendments, corrigenda, or errata then in effect.
27、 Every IEEE standard is subjected to review at least every ten years. When a document is more than ten years old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cauti
28、oned to check to determine that they have the latest edition of any IEEE standard. 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-SA Website at http:/ieeexplore.ieee.org/x
29、pl/standards.jsp or contact IEEE at the address listed previously. For more information about the IEEE SA or IEEEs standards development process, visit the IEEE-SA Website at http:/standards.ieee.org. Errata Errata, if any, for all IEEE standards can be accessed on the IEEE-SA Website at the followi
30、ng URL: http:/standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata periodically. 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
31、, 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 assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website at http:/stand
32、ards.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 reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimina
33、tion 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 Patent Claims for which a license may be required, for conducting inquiries into the legal validity or s
34、cope 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 reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validi
35、ty 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. Participants At the time this IEEE standard was completed, the Life Cycle Processes Working Group had the following mem
36、bership: 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 standard. Balloters may have voted for approval, disapproval, or abstention. Johann Amsenga T Scott Ankrum Pieter Botman Bill Brown Susan Burgess Jua
37、n Carreon Sue Carroll Lawrence Catchpole Keith Chow Daniel Costa Rita Costello Creel Paul Croll Geoffrey Darnton Darold Davis Ronald Dean Andrew Fieldsend Ronald Fradenburg David Friscia David Fuschi Gregg Giesler Lewis Gray Randall Groves Louis Gullo John Harauz Mark Henley Werner Hoelzl Ruimin Hu
38、Peter Hung Noriyuki Ikeuchi Atsushi Ito Mark Jaeger Cheryl Jones Adri Jovin Piotr Karocki Yuri Khersonsky Thomas Kurihara Vincent Lipsio Claire Lohr Edward Mccall James W. Moore Robert Robinson Garry Roedler Terence Rout Bartien Sayogo Robert Schaaf Maud Schlich Carl Singer James Sivak Kendall South
39、wick Luca Spotorno Friedrich Stallinger Thomas Starai Eugene Stoudenmire Walter Struppler Marcy Stutzman Vincent Tume John Vergis David Walden Michael Waterman Chun Yu Charles Wong Oren Yuen Kenneth Zemrowski Daidi Zhong Copyright 2014 IEEE. All rights reserved. vi When the IEEE-SA Standards Board a
40、pproved this standard on 3 November 2014, it had the following membership: John Kulick, Chair Jon Walter Rosdahl, Vice Chair Richard H. Hulett, Past Chair Konstantinos Karachalios, Secretary Peter Balma Farooq Bari Ted Burse Clint Chaplin Stephen Dukes Jean-Philippe Faure Gary Hoffman Michael Janezi
41、c Jeffrey Katz Joseph L. Koepfinger* David J. Law Hung Ling Oleg Logvinov Ted Olsen Glenn Parsons Ron Petersen Adrian Stephens Peter Sutherland Yatin Trivedi Phil Winston Don Wright Yu Yuan *Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Richard DeBlasio,
42、 DOE Representative Michael Janezic, NIST Representative Catherine Berger IEEE-SA Content Publishing Malia Zamann IEEE-SA Technical Community Programs Copyright 2014 IEEE. All rights reserved. vii Introduction This introduction is not part of IEEE Std 15026-1-2014, IEEE Standard Adoption of ISO/IEC
43、15026-1Systems and Software EngineeringSystems and Software AssurancePart 1: Concepts and Vocabulary. The 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 comm
44、ittee for software and systems engineering. In areas of overlap, one organization sometimes adopts the relevant 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 IEE
45、E standard is an adoption of ISO/IEC 15026-1:2013. References to some ISO/IEC standards should be considered as references to the identical IEEE standard: IEEE Std 15026-2-2011 is identical to ISO/IEC 15026-2:2011 IEEE Std 15026-3-2013 is identical to ISO/IEC 15026-3:2011 IEEE Std 15026-4-2013 is id
46、entical to ISO/IEC 15026-4:2012 IEEE Std 15939-2011 is identical to ISO/IEC 15939:2007 IEEE Std 24748-2011 is identical to ISO/IEC TR 24748-1:2010 IEEE Std 1220-2005 is identical to ISO/IEC 26702:2007 IEEE Std 90003-2008 is identical to ISO/IEC 90003:2004 ISO/IEC/IEEE 16085:2006 is identical to ISO/
47、IEC 16085:2006 Errata The following editorial corrections are made in the adopted document: Page iv, Foreword, final paragraph: Change: “IEEE Std 1228-1994 and IEEE Standard for Safety Plan were” to “IEEE Std 1228-1994, IEEE Standard for Safety Plans 75 was”. Page 4, 3.1.8: The definition is numbere
48、d incorrectly. The incorrect number may be ignored. Page 8, 5.5.1, second paragraph: delete “1)”. Page 11, 7.1, 2ndnote: Change “consequences (2)” to “consequences, and (2)”. Page 12, 7.2: Add a closing parenthesis to the end of last item of the list. Page 13, 8.1, fourth paragraph: Change “affect”
49、to “effect”. Page 15, 9.2, second paragraph, second sentence: Replace the words, “systems 140 and Appendix B in 22, and became” with “systems 140, and become”. Page 16, Bibliography, reference 15: Delete the words, “About reliability not security” Page 19, Bibliography, reference 75: Change “STD IEEE” to “IEEE Std”. Page 19, Bibliography, reference 86 and elsewhere: Change “ISO/IEC 12207:2008” to “ISO/IEC/IEEE 12207:2008”. Page 19, Bibliography, reference 87 and elsewhere: Change “ISO/IEC 15288:2008” to “ISO
