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

Source: JongelingCCC2022
Categories: C7 (primary); C1 (secondary)
Domain: industrial continuous model-based development
Views: software design models; generated+manually modified implementation code
Artefacts: generated code; models intended to document implementation
Quotes: "To customize this code for different operational environments, the generated code, rather than the model, is modified, leading to inconsistency between the code and the model."; "This inconsistency mainly impacts the maintainability of the code, since the models can no longer be used as accurate documentation of the implementation."
Summary: Code is customised after generation, but the originating model is left behind.; Cause: manual post-generation evolution of code without reverse synchronisation to the model.; As a result, model ceases to be a trustworthy description of the implementation; maintainability suffers.

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.