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

Source: StunkelKRL2021
Categories: C4 (primary); C6 (secondary)
Domain: general multi-model management
Views: requirements model; code model; test model
Artefacts: mandatory requirement; realising method; associated test case
Quotes: "Every method, which realizes a requirement must have an associated test case and for every mandatory requirement there has to be at least one test case."
Summary: A new mandatory requirement is introduced without adding or linking a corresponding test.; Cause: a consistency rule spanning requirements, implementation, and tests is broken by partial co-evolution.; As a result, the multi-model set becomes invalid under the stated coverage/satisfaction rule.

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.