EN 62628-2012 en Guidance on software aspects of dependability.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationGuidance on software aspects of dependabilityBS EN IEC 62628:2012BS EN 62628:2012National forewordThis British Standard is the UK implementation of EN IEC 62628:2012. Itsupersede

2、s BS 5760-8:1998 which is withdrawn.The UK participation in its preparation was entrusted to Technical CommitteeDS/1, Dependability.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisio

3、ns of acontract. Users are responsible for its correct application. The British Standards Institution 2012Published by BSI Standards Limited 2012ISBN 978 0 580 76381 6ICS 03.120.01 Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published und

4、er the authority of the StandardsPolicy and Strategy Committee on 31 October 2012.Amendments issued since publicationAmd. No. Date Text affectedBRITISH STANDARDBS EN IEC 62628:2012BS EN 62628:2012 BRITISH STThis British Standard is the UK implementation of EN 62628:2012. It is identical to IEC 62628

5、:2012.EUROPEAN STANDARD EN 62628 NORME EUROPENNE EUROPISCHE NORM September 2012 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Management Centre: Avenue Marnix 17, B - 1000 Brussels 2012

6、 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. EN 62628:2012 E ICS 03.120.01 English version Guidance on software aspects of dependability (IEC 62628:2012) Lignes directrices concernant la sret de fonctionnement du logiciel (CEI 62

7、628:2012) Leitlinien zu Softwareaspekten der Zuverlssigkeit (IEC 62628:2012) This European Standard was approved by CENELEC on 2012-09-12. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a na

8、tional standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CENELEC member. This European Standard exists in three official versions (English, French, German).

9、 A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bu

10、lgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switz

11、erland, Turkey and the United Kingdom. BS EN IEC 62628:2012BS EN 62628:2012EN 62628:2012 - 2 - Foreword The text of document 56/1469/FDIS, future edition 1 of IEC 62628, prepared by IEC/TC 56, “Dependability“ was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as EN 62628:2012. Th

12、e following dates are fixed: latest date by which the document has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2013-06-12 latest date by which the national standards conflicting with the document have to be withdrawn (dow) 2015-09-12 A

13、ttention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CENELEC and/or CEN shall not be held responsible for identifying any or all such patent rights. Endorsement notice The text of the International Standard IEC 62628:2012 was approved b

14、y CENELEC as a European Standard without any modification. In the official version, for Bibliography, the following notes have to be added for the standards indicated: IEC 62508 IEC 60300-1 IEC 60300-2 IEC 60300-3-3 IEC 62347 IEC 61160 IEC 61078 IEC 61025 IEC 61165 IEC 625511)IEC 60812 IEC 60300-3-1

15、 IEC 61508-3 IEC 62429 IEC 61014 IEC 61164 IEC 625061)NOTE Harmonized as EN 62508. NOTE Harmonized as EN 60300-1. NOTE Harmonized as EN 60300-2. NOTE Harmonized as EN 60300-3-3. NOTE Harmonized as EN 62347. NOTE Harmonized as EN 61160. NOTE Harmonized as EN 61078. NOTE Harmonized as EN 61025. NOTE H

16、armonized as EN 61165. NOTE Harmonized as EN 625511). NOTE Harmonized as EN 60812. NOTE Harmonized as EN 60300-3-1. NOTE Harmonized as EN 61508-3. NOTE Harmonized as EN 62429. NOTE Harmonized as EN 61014. NOTE Harmonized as EN 61164. NOTE Harmonized as EN 625061). 1)To be published. BS EN IEC 62628:

17、2012BS EN 62628:2012EN 62628:2012- 3 - EN 62628:2012 Annex ZA (normative) Normative references to international publications with their corresponding European publications The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its applicat

18、ion. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies. Publi

19、cation Year Title EN/HD Year IEC 60050-191 - International Electrotechnical Vocabulary (IEV) - Chapter 191: Dependability and quality of service - - IEC 60300-3-15 - Dependability management - Part 3-15: Application guide - Engineering of system dependability EN 60300-3-15 - BS EN IEC 62628:2012BS E

