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

Source: JongelingCCC2022
Categories: C1 (primary); C7 (secondary)
Domain: industrial continuous model-based development
Views: high-level system/architecture models; implementation
Artefacts: system models; implementation artefacts; feedback links
Quotes: "It is accepted by engineers that the models are not fully consistent with the eventual implementation, so the initial impact of an inconsistency is small. Nevertheless, it is required that the eventual implementation conforms to the requirements."
Summary: Engineers temporarily accept mismatch between high-level models and implementation, but lack of feedback makes the mismatch persist.; Cause: asynchronous development and missing feedback loop between abstraction levels.; As a result, implementation may drift from the intended design and engineers lose model-based overview.

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.