The way in which a ↑system reacts to stimuli, changes its state and produces observable results.
Stimuli may be events or changes of conditions. Their origin may be external or system-internal.
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.
The way in which a ↑system reacts to stimuli, changes its state and produces observable results.
Stimuli may be events or changes of conditions. Their origin may be external or system-internal.
A ↑model describing the ↑behavior of a ↑system , e.g., by a ↑state machine.
1. For a single ↑requirement : The degree to which the specification of a requirement is self-contained.
2. For a ↑work product covering multiple requirements: The degree to which the work product contains all known requirements that are relevant in the scope of this work product.
1. In general: The ability to establish explicit relationships between related ↑work products or ↑items within work products.
2. In RE: The ability to trace a ↑requirement
(a) back to its origins,
(b) forward to its implementation in design and code and its associated tests,
(c) to requirements it depends on (and vice-versa).
The degree to which an ↑item is comprehensible to its intended users.
Typical items are: a ↑system , a ↑work product , or a part thereof.
The ↑process of confirming that an ↑item (a ↑system , a ↑work product or a part thereof) matches its ↑stakeholders’ needs.
In RE, validation is the process of confirming that the documented ↑requirements match their ↑stakeholders’ needs; in other words: whether the right requirements have been specified.
An occurrence of an ↑item which exists in multiple, time-ordered occurrences where each occurrence has been created by modifying one of its previous occurrences.