EN 16603-10:2018

Space engineering - System engineering general requirements

This standard specifies the system engineering implementation requirements for space systems and space products development.
Specific objectives of this standard are:
-   to implement the system engineering requirements to establish a firm technical basis and to minimize technical risk and cost for space systems and space products development;
-   to specify the essential system engineering tasks, their objectives and outputs;
-   to implement integration and control of engineering disciplines and lower level system engineering work;
-   to implement the "customer-system-supplier mode" through the development of systems and products for space applications.
Depending of the product category, the application of this standard needs to be checked and if needed tailored. The pre-tailoring table in clause 7 contains the applicability of the requirements of this document and its annexes according to product type. Specific requirements related to system engineering, like technical specification, verification, and testing are specified in dedicated documents and standards within the set of ECSS system engineering standards ECSS-E-ST-10-XX.
Discipline or element specific engineering implementation requirements are covered in dedicated ECSS standards. These standards are based on the same principles, process and documentation model. The applicability of each these standards can therefore not be considered in isolation from the others.
NOTE 1   The term "Discipline" is defined in ECSS-M-ST-10, as "a specific area of expertise within a general subject". The name of the discipline normally indicates the type of expertise, e.g. in the ECSS system mechanical engineering, software and communications are disciplines within the engineering domain.
NOTE 2   The requirements on the system engineering process are gathered in this standard; specific aspects of the SE process are further elaborated in dedicated standards.
For engineering process both for SW and for Ground Segment and Operations the following standards are considered fully sufficient for development of these items:
-   ECSS-E-ST-70 Space engineering - Ground systems and operations
-   ECSS-E-ST-40 Space engineering - Software
-   ECSS-Q-ST-80 Space product assurance - Software product assurance
This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00.

Raumfahrttechnik - Allgemeine Anforderungen an das Systemengineering

Ingénierie spatiale - Exigences générales d'ingénierie système

La présente Norme expose les exigences de mise en oeuvre de l’ingénierie système pour le développement des systèmes et des produits spatiaux.
Les objectifs précis de la présente Norme sont les suivants :
-   appliquer les exigences d’ingénierie système pour créer une base technique solide et minimiser les coûts et les risques techniques pour le développement des systèmes et des produits spatiaux ;
-   définir les principales tâches d’ingénierie système, leurs objectifs et leurs résultats ;
-   mettre en oeuvre l’intégration et le contrôle des disciplines d’ingénierie, ainsi que les travaux d’ingénierie système de niveau inférieur ;
-   mettre en oeuvre le « modèle client-système-fournisseur » à travers le développement de systèmes et de produits pour les applications spatiales.
En fonction de la catégorie de produit, il faut vérifier si la présente norme doit être appliquée et si besoin adaptée. Le tableau de préadaptation de l’article 7 présente l’applicabilité des exigences du présent document et de ses annexes selon le type de produit. Les exigences spécifiques relatives à l’ingénierie système, telles que les spécifications techniques, la vérification et les essais, sont spécifiées dans des documents et normes dédiés de la série ECSS-E-ST-10-XX, relative à l’ingénierie système de l’ECSS.
Les exigences de mise en oeuvre de l’ingénierie propres à chaque discipline ou à chaque élément sont décrites dans les normes ECSS associées. Ces normes se fondent sur les mêmes principes, les mêmes processus et le même modèle de documentation. L’applicabilité de chacune de ces normes ne peut donc être envisagée de manière indépendante.
NOTE 1   Le terme « Discipline » est défini dans l’ECSS-M-ST-10 comme étant une « spécialité entrant dans le cadre d’un sujet général ». Le nom de la discipline indique généralement le type d’expertise auquel elle est associée ; par exemple, dans le système ECSS, l’ingénierie mécanique, les logiciels et les communications sont des disciplines du domaine de l’ingénierie.
NOTE 2   Les exigences relatives au processus d’ingénierie système sont réunies dans cette norme ; les aspects spécifiques au processus d’ES sont décrits de façon plus détaillée dans des normes dédiées.
En matière de processus d’ingénierie relatif aux logiciels ainsi qu’au segment sol et aux opérations, les normes suivantes sont considérées comme étant amplement suffisantes pour le développement de ces articles :
-   ECSS-E-ST-70 Ingénierie spatiale - Systèmes sol et opérations
-   ECSS-E-ST-40 Ingénierie spatiale - Logiciels
-   ECSS-Q-ST-80 Assurance produit des projets spatiaux - Assurance produit logiciel
La présente Norme peut être adaptée aux caractéristiques et contraintes spécifiques d’un projet spatial, conformément à l’ECSS-S-ST-00.

