Multiple occurrence of the same information or resource.
The CPRE Glossary
The basis for successful RE is a common understanding of the terms used. The CPRE Glossary covers the core terms of Requirements Engineering—it is the central reference work across all CPRE modules and levels! The RE@Agile Glossary supplements the CPRE Glossary with terms for Requirements Engineering in an agile environment.
The glossaries are also available in various languages for download.
The CPRE Glossary: An overview of the most important Requirements Engineering terms
Please note that the definitions of terms in the glossaries are deliberately in English only in order to exclude any ambiguities or scope for interpretation that may result from translations.
No matching results found.
Reset filter
R
Reset filter
-
Redundancy
-
Refactoring
The improvement of the internal ↑quality of source code, particularly the structure of the code, without changing its observable behavior.
-
Release
A ↑configuration that has been released for installation and use by ↑customers.
-
Reliability
The degree to which a ↑system performs specified functions under specified conditions for a specified period of time.
Note:Reliability may be stated as a ↑quality requirement .
-
Requirement
1. A need perceived by a ↑stakeholder .
2. A capability or property that a ↑system shall have.
3. A documented representation of a need, capability or property. -
Requirements analysis
1. Analysis of elicited ↑requirements in order to understand and document them.
2. Synonym for ↑Requirements Engineering. -
Requirements baseline
A ↑baseline for a set of ↑requirements.
-
Requirements branching
-
Requirements configuration
-
Requirements conflict
1. A situation where two or more ↑requirements cannot be satisfied together.
2. A situation where two or more ↑stakeholders disagree about certain ↑requirements.Note:Requirements conflicts have to be solved by ↑requirements negotiation.
-
Requirements discovery
-
Requirements document
A document consisting of a ↑requirements specification.
Note:Requirements document is frequently used as a synonym for requirements specification.
-
Requirements elicitation
Synonym: elicitation (of requirements)
The process of seeking, capturing and consolidating ↑requirements from available ↑sources, potentially including the re-construction or creation of requirements.
-
Requirements Engineer
A person who – in collaboration with ↑stakeholders – elicits, documents, validates, and manages ↑requirements.
Note:In most cases, requirements engineer is a ↑role and not a job title.
-
Requirements Engineering
The systematic and disciplined approach to the ↑specification and management of ↑requirements with the goal of understanding the ↑stakeholders’ desires and needs and minimizing the risk of delivering a ↑system that does not meet these desires and needs.
Abbreviation: RE -
Requirements management
The process of managing existing ↑requirements and requirements-related ↑work products, including the storing, changing and tracing of requirements ( ↑traceability ).
-
Requirements model
A ↑model that has been created with the purpose of specifying ↑requirements.
-
Requirements negotiation
A ↑process where ↑stakeholders are working toward reaching an agreement to resolve ↑requirements conflicts.
-
Requirements source
The source from which a ↑requirement has been derived.
Note:Typical sources are ↑stakeholders, documents, existing ↑systems and observations.
-
Requirements specification
A systematically represented collection of ↑requirements , typically for a ↑system , that satisfies given criteria.
Note:1. In some situations we distinguish between a ↑customer requirements specification (typically written by the customer) and a ↑system requirements specification or ↑software requirements specification (written by the supplier).
2. Requirements specification may also denote the ↑process of specifying ( ↑eliciting , documenting and ↑validating ) requirements. -
Requirements template
A template for specifying ↑requirements.
Note:In RE, several forms of templates are used. ↑Phrase templates are used for specifying individual ↑requirements or ↑user stories . ↑Form templates can be used to specify ↑use cases or ↑quality requirements. ↑Document templates provide a predefined structure for ↑requirements documents.
-
Review
An evaluation of a ↑work product by an individual or a group in order to find problems or suggest improvements.
Note:Evaluation may be performed with respect to both contents and conformance.
-
Risk
A possible event that threatens the success of an endeavor.
Note:A risk is typically assessed in terms of its probability and potential damage.
-
Role
1. A part played by a person in a given context.
2. In ↑UML ↑class models : The parts played by the linked ↑objects in an ↑association .