EN 16603-40-2014 en Space engineering - Part 40 Software《航天工程 第40部分 软件》.pdf

1、BSI Standards PublicationBS EN 16603-40:2014Space engineeringPart 40: SoftwareBS EN 16603-40:2014 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of EN 16603-40:2014.It supersedes BS EN 14160:2002 which is withdrawn.The UK participation in its preparation was entruste

2、d to TechnicalCommittee ACE/68, Space systems and operations.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The

3、British Standards Institution 2014. Published by BSI StandardsLimited 2014ISBN 978 0 580 83979 5ICS 49.140Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 30 Septem

4、ber 2014.Amendments issued since publicationDate Text affectedBS EN 16603-40:2014EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16603-40 August 2014 ICS 49.140 Supersedes EN 14160:2001 English version Space engineering - Part 40: Software Ingnirie spatiale - Partie 40: Logiciel Raumfahrttechni

5、k - Teil 40: Software This European Standard was approved by CEN on 10 February 2014. CEN and 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 national standard without any alteration. Up-to

6、-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN and CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other language made

7、 by translation under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions. CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Be

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

9、zerland, Turkey and United Kingdom. CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2014 CEN/CENELEC All rights of exploitation in any form and by any means reserved worldwide for CEN national Members and for CENELEC Members. Ref. No. EN 16603-40:2014 EBS EN 16603-40:2014EN 16603-40

10、:2014 (E) 2 Table of contents Foreword 7 Introduction 8 1 Scope. 9 2 Normative references . 10 3 Terms, definitions and abbreviated terms 11 3.1 Terms for other standards . 11 3.2 Terms specific to the present standard . 11 3.3 Abbreviated terms. 17 4 Space system software product assurance principl

11、es 19 4.1 Introduction . 19 4.2 Overview of space system software engineering processes . 20 4.2.1 General . 20 4.2.2 Software related system requirements process . 23 4.2.3 Software management process . 23 4.2.4 Software requirements and architecture engineering process . 24 4.2.5 Software design a

12、nd implementation engineering process 24 4.2.6 Software validation process 25 4.2.7 Software delivery and acceptance process . 25 4.2.8 Software verification process 25 4.2.9 Software operation process . 26 4.2.10 Software maintenance process . 27 4.3 Organization of this Standard . 27 4.4 Tailoring

13、 of this Standard 29 5 Requirements 30 5.1 Introduction . 30 5.2 Software related system requirement process 31 5.2.1 Overview . 31 5.2.2 Software related system requirements analysis 31 5.2.3 Software related system verification 32 BS EN 16603-40:2014EN 16603-40:2014 (E) 3 5.2.4 Software related sy

14、stem integration and control 33 5.2.5 System requirements review . 34 5.3 Software management process 34 5.3.1 Overview . 34 5.3.2 Software life cycle management 35 5.3.3 Joint review process 36 5.3.4 Software project reviews description . 38 5.3.5 Software technical reviews description 39 5.3.6 Rev

15、iew phasing . 40 5.3.7 Interface management 40 5.3.8 Technical budget and margin management. 41 5.3.9 Compliance to this Standard . 42 5.4 Software requirements and architecture engineering process . 42 5.4.1 Overview . 42 5.4.2 Software requirements analysis 43 5.4.3 Software architectural design 4

16、4 5.4.4 Conducting a preliminary design review 46 5.5 Software design and implementation engineering process . 46 5.5.1 Overview . 46 5.5.2 Design of software items . 46 5.5.3 Coding and testing 49 5.5.4 Integration . 50 5.6 Software validation process 50 5.6.1 Overview . 50 5.6.2 Validation process

17、 implementation 51 5.6.3 Validation activities with respect to the technical specification . 51 5.6.4 Validation activities with respect to the requirements baseline 53 5.7 Software delivery and acceptance process . 54 5.7.1 Overview . 54 5.7.2 Software delivery and installation 54 5.7.3 Software ac

18、ceptance . 55 5.8 Software verification process 56 5.8.1 Overview . 56 5.8.2 Verification process implementation 56 5.8.3 Verification activities 57 5.9 Software operation process 65 5.9.1 Overview . 65 BS EN 16603-40:2014EN 16603-40:2014 (E) 4 5.9.2 Process implementation 65 5.9.3 Operational testi

