Taxonomy of Inconsistency Patterns
in Multi-View Modelling
Category
C5: Terminology divergence
Taxonomy of Inconsistency Patterns
in Multi-View Modelling
C5: Terminology divergence
Corresponding concepts are named differently, or the same label is used for non-equivalent concepts across views.
C5 captures lexical and terminological disagreement, be it simply naming or representative of semantic mismatches. Illustrative cases include class renaming in a library that is not propagated across related artefacts, inconsistent names for linked properties, and fragile model-code correspondence rules that depend on naming conventions being followed uniformly. We retained naming as a top-level category because the surveys already indicate that terminology inconsistency is a real obstacle in multi-view work, and because naming problems often act as the first point of failure for correspondence mechanisms.
| 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 |
