National foreword

This British 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 publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application.

Compliance with a British Standard cannot confer immunity from legal obligations.

This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 December 2011.

Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for 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 collaborate 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 are 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 volunteers 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 not 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 International 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 require 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 may 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 licensing 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 Standards 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 Standards Development Organization cooperation agreement between ISO and IEEE.

Introduction

This International Standard provides a unified treatment of the processes and products involved 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 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 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 engineering — Life cycle management — Part 1: Guide for life cycle management
ISO/IEC/IEEE 24765, Systems and software engineering — Vocabulary

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,
gives 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 processes,
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 systems, 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:2011 on projects dealing with man-made systems, 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, and
anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.

2 Conformance

2.1 Intended Usage

2.2 Conformance to processes

2.3 Conformance to information item content

2.4 Full conformance

2.5 Tailored conformance

3 Normative references

4 Terms, definitions and abbreviated terms

4.1 Terms and definitions

4.2 Abbreviated terms

5 Concepts

5.1 Introduction

5.2 Requirements fundamentals

5.3 Practical considerations

5.4 Requirement information items

6 Processes

6.1 Requirement processes

6.2 Stakeholder requirements definition process

6.3 Requirements analysis process

6.4 Requirements engineering activities in other technical processes

6.5 Requirements management

7 Information items

8 Guidelines for information items

8.1 Requirements information item outlines

8.2 Stakeholder requirements specification document

8.3 System requirements specification document

8.4 Software requirements specification document

9 Information item content

9.1 Introduction

9.2 General content

9.3 Stakeholder requirements specification (StRS) document

9.4 System requirements specification (SyRS) document

9.5 Software requirements specification (SRS) document

Bibliography

BS ISO/IEC/IEEE 29148:2011

Systems and software engineering. Life cycle processes. Requirements engineering

Published:

31 Dec 2011

Withdrawn:

30 Nov 2018