Taxonomy of Inconsistency Patterns
in Multi-View Modelling
Category
C4: Requirement satisfaction gap
Taxonomy of Inconsistency Patterns
in Multi-View Modelling
C4: Requirement satisfaction gap
A requirement is not adequately realised, linked, tested, or accompanied by the artefacts needed to justify satisfaction.
C4 covers failures to justify that requirements are satisfied or covered. Some examples are classical viewpoint gaps, such as a required dependent view not being created, or a formal schema lacking its required associated description. Others arise later in the lifecycle, for instance when critical requirements are not traced through to tests, or when tests continue to execute but no longer cover the intended behaviour after model evolution.
| Code | Label | As primary | As secondary |
| C1 | Structural mismatch | 13 | 7 |
| C2 | Interface contract mismatch | 4 | 5 |
| C3 | Behavioural contradiction | 3 | 6 |
| C4 | Requirement satisfaction gap | 7 | 1 |
| C5 | Terminology divergence | 3 | 3 |
| C6 | Traceability disruption | 7 | 6 |
| C7 | Temporal skew | 3 | 9 |