Vesoljska tehnika - Sistemskotehnične splošne zahteve

Ta standard določa zahteve za izvajanje sistemskega inženiringa za vesoljske sisteme in razvoj vesoljskih izdelkov. Namen tega standarda je zlasti: • izvajanje zahtev za sistemski inženiring z namenom zagotavljanja trdne tehnične podlage in zmanjševanja tehničnih tveganj in stroškov vesoljskih sistemov ter razvoja vesoljskih izdelkov; • določanje bistvenih nalog sistemskega inženiringa ter njihovih ciljev in rezultatov; • izvajanje povezovanja in nadzora nad različnimi inženirskimi disciplinami in dela v zvezi s sistemskim inženiringom na nižji ravni; • izvajanje »modela odjemalec-sistem-dobavitelj« s pomočjo razvoja sistemov in izdelkov za vesoljske aplikacije. Ta standard je namenjen za uporabo pri vseh vesoljskih sistemih in izdelkih, na kateri koli ravni razstavljanja sistema, vključno s strojno opremo, programsko opremo, postopki, modeli z vključitvijo človeka, objekti in storitvami. V celotnem dokumentu in njegovih dodatkih zahteve kot take veljajo samo za kompleksne sisteme; za elemente nižje ravni je potrebna prilagoditev. Posebne zahteve v zvezi s sistemskim inženiringom, kot so tehnične specifikacije, preverjanje in preskušanje, določajo namenski dokumenti in standardi v sklopu standardov ECSS za sistemski inženiring ECSS-E-ST-10-XX. Zahteve za izvajanje inženiringa, vezanega na discipline ali elemente, so zajete namenskih standardih ECSS. Navedeni standardi temeljijo na enakih načelih, procesu in modelu dokumentiranja. Zato uporabnosti posameznega standarda ni mogoče presojati ločeno od ostalih standardov. Dokument ECSS-E-HB-10 »Smernice za sistemski inženiring« vsebuje smernice, ki se navezujejo na ta standard, vključno z opisom postopka inženiringa za vesoljski sistem in njegove izdelke. OPOMBA 1: izraz »disciplina« je v standardu ECSS-M-ST-10 opredeljen kot »določeno strokovno področje v okviru splošne tematike«. Iz imena discipline je običajno razvidna vrsta strokovnega znanja, npr. v okviru mehanskega inženiringa sistema ECSS sta programska oprema in komunikacije disciplini s področja inženiringa. OPOMBA 2: v tem standardu so zajete zahteve za postopek sistemskega inženiringa; posebni vidiki postopka sistemskega inženiringa so natančneje določeni v namenskih standardih.  Ta standard se lahko prilagodi posameznim lastnostim in omejitvam vesoljskega projekta v skladu s standardom ECSS-S-ST-00.

General Information

• Status: Published
• Publication Date: 17-Apr-2018
• Withdrawal Date: 30-Oct-2018
• ICS: 49.140 - Space systems and operations
• Technical Committee: CEN/CLC/TC 5 - Space
• Drafting Committee: CEN/CLC/TC 5 - Space
• Current Stage: 6060 - Definitive text made available (DAV) - Publishing
• Start Date: 18-Apr-2018
• Completion Date: 18-Apr-2018
• Mandate: M/496 - Mandate addressed to CEN, CENELEC and ETSI to develop standardisation regarding space industry (Phase 3 of the process)
• Ref Project: SIST EN 16603-10:2018 - Space engineering - System engineering general requirements

