《IEEE-1228-1994-R2002.pdf》由会员分享，可在线阅读，更多相关《IEEE-1228-1994-R2002.pdf（23页珍藏版）》请在三一文库上搜索。
1、 The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright 1994 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 1994. Printed in the United States of America. ISBN 1-55937-425-X No part of th
2、is publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. IEEE Std 1228-1994 IEEE Standard for Software Safety Plans Sponsor Software Engineering Standards Committee of the IEEE Computer Society Approved March
3、 17, 1994 IEEE Standards Board Abstract: The minimum acceptable requirements for the content of a software safety plan are established. This standard applies to the software safety plan used for the development, procure- ment, maintenance, and retirement of safety-critical software. This standard re
4、quires that the plan be prepared within the context of the system safety program. Only the safety aspects of the soft- ware are included. This standard does not contain special provisions required for software used in distributed systems or in parallel processors. Keywords: safety-critical software,
5、 software safety plan, software safety program, safety requirements Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/28/2007 22:00:50 MDTNo reproduction or networki
6、ng permitted without license from IHS -,-,- Print: ISBN 1-55937-496-9, SH94255 PDF: ISBN 0-7381-0419-1, SS94255 Reaffirmed December 10, 2002 IEEE Std 1228-1994 (R2002) IEEE Standards documents are developed within the Technical Committees of the IEEE Societies and the Standards Coordinating Committe
7、es of the IEEE Standards Board. Members of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities ou
8、tside of IEEE that have expressed an interest in partici- pating in the development of the standard. 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, mar- ket, or provide other goods and se
9、rvices 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. Every IEEE Standard is subjected to r
10、eview at least every ve years for revision or reafrmation. When a document is more than ve years old and has not been reafrmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reect the present state of the art. Users are cautioned to check to determine th
11、at they have the latest edition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership afliation with IEEE. Suggestions for changes in docu- ments should be in the form of a proposed change of text, together with appropriate supp
12、orting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specic applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appro- priate responses. Since
13、 IEEE Standards represent a consensus of all concerned inter- ests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason IEEE and the members of its technical com- mittees are not able to provide an instant response to interpr
14、etation requests except in those cases where the matter has previously received formal consideration. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE Standards Board 445 Hoes Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA IEEE standards documents may
15、involve the use of patented technology. Their approval by the Institute of Electrical and Electronics Engineers does not mean that using such technology for the purpose of conforming to such standards is authorized by the patent owner. It is the obligation of the user of such technology to obtain al
16、l necessary permissions. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/28/2007 22:00:50 MDTNo reproduction or networking permitted without license from IHS -,-,-
17、 iii Introduction (This introduction is not part of IEEE Std 1228-1994, IEEE Standard for Software Safety Plans.) This standard describes the minimum acceptable requirements for the content of a software safety plan. This standard contains four clauses. Clause 1 discusses the application of the stan
18、dard. Clause 2 lists references to other standards. Clause 3 provides a set of denitions and acronyms used in the standard. Clause 4 contains the required content of a software safety plan. In order to be in compliance with this standard, users of the standard shall adhere to clause 4. The informati
19、ve annex discusses software safety analyses. This standard was written for those who are responsible for dening, planning, implementing, or supporting software safety plans. Participants in the working group were individually supported by their employers with travel expenses and working days. This s
20、upport does not constitute or imply approval or endorsement of this standard. This standard was developed by the Software Safety Plans Working Group consisting of the following members who attended two or more meetings, provided text, or submitted comments on two or more drafts of the standard. Cynt
21、hia L. Wright, Chair Anthony J. Zawilski, Vice chair Patricia Trellue, Conguration manager Dick BairJohn HorchNorman Schneidewind Leo BeltracchiGrady LeeDavid Schultz Mordechai Ben-MenachemNancy LevesonAnita Shagnea P. V. BhansaliStanley LevinsonPeter Shilling David BurrowsBen Livson Edgar Sibley Be
22、tty ChaoD. P. ManneringMel Smyre John CherviavskyScott MathewsJack Spraul Tony ClarkJohn McHughLeslie Stepanek Taz DaughtreyArchibald McKinlayV. K. Srivastava David DiniBonnie MelhartLeonard Tripp L. G. EganBret MichaelRon Vaickavski Alwyn GoodloeTammy PelnikDelores Wallace Herb HechtJohn PerryChuck
23、 Weinstock The following individuals also contributed to the development of the standard by attending one meeting or providing comments on one draft: Paul AmmannJohn HarauzDave Peercy Jordan AndersonAlbert HohebDev Raheja Ron BerlackCharles HornSteven Rakitin Richard BlauwFrank HoustonJuri Reinfelds
24、 Thomas BraudtDiane JachinowskiHeinz Rogen J. BrazendaleJon JackyArt Rubino Fletcher BuckleyGeorge KambicLeonard Russo David CardAlasdair KempDamian Saccochio James CardowPhil KeysHans Schaefer Geoff CozensThomas KuriharaRobert Shillato Ron DalyVictor MaggioliRichard Thayer Paul DavisJohn MatrasJerr
25、y Thrasher C. G. DiderichA. D. McGettrickDinos Tsagoes Audrey DorofeeRovert MetroDavid Vickers Caroline EvansJudy MooreJim Widmyer Peter Farrell-VinayBahman MostafazadehEugene Wilhelm Fred FreiburgerMelissa MurphyBill Wood Al FriendDennis NickleN. Yogaramanan David GelperinMark OliverJanusz Zalewski
26、 Donna GrushTuncer OrenPeter Zoll Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/28/2007 22:00:50 MDTNo reproduction or networking permitted without license from
27、IHS -,-,- iv The following persons were on the balloting committee: William BatesWilliam HeeyDave Peercy Mordechai Ben-MenachemJanene HeinzmanTammy Pelnik Ron BerlackDavid HeronJuri Reinfelds Sandro BolognaJohn HorchJames Ronback Fletcher BuckleyCharles HowellStephen Schach Kay BydalekLynn Ihlenfeld
28、tHans Schaefer David CardWilliam JunkNorman Schneidewind Betty ChaoGeorge KambicDavid Schultz Tony ClarkThomas KuriharaGregory Schumacher Geoff CozensRobert LaneRobert Shillato Taz DaughtreyCharles LavineEdgar Sibley Paul DavisDennis LawrenceMel Smyre Einar DragstedtNancy LevesonV. K. Srivastava L.
29、G. EganStanley LevinsonRichard Thayer Caroline EvansBen LivsonGeorge Tice John FendrichJoseph MaayanPatrica Trellue Joanna FrawleyJohn MacMillanLeonard Tripp Roger FujiiJukka MarijarviRon Vaickavski David GelperinRoger MartinDavid Vickers Yair GershkovitchScott MathewsUdo Voges Julio Gonzalez-SanzIv
30、ano MazzaDelores Wallace David GustafsonJohn McHughPaul Work John HarauzJames MichaelCynthia Wright Herb HechtDennis NickleJanusz Zalewski When the IEEE Standards Board approved this standard on March 17, 1994, it had the following membership: Wallace S. Read, Chair Donald C. Loughry, Vice Chair And
31、rew G. Salem, Secretary Gilles A. BarilDonald N. HeirmanJoseph L. Koepnger* Bruce B. BarrowRichard J. HollemanD. N. Jim Logothetis Jos A. Berrios de la PazJim IsaakL. Bruce McClung Clyde R. CampBen C. JohnsonMarco W. Migliaro James CostantinoSonny KasturiMary Lou Padgett Stephen L. DiamondLorraine C
32、. KevraArthur K. Reilly Donald C. FleckensteinE. G. Al KienerRonald H. Reimer Jay Forster*Ivor N. KnightGary S. Robinson Ramiro GarciaLeonard L. Tripp *Member Emeritus Also included are the following nonvoting IEEE Standards Board liaisons: Satish K. Aggarwal James Beall Richard B. Engelman David E.
33、 Soffrin Stanley I. Warshaw Rachel A. Meisel IEEE Standards Project Editor Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/28/2007 22:00:50 MDTNo reproduction or n
34、etworking permitted without license from IHS -,-,- v Contents CLAUSEPAGE 1.Overview 1 1.1 Purpose.1 1.2 Scope1 1.3 Application.1 1.4 Disclaimer2 2.References2 3.Definitions and abbreviations3 3.1 Definitions3 3.2 Abbreviations.3 4.Contents of a software safety plan.4 4.1 Purpose (Section 1 of the Pl
35、an) 5 4.2 Definitions, acronyms and abbreviations, and references (Section 2 of the Plan) 5 4.3 Software safety management (Section 3 of the Plan)5 4.4 Software safety analyses (Section 4 of the Plan). 10 4.5 Post development (Section 5 of the Plan) 12 4.6 Plan approval (Section 6 of the Plan) 14 AN
36、NEX Discussion of software safety analyses (informative) . 15 A.1 Software safety requirements analyses 15 A.2 Software safety design analysis. 15 A.3 Software safety code analysis 16 A.4 Software safety test analysis 17 A.5 Software safety change analysis 17 Copyright The Institute of Electrical an
37、d Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/28/2007 22:00:50 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright The Institute of Electrical and Electronics Engineers,
38、 Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/28/2007 22:00:50 MDTNo reproduction or networking permitted without license from IHS -,-,- 1 IEEE Standard for Software Safety Plans 1. Overview 1.1 Purpose This standard establis
39、hes the minimum acceptable requirements for the content of a Software Safety Plan (also referred to as the Plan) to address the processes and activities intended to improve the safety of safety- critical software. 1.2 Scope This standard applies to the Plan used for the development, procurement, mai
40、ntenance, and retirement of safety-critical software; for example, software products whose failure could cause loss of life, serious harm, or have widespread negative social impact. This standard requires that the Plan be prepared within the con- text of the system safety program. The scope of this
41、standard includes only the safety aspects of the soft- ware. This standard does not contain special provisions required for software used in distributed systems or in parallel processors. 1.3 Application The Plan is prepared under the direction of project or system safety program management to addre
42、ss the identied potential software safety risks. Compliance with this standard requires the creation of a written plan that addresses each topic, subtopic, and stipulation described in clause 4. The level of detail in, and the resources required by an software safety plan will be determined by facto
43、rs including the type and level of risks associated with the software product, the complexity of the application, and external forces such as contractual requirements. Software is a portion of a system. Other portions of that system include computer hardware, other devices (possibly including mechan
44、ical, electrical, chemical, or nuclear devices), and people. Software alone is not a safety issue; it is only an issue in the context of this larger system. Hence, software safety must begin with the larger system. Software safety must be considered in the context of its associated hardware, environ
45、- ment, and operators. The Plan needs to address interfaces with these elements. The existence of this standard should not be construed to discourage or prohibit the imposition of additional or more stringent requirements where the need exists. An assessment should be made for the specic soft- ware
46、project to ensure adequacy of coverage and safety assurance. Where this standard is invoked for a Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/28/2007 22:00:50
47、MDTNo reproduction or networking permitted without license from IHS -,-,- IEEE Std 1228-1994IEEE STANDARD FOR 2 project engaged in producing several software products, the applicability of the standard should be specied for each of the software products encompassed by the project. This standard cont
48、ains a minimum set of requirements for the content of software safety plans. The addition of more stringent requirements shall be the only acceptable tailoring process for this standard. 1.4 Disclaimer Preparation of software safety plans according to this standard does not automatically ensure software safety. Compliance with this standard does not absolve the software designer, producer, or vendor from any statutory obligations. 2. References This standard shall be used in conjunction with the following publications.The latest revisions shall apply. IEEE Std 610.12-1990, IEEE