19、ng 66 5.9.4 Software operation support . 66 5.9.5 User support . 67 5.10 Software maintenance process . 68 5.10.1 Overview . 68 5.10.2 Process implementation 68 5.10.3 Problem and modification analysis 69 5.10.4 Modification implementation 70 5.10.5 Conducting maintenance reviews 70 5.10.6 Software

20、migration 71 5.10.7 Software retirement . 72 Annex A (informative) Software documentation 74 Annex B (normative) Software system specification (SSS) - DRD . 80 Annex C (normative) Software interface requirements document (IRD) - DRD 88 Annex D (normative) Software requirements specification (SRS) -

21、DRD . 91 Annex E (normative) Interface Control Document (ICD) - DRD . 98 Annex F (normative) Software design document (SDD) - DRD .102 Annex G (normative) Software release document (SRelD) - DRD 112 Annex H (normative) Software User Manual (SUM) - DRD 114 Annex I (normative) Software verification pl

22、an (SVerP) - DRD .119 Annex J (normative) Software validation plan (SValP) - DRD.124 Annex K (normative) Software unit/integration test plan (SUITP) - DRD .129 Annex L (normative) Software validation specification (SVS) - DRD .137 Annex M (normative) Software verification report (SVR) - DRD .144 Ann

23、ex N (normative) Software reuse file (SRF) - DRD .151 Annex O (normative) Software development plan (SDP) - DRD 155 Annex P (normative) Software review plan (SRevP) - DRD .161 Annex Q (informative) Document organization and contents at each milestones 170 BS EN 16603-40:2014EN 16603-40:2014 (E) 5 An

24、nex R (normative) Tailoring of this Standard based on software criticality.188 Annex S (informative) General Tailoring .199 Bibliography .203 Figures Figure 4-1: Software related processes in ECSS Standards.20Figure 4-2: Overview of the software life cycle process 22 Figure 4-3: Structure of this St

25、andard . 28 Figure A-1 : Overview of software documents 74 Tables Table A-1 : ECSS-E-ST-40 and ECSS-Q-ST-80 Document requirements list (DRL) . 75 Table B-1 : SSS traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses 80 Table C-1 : IRD traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses . 88 Table

26、D-1 : SRS traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses 91 Table E-1 : ICD traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses . 98 Table F-1 : SDD traceability to ECSS-E-ST-40 Part 1 and ECSS-Q-ST-80 clauses . 102 Table G-1 : SRelD traceability to ECSS-E-ST-40 and ECSS-QST-80 clauses 112

27、Table H-1 : SUM traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses . 114 Table I-1 : SVerP traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses 119 Table J-1 : SValP traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses 124 Table K-1 : SUITP traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses

28、129 Table L-1 : SVS traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses 137 Table M-1 : SVR traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses . 144 Table N-1 : SRF traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses 151 Table O-1 : SDP traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses .

29、155 Table P-1 : SRevP traceability to ECSS-E-ST-40 and ECSS-Q-ST-80 clauses 161 Table Q-1 : Documents content at milestone SRR . 170 Table Q-2 : Documents content at milestone PDR/SWRR 173 Table Q-3 : Documents content at milestone PDR (in addition to PDR/SWRR) 174 Table Q-4 : Documents content at m

30、ilestone TRR 177 Table Q-5 : Documents content at milestone TRB 177 Table Q-6 : Documents content at milestone CDR/DDR . 177 Table Q-7 : Documents content at milestone CDR (in addition to CRD/DDR) . 179 Table Q-8 : Documents content at milestone QR 181 Table Q-9 : Documents content at milestone AR 1

31、83 BS EN 16603-40:2014EN 16603-40:2014 (E) 6 Table Q-10 : Documents content at milestone ORR . 185 Table Q-11 : Documents content of documents with no explicit review . 186 Table R-1 : Criticality applicability . 189 BS EN 16603-40:2014EN 16603-40:2014 (E) 7 Foreword This document (EN 16603-40:2014)

