Version 1.4 2015 Page 20 of 27
© Requirements Engineering Qualifications Board
requirement that enriches its definition beyond the statement of intended functionality. Examples
include origin, rationale, priority, owner, release number, and version number [Wiegers].
Requirements Development (RD): A collection of activities, tasks, techniques and tools to identify,
analyze, document and validate customer, product and product component/system requirements.
Requirements Elicitation: see Elicitation.
Requirements Engineering (RE): Is a sub-discipline of Software Engineering, focused on determining
and managing the requirements of hardware and software systems..
Requirements Management (RM):
The management of all requirements received by or generated
by the project or work group, including both technical and nontechnical requirements as well as
those requirements levied on the project or work group by the organization. [after CMMI]
Requirements Management tool: A tool that supports the recording of requirements, requirements
attributes (e.g. priority, knowledge responsible) and annotation, and facilitates traceability through
layers of requirements and requirements change management. Some requirements management
tools also provide facilities for static analysis, such as consistency checking and violations to pre-
defined requirements rules.
Requirements model: A representation of user requirements using text and diagrams. Requirements
models can also be called user requirements models or analysis models and can supplement textual
requirements specifications.
Requirements phase: The period of time in the software lifecycle during which the requirements for
a software product are defined and documented [IEEE 610].
Requirements source: The source from which requirements have been derived. Requirements
sources can be stakeholders, documents, business processes, existing systems, market etc.
Requirements specification: A specification describing the business problem area. Requirements
specification is usually provided by the customer and contains a description of the required
capabilities of a solution from the customer's point of view.
Requirements traceability: The ability to define, capture and follow the traces left by requirements
on other elements of the software development environment and the trace left by those elements
on requirements [Pinheiro F.A.C. and Goguen J.A].
Requirements Traceability Matrix (RTM): A document, usually in the form of a table, which
correlates any two baselined documents that require a many to many relationship to determine the
completeness of the relationship.
Requirement Validation: confirmation by examination that requirements (individually and as a set)
define the right system as intended by stakeholders [after ISO/IEC/IEEE 29148]