Taxonomy of Inconsistency Patterns
in Multi-View Modelling
Category
C1: Structural mismatch
Taxonomy of Inconsistency Patterns
in Multi-View Modelling
C1: Structural mismatch
An expected correspondence, allocation, or refinement relation between views is missing, extra, or incompatible.
C1 captures the broad family of cases where views are expected to align through some correspondence or refinement relation but do not. Examples include a design-level call relation that is added without a matching implementation update, a missing subsystem in a lower-level model, and failure of a one-to-one model-to-code decomposition mapping. The same family also subsumes many formal refinement cases where a lower-level model changes the realised structure in a way that no longer preserves the intent of the higher-level one.
| 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 |
