1、BSI Standards PublicationBS EN 16603-10-06:2014Space engineeringPart 10-06: Technical requirementsspecificationBS EN 16603-10-06:2014 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of EN16603-10-06:2014. It supersedes BS EN ISO 21351:2005 which iswithdrawn.The UK par
2、ticipation in its preparation was entrusted 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 re
3、sponsible for its correctapplication. The British Standards Institution 2014. Published by BSI StandardsLimited 2014ISBN 978 0 580 83405 9ICS 49.140Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards
4、Policy and Strategy Committee on 30 September 2014.Amendments issued since publicationDate Text affectedBS EN 16603-10-06:2014EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16603-10-06 August 2014 ICS 49.140 Supersedes EN ISO 21351:2005 English version Space engineering - Part 10-06: Technical
5、 requirements specification Ingnierie spatiale - Partie 10-06: Spcification technique de besoin Raumfahrttechnik - Teil 10-06: Spezifizierung technischer Anforderungen This European Standard was approved by CEN on 28 December 2013. CEN and CENELEC members are bound to comply with the CEN/CENELEC Int
6、ernal Regulations which stipulate the conditions for giving this European Standard the status of a national 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 an
7、y CEN and CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other language made 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
8、status as the official versions. CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Icel
9、and, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2014 CEN/CENELEC All rights of exploitation in any fo
10、rm and by any means reserved worldwide for CEN national Members and for CENELEC Members. Ref. No. EN 16603-10-06:2014 EBS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 2 Table of contents Foreword 4 Introduction 5 1 Scope. 6 2 Normative references . 7 3 Terms, definitions and abbreviated terms 8 3.1 Te
11、rms from other standards 8 3.2 Terms specific to the present standard . 8 3.3 Abbreviated terms. 10 4 Technical requirements specification purpose and description 11 4.1 Technical requirements specification purpose and description . 11 4.2 TS content 11 5 Process for establishing a technical require
12、ments specification 13 5.1 General . 13 5.2 Process for establishing a technical requirements specification 13 6 Technical requirements types . 16 6.1 General . 16 6.2 Identification of types of technical requirements 16 6.2.1 Introduction . 16 6.2.2 Functional requirements 16 6.2.3 Mission requirem
13、ents 17 6.2.4 Interface requirements 17 6.2.5 Environmental requirements . 17 6.2.6 Operational requirements 17 6.2.7 Human factor requirements . 17 6.2.8 (Integrated) logistics support requirements . 18 6.2.9 Physical requirements . 18 6.2.10 Product assurance (PA) induced requirements . 19 6.2.11
14、Configuration requirements . 19 BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 3 6.2.12 Design requirements . 19 6.2.13 Verification requirements. 19 7 Overall Requirements for technical requirements specifications 20 7.1 Overview 20 7.2 Requirements for technical requirements specifications . 20 7.2
15、.1 General . 20 7.2.2 Responsibility 20 7.2.3 Technical requirements organisation . 20 7.2.4 Technical reference . 21 7.2.5 Configuration management . 21 7.2.6 Format 21 7.2.7 Supplementary information . 21 7.2.8 Restrictions . 21 8 Requirements for formulating technical requirements . 22 8.1 Genera
16、l . 22 8.2 Requirements for the characteristics of a technical requirement of a TS . 22 8.2.1 Performance . 22 8.2.2 Justification . 22 8.2.3 Configuration management and traceability 23 8.2.4 Ambiguity 23 8.2.5 Uniqueness . 23 8.2.6 Identifiability 23 8.2.7 Singularity . 23 8.2.8 Completeness . 24
17、8.2.9 Verification 24 8.2.10 Tolerance 24 8.3 Recommendations for the wording of requirements 24 8.3.1 General format 24 8.3.2 Required verbal form . 24 8.3.3 Format restrictions 25 Annex A (normative) Technical requirements specification (TS) - DRD . 26 Bibliography . 29 Figures Figure 5-1: Process
18、 to establish the preliminary TS in Phase 0 14 Figure 5-2: Process to establish the TS in phase A 15 BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 4 Foreword This document (EN 16603-10-06:2014) has been prepared by Technical Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN. Th
19、is standard (EN 16603-10-06:2014) originates from ECSS-E-ST-10-06C. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by February 2015, and conflicting national standards shall be withdrawn at the late
20、st 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 identifying any or all such patent rights. This document will supersede EN ISO 21351:2005. This document has
21、 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 precedence over any EN covering the same scope but with a wider domain of applicability (e.g. : aeros
22、pace). 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, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, Fran
23、ce, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 5 Introduction This Standard addre
24、sses the process for and the content of the Technical requirements specification (TS). This document is an adaptation of ISO 21351 “Space systems Functional and technical specifications” to the ECSS context. BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 6 1 Scope This Standard provides an overview o
25、f the purposes and positions of the technical requirements specification, defines the different types of requirements, and defines requirements on the TS and on its requirements. This Standard is applicable to all types of space systems, all product elements, and projects. This standard may be tailo
26、red for the specific characteristic and constraints of a space project in conformance with ECSS-S-ST-00. BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 7 2 Normative references The following normative documents contain provisions which, through reference in this text, constitute provisions of this EC
27、SS Standard. For dated references, subsequent amendments to, or revision of any of these publications, do not apply. However, 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 belo
28、w. For undated references, the latest edition of the publication referred to applies. EN reference Reference in text Title EN 16601-00-01 ECSS-S-ST-00-01 ECSS system Glossary of terms EN 16603-10-02 ECSS-E-ST-10-02 Space engineering Verification BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 8 3 Term
29、s, definitions and abbreviated terms 3.1 Terms from other standards For the purposes of this Standard, the terms and definitions from ECSS-S-ST-00-01 apply. 3.2 Terms specific to the present standard3.2.1 constraint characteristic, result or design feature which is made compulsory or has been prohib
30、ited for any reason NOTE 1 Constraints are generally restrictions on the choice of solutions in a system. NOTE 2 Two kinds of constraints are considered, those which concern solutions, and those which concern the use of the system. NOTE 3 For example constraints can come from environmental and opera
31、tional conditions, law, standards, market demand, investments and means availability, or the organizations policy. NOTE 4 Adapted from EN 1325-1. 3.2.2 environment natural conditions and induced conditions that constrain the design definitions for end products and their enabling products NOTE Exampl
32、es of natural conditions are weather, climate, ocean conditions, terrain, vegetation, dust, light and radiation. Example of induced conditions are electromagnetic interference, heat, vibration, pollution and contamination. 3.2.3 environment external factors affecting an enterprise or project 3.2.4 e
33、nvironment external factors affecting development tools, methods, or processes BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 9 3.2.5 function intended effect of a system, subsystem, product or part NOTE 1 Adapted from EN 1325-1. NOTE 2 Functions should have a single definite purpose. Function names
34、should have a declarative structure (e.g. “Validate Telecommands”), and say “what” is to be done rather than “how”. Good naming allows design components with strong cohesion to be easily derived. 3.2.6 functional analysis technique of identifying and describing all functions of a system NOTE Adapted
35、 from EN 1325-1. 3.2.7 life cycle time interval between the conceptual exploration of the product introduction to its withdrawal from service 3.2.8 mission a possible instantiation of the mission statement in a mission concept NOTE 1 Each mission is described in an MDD. NOTE 2 The implementation in
36、time is called mission scenario. 3.2.9 need what is necessary for, or desired by, the user NOTE 1 A need can be declared or undeclared; it can be an existing or a potential one. NOTE 2 The user is a person or an organization for which the product is designed and which exploits at least one of its fu
37、nctions at any time during its life cycle. NOTE 3 For the space community, the needs are often called mission statement. NOTE 4 Adapted from EN 1325-1. 3.2.10 specification document stating requirements NOTE 1 A specification can be related to activities (e.g. procedure document, process specificati
38、on and test specification), or products (e.g. technical requirements specification) NOTE 2 Adapted from ISO 9000:2000. BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 10 3.2.11 technical requirements specification document by which the customer establishes the intended purpose of a product, its associ
39、ated constraints and environment, the operational and performances features NOTE The TS is the baseline of the business agreement to develop or purchase the selected solution. This specification is called in some projects System Requirements Document (SRD). 3.3 Abbreviated terms For the purpose of t
40、his Standard, the abbreviated terms from ECSS-S-ST-00-01 and the following apply: Abbreviation Meaning IEC International Electrotechnical Commission TS technical requirements specification MDD mission definition documentBS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 11 4 Technical requirements specif
41、ication purpose and description 4.1 Technical requirements specification purpose and description The technical requirements specification is a document through which a customer expresses his needs (or those that he is responsible for expressing) and the related environment and constraints in terms o
42、f technical requirements. The technical requirements contained in the TS allow for potential suppliers to propose the best technical and programmatic solutions. NOTE The intention of the technical requirements specification is not to assume or refer to specific solutions. The TS is the technical ref
43、erence for the qualification of the design and for the acceptance of the end product. In that scope, the technical requirements contained in the TS are subject to the agreed change process defined in the business agreement. They are attainable and verifiable. NOTE The change process itself can chang
44、e in between project phases (Phase 0, A, B, C/D). 4.2 TS content A technical requirements specification is typically composed of three major sets of information: General information related to the context of the document (e.g. administrative information, normative documents and informative documents
45、); General information related to the context of the project, the product or system; Technical requirements (described in clauses 6 and 8). BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 12 The specification provides the general information related to its context: Administrative information: to provi
46、de all the information regarding, for example, the owner, status, identification, distribution list, and management rule; Scope: to define without ambiguity the subject of the TS and aspects covered, thereby indicating limits of applicability; References: to list all the normative (applicable) docum
47、ents and standards, with titles, issue revision, and dates that are referred to in the TS; Terms, definitions and abbreviated terms: to list the specific terms and abbreviated terms used in the TS. It also provides general information related to the context of the project, product or system: to prov
48、ide a clear and rapid understanding of the project and the main needs or mission statements; to give indications of the market as additional information, as well as information about the context of the project and the objectives (situation of the project in a larger programme, further developments);
49、 to provide information on the environment and its constraints; to detail the different situations of the product or system life cycle. BS EN 16603-10-06:2014EN 16603-10-06:2014 (E) 13 5 Process for establishing a technical requirements specification 5.1 General The management of a programme necessitates the establishment of a set of successive states of a product and a network of customer and supplier relationships. The successive states of a product are characterised by initially a “high level” (e.g. rather of functional type) definition of needs / r
