The degree to which an ↑item produces the intended results.
The degree to which resources are expended in relation to results achieved.
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
E
Reset filter
-
Effectiveness
-
Efficiency
-
Elaboration (of requirements)
An umbrella term for requirements ↑elicitation, ↑negotiation and ↑validation.
-
Elicitation (of requirements)
-
End user
-
Entity
-
Entity-relationship diagram
A diagrammatic representation of an ↑entity-realtionship model .
Abbreviation: ERD -
Entity-relationship model
A ↑model of data that are relevant for a ↑system or of the data of an ↑application domain , consisting of a set of entity types that are each characterized by ↑attributes and linked by relationships.
Abbreviation: ER Model -
Epic
In agile development: An abstract description of a ↑stakeholder need which is larger than what can be implemented in a single ↑iteration .
-
Error
1. A human action that produces an incorrect result.
2. A discrepancy between an observed ↑behavior or result and the specified behavior or result.Note:In practice, both meanings are used. Where needed, the meaning of error can be disambiguated by using human error and observed error or observed fault, respectively.
-
Evolutionary prototype
A pilot system forming the core of a ↑system to be developed.
-
Exploratory prototype
A throwaway ↑prototype used to create shared understanding, clarify ↑requirements or validate ↑requirements .