20、N 62628:2012EN 62628:2012 2 62628 IEC:2012 CONTENTS INTRODUCTION . 6 1 Scope . 7 2 Normative references . 7 3 Terms, definitions and abbreviations 7 3.1 Terms and definitions 7 3.2 Abbreviations 9 4 Overview of software aspects of dependability . 9 4.1 Software and software systems . 9 4.2 Software

21、dependability and software organizations . 10 4.3 Relationship between software and hardware dependability 10 4.4 Software and hardware interaction 11 5 Software dependability engineering and application 12 5.1 System life cycle framework 12 5.2 Software dependability project implementation 12 5.3 S

22、oftware life cycle activities 13 5.4 Software dependability attributes . 14 5.5 Software design environment 15 5.6 Establishing software requirements and dependability objectives 15 5.7 Classification of software faults . 16 5.8 Strategy for software dependability implementation . 17 5.8.1 Software

23、fault avoidance . 17 5.8.2 Software fault control . 17 6 Methodology for software dependability applications 18 6.1 Software development practices for dependability achievement . 18 6.2 Software dependability metrics and data collection 18 6.3 Software dependability assessment . 19 6.3.1 Software de

24、pendability assessment process 19 6.3.2 System performance and dependability specification . 20 6.3.3 Establishing software operational profile 21 6.3.4 Allocation of dependability attributes . 21 6.3.5 Dependability analysis and evaluation . 22 6.3.6 Software verification and software system valida

25、tion . 24 6.3.7 Software testing and measurement 25 6.3.8 Software reliability growth and forecasting . 28 6.3.9 Software dependability information feedback . 29 6.4 Software dependability improvement . 29 6.4.1 Overview of software dependability improvement . 29 6.4.2 Software complexity simplifica

26、tion . 29 6.4.3 Software fault tolerance . 30 6.4.4 Software interoperability 30 6.4.5 Software reuse 31 6.4.6 Software maintenance and enhancement 31 6.4.7 Software documentation 32 6.4.8 Automated tools 33 6.4.9 Technical support and user training . 33 BS EN IEC 62628:2012BS EN 62628:2012EN 62628:

27、2012 2 62628 IEC:2012 CONTENTS INTRODUCTION . 6 1 Scope . 7 2 Normative references . 7 3 Terms, definitions and abbreviations 7 3.1 Terms and definitions 7 3.2 Abbreviations 9 4 Overview of software aspects of dependability . 9 4.1 Software and software systems . 9 4.2 Software dependability and sof

28、tware organizations . 10 4.3 Relationship between software and hardware dependability 10 4.4 Software and hardware interaction 11 5 Software dependability engineering and application 12 5.1 System life cycle framework 12 5.2 Software dependability project implementation 12 5.3 Software life cycle ac

29、tivities 13 5.4 Software dependability attributes . 14 5.5 Software design environment 15 5.6 Establishing software requirements and dependability objectives 15 5.7 Classification of software faults . 16 5.8 Strategy for software dependability implementation . 17 5.8.1 Software fault avoidance . 17

30、5.8.2 Software fault control . 17 6 Methodology for software dependability applications 18 6.1 Software development practices for dependability achievement . 18 6.2 Software dependability metrics and data collection 18 6.3 Software dependability assessment . 19 6.3.1 Software dependability assessmen

31、t process 19 6.3.2 System performance and dependability specification . 20 6.3.3 Establishing software operational profile 21 6.3.4 Allocation of dependability attributes . 21 6.3.5 Dependability analysis and evaluation . 22 6.3.6 Software verification and software system validation . 24 6.3.7 Softw

32、are testing and measurement 25 6.3.8 Software reliability growth and forecasting . 28 6.3.9 Software dependability information feedback . 29 6.4 Software dependability improvement . 29 6.4.1 Overview of software dependability improvement . 29 6.4.2 Software complexity simplification . 29 6.4.3 Softw

