BS ISO IEC IEEE 29148-2011 Systems and software engineering Life cycle processes Requirements engineering《系统和软件工程 生存周期过程 需求工程》.pdf

1、raising standards worldwide NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW BSI Standards Publication BS ISO/IEC/IEEE 29148:2011 Systems and software engineering Life cycle processes Requirements engineeringBS ISO/IEC/IEEE 29148:2011 BRITISH STANDARD National foreword This Bri

2、tish Standard is the UK implementation of ISO/IEC/IEEE 29148:2011. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained on request to its secretary. This publicatio

3、n does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. BSI 2011 ISBN 978 0 580 71995 0 ICS 35.080 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the auth

4、ority of the Standards Policy and Strategy Committee on 31 December 2011. Amendments issued since publication Date Text affectedBS ISO/IEC/IEEE 29148:2011Reference number ISO/IEC/IEEE 29148:2011(E) ISO/IEC 2011 IEEE 2011INTERNATIONAL STANDARD ISO/IEC/ IEEE 29148 First edition 2011-12-01 Systems and

5、software engineering Life cycle processes Requirements engineering Ingnierie des systmes et du logiciel Processus du cycle de vie Ingnierie des exigences BS ISO/IEC/IEEE 29148:2011 ISO/IEC/IEEE 29148:2011(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licen

6、sing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO

7、 Central Secretariat, the IEC Central Office and IEEE do not accept any liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were op

8、timized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies and IEEE members. In the unlikely event that a problem relating to it is found, please inform the ISO Central Secretariat or IEEE at the address given below. COPYRIGHT PROTECTED DOCUMENT

9、ISO/IEC 2011 IEEE 2011 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ISO, IEC or IEEE at the respective address

10、 below. ISO copyright office IEC Central Office Institute of Electrical and Electronics Engineers, Inc. Case postale 56 3, rue de Varemb 3 Park Avenue, New York CH-1211 Geneva 20 CH-1211 Geneva 20 NY 10016-5997, USA Tel. + 41 22 749 01 11 Switzerland E-mail stds.iprieee.org Fax + 41 22 749 09 47 E-m

11、ail inmailiec.ch Web www.ieee.org E-mail copyrightiso.org Web www.iec.ch Web www.iso.org Published in Switzerland ii ISO/IEC 2011 All rights reserved IEEE 2011 All rights reservedBS ISO/IEC/IEEE 29148:2011 ISO/IEC/IEEE 29148:2011(E) ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved iiiC

12、ontents Page Foreword vi Introduction . vii 1 Scope 1 2 Conformance . 1 2.1 Intended Usage 1 2.2 Conformance to processes 2 2.3 Conformance to information item content 2 2.4 Full conformance . 2 2.5 Tailored conformance . 2 2.5.1 Processes . 2 2.5.2 Information items 3 3 Normative references 3 4 Ter

13、ms, definitions and abbreviated terms 3 4.1 Terms and definitions . 3 4.2 Abbreviated terms . 8 5 Concepts 8 5.1 Introduction 8 5.2 Requirements fundamentals 8 5.2.1 General . 8 5.2.2 Stakeholders 8 5.2.3 Transformation of needs into requirements . 9 5.2.4 Requirements construct . 9 5.2.5 Characteri

14、stics of individual requirements 11 5.2.6 Characteristics of a set of requirements . 11 5.2.7 Requirement language criteria . 12 5.2.8 Requirements attributes . 12 5.3 Practical considerations . 14 5.3.1 Iteration and recursion of processes 14 5.3.2 Iteration and recursion in requirements engineerin

15、g 16 5.4 Requirement information items . 17 6 Processes . 18 6.1 Requirement processes 18 6.1.1 Guidelines for Processes . 19 6.2 Stakeholder requirements definition process 19 6.2.1 Purpose 19 6.2.2 Outcomes . 19 6.2.3 Activities and tasks . 20 6.3 Requirements analysis process 27 6.3.1 Purpose 27

16、6.3.2 Outcomes . 27 6.3.3 Activities and tasks . 27 6.4 Requirements engineering activities in other technical processes . 33 6.4.1 Requirements in architectural design . 33 6.4.2 Requirements in verification 34 6.4.3 Requirements in validation 36 6.5 Requirements management . 37 6.5.1 Management Ov

17、erview 37 6.5.2 Change management 37 6.5.3 Measurement for requirements 39 BS ISO/IEC/IEEE 29148:2011 ISO/IEC/IEEE 29148:2011(E) iv ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved7 Information items .41 8 Guidelines for information items .42 8.1 Requirements information item outlines

18、.42 8.2 Stakeholder requirements specification document .42 8.2.1 Introduction 42 8.2.2 StRS example outline 42 8.3 System requirements specification document .43 8.3.1 Introduction 43 8.3.2 SyRS example outline .44 8.4 Software requirements specification document 45 8.4.1 Introduction 45 8.4.2 SRS

19、example outline .45 9 Information item content .46 9.1 Introduction 46 9.2 General content 46 9.2.1 Identification .46 9.2.2 Front matter 47 9.2.3 Definitions 47 9.2.4 References 47 9.2.5 Acronyms and abbreviations .47 9.3 Stakeholder requirements specification (StRS) document .47 9.3.1 Business pur

20、pose 47 9.3.2 Business scope 48 9.3.3 Business overview 48 9.3.4 Stakeholders 48 9.3.5 Business environment 48 9.3.6 Goal and Objective 48 9.3.7 Business model .48 9.3.8 Information environment 48 9.3.9 Business processes 49 9.3.10 Business operational policies and rules .49 9.3.11 Business operatio

21、nal constraints 49 9.3.12 Business operation modes .49 9.3.13 Business operational quality 49 9.3.14 Business structure 49 9.3.15 User requirements .49 9.3.16 Operational concept 50 9.3.17 Operational scenarios .50 9.3.18 Project constraints 50 9.4 System requirements specification (SyRS) document 5

22、0 9.4.1 System purpose .50 9.4.2 System scope .50 9.4.3 System overview 51 9.4.4 Functional requirements .51 9.4.5 Usability requirements 51 9.4.6 Performance requirements .51 9.4.7 System interfaces 51 9.4.8 System Operations 52 9.4.9 System modes and states .52 9.4.10 Physical characteristics 52 9

23、.4.11 Environmental conditions .53 9.4.12 System security .53 9.4.13 Information management 53 9.4.14 Policies and regulations .53 9.4.15 System life cycle sustainment 53 9.4.16 Packaging, handling, shipping and transportation 53 9.4.17 Verification .54 9.4.18 Assumptions and dependencies 54 9.5 Sof

24、tware requirements specification (SRS) document 54 BS ISO/IEC/IEEE 29148:2011 ISO/IEC/IEEE 29148:2011(E) ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved v9.5.1 Purpose 54 9.5.2 Scope 54 9.5.3 Product perspective 54 9.5.4 Product functions 56 9.5.5 User characteristics 57 9.5.6 Limitat

25、ions . 57 9.5.7 Assumptions and dependencies . 57 9.5.8 Apportioning of requirements 57 9.5.9 Specific requirements . 57 9.5.10 External interfaces 58 9.5.11 Functions . 58 9.5.12 Usability requirements 59 9.5.13 Performance requirements . 59 9.5.14 Logical database requirements . 59 9.5.15 Design c

26、onstraints 60 9.5.16 Standards compliance 60 9.5.17 Software system attributes. 60 9.5.18 Verification . 61 9.5.19 Supporting information . 61 Annex A (normative) System operational concept . 62 A.1 Overview . 62 A.2 Operational concept document (OpsCon) 62 A.2.1 Scope 63 A.2.2 Referenced documents

27、. 63 A.2.3 Current system or situation . 63 A.2.4 Justification for and nature of changes 66 A.2.5 Concepts for the proposed system . 68 A.2.6 Operational scenarios . 70 A.2.7 Summary of impacts . 71 A.2.8 Analysis of the proposed system 72 A.2.9 Appendices 73 A.2.10 Glossary . 73 Annex B (informati

28、ve) Concept of operations 74 B.1 Overview . 74 B.2 Concept of operation document 74 B.2.1 Purpose 74 B.2.2 Scope 74 B.2.3 Strategic plan . 74 B.2.4 Effectiveness . 74 B.2.5 Overall operation . 74 B.2.6 Governance 75 Annex C (informative) Process Mapping from ISO/IEC 15288 and ISO/IEC 12207 . 76 C.1

29、Stakeholder requirements definition process 76 C.2 Requirements analysis Process 77 C.3 Other technical requirements-related processes 78 Annex D (normative) Tailoring policies 80 D.1 Introduction 80 D.2 Information item tailoring process 80 D.2.1 Purpose 80 D.2.2 Outcomes . 80 D.2.3 Activities and

30、tasks . 80 Bibliography 82 BS ISO/IEC/IEEE 29148:2011 ISO/IEC/IEEE 29148:2011(E) vi ISO/IEC 2011 All rights reserved IEEE 2011 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for

31、worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collabora

32、te in fields of mutual interest. Other international organizations, governmental and non- governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. IEEE Standards documents a

33、re developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together voluntee

34、rs representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does n

35、ot independently evaluate, test, or verify the accuracy of any of the information contained in its standards. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft Internat

36、ional Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is called to the possibility that implementation of this standard may re

37、quire the use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential patents or patent claims for which a license m

38、ay be required, for conducting inquiries into the legal validity or scope of patents or patent claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if any, or in any licen

39、sing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from ISO or the IEEE Stan

40、dards Association. ISO/IEC/IEEE 29148 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Software & Systems Engineering Standards Committee of the IEEE Computer Society, under the Partner Stand

41、ards Development Organization cooperation agreement between ISO and IEEE. BS ISO/IEC/IEEE 29148:2011 ISO/IEC/IEEE 29148:2011(E) ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved viiIntroduction This International Standard provides a unified treatment of the processes and products involv

42、ed in engineering requirements throughout the life cycle of systems and software. This International Standard is the result of harmonization of the following sources: ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering Software life cycle processes ISO/IEC 15288:2008 (IEEE Std

43、 15288-2008), Systems and software engineering System life cycle processes ISO/IEC/IEEE 15289:2011, Systems and software engineering Content of life-cycle information products (documentation) ISO/IEC TR 19759, Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) IEEE Std

44、 830, IEEE Recommended Practice for Software Requirements Specifications IEEE Std 1233, IEEE Guide for Developing System Requirements Specifications IEEE Std 1362, IEEE Guide for Information Technology System Definition Concept of Operations (ConOps) Document ISO/IEC TR 24748-1, Systems and software

45、 engineering Life cycle management Part 1: Guide for life cycle management ISO/IEC/IEEE 24765, Systems and software engineering Vocabulary BS ISO/IEC/IEEE 29148:2011BS ISO/IEC/IEEE 29148:2011 INTERNATIONAL STANDARD ISO/IEC/IEEE 29148:2011(E) ISO/IEC 2011 All rights reserved IEEE 2011 All rights rese

46、rved 1Systems and software engineering Life cycle processes Requirements engineering 1 Scope This International Standard specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle, g

47、ives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), specifies the required information items that are to be produced through the implementation of the requirements process

48、es, specifies the required contents of the required information items, and gives guidelines for the format of the required and related information items. This International Standard is applicable to those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made system

49、s, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008), those who use or plan to use ISO/IEC/IEEE 15289