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

Source: JongelingCCC2022
Categories: C4 (primary); C7 (secondary)
Domain: industrial continuous model-based development
Views: design models; tests; implementation models
Artefacts: test cases/scripts/models; models under test
Quotes: "When tests are consistent with the design models, it is meant that not only the test cases pass, but also that the test cases appropriately cover the models, i.e., test the correct things."; "Inconsistency caused by, e.g., a drop in test coverage is much more subtle to detect than test case failure."
Summary: Tests still run, but no longer cover the intended model elements or behaviours after evolution.; Cause: co-evolution of tests lags behind changes in design/implementation models.; As a result, passing tests may become misleading or meaningless as evidence for the model.

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.