32、 has been prepared by Technical Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN. This standard (EN 16603-40:2014) originates from ECSS-E-ST-40C. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorseme

33、nt, at the latest by February 2015, and conflicting national standards shall be withdrawn at the latest by February 2015. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identif

34、ying any or all such patent rights. This document supersedes EN 14160:2001. This document has been prepared under a mandate given to CEN by the European Commission and the European Free Trade Association. This document has been developed to cover specifically space systems and has therefore preceden

35、ce over any EN covering the same scope but with a wider domain of applicability (e.g. : aerospace). According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, C

36、yprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the Uni

37、ted Kingdom. BS EN 16603-40:2014EN 16603-40:2014 (E) 8 Introduction This Standard defines the principles and requirements applicable to space software engineering. ECSS-Q-ST-80 defines the principles and requirements applicable to space software product assurance. The formulation of this Standard ta

38、kes into account the existing ISO 9000 family of documents, and the ISO/IEC 12207 standard. BS EN 16603-40:2014EN 16603-40:2014 (E) 9 1 Scope This software engineering Standard concerns the “product software”, i.e. software that is part of a space system product tree and developed as part of a space

39、 project. This Standard is applicable, to the extent defined by the tailoring process, to all the elements of a space system, including the space segment, the launch service segment and the ground segment. This Standard covers all aspects of space software engineering including requirements definiti

40、on, design, production, verification and validation, transfer, operations and maintenance. It defines the scope of the space software engineering processes and its interfaces with management and product assurance, which are addressed in the Management (M) and Product assurance (Q) branches of the EC

41、SS System, and explains how they apply in the software engineering processes. This Standard reflects the specific methods used in space system developments, and the requirements for the software engineering processes in this context. Together with the requirements found in the other branches of the

42、ECSS Standards, this Standard provides a coherent and complete framework for software engineering in a space project. This Standard is intended to help the customers to formulate their requirements and suppliers to prepare their responses and to implement the work. This Standard is not intended to r

43、eplace textbook material on computer science or technology, and such material is avoided in this Standard. The readers and users of this Standard are assumed to possess general knowledge of computer science. The scope of this Standard is the software developed as part of a space project, i.e. “Space

44、 system product software”. This Standard also applies to the development of nondeliverable software that affects the quality of the deliverable product. This Standard may be tailored for the specific characteristics and constraints of a space project in conformance with ECSS-S-ST-00. BS EN 16603-40:

45、2014EN 16603-40:2014 (E) 10 2 Normative references The following normative documents contain provisions which, through reference in this text, constitute provisions of this ECSS Standard. For dated references, subsequent amendments to, or revision of any of these publications do not apply, However,

46、parties to agreements based on this ECSS Standard are encouraged to investigate the possibility of applying the more recent editions of the normative documents indicated below. For undated references, the latest edition of the publication referred to applies. EN reference Reference in text Title EN

47、16601-00-01 ECSS-S-ST-00-01 ECSS system Glossary of terms EN 16603-10-11 ECSS-E-ST-10-11 Space product assurance Human factors engineering EN 16601-10 ECSS-M-ST-10 Space project management Project planning and implementation EN 16601-10-01 ECSS-M-ST-10-01 Space project management Organization and co

48、nduct of reviews EN 16601-40 ECSS-M-ST-40 Space project management Configuration and information management EN 16602-80 ECSS-Q-ST-80 Space product assurance Software product assurance BS EN 16603-40:2014EN 16603-40:2014 (E) 11 3 Terms, definitions and abbreviated terms 3.1 Terms for other standards

49、For the purpose of this Standard, the terms and definitions from ECSS-ST-00-01, in particular for the following terms: acceptance test software product NOTE The terms and definitions are common for the ECSS-E-ST-40 and ECSS-Q-ST-80 Standards. 3.2 Terms specific to the present standard 3.2.1 automatic code generation generation of source code with a tool from a model 3.2.2 code coverage percentage of the software that has been executed (covered) by the test suite 3.2.3 competent assessor person who has demonstrated the necessary skills, competencies and experience