A diagram type in ↑UML which models the flow of actions in some part of a ↑system including ↑data flows and areas of responsibility where necessary.
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
A
Filter zurücksetzen
-
AktivitätsdiagrammActivity diagram
-
AktivitätsmodellActivity model
-
AkteurActor
-
Adäquatheit (einer Anforderung)Adequacy (of a requirement)
The degree to which a ↑requirement expresses the ↑stakeholders' true and agreed desires and needs (i.e., those they had actually in mind when stating the requirement).
-
AnwendungsbereichApplication domain
-
AttributAttribute
-
ÄnderungsantragChange request
In RE: A well-argued request for changing one or more ↑baselined ↑requirements.
-
AnforderungsartKind of requirement
A classification of requirements according to their kind into ↑system requirements (consisting of ↑functional requirements , ↑quality requirements and ↑constraints ), project requirements, and process requirements.
Note:1. RE is primarily concerned with system requirements.
2. Quality requirements and constraints are also called ↑non-functional requirements . -
ÄnderbarkeitModifiability
The degree to which a ↑work product or ↑system can be modified without degrading its ↑quality .
-
AnforderungsdokumentRequirements document
A document consisting of a ↑requirements specification.
Note:Requirements document is frequently used as a synonym for requirements specification.
-
AnforderungsermittlungRequirements elicitation
Synonym: elicitation (of requirements)
The process of seeking, capturing and consolidating ↑requirements from available ↑sources, potentially including the re-construction or creation of requirements.
-
AnforderungsmanagementRequirements management
The process of managing existing ↑requirements and requirements-related ↑work products, including the storing, changing and tracing of requirements ( ↑traceability ).
-
Abstimmung von AnforderungenRequirements negotiation
Synonym: Verhandlung (von Anforderungen)
A ↑process where ↑stakeholders are working toward reaching an agreement to resolve ↑requirements conflicts.
-
AnforderungsquelleRequirements source
The source from which a ↑requirement has been derived.
Note:Typical sources are ↑stakeholders, documents, existing ↑systems and observations.
-
AnforderungsspezifikationRequirements specification
A systematically represented collection of ↑requirements , typically for a ↑system , that satisfies given criteria.
Note:1. In some situations we distinguish between a ↑customer requirements specification (typically written by the customer) and a ↑system requirements specification or ↑software requirements specification (written by the supplier).
2. Requirements specification may also denote the ↑process of specifying ( ↑eliciting , documenting and ↑validating ) requirements. -
AnforderungsvorlageRequirements template
Synonym: Anforderungsschablone
A template for specifying ↑requirements.
Note:In RE, several forms of templates are used. ↑Phrase templates are used for specifying individual ↑requirements or ↑user stories . ↑Form templates can be used to specify ↑use cases or ↑quality requirements. ↑Document templates provide a predefined structure for ↑requirements documents.
-
ArbeitsergebnisWork product
Synonym: artifact
A recorded, intermediate or final result generated in a work ↑process .