SAE AS 9115-2010 Quality Management Systems - Requirements for Aviation Space and Defense Organizations - Deliverable Software (Supplement to 9100)《航空、航天和防御组织可交付软件用质量管理系统要求(9100的增补.pdf

1、_SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising theref

2、rom, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions. Copyright 2010 SAE International All rights reserved. No part of this publication ma

3、y be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-4970 (outside US

4、A) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/AS9115AEROSPACESTANDARDAS9115 Technically equivalent to ASD prEN 9115 Issued 2010-04Quality Man

5、agement Systems Requirements for Aviation, Spaceand Defense Organizations Deliverable Software (Supplement to 9100) FOREWORDThis document standardizes, to the greatest extent possible, the software quality management system requirements for the aviation, space, and defense industry. This was accompl

6、ished through the harmonization of quality management system requirements from international aviation, space, and defense software standards and other applicable documents. The establishment of common requirements for use at all levels of the supply-chain by organizations around the world should res

7、ult in improved quality, schedule, and cost performance by the reduction or elimination of organization unique requirements and wider application of good practice. SUMMARY/RATIONALEThe 9115 document supersedes AS9006, “Deliverable Aerospace Software Supplement for AS9100A, Quality Management Systems

8、 Aerospace Requirements for Software”, published in March 2003. The AS9006 standard was published as an Americas Aerospace Quality Group (AAQG) sector specific document. This is the initial release of 9115, which is an international supplement to 9100 providing clarification of the corresponding 910

9、0 requirements, as necessary, for deliverable software. In some cases, where clarification is needed, it was necessary due to the complexity of software to decompose “shall” statements in 9100 into more granular requirements. Where no software clarification is required of the 9100 requirements, the

10、following phrase will be presented: “The requirements of 9100 apply. No clarification required for software.” NOTE: This document must be used in conjunction with 9100; references throughout the text to 9100 are understood to mean 9100:2009. Copyright SAE International Provided by IHS under license

11、with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS9115 Page 2 of 21TABLE OF CONTENTS FOREWORD 1SUMMARY/RATIONALE 1INTRODUCTION. 50.1 General . 50.2 Process Approach . 5QUALITY MANAGEMENT SYSTEMS REQUIREMENTS 51. SCOPE 51.1 General . 51.2 Application . 5

12、2. REFERENCES 52.1 Applicable Documents 52.1.1 SAE Publications . 62.1.1.1 Normative References 62.1.2 IEEE Publications 62.1.3 ISO Publications 62.1.4 RTCA Publications 63. TERMS AND DEFINITIONS . 63.1 Baseline 63.2 Commercial-off-the-Shelf (COTS) Software . 73.3 Configuration Item . 73.4 Critical

13、Items . 73.5 Cyclic Redundancy Check (CRC) . 73.6 Digital Signature 73.7 Key Characteristic . 73.8 Monitoring . 73.9 Non-developmental Software 73.10 Phase 83.11 Release . 83.12 Reliability . 83.13 Risk . 83.14 Robustness . 83.15 Secure Hash Algorithm . 83.16 Software 83.17 Software Life Cycle . 83.

14、18 Software Product . 93.19 Special Requirements . 93.20 Stakeholder . 93.21 Support Software 93.22 Validation 93.23 Verification 94. QUALITY MANAGEMENT SYSTEM 94.1 General Requirements 94.2 Documentation Requirements 94.2.1 General . 94.2.2 Quality Manual 104.2.3 Control of Documents . 104.2.4 Cont

15、rol of Records 10Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS9115 Page 3 of 215. MANAGEMENT RESPONSIBILITY 105.1 Management Commitment 105.2 Customer Focus 105.3 Quality Policy 105.4 Planni

16、ng 105.4.1 Quality Objectives . 105.4.2 Quality Management System Planning . 105.5 Responsibility, Authority and Communication 105.5.1 Responsibility and Authority 105.5.2 Management Representative 105.5.3 Internal Communication 105.6 Management Review 115.6.1 General . 115.6.2 Review Input . 115.6.

17、3 Review Output . 116. RESOURCE MANAGEMENT . 116.1 Provision of Resources . 116.2 Human Resources 116.2.1 General . 116.2.2 Competence, Training and Awareness . 116.3 Infrastructure . 116.4 Work Environment. 127. PRODUCT REALIZATION 127.1 Planning of Product Realization 127.1.1 Project Management .

18、127.1.2 Risk Management . 137.1.3 Configuration Management . 137.1.3.1 Configuration Management Planning . 137.1.3.2 Configuration Identification . 137.1.3.3 Change Control . 147.1.3.4 Configuration Status Accounting. 147.1.3.5 Configuration Audit 147.1.4 Control of Work Transfers . 157.2 Customer-R

19、elated Processes . 157.2.1 Determination of Requirements Related to the Product . 157.2.2 Review of Requirements Related to the Product 157.2.3 Customer Communication 157.3 Design and Development 157.3.1 Design and Development Planning 157.3.2 Design and Development Inputs . 167.3.3 Design and Devel

20、opment Outputs 167.3.4 Design and Development Review . 167.3.5 Design and Development Verification . 167.3.6 Design and Development Validation . 177.3.6.1 Design and Development Verification and Validation Testing 177.3.6.2 Design and Development Verification and Validation Documentation . 177.3.7 C

21、ontrol of Design and Development Changes . 177.4 Purchasing 177.4.1 Purchasing Process 177.4.2 Purchasing Information . 177.4.3 Verification of Purchased Product 187.5 Production and Service Provision . 187.5.1 Control of Production and Service Provision 187.5.1.1 Production Process Verification 187

22、.5.1.2 Control of Production Process Changes . 187.5.1.3 Control of Production Equipment, Tools and Software Programs 187.5.1.4 Post-Delivery Support . 19Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,

23、-,-SAE AS9115 Page 4 of 217.5.2 Validation of Processes for Production and Service Provision . 197.5.3 Identification and Traceability . 197.5.4 Customer Property 197.5.5 Preservation of Product 197.6 Control of Monitoring and Measuring Equipment . 198. MEASUREMENT, ANALYSIS AND IMPROVEMENT 208.1 Ge

24、neral . 208.2 Monitoring and Measurement . 208.2.1 Customer Satisfaction . 208.2.2 Internal Audit . 208.2.3 Monitoring and Measurement of Processes . 208.2.4 Monitoring and Measurement of Product 208.3 Control of Nonconforming Product . 208.4 Analysis of Data 218.5 Improvement . 218.5.1 Continual Im

25、provement . 218.5.2 Corrective Action . 218.5.3 Preventive Action 219. NOTES 21Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS9115 Page 5 of 21INTRODUCTION0.1 General The requirements of 9100

26、apply. No clarification required for software. 0.2 Process Approach The requirements of 9100 apply. No clarification required for software. QUALITY MANAGEMENT SYSTEMS REQUIREMENTS 1. SCOPE 1.1 General The requirements of 9100 apply with the following clarification for software. This document supplem

27、ents the 9100 standard requirements for deliverable software and contains quality management system requirements for organizations that design, develop, and/or produce deliverable software for the aviation, space, and defense industry. This includes, as required, support software that is used in the

28、 development and maintenance of deliverable software. The deliverable software may be stand-alone, embedded, or loadable into a target computer. Where the use of Hardware Description Language (HDL) or high order language is utilized as the design source of electronic hardware e.g., Application Speci

29、fic Integrated Circuit (ASIC), Programmable Logic Device (PLD), the organization and customer shall agree on the extent of applicability of this supplement. NOTE 1: For airborne electronic hardware guidance, see RTCA/DO-254 or EUROCAE ED-80; and for product realization requirements, see 9100. Where

30、Commercial-off-the-Shelf (COTS) or non-developmental software is integrated into a deliverable product, the organization and customer shall agree on the extent of applicability of this supplement. For the purposes of this document, the terms “product” and “software product” are considered synonymous

31、. NOTE 2: This document is independent of the life cycle models (e.g., waterfall, spiral, evolutionary, incremental) or methodology (e.g., objected oriented design, unified modeling language, agile). 1.2 Application The requirements of 9100 apply with the following clarification for software.Exclusi

32、ons to requirements in clause 7 should only be considered after analysis of software attributes (e.g., size, safety, security, complexity, criticality, risk). 2. REFERENCES 2.1 Applicable Documents The following publications form a part of this document to the extent specified herein. The latest iss

33、ue of SAE publications shall apply. The applicable issue of the other publications shall be the issue in effect on the date of the purchase order. In the event of conflict between the text of this document and references cited herein, the text of this document takes precedence. Nothing in this docum

34、ent, however, supersedes applicable laws and regulations unless a specific exemption has been obtained. Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS9115 Page 6 of 212.1.1 SAE Publications A

35、vailable from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or 724-776-4970 (outside USA), www.sae.org.AS9006 Deliverable Aerospace Software Supplement for AS9100A, Quality Management Systems - Aerospace - Requirements for Software 2.

36、1.1.1 Normative References The requirements of 9100 apply with the following clarification for software. 9100:2009 Quality Management Systems Requirements for Aviation, Space and Defense Organizations NOTE: For undated references, the latest edition of the referenced document (including any amendmen

37、ts) applies. The referenced documents are “informative” references; the requirements of these referenced documents do not add any additional requirements to this standard. 2.1.2 IEEE Publications Available from Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 08854-41

38、41,Tel: 732-981-0060, www.ieee.org.IEEE-STD-610.12-1990 Standard Glossary of Software Engineering Terminology IEEE-STD-982.1-1988 IEEE Standard Dictionary of Measures to Produce Reliable Software 2.1.3 ISO Publications Available from American National Standards Institute, 25 West 43rdStreet, New Yor

39、k, NY 10036-8002, Tel: 212-642-4900, www.ansi.org.ISO/IEC 12207:1995 Information technology Software life cycle processes ISO/IEC 15288 Systems engineering System life cycle processes 2.1.4 RTCA Publications Available from Radio Technical Commission for Aeronautics Inc., 1828 L Street, NW, Suite 805

40、, Washington, DC 20036, Tel: 202-833-9339, www.rtca.org.RTCA/DO-178, EUROCAE ED-12 Software Considerations in Airborne Systems and Equipment Certification RTCA/DO-254, EUROCAE ED-80 Design Assurance Guidance for Airborne Electronic Hardware 3. TERMS AND DEFINITIONS For the purposes of this document,

41、 the terms and definitions given in 9100 and ISO 9000 apply. The following terms and definitions are included to support the understanding of this document. 3.1 Baseline The approved, recorded configuration of one or more configuration items, that thereafter serves as the basis for further developme

42、nt, and that is changed only through change control procedures RTCA/DO-178, EUROCAE ED-12. Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SAE AS9115 Page 7 of 213.2 Commercial-off-the-Shelf (COTS) S

43、oftware Commercially available applications sold by vendors through public catalog listings. COTS software is not intended to be customized or enhanced. Contract-negotiated software developed for a specific application is not COTS software RTCA/DO-178, EUROCAE ED-12. NOTE: COTS software is a type of

44、 non-developmental software. 3.3 Configuration Item One or more hardware/software entities treated as a unit for configuration management purposes or software life cycle data treated as a unit for configuration management purposes based on RTCA/DO-178, EUROCAE ED-12. 3.4 Critical Items The definitio

45、n in 9100, clause 3.3, applies with the following clarification for software.Critical items in software are those characteristics, requirements, or attributes that have been determined to be most important to achieve product realization (e.g., safety, maintainability, testability, usability, perform

46、ance). Critical items should be adequately managed and appropriate action taken to ensure visibility throughout the product life cycle. For example, in a flight control system software response time can be elevated to a critical item to ensure performance characteristics are met. Furthermore, if the

47、 project has specific testability requirements, cyclomatic complexity may become a critical item. 3.5 Cyclic Redundancy Check (CRC) A type of function that takes as input a data stream of any length and produces as output a value of a certain space, commonly a 32-bit integer. A CRC can be used to detect alteration of data during transmission or storage. 3.6 Dig