BS ISO 16404-2013 Space systems Programme management Requirements management《空间系统 项目管理 需求管理》.pdf

1、BSI Standards PublicationBS ISO 16404:2013Space systems Programmemanagement RequirementsmanagementBS ISO 16404:2013 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO 16404:2013.The UK participation in its preparation was entrusted to TechnicalCommittee ACE/68/-/5

2、, Space systems and operations - Programmemanagement.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 British

3、Standards Institution 2013. Published by BSI StandardsLimited 2013ISBN 978 0 580 75950 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 31 October 2013.A

4、mendments issued since publicationDate Text affectedBS ISO 16404:2013 ISO 2013Space systems Programme management Requirements managementSystmes spatiaux - Management de programme - Programme management - Management des ExigencesINTERNATIONAL STANDARDISO16404First edition2013-11-15Reference numberISO

5、 16404:2013(E)BS ISO 16404:2013ISO 16404:2013(E)ii ISO 2013 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO 2013All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including ph

6、otocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester.ISO copyright officeCase postale 56 CH-1211 Geneva 20Tel. + 41 22 749 01 11Fax + 41 22 749 09

7、47E-mail copyrightiso.orgWeb www.iso.orgPublished in SwitzerlandBS ISO 16404:2013ISO 16404:2013(E) ISO 2013 All rights reserved iiiContents PageForeword ivIntroduction v1 Scope . 12 Normative references 13 Terms and definitions . 24 Abbreviated terms 45 Objective and scope of Requirements Management

8、 45.1 Objective of Requirements Management . 45.2 Scope and interfaces. 46 Requirements Management overall process . 76.1 Capture needs and develop requirements 96.2 Allocation and flow down requirements . 106.3 Validate requirements . 106.4 Verify design against requirements . 106.5 Verify product

9、against requirements 106.6 Requirements change management 107 Requirements Management plan .117.1 General 117.2 Functional and technical specifications . 118 Rules for Requirements Management .128.1 Rules for deployment of Requirements Management activities .128.2 Rules for Requirements Management 1

10、28.3 Key Performance Indicators . 13Annex A (informative) Requirements Management plan template .15Bibliography .16BS ISO 16404:2013ISO 16404:2013(E)ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work o

11、f preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmenta

12、l, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.The procedures used to develop this document and those intended for its further maintenance are described in the IS

13、O/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2. www.iso.org/directivesAttention is drawn to the possibility tha

14、t some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent de

15、clarations received. www.iso.org/patentsAny trade name used in this document is information given for the convenience of users and does not constitute an endorsement.For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about

16、 ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: http:/www.iso.org/iso/home/standards_development/resources-for-technical-work/foreword.htmThe committee responsible for this document is ISO/TC 20, Aircraft and space vehicles, Subcommittee SC 14, S

17、pace systems and operations.iv ISO 2013 All rights reservedBS ISO 16404:2013ISO 16404:2013(E)IntroductionThere is consensus that successful aerospace programmes/projects depend on meeting the needs and requirements of the stakeholders/customers. When the requirements are for a complex system or for

18、a system that may take many years to be developed, a formal Requirements Management (RM) process is mandatory and justified.Requirements Management concerns the collection, analysis, and validation of requirements with all the communications and negotiations inherent in working with people.This Inte

19、rnational Standard will help to clarify and enhance current practices to improve Programme Management. It is intended to be used by space programmes when establishing, performing, or evaluating Requirements Management processes in the space sector.This International Standard describes Requirements M

20、anagement functions and principles and defines a common Requirements Management terminology for use with any product line.Requirements Management is an integral element of any programme, but, in space, it is particularly important due to specific environmental conditions in space, a need for a high

21、level of performance, a limited number of models, limited access to the product during operations, quasi-impossibility of repairing in the case of failure during flight, often high complexity of the organization, and associated high costs.The deployment of this standardized common set of Requirement

22、s Management is intended to encourage and facilitate international space cooperation.Annex A of this International Standard gives the general template for a Requirements Management plan. ISO 2013 All rights reserved vBS ISO 16404:2013BS ISO 16404:2013Space systems Programme management Requirements m

23、anagement1 ScopeThis International Standard presents the requirements for Requirements Management (RM) for space projects.This International Standard addresses the space programme/project management requirements, applicable through a top-down approach in a contractual relationship between customers

24、and suppliers.The objective of this International Standard is to state and establish a common reference framework for all the customers and suppliers in the space sector to deploy Requirements Management for all space products and projects.This International Standard on Requirements Management inclu

25、des a definition of the Requirements Management scope for the space sector, the standard processes for Requirements Management within the product lifecycle management, and a set of rules for Requirements Management activities to be implemented by the actors (customers and suppliers), including rules

26、 derived from best practices.The primary target audience for this International Standard includes the Requirements Management/Systems Engineering process owners of the customers and suppliers, the Programme/Project Managers managing the space programmes, and the Chief Engineers and the Quality Manag

27、ers.The term programme is understood as a group of several projects. Both “programme” and “project” may be used in the same context throughout this International Standard.ISO 21351 defines the requirements for the format and the content of the functional and technical specifications.In addition, it

28、allows customer/supplier flexibility in its implementation and tailoring.2 Normative referencesThe following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated refere

