SIST EN 16603-10-06:2014
(Main)Space engineering - Part 10-06: Technical requirements specification
Space engineering - Part 10-06: Technical requirements specification
EN 16603-10-06 provides an overview of 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 tailored for the specific characteristic and constraints of a space project in conformance with ECSS-S-ST-00.
Raumfahrttechnik - Teil 10-06: Spezifizierung technischer Anforderungen
Ingénierie spatiale - Partie 10-06: Spécification technique de besoin
Vesoljska tehnika - 10-6. del: Specifikacija tehničnih zahtev
Standard EN 16603-10-06 zagotavlja pregled namenov in stališč specifikacije tehničnih zahtev, opredeljuje različne vrste zahtev ter določa zahteve glede tehnične specifikacije in njenih zahtev. Ta standard se uporablja za vse vrste vesoljskih sistemov, vse elemente izdelkov in projekte. Ta standard se lahko prilagodi posameznim lastnostim in omejitvam vesoljskega projekta v skladu s standardom ECSS-S-ST-00.
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 16603-10-06:2014
01-november-2014
1DGRPHãþD
SIST EN ISO 21351:2005
9HVROMVNDWHKQLNDGHO 6SHFLILNDFLMDWHKQLþQLK]DKWHY
Space engineering - Part 10-06: Technical requirements specification
Raumfahrttechnik - Teil 10-06: Spezifizierung technischer Anforderungen
Ingénierie spatiale - Partie 10-06: Spécification technique de besoin
Ta slovenski standard je istoveten z: EN 16603-10-06:2014
ICS:
49.140 Vesoljski sistemi in operacije Space systems and
operations
SIST EN 16603-10-06:2014 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 16603-10-06:2014
---------------------- Page: 2 ----------------------
SIST EN 16603-10-06:2014
EUROPEAN STANDARD
EN 16603-10-06
NORME EUROPÉENNE
EUROPÄISCHE NORM
August 2014
ICS 49.140 Supersedes EN ISO 21351:2005
English version
Space engineering - Part 10-06: Technical requirements
specification
Ingénierie spatiale - Partie 10-06: Spécification technique Raumfahrttechnik - Teil 10-06: Spezifizierung technischer
de besoin Anforderungen
This European Standard was approved by CEN on 28 December 2013.
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, 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 form and by any means reserved Ref. No. EN 16603-10-06:2014 E
worldwide for CEN national Members and for CENELEC
Members.
---------------------- Page: 3 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
Table of contents
Foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 7
3 Terms, definitions and abbreviated terms . 8
3.1 Terms 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 requirements 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 requirements . 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 Configuration requirements . 19
2
---------------------- Page: 4 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
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.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 General . 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
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 to establish the preliminary TS in Phase 0 . 14
Figure 5-2: Process to establish the TS in phase A . 15
3
---------------------- Page: 5 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
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.
This 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 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 identifying any or all such patent rights.
This document will supersede EN ISO 21351:2005.
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 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
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, France,
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.
4
---------------------- Page: 6 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
Introduction
This Standard addresses 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.
5
---------------------- Page: 7 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
1
Scope
This Standard provides an overview of 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 tailored for the specific characteristic and constraints of a
space project in conformance with ECSS-S-ST-00.
6
---------------------- Page: 8 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
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, 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 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
7
---------------------- Page: 9 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
3
Terms, 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 standard
3.2.1 constraint
characteristic, result or design feature which is made compulsory or has been
prohibited 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 operational conditions, law,
standards, market demand, investments and
means availability, or the organization’s 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 Examples 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 environment
external factors affecting development tools, methods, or
processes
8
---------------------- Page: 10 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
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 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 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 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 functions 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 specification and
test specification), or products (e.g. technical
requirements specification)
NOTE 2 Adapted from ISO 9000:2000.
9
---------------------- Page: 11 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
3.2.11 technical requirements specification
document by which the customer establishes the intended purpose of a
product, its associated 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 this Standard, the abbreviated terms from ECSS-S-ST-00-01
and the following apply:
Abbreviation Meaning
International Electrotechnical Commission
IEC
technical requirements specification
TS
mission definition document
MDD
10
---------------------- Page: 12 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
4
Technical requirements specification
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 of 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 reference 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 change 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);
• General information related to the context of the project, the product or
system;
• Technical requirements (described in clauses 6 and 8).
11
---------------------- Page: 13 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
The specification provides the general information related to its context:
• Administrative information: to provide 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) documents 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 provide 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);
• to provide information on the environment and its constraints;
• to detail the different situations of the product or system life cycle.
12
---------------------- Page: 14 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
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 / requirements (e.g. at
Phase 0), evolving progressively to a more precise (e.g. at phase B) or frozen
(e.g. Phase C, or procurement of an equipment) definition of all requirements.
The procurement of products is governed by business agreements between two
parties - the customer and the supplier. At any intermediate level, the supplier
of an item acts as customer in specifying components towards its suppliers.
A business agreement results from a process between a customer with a
problem to solve, and a supplier with potential solutions. This results in a set of
requirements that engages both parties. The list of technical requirements
constitutes an important part of the business agreement and is adapted to the
nature of the expected outcome. This list is contained in the technical
requirements specification.
5.2 Process for establishing a technical requirements
specification
The process to establish the technical requirements specification during Phase 0
of a project starts with the identification and evaluation of the different possible
concepts to establish the TS . This step is needed in phase 0 for space projects
with low heritage. It can also be required in Phase A.
NOTE A functional analysis can be performed to
capture the technical requirements
(see EN 12973).
It consists of an initial assessment of the project and results in the preliminary
TS, as illustrated in Figure 5-1. The purpose of this preliminary TS is to express
the customer’s need, mission statement, associated environmental constraint
and programmatic element in terms of technical requirements (i.e. the problem
to solve). This document serves as a basis to initiate the next step.
13
---------------------- Page: 15 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
Environmental Programmatic
constraint elements
Mission statement General recommendation for
F1.1:
specification establishment
Need analysis Identify &
capture F1.4: Preliminary technical
Lessons learned
specification
Establish
#a
F1.2:
Structure
#c
#b
F1.3:
Assess
Customer
With:
#a = Rough technical requirements
#b = Structured technical requirements
#c = Assessed technical requirements
Figure 5-1: Process to establish the preliminary TS in Phase 0
Where:
• The F1.1 task: The customer identifies and captures the user’s needs or
mission statements, associated environments and constraints. He
expresses these in terms of technical requirements;
• The F1.2 task: The customer structures, classifies and justifies (see 8.1.1)
individual technical requirements;
• The F1.3 task: The customer assesses the entire set of technical
requirements for correctness, consistency and suitability for the intended
use;
• The F1.4 task: The customer establishes the preliminary TS and releases it.
The second step consists of the exploration among the different possible
concepts ensuring the conformity to the defined needs, then the selection of one
concept, and results in the TS. This version is progressively drafted from the
preliminary TS and takes into account the induced constraints from the possible
concepts. Figure 5-2 illustrates this process.
14
---------------------- Page: 16 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
Technology Programmatic
maturity elements
Lessons learned F1.5:
Identify
General recommendation for
Database of concepts
possible
specification establishment
Technical specification
concepts
#a
F1.10:
Preliminary technical
Establish
specification
F1.6: Invitation to tender
Select Environmental
constraint
possible
#e
concepts
F1.9:
#b
Assess
F1.7:
Enhance
#d
#c
F1.8:
Structure
Customer Customer
With:
#a = Proposal of possible concepts
#b = Selected preferred concepts
#c = New or adjusted technical requirements
#d = Structured technical requirements
#e = Assessed technical requirements
Figure 5-2: Process to establish the TS in phase A
Where:
• The F1.5 task: The customer reviews the preliminary TS, identifies and
proposes possible concepts;
• The F1.6 task: The customer evaluates and selects preferred concepts;
• The F1.7 task: The customer identifies the need for changes to the
preliminary TS taking into account the limitations and possibilities
induced by the selected preferred concepts. Then, he expresses the
adjusted or new individual technical requirements;
• The F1.8 task: The customer structures, classifies and justifies (see 8.2.1)
the individual technical requirements;
• The F1.9 task: The customer assesses the entire set of technical requirements
for correctness, consistency and suitability for the intended use;
• The F1.10 task: The customer establishes the TS and releases it.
The process described is applicable at each decomposition level where the
solution to be developed is chosen (e.g. for establishing a system level
specification, or a lower level specification).
The outcome of this process, the technical requirements specification (TS), is a
set of technical requirements to be issued by the customer and to be included in
the business agreement for the development.
NOTE The customer, as a result of the negotiation of the
business agreement with the supplier, can decide to
update a few elements of his TS (as of other requirements
specifications attached to the business agreement). This
updated TS is then included in the business agreement
for the next phase. In conformance with ECSS-M-ST-10,
this update is typically done as a result of the SRR.
15
---------------------- Page: 17 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
6
Technical requirements types
6.1 General
The management of the technical requirements is based upon recognition of the
attributes of these technical requirements.
6.2 Identification of types of technical requirements
6.2.1 Introduction
The differing types of technical requirements contained in the TS are as follows
• functional requirements,
• mission requirements,
• interface requirements,
• environmental requirements,
• operational requirements,
• human factor requirements,
• (integrated) logistics support requirements,
• physical requirements,
• product assurance (PA) induced requirements,
• configuration requirements,
• design requirements,
• verification requirements.
NOTE These different technical requirements are
called “user related functions” and constraints
in EN 1325-1.
6.2.2 Functional requirements
Requirements that define what the product shall perform, in order to conform
to the needs / mission statement or requirements of the user.
NOTE For example: “The product shall analyse the
surface of Mars and transmit the data so that it
is at the disposal of the scientific community”.
16
---------------------- Page: 18 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
6.2.3 Mission requirements
Requirements related to a task, a function, a constraint, or an action induced by
the mission scenario.
NOTE For example: “The product shall be designed to
be put in its final position after a transfer
duration shorter than 90 days”.
6.2.4 Interface requirements
Requirements related to the interconnection or relationship characteristics
between the product and other items.
NOTE 1 This includes different types of interfaces (e.g.
physical, thermal, electrical, and protocol).
NOTE 2 For example: “The product shall dialogue with
the ground segment using telemetry”.
6.2.5 Environmental requirements
Requirements related to a product or the system environment during its life
cycle; this includes the natural environments (e.g. planet interactions, free space
and dust) and induced environments (e.g. radiation, electromagnetic, heat,
vibration and contamination).
NOTE For example: “The product shall operate within
the temperature range from 30 ºC to 50 ºC”.
6.2.6 Operational requirements
Requirements related to the system operability.
NOTE 1 This includes operational profiles and the
utilization environment and events to which
the product shall respond (e.g. autonomy,
control and contingency) for each operational
profile.
NOTE 2 For example: “The product shall be designed to
accept control of the viewing function from the
ground segment”.
6.2.7 Human factor requirements
Requirements related to a product or a process adapted to human capabilities
considering basic human characteristics.
NOTE 1 This includes the following basic human
capability characteristics:
• decision making,
• muscular strength, coordination and
craftsmanship,
17
---------------------- Page: 19 ----------------------
SIST EN 16603-10-06:2014
EN 16603-10-06:2014 (E)
• body dimensions,
• perception and judgement,
• workload, and
• comfort and freedom from environmental
stress.
NOTE 2 For example: “The product shall display the
information with no more than two windows
on the screen at the same time”.
6.2.8 (Integrated) logistics support requirements
Requirements related to the (integrated) logistics support considerations to
ensure the effective and economical support of a system for its life cycle.
NOTE 1 This includes the following subjects:
• the constraints concerning the maintenance
(e.g. minimum periodicity, intervention
duration, infrastruct
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.