The capability of a ↑system to operate as intended despite the presence of (hardware or software) ↑faults .
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
F
Reset filter
-
Fault
-
Fault toleranceNote:
Fault tolerance may be stated as a ↑quality requirement .
-
Feasibility (of a requirement)
The degree to which a ↑requirement for a ↑system can be implemented under existing ↑constraints .
-
Feature
A distinguishing characteristic of a ↑system that provides value for ↑stakeholders .
Note:A feature typically comprises several ↑requirements and is used for communicating with ↑stakeholders on a higher level of abstraction and for expressing variable or optional characteristics.
-
Feature diagram
A diagrammatic representation of a ↑feature model .
-
Feature model
A ↑model describing the variable features of a ↑product line , including their relationships and dependencies.
-
Form template
A template providing a form with predefined fields to be filled-in. ( ↑Requirements template )
Note:In RE, form templates can be used to specify ↑use cases or ↑quality requirements .
-
Functional requirement
A ↑requirement concerning a result or ↑behavior that shall be provided by a function of a ↑system .
-
Functionality
The capabilities of a ↑system as stated by its ↑functional requirements .