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! Das RE@Agile Glossar ergänzt das CPRE Glossar durch Begriffe für das Requirements Engineering im agilen Umfeld.
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.
In agile: Criteria that the implementation of a ↑user story must satisfy in order to be accepted by the ↑stakeholders.
Acceptance criteria may also be written for ↑backlog items other than user stories.
A test that assesses whether a ↑system satisfies its ↑requirements.
Typically used by ↑customers to determine whether or not to accept a system.
An action or a set of actions that a person or group performs to accomplish a ↑task .
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.
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).
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 ).
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.
In UML: A relationship between two ↑classes in a ↑UML ↑class model.
Synonym: Change Control Board
A committee of ↑customer and ↑supplier representatives that decides on ↑change requests .
Abbreviation: CCB
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.
A controlled way to effect or deny a requested change of a ↑work product.
In RE: A well-argued request for changing one or more ↑baselined ↑requirements.
A classification of requirements according to their kind into ↑system requirements (consisting of ↑functional requirements , ↑quality requirements and ↑constraints ), project requirements, and process requirements.
1. RE is primarily concerned with system requirements.
2. Quality requirements and constraints are also called ↑non-functional requirements .
The degree to which a ↑work product or ↑system can be modified without degrading its ↑quality .
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.
1. Analysis of elicited ↑requirements in order to understand and document them.
2. Synonym for ↑Requirements Engineering.
A ↑baseline for a set of ↑requirements.
1. A situation where two or more ↑requirements cannot be satisfied together.
2. A situation where two or more ↑stakeholders disagree about certain ↑requirements.
Requirements conflicts have to be solved by ↑requirements negotiation.
A document consisting of a ↑requirements specification.
Requirements document is frequently used as a synonym for requirements specification.
Synonym: elicitation (of requirements)
The process of seeking, capturing and consolidating ↑requirements from available ↑sources, potentially including the re-construction or creation of requirements.
The process of managing existing ↑requirements and requirements-related ↑work products, including the storing, changing and tracing of requirements ( ↑traceability ).
A ↑model that has been created with the purpose of specifying ↑requirements.
Synonym: Verhandlung (von Anforderungen)
A ↑process where ↑stakeholders are working toward reaching an agreement to resolve ↑requirements conflicts.
The source from which a ↑requirement has been derived.
Typical sources are ↑stakeholders, documents, existing ↑systems and observations.
A systematically represented collection of ↑requirements , typically for a ↑system , that satisfies given criteria.
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.
Synonym: Anforderungsschablone
A template for specifying ↑requirements.
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.
A coherent chunk of work to be done.
Synonym: artifact
A recorded, intermediate or final result generated in a work ↑process .