33、are fault tolerance . 30 6.4.4 Software interoperability 30 6.4.5 Software reuse 31 6.4.6 Software maintenance and enhancement 31 6.4.7 Software documentation 32 6.4.8 Automated tools 33 6.4.9 Technical support and user training . 33 BS EN IEC 62628:201262628 IEC:2012 3 7 Software assurance 34 7.1 O

34、verview of software assurance 34 7.2 Tailoring process . 34 7.3 Technology influence on software assurance. 34 7.4 Software assurance best practices 35 Annex A (informative) Categorization of software and software applications 37 Annex B (informative) Software system requirements and related dependa

35、bility activities . 39 Annex C (informative) Capability maturity model integration process . 43 Annex D (informative) Classification of software defect attributes 46 Annex E (informative) Examples of software data metrics obtained from data collection 50 Annex F (informative) Example of combined har

36、dware/software reliability functions . 53 Annex G (informative) Summary of software reliability model metrics . 55 Annex H (informative) Software reliability models selection and application . 56 Bibliography 59 Figure 1 Software life cycle activities . 14 Figure F.1 Block diagram for a monitoring c

37、ontrol system 53 Table C.1 Comparison of capability and maturity levels . 43 Table D.1 Classification of software defect attributes when a fault is found 46 Table D.2 Classification of software defect attributes when a fault is fixed . 47 Table D.3 Design review/code inspection activity to triggers

38、mapping 47 Table D.4 Unit test activity to triggers mapping 48 Table D.5 Function test activity to triggers mapping . 48 Table D.6 System test activity to triggers mapping . 49 Table H.1 Examples of software reliability models 57 BS EN IEC 62628:2012BS EN 62628:2012EN 62628:2012 6 62628 IEC:2012 INT

39、RODUCTION Software has widespread applications in todays products and systems. Examples include software applications in programmable control equipment, computer systems and communication networks. Over the years, many standards have been developed for software engineering, software process manageme

40、nt, software quality and reliability assurance, but only a few standards have addressed the software issues from a dependability perspective. Dependability is the ability of a system to perform as and when required to meet specific objectives under given conditions of use. The dependability of a sys

41、tem infers that the system is trustworthy and capable of performing the desired service upon demand to satisfy user needs. The increasing trends in software applications in the service industry have permeated in the rapid growth of Internet services and Web development. Standardized interfaces and p

42、rotocols have enabled the use of third-party software functionality over the Internet to permit cross-platform, cross-provider, and cross-domain applications. Software has become a driving mechanism to realize complex system operations and enable the achievement of viable e-businesses for seamless i

43、ntegration and enterprise process management. Software design has assumed the primary function in data processing, safety monitoring, security protection and communication links in network services. This paradigm shift has put the global business communities in trust of a situation relying heavily o

44、n the software systems to sustain business operations. Software dependability plays a dominant role to influence the success in system performance and data integrity. This International Standard provides current industry best practices and presents relevant methodology to facilitate the achievement

45、of software dependability. It identifies the influence of management on software aspects of dependability and provides relevant technical processes to engineer software dependability into systems. The evolution of software technology and rapid adaptation of software applications in industry practice

46、s have created the need for practical software dependability standard for the global business environment. A structured approach is provided for guidance on the use of this standard. The generic software dependability requirements and processes are presented in this standard. They form the basis for

47、 dependability applications for most software product development and software system implementation. Additional requirements are needed for mission critical, safety and security applications. Industry specific software qualification issues for reliability and quality conformance are not addressed i

48、n this standard. This standard can also serve as guidance for dependability design of firmware. It does not however, address the implementation aspects of firmware with software contained or embedded in the hardware chips to realize their dedicated functions. Examples include application specific in

49、tegrated circuit (ASIC) chips and microprocessor driven controller devices. These products are often designed and integrated as part of the physical hardware features to minimize their size and weight and facilitate real time applications such as those used in cell phones. Although the general dependability principles and practices described in this standard can be used to guide design and application of firmware, specific requirements are needed for their physical construction, device fabrication