The process of assessing whether a ↑system satisfies all its ↑requirements.
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
-
AbnahmeAcceptance
-
AbnahmekriterienAcceptance criteria
1. The criteria that a ↑work product must satisfy to be accepted by the ↑stakeholders .
2. In agile development: Criteria that the implementation of a ↑backlog item must satisfy in order to be accepted by the stakeholders. -
AbnahmetestAcceptance test
A test that assesses whether a ↑system satisfies its ↑requirements.
Note:Typically used by ↑customers or ↑clients to determine whether or not to accept a system.
-
AktivitätActivity
An action or a set of actions that a person or group performs to accomplish a ↑task .
-
AktivitätsdiagrammActivity diagram
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.
-
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).
-
AgilAgile
Synonym: Agilität
1. In general:
a. Able to move quickly and easily.
b. Quick, smart, and clever.
2. In software development: A development approach which builds a product ↑incrementally by dividing work into ↑iterations of fixed duration ( ↑timeboxes ).Note:Agile development is characterized by focusing on delivering a working product in each iteration, collaboration with ↑stakeholders with frequent feedback and adaptation of plans after each iteration based on feedback and changed ↑requirements.
-
AnwendungsbereichApplication domain
-
ArtefaktArtifact
-
AssoziationAssociation
In UML: A relationship between two ↑classes in a ↑UML ↑class model.
-
AttributAttribute
-
ÄnderungsausschussChange control board
Synonym: Change Control Board
A committee of ↑client and ↑supplier representatives that decides on ↑change requests .
Abbreviation: CCBNote:The Change control board should not be confused with a change advisory board, which is a committee that evaluates change requests for a ↑system in operation and typically has no decision power.
-
ÄnderungsmanagementChange management
A controlled way to effect or deny a requested change of a ↑work product.
-
ÄnderungsantragChange request
In RE: A well-argued request for changing one or more ↑baselined ↑requirements.
-
ÄnderbarkeitChangeability
-
AuftraggeberClientNote:
1. In most cases, clients are ↑stakeholders .
2. Frequently, the persons or organizatons who order a system are different from those who receive the systen after it has been built. Therefore, we distginguish between clients and ↑customers . -
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 .
-
AnforderungRequirement
1. A need perceived by a ↑stakeholder .
2. A capability or property that a ↑system shall have.
3. A documented representation of a need, capability or property. -
AnforderungsanalyseRequirements analysis
1. Analysis of elicited ↑requirements in order to understand and document them.
2. Synonym for ↑Requirements Engineering. -
AnforderungsbasislinieRequirements baseline
A ↑baseline for a set of ↑requirements.
-
AnforderungsverzweigungRequirements branching
-
AnforderungskonfigurationRequirements configuration
-
AnforderungskonfliktRequirements conflict
1. A situation where two or more ↑requirements cannot be satisfied together.
2. A situation where two or more ↑stakeholders disagree about certain ↑requirements.Note:Requirements conflicts have to be solved by ↑requirements negotiation.
-
AnforderungsermittlungRequirements discovery
-
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 ).
-
AnforderungsmodellRequirements model
A ↑model that has been created with the purpose of specifying ↑requirements.
-
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.
-
AufgabeTask
A coherent chunk of work to be done.
-
ArbeitsergebnisWork product
Synonym: artifact
A recorded, intermediate or final result generated in a work ↑process .