The range of things that can be shaped and designed when developing a ↑system .
Das CPRE Glossar
Ein gemeinsames Verständnis der verwendeten Begriffe ist die Grundlage für erfolgreiches RE. Das CPRE Glossar umfasst die Kernbegriffe des Requirements Engineering - es ist das zentrale Nachschlagewerk über alle CPRE Module und Ebenen hinweg!
Die Glossare sind in verschiedenen Sprachen auch zum Download verfügbar.
Das CPRE Glossar: Die wichtigsten Begriffe des Requirements Engineering im Überblick
Bitte beachten Sie, dass die Begriffsdefinitionen in den Glossaren bewusst nur auf Englisch existieren, um Unschärfen oder Interpretationsspielraum, die aus Übersetzungen resultieren können, auszuschließen.
Zu dieser Filterung wurden keine Einträge gefunden.
Filter zurücksetzen
U
Filter zurücksetzen
-
Umfang (einer Systementwicklung)Scope (of a system development)
-
UMLUML
Abbreviation for Unified Modeling Language, a standardized language for modeling problems or solutions.
-
Use CaseUse 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 DiagrammUse 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 ModellUse case model
Synonym: Anwendungsfallmodell
A ↑model consisting of a set of ↑use cases , typically together with a ↑use case diagram.
-
User StoryUser 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 VorlageUser 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>. -
Überprüfbarkeit (von Anforderungen)Verifiability (of requirements)
The degree to which the fulfillment of a ↑requirement by an implemented ↑system can be verified.
Note:Such ↑verification can be performed, for example by defining ↑acceptance test cases, measurements or ↑inspection procedures.