Abbreviation for Unified Modeling Language, a standardized language for modeling problems or solutions.
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 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
U
Reset filter
-
UML
-
Unambiguity (of requirements)
The degree to which a ↑requirement is expressed such that it cannot be understood differently by different people.
-
Understandability
The degree to which an ↑item is comprehensible to its intended users.
Note:Typical items are: a ↑system , a ↑work product , or a part thereof.
-
Usability
-
Use case
A set of possible interactions between external ↑actors and a ↑system that provide a benefit for the actor(s) involved.
Note:Use cases specify a system from a user’s (or other external actor’s) perspective: every use case describes some ↑functionality that the system must provide for the actors involved in the use case.
-
Use case diagram
A diagram type in UML that models the ↑actors and the ↑use cases of a ↑system .
Note:The boundary between the actors and the use cases constitutes the ↑system boundary.
-
Use case model
A ↑model consisting of a set of ↑use cases , typically together with a ↑use case diagram.
-
User
A person who uses the ↑functionality provided by a ↑system .
Note:Users (also called end users) always are ↑stakeholders of a ↑system .
-
User requirement
A ↑requirement expressing a ↑user need.
Note:User requirements are typically about what a system should do for certain users and how they can interact with the system. User requirements are a subset of ↑stakeholder requirements .
-
User story
A short narrative describing a need from a ↑user’s perspective together with the expected benefit when this need is satisfied. Also see ↑story .
Note:1. User stories are typically written in ↑natural language using the ↑user story template and are usually accompanied by ↑acceptance criteria .
2. In agile development, user stories serve as a user-oriented way to discuss and formulate ↑requirements . They are typically considered to be atomic ↑backlog items , that is, items which are not further decomposed in the ↑backlog (see ↑story ). -
User story template
A ↑phrase template of the form As a <role/person>, I want <something> so that <benefit>.
Note:1. Most ↑user stories are written using this template.
2. In agile development, this template is also used for expressing other ↑backlog items that communicate stakeholder needs, for example, ↑epics.
3. Some authors replace <something> by more concrete concepts such as <goal>, <desire>, or <target>.