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

Source: GrundyHM1998
Categories: C2 (primary); C1 (secondary)
Domain: software development environments; UML-like OO design
Views: multiple design and implementation views
Artefacts: method calls; argument lists; class methods
Quotes: "Inconsistency detection is needed after one view is edited in order to detect: […] semantic inconsistencies in specifications (e.g., a type mismatch between method calls or a nonexistent method is called); […]."
Summary: Two related artefacts agree enough to connect, but disagree on call signature or method existence.; Cause: semantic/interface constraints between linked elements are violated.; As a result, incorrect or impossible interaction between components/classes; manual correction required.

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.