The Anatomy of Requirements
Bertrand Meyer, Jean-Michel Bruel, Sophie Ebersold, Florian Galinier,, Alexandr Naumchev

TL;DR
This paper clarifies fundamental concepts in requirements engineering by providing precise definitions and taxonomies of requirement elements and their relations, aiming to improve understanding and practice in the field.
Contribution
It introduces systematic taxonomies of requirement components and their relationships, addressing vagueness in existing definitions and standards.
Findings
Taxonomies evaluated on published requirements documents
Online quizzes enable testing of the concepts
Clarification aims to foster advances in requirements study and practice
Abstract
Requirements engineering is crucial to software development but lacks a precise definition of its fundamental concepts. Even the basic definitions in the literature and in industry standards are often vague and verbose. To remedy this situation and provide a solid basis for discussions of requirements, this work provides precise definitions of the fundamental requirements concepts and two systematic classifications: a taxonomy of requirement elements (such as components, goals, constraints...) ; and a taxonomy of possible relations between these elements (such as "extends", "excepts", "belongs"...). The discussion evaluates the taxonomies on published requirements documents; readers can test the concepts in two online quizzes. The intended result of this work is to spur new advances in the study and practice of software requirements by clarifying the fundamental concepts.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsModel-Driven Software Engineering Techniques · Advanced Software Engineering Methodologies · Web Applications and Data Management
