Taxonomy of Inconsistency Patterns
in Multi-View Modelling
Category
C2: Interface contract mismatch
Taxonomy of Inconsistency Patterns
in Multi-View Modelling
C2: Interface contract mismatch
Views disagree at a boundary on signatures, ports, parameter sets, types, units, directions, or equivalent exchanged values.
C2 is about interfacing between components, it isolates boundary-level disagreements. Typical exam-ples include incompatible call signatures, wrong connector direction, inconsistent parametrisation of the same physical quantity, or mismatched equivalent values in aligned models [7, 8, 11]. We separated C2 from C1 because many inter-view defects arise not from missing correspondence, but from correspondence that exists yet disagrees on the contract at the boundary.
| 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 |
