-
Notifications
You must be signed in to change notification settings - Fork 8
Model for traceability between requirements and evidence
Paul Albertella edited this page Sep 20, 2024
·
1 revision
Expectation records document the goals or requirements applying to a project. These may include:
- product or software requirements
- process or evidence requirements from a standard or regulation
- design or architectural objectives defined by a different project
- any other kind of goal, need, objective or criterion
Assertion records express conditions that must be true in order for an expectation (or another assertion) to be fulfilled. The language used to express an Assertion should be short, unambiguous, specific, and easy to understand. The statements composing an assertion should be falsifiable and verifiable by reference to the linked evidence.
Evidence records provide references to test steps, documents, results or process outputs, which collectively demonstrate that a linked set of assertions are satisfied.