A high-fidelity ↑prototype that implements critical parts of a ↑system to an extent that ↑stakeholders can use the prototype to see whether the prototyped part of the system will work and behave as expected.
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.
Reset filter
-
Native prototype
-
Natural language
A ↑language that people use for speaking and writing in everyday life.
Note:This is in contrast to artificial languages that people have deliberately created for specific purposes such as programming or specifying.
-
Necessity (of a requirement)
The degree to which an individual ↑requirement is a necessary part of the ↑requirements specification of a ↑system .
-
Negotiation (of requirements)
-
Non-functional requirement
A ↑quality requirement or a ↑constraint .
Note:↑Performance requirements may be regarded as another category of non-functional requirements. In this glossary, performance requirements are considered to be a sub-category of ↑quality requirements .