Taxonomy of Inconsistency Patterns in Multi-View Modelling
Case `DSS22-3`

Source: JongelingFCCC2022
Categories: C5 (primary); C1 (secondary)
Domain: industrial model-code consistency
Views: system model; code
Artefacts: matched element names under architectural guidelines
Quotes: "This puts a requirement on following a specific naming convention. Not everybody does this."
Summary: Model-code correspondence depends on naming conventions that are not uniformly followed.; Cause: informal naming discipline is relied upon for correspondence but is not socially enforced consistently.; As a result, reduced precision/usefulness of consistency checks and disagreement over enforcement strictness.

Taxonomy Categories

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

The page is maintained by Dr. Vadim Zaytsev a.k.a. @grammarware. Last updated: March 2026.