1、November 2014 Translation by DIN-Sprachendienst.English price group 13No part of this translation may be reproduced without prior permission ofDIN Deutsches Institut fr Normung e. V., Berlin. Beuth Verlag GmbH, 10772 Berlin, Germany,has the exclusive right of sale for German Standards (DIN-Normen).I
2、CS 49.140!% 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 elect
3、romagnetic 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 DIN EN 16603-10-06:2014-11 EN 16603-10-06:2014 (E) 9 3.2.5 function inten
4、ded 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 compo
5、nents 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
6、 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 a
7、n 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 132
8、5-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. DIN EN 16603-10-06:2014-11 E
9、N 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 associated constraints and environment, the operational and performances features NOTE The TS is the baseline of the business agreement to develop or
10、 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 IEC International Electrotechnical Commi
11、ssion TS technical requirements specification MDD mission definition document DIN EN 16603-10-06:2014-11 EN 16603-10-06:2014 (E) 11 4 Technical requirements specification purpose and description 4.1 Technical requirements specification purpose and description The technical requirements specification
12、 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
13、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
14、 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 ma
15、jor 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
16、). DIN EN 16603-10-06:2014-11 EN 16603-10-06:2014 (E)12 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 d
17、efine 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:
18、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 add
19、itional 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 cycl
20、e. DIN EN 16603-10-06:2014-11 EN 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 suc
21、cessive 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 requi
22、rements. 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 custo
23、mer 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 contain
24、ed 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 establ
25、ish 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 T
26、S, as illustrated in Figure 5-1. The purpose of this preliminary TS is to express the customers 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 s
27、tep. DIN EN 16603-10-06:2014-11 EN 16603-10-06:2014 (E)14 With:#a = Rough technical requirements#b = Structured technical requirements#c = Assessed technical requirementsF1.3:AssessF1.2:StructureF1.4:Establish#a#b#cPreliminary technical specificationMission statementNeed analysisLessons learnedF1.1:
28、Identify 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 establ
29、ishes 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
30、into account the induced constraints from the possible concepts. Figure 5-2 illustrates this process. DIN EN 16603-10-06:2014-11 EN 16603-10-06:2014 (E) 15 F1.5:Identify possible conceptsF1.6:Select possible conceptsF1.7:EnhanceF1.9:AssessF1.8:StructureF1.10:Establish#a#b#c#d#eLessons learnedTechnol
31、ogy maturityProgrammatic elementsPreliminary technical specificationEnvironmental constraintGeneral recommendation for specification establishmentInvitation to tenderTechnical specificationWith:#a = Proposal of possible concepts#b = Selected preferred concepts#c = New or adjusted technical requireme
32、nts#d = Structured technical requirements#e = Assessed technical requirementsDatabase of conceptsCustomerCustomerFigure 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 ev
33、aluates 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
34、.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
35、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
36、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 specificatio
37、ns 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. DIN EN 16603-10-06:2014-11 EN 16603-10-06:2014 (E)16 6 Technical requirements types 6.1 Gener
38、al 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 requiremen
39、ts, 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, verific
40、ation 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. N
41、OTE 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”. DIN EN 16603-10-06:2014-11 EN 16603-10-06:2014 (E) 17 6.2.3 Mission requirements Requirements related to a task, a function, a constraint, or an action in
42、duced 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 item
43、s. 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
44、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 nullC to 50 nullC”. 6.2.
45、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 s
46、hall 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 charact
47、eristics: decision making, muscular strength, coordination and craftsmanship, DIN EN 16603-10-06:2014-11 EN 16603-10-06:2014 (E)18 body dimensions, perception and judgement, workload, and comfort and freedom from environmental stress. NOTE 2 For example: “The product shall display the information wi
48、th 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 s
49、ubjects: the constraints concerning the maintenance (e.g. minimum periodicity, intervention duration, infrastructure, tooling, intervention modes), packaging, transportation, handling and storage, training of product users, user documentation, implementation of the product at the users site, and reuse of the product or its elements. NOTE 2 For example: “The product shall be designed to be installed at the customers site within two days”. 6.2.9 Physical requirements Requirements that establish the bound
