National foreword

This British Standard is the UK implementation of ISO/IEC/IEEE 29148:2018. It supersedes BS ISO/IEC/IEEE 29148:2011, which is withdrawn.

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 30 November 2018.

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 nongovernmental, 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.

The procedures used to develop this document and those intended for its further maintenance are described in the ISO/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 rules given in the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

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.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC 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 declarations received (see www.iso.org/patents).

Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISO's adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.

This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Systems and software engineering, in cooperation with the Systems and Software Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE.

This second edition cancels and replaces the first edition (ISO/IEC/IEEE 29148:2011), which has been technically revised.

Changes in this revision of ISO/IEC/IEEE 29148 were developed in response to the revision of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. The purpose of these revisions is to accomplish the harmonization of the structures and contents of the two documents, while supporting the requirements of the assessment community.

Any feedback or questions on this document should be directed to the user’s national standards body. A complete listing of these bodies can be found at www.iso.org/members.html.

Introduction

This document provides a unified treatment of the processes and products involved in engineering requirements throughout the life cycle of systems and software. It provides details for the construct of well-formed textual requirements, to include characteristics and attributes, in the context of system and software engineering. This document also provides guidance for the implementation of requirements related processes from ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. Finally, this document identifies information items related to requirements engineering and their content.

1 Scope

This document:

specifies the required processes implemented in the engineering activities that result in requirements for systems and software products (including services) throughout the life cycle;
provides guidelines for applying the requirements and requirements-related processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207;
specifies the required information items produced through the implementation of the requirements processes;
specifies the required contents of the required information items;
provides guidelines for the format of the required and related information items.

This document is applicable to:

those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 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 the 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/IEEE 15288 and/or ISO/IEC/IEEE12207;
those who use or plan to use ISO/IEC/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software and hardware products and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity;
anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conforms to ISO/IEC/IEEE 15289.

2 Normative references

3 Terms, definitions and abbreviated terms

3.1 Terms and definitions

3.2 Abbreviated terms

4 Conformance

4.1 Intended usage

4.2 Full conformance

4.3 Conformance to processes

4.4 Conformance to information item content

4.5 Tailored conformance

5 Concepts

5.1 General

5.2 Requirements fundamentals

5.3 Practical considerations

5.4 Requirement information items

6 Processes

6.1 Requirement processes

6.2 Business or mission analysis process

6.3 Stakeholder needs and requirements definition process

6.4 System [System/Software] Requirements definition process

6.5 Requirements engineering activities in other technical processes

6.6 Requirements management

7 Information items

8 Guidelines for information items

8.1 Requirements information item outlines

8.2 Business requirements specification

8.3 Stakeholder requirements specification

8.4 System requirements specification

8.5 Software requirements specification

9 Information item content

9.1 General

9.2 General content

9.3 Business requirements specification (BRS) content

9.4 Stakeholder requirements specification (StRS) content

9.5 System requirements specification (SyRS) content

9.6 Software requirements specification (SRS) content

Bibliography

BS ISO/IEC/IEEE 29148:2018

Systems and software engineering. Life cycle processes. Requirements engineering

Current

Published:

30 Nov 2018