Relations

• Replaces: EN 13292:1999 - Space engineering standards - Policy and principles
• Effective Date: 25-Apr-2018
• Replaces: EN 14607-7:2004 - Space engineering - Mechnical - Part 7: Mechnical parts
• Effective Date: 25-Apr-2018
• Replaces: EN 14514:2004 - Space engineering standards - Functional analysis
• Effective Date: 03-Aug-2016

Standards Content (Sample)

SLOVENSKI STANDARD
01-julij-2018
1DGRPHãþD
SIST EN 13292:2000
SIST EN 14514:2005
SIST EN 14607-7:2005
9HVROMVNDWHKQLND6LVWHPVNRWHKQLþQHVSORãQH]DKWHYH
Space engineering - System engineering general requirements
Raumfahrttechnik - Grundsätze und Verfahrensweise
Ta slovenski standard je istoveten z: EN 16603-10:2018
ICS:
49.140 Vesoljski sistemi in operacije Space systems and
operations
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 16603-10
NORME EUROPÉENNE
EUROPÄISCHE NORM
April 2018
ICS 49.140
Supersedes EN 13292:1999, EN 14514:2004, EN
14607-7:2004
English version
Space engineering - System engineering general
requirements
Ingénierie spatiale - Exigences générales d'ingénierie Raumfahrttechnik - Grundsätze und Verfahrensweise
système
This European Standard was approved by CEN on 21 August 2017.

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-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 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, Belgium,
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,
Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.

CEN-CENELEC Management Centre:
Rue de la Science 23, B-1040 Brussels
© 2018 CEN/CENELEC All rights of exploitation in any form and by any means Ref. No. EN 16603-10:2018 E
reserved worldwide for CEN national Members and for
CENELEC Members.
Table of contents
European Foreword . 5
1 Scope . 7
2 Normative references . 9
3 Terms, definitions and abbreviated terms . 10
3.1 Terms from other standards . 10
3.2 Terms specific to the present standard . 10
3.3 Abbreviated terms. 11
4 Overview of system engineering . 14
4.1 The system engineering discipline . 14
4.2 The system engineering process . 18
4.3 Overview of system engineering tasks per project phase. 19
4.3.1 Overview . 19
4.3.2 General . 19
4.3.3 Phase 0 Overview: Mission analysis-need identification . 20
4.3.4 Phase A Overview: Feasibility . 20
4.3.5 Phase B Overview: Preliminary definition . 20
4.3.6 Phase C Overview: Detailed definition . 21
4.3.7 Phase D Overview : Qualification and production . 21
4.3.8 Phase E Overview: Operations / utilization . 21
4.3.9 Phase F Overview: Disposal . 21
5 General requirements. 23
5.1 System engineering plan . 23
5.2 Requirement engineering . 24
5.2.1 General . 24
5.2.2 Requirement traceability. 24
5.2.3 Requirement engineering process . 25
5.3 Analysis . 27
5.3.1 System analysis . 27
5.3.2 System environments and design and test factors . 28
5.3.3 Trade-off analyses . 28
5.3.4 Analysis methods, tools and models . 29
5.4 Design and configuration . 30
5.4.1 Design . 30
5.4.2 Configuration . 31
5.5 Verification . 32
5.5.1 General . 32
5.5.2 Product verification. 32
5.6 System engineering integration and control . 33
5.6.1 Management of system engineering activities . 33
5.6.2 Planning . 33
5.6.3 Engineering data . 33
5.6.4 Interface control . 34
5.6.5 Coordinate systems and units . 34
5.6.6 Technical budgets and margin policy . 34
5.6.7 Technology . 34
5.6.8 Risk management . 35
5.6.9 Changes and nonconformances control . 35
6 <> . 36
7 Pre-tailoring matrix per space product types . 37
Annex A (informative) System engineering documents delivery per review . 51
Annex B (normative) Mission description document (MDD) – DRD . 55
Annex C (normative) System concept report – DRD . 59
Annex D (normative) System engineering plan (SEP) – DRD . 60
Annex E (normative) Technology plan (TP) – DRD . 69
Annex F (normative) Technology matrix - DRD . 73
Annex G (normative) Design definition file (DDF) - DRD . 75
Annex H (normative) Function tree - DRD . 80
Annex I (normative) Technical budget - DRD . 82
Annex J (normative) Specification tree - DRD . 84
Annex K (normative) Design justification file (DJF) - DRD . 86
Annex L (normative) Trade-off report - DRD . 93
Annex M (normative) <> . 96
Annex N (normative) Requirements traceability matrix (RTM) - DRD . 97
Annex O (normative) Requirements justification file (RJF) - DRD . 99
Annex P (normative) Product user manual (PUM or UM) - DRD . 102
Annex Q <> . 110
Annex R (informative) Mapping of typical DDP to ECSS documents . 111
Annex S (informative) Guideline content of Analysis Report . 113
Bibliography . 115

Figures
Figure 4-1: System engineering, sub-functions and boundaries . 16
Figure 4-2: System engineering sub-functions inter-relationships . 17

Figure B-1 : Relationship between documents . 56
Figure E-1 : TRSL template . 72

Tables
Table A-1 : System engineering deliverable documents . 52

European Foreword
This document (EN 16603-10:2018) has been prepared by Technical Committee CEN-CENELEC/JTC 5
“Space”, the secretariat of which is held by DIN.
This standard (EN 16603-10:2018) originates from ECSS-E-ST-10C Rev.1.
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 October 2018, and conflicting national standards shall
be withdrawn at the latest by October 2018.
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 supersedes EN 13292:1999, EN 14514:2004 and EN 14607-7:2004.
The main changes with respect to EN 13292:1999, EN 14514:2004 and EN 14607-7:2004 are:
• The main driver for the changes in this issue of the standard comes from the intention to include in
this document only requirements and remove all informative material related to the process for
inclusion in a future handbook.
• Inclusion of EN 16603-11 (ECSS-E-AS-11) "Adoption Notice of ISO 16290, Space systems -
Definition of the Technology Readiness Levels (TRLs) and their criteria of assessment" as
Normative Reference.
• Former clause 5 “System engineering process”, replaced by a brief overview of the project phases
and related system engineering tasks in the current clause 4.3 “Overview of system engineering
tasks per project phase”.
• Former Clause 4 split into an introductory clause 4 “Overview of Systems engineering” and clause
5 “General Requirements”.
• Clause 7 "Pre-tailoring matrix per space product types" added
• The remaining requ irements have been reworded for readability and consistency. Repetition of
requirements included in other related standards have been eliminated.
• Regarding the documentation model, the only significant modification originates in the
simplification of the concept of Functional Specification and Technical Specification. In EN 16603-
10-06 only one specification, the technical requirements specification (customer specification), is
considered. This is reflected in this standard, as explained in clause 5.2.3.1
• Annex A: System engineering documents delivery per review: This annex replaces and expands
old Annex B. It includes the listing of the main documents per phase of the project development
indicating when the document needs to be available.
• Document Requirements Descriptions (DRD) added in several Annexes that include all the project
documents pertinent to this standard. In the previous issue the DRDs were not included.
• Annex R: Mapping of typical DDP to ECSS documents: This is an addition with respect to the
previous issue. It presents where specific subjects contained in the previously used Design and
Development Plan are located in the new set of ECSS documents.
This document has been prepared under a standardization request 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. : aerospace).
According to the CEN-CENELEC Internal Regulations, the national standards organisations 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, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia,
Spain, Sweden, Switz
...