29、nces, the latest edition of the referenced document (including any amendments) applies.ISO 9000:2005, Quality management systems Fundamentals and vocabularyISO 10795, Space systems Programme management and quality VocabularyISO 14300-1, Space systems Programme management Part 1: Structuring of a pro

30、jectISO 21351, Space systems Functional and technical specificationISO/IEC/IEEE 29148 Systems and software engineering Life cycle processes Requirements engineeringINTERNATIONAL STANDARD ISO 16404:2013(E) ISO 2013 All rights reserved 1BS ISO 16404:2013ISO 16404:2013(E)3 Terms and definitionsFor the

31、purposes of this document, the terms and definitions in ISO 9000:2005 and ISO 10795 and the following apply.3.1design verificationevaluation of the implementation of the design (architecture, components) against the requirements to determine that they can be metNote 1 to entry: This is compliant wit

32、h ISO 9001 Verification.3.2product lifecycledescription of all stages of the product throughout its life starting from the expression of its need until the disposal, whatever the form is3.3product verificationevaluation of the implementation of the product against the requirements to determine that

33、they have been metNote 1 to entry: This is compliant with ISO 9001 Verification.3.4qualificationact or conduct of the supplier to provide evidences to prove that the design and manufacturing (including manufacturing process) of hardware/software is adequate to fulfil all requirements under required

34、environment conditionsNote 1 to entry: This may be implemented by analysis, test, inspection, or demonstration of a set of tasks that provide proofs, while basing on theoretical and experimental justifications that the defined product satisfies the specified need and can be produced.Note 2 to entry:

35、 The qualification decision is the act by which the customer, at the origin of the technical specification, attests on the basis of theoretical and experimental justifications that the defined product, identified by the design data file, meets all the requirements of the technical specification and

36、can be produced.3.5requirementformalized statement identifying a capability, a functionality, a physical characteristic, or a quality that must be met or possessed by a system or system component to satisfy a contract, a standard, a specification, or other formally imposed documentsNote 1 to entry:

37、A requirement may be developed at any point in the product lifecycle by any number of stakeholders.Note 2 to entry: A requirement is a need or expectation that is stated, generally implied, or obligatory.SOURCE: ISO 107953.6requirements baselineset of requirements that has been formally reviewed and

38、 agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures3.7Requirements ManagementRMdiscipline that covers all the tasks that shall be performed to manage requirements, such as gathering, developing, organizing,

39、tracing, analysing, reviewing, allocating, changing, and validating requirement objects, as well as managing documents and databases that contain them with the purpose of defining and delivering the right product or service2 ISO 2013 All rights reservedBS ISO 16404:2013ISO 16404:2013(E)3.8Requiremen

40、ts Management planRM planmanagement plan which describes all the activities related to Requirements Management for a specific project or programme that includes the requirement cascading activity and the Requirements Management interaction with Configuration Management and Functional AnalysisNote 1

41、to entry: This plan describes the activities that need to be performed to support the verification and validation activities in order that the design and product can be verified against requirements.3.9requirement validationset of activities to ensure that requirements are correct and complete so th

42、at the product meets upper-level requirements and user needs3.10stakeholderscustomers and/or users3.11Systems Engineeringinterdisciplinary approach and means to enable the realization of successful systems, starting with the definition of customer needs, the identification of product functionality,

43、and the intended validation very early in the lifecycleNote 1 to entry: Systems Engineering considers both the business and the technical needs of all customers with the goal of providing a quality product that meets the users needs.3.12traceabilityability to identify the relationship between variou

44、s artefacts of the development processEXAMPLE Artefacts of the development process include the lineage of requirements, the relationship between a design decision and the affected requirements and design features, the assignments of requirements to design features, and the relationship of test resul

45、ts to the original source of the requirement.Note 1 to entry: Bidirectional traceability is required to permit top-down impact analysis and down-top traceability analysis.Note 2 to entry: Traceability is the ability to trace the history, application, or location of that which is under consideration.

46、SOURCE: ISO 10795 ISO 2013 All rights reserved 3BS ISO 16404:2013ISO 16404:2013(E)4 Abbreviated termsThe following abbreviated terms are used in this document.CM Configuration ManagementKPI Key Performance IndicatorsPLM Product Lifecycle ManagementRM Requirements ManagementROI Return on InvestmentSE

47、 Systems EngineeringSMART Specific, Measurable, Achievable, Relevant, and TraceableTBC to be confirmedTBD to be definedV2) allocate and flow down the requirements;3) validate the requirements;4) verify the design against the requirements;5) verify the product against the requirements;6) manage the r

48、equirement changes.d) Requirements Management is an essential part of Systems Engineering. Requirements Management does not cover the full Systems Engineering discipline, but it is strongly linked to all elements of Systems Engineering.e) The major objects managed by Requirements Management are1) “R

49、equirement” (object to be detailed with attributes such as stakeholder, source, rationale, identification, author, status, allocation to design, and statement of the verification method),2) “Links” (object to be detailed as the link between requirements, but also links from/to other objects enabling Requirements Management to reach its primary objective and ensuring that stakeholders needs are understood and realized),3) “Input documents” (source documents or data that contain the requirements),4) “Output documen