1、 IEEE Standard for Software Quality Assurance Processes Sponsored by the Software 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: results; and workmanlike
2、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 services related to the scop
3、e 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 standards available, IEEE is not s
4、uggesting 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 independent judgment in the ex
5、ercise 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 CONSEQUENTIAL DAMAGES (INCLU
6、DING, 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 WAY OUT OF THE PUBLICATION,
7、 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 standard is translated, onl
8、y 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 official position of IEEE or
9、 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 considered the personal views
10、 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 or advice pertaining to IE
11、EE 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 and questions also receive
12、 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 addressed. For the same reason, IEE
13、E 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 Board 445 Hoes Lane Piscataway
14、, 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 standard are responsible fo
15、r 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 approved standards are copyrig
16、hted 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, and the promotion of engin
17、eering 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 limited, non-exclusive license
18、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 USA; +1 978 750 8400. Permi
19、ssion 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 at any time by the issuance
20、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. Every IEEE standard is sub
21、jected 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 cautioned to check to determine
22、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/xpl/standards.jsp or contact
23、 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 following URL: http:/standards.iee
24、e.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, no position is taken by t
25、he 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:/standards.ieee.org/about/sasb/pa
26、tcom/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 discrimination to applicants desiring
27、 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 scope of Patents Claims, or
28、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 validity of any patent rights, an
29、d the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. Copyright 2014 IEEE. All rights reserved. viParticipants At the time this IEEE standard was completed, the Software Quality Assurance Plans (C/S2E
30、SC/730_WG) Working Group had the following membership: Sue McGrath Carroll, Chair John Walz, Vice Chair Steven Rakitin, Vice Chair J. David Blaine, Editor Byron Frank, Secretary T. Scott Ankrum Bakul Banerjee Linda Binkley Pieter Botman Yegor Bugayenko Emile Captain Irene Chan Shumin Cheng Milton Co
31、ncepcion Ken Costello Cynthia Didio Rebecca Draxten Tom Ehrhorn Eva Freund Mike Gayle Gregg Giesler Marilyn Ginsberg-Finner Robin Goldsmith Michelle Gross David Heimann Bernard Homes John Janeri Mike Kress Claude Laporte Carla Lienhard H. Clark Leiphart George Lipscomb Linda McInnis Denis Meredith K
32、eith Middleton Prabhu Parthasarathy Michelle Pierce Mark Paulk Nancy Phillips Sheila Ray Annette Reilly Jeanne Ruggles Robert Schaaf Kandy Senthilmaran Maud Schlich Peter Schulz Jeet Shangari Maury Skibba Lisa Smith Malcolm Stiefel Teri Stokes John Suzuki Bill Trest* Vincent Tume Linda Wharton Dan Z
33、rymiak * Deceased The following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. Edward Addy Johann Amsenga T. Scott Ankrum Angela Anuszewski Chris Bagge Bakul Banerjee Pieter Botman Bill Brown Lyle Bullock Juan
34、Carreon Sue McGrath Carroll Lawrence Catchpole Keith Chow Paul Croll Geoffrey Darnton Ray Davis Ronald Dean Andrew Fieldsend Andre Fournier Byron Frank Eva Freund David Friscia David Fuschi Gregg Giesler Robin Goldsmith Randall Groves Louis Gullo John Harauz David Heimann Mark Henley David Herrell R
35、utger A. Heunks Werner Hoelzl Bernard Homes Peter Hung Noriyuki Ikeuchi Atsushi Ito Mark Jaeger Cheryl Jones Piotr Karocki John Kay Thomas Kurihara Susan Land Claude Laporte Michael Lauxman David Leciston H. Clark Leiphart Claire Lohr Greg Luri Edward McCall James Moore Michael Newman Charles Ngethe
36、 Mark Paulk Robert Peterson William Petit Ulrich Pohl Steven Rakitin Annette Reilly Robert Robinson Terence Rout Randall Safier Bartien Sayogo Robert Schaaf Hans Schaefer David Schultz Stephen Schwarm Raymond Senechal Gil Shultz Carl Singer Kapil Sood Luca Spotorno Copyright 2014 IEEE. All rights re
37、served. viiFriedrich Stallinger Thomas Starai Eugene Stoudenmire Walter Struppler Gerald Stueve Marcy Stutzman Chandrasekaran Subramaniam John Suzuki Thomas Tullia Vincent Tume Charlene Walrad John Walz Jingxin Wang Michael Waterman Stephen Webb M. Karen Woolf Oren Yuen Janusz Zalewski Daidi Zhong W
38、hen the IEEE-SA Standards Board approved this standard on 27 March 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 Chaplain Stephen Dukes Jean-Phillippe
39、Faure Gary Hoffman Michael Janezic Jeffrey Katz Joseph L. Koepfinger* David Law Hung Ling Oleg Logvinov Ted Olsen Glenn Parsons Ron Peterson Adrian Stephens Peter Sutherland Yatin Trivedi Phil Winston Don Wright Yu Yuan *Member Emeritus Also included are the following nonvoting IEEE-SA Standards Boa
40、rd liaisons: Richard DeBlasio, DOE Representative Michael Janezic, NIST Representative Michelle Turner IEEE Standards Program Manager, Document Development Malia Zaman IEEE Standards Program Manager, Technical Program Development Copyright 2014 IEEE. All rights reserved. viiiIntroduction This introd
41、uction is not part of IEEE Std 730-2014, IEEE Standard for Software Quality Assurance Processes. IEEE Std 730 has been a benchmark for Software Quality Assurance (SQA) professionals since it was first published in 1979. While previous versions of IEEE Std 730 provided an SQA plan outline this revisi
42、on expands the scope of this standard to address the processes defined in software life cycle framework standard, ISO/IEC/IEEE 12207:2008. This change in emphasis is consistent with and elaborates the process requirements in ISO/IEC/IEEE 12207:2008. Copyright 2014 IEEE. All rights reserved. ixConten
43、ts 1. Overview 1 1.1 Scope . 1 1.2 Purpose 1 1.3 Field of application 2 1.4 Limitations. 2 1.5 Conformance . 2 1.6 Intended usage of this standard 3 1.7 Organization of this standard. 3 2. Normative references 5 3. Definitions, acronyms, and abbreviations 5 3.1 Conventions. 5 3.2 Definitions . 5 3.3
44、 Acronyms and abbreviations . 9 4. Key concepts of Software Quality Assurance 9 4.1 Organizational management responsibility 9 4.2 Organization and project relationship 9 4.3 Software quality and relationship to requirements 12 4.4 Overview of SQA activities. 14 4.5 Acquirer and supplier perspective
45、s 15 4.6 Key concepts of this standard 15 4.7 Software process improvement 16 4.8 Maintaining quality management system consistency. 16 5. Software Quality Assurance process 17 5.1 Purpose 17 5.2 Organization of SQA process outcomes 17 5.3 SQA process implementation activities. 19 5.4 Product assura
46、nce activities. 27 5.5 Process assurance activities . 31 Annex A (informative) Mapping between 7.2.3 of ISO/IEC/IEEE 12207:2008 and IEEE Std 730-2014 37 Annex B (informative) Mapping between SQA Plan outlines contained in IEEE Std 730-2002 and IEEE Std 730-2014 41 Annex C (informative) Guidance for
47、creating Software Quality Assurance Plans 44 C.1 Introduction. 44 C.2 Organization of this annex 47 C.3 Guidance . 47 Annex D (informative) Mapping IEEE Std 730-2014 and ISO/IEC 15504 (SPICE) 81 D.1 Capability Level 1 for SQA 81 D.2 Capability Level 2 for SQA 81 D.3 Capability Level 3 to Capability
48、Level 5 for SQA . 83 D.4 Capability Level 3 to Capability Level 5 for other SLC processes. 84 Annex E (informative) Applying IEEE Std 730-2014 Industry-specific guidance 86 E.1 Medical device industry 86 Copyright 2014 IEEE. All rights reserved. xE.2 Nuclear power generation industry . 90 Annex F (i
49、nformative) SQA activities and their relationship to the agile development process. 95 F.1 Introduction . 95 F.2 Modifying the 16 SQA activities to accommodate agile software development. 96 Annex G (informative) Mapping between IEEE Std 730-2014 and ISO/IEC 29110 standard for Very Small Entities 99 Annex H (informative) Software tool validation. 104 Annex I (informative) Assessing product risk: Software integrity levels and assurance cases . 106 I.1 Software integrity levels. 106 I.2 Overview of activities for integrity level determination. 109 I.3 Assurance cases 111 Annex
