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

Source: GeorgeFHKBA2012
Categories: C6 (primary); C4 (secondary)
Domain: model-based testing
Views: requirements model; design model; test model
Artefacts: relationships among requirements, design, tests, and executable tests
Quotes: "Relationships between the different models will help to navigate from one model to another, and trace back to the respective requirements and the design model when the test fails."
Summary: When a test fails, missing cross-model relationships prevent reliable backward navigation to the responsible requirement/design elements.; Cause: gaps between requirements, design, and test models are not bridged by explicit relations.; As a result, failed tests are harder to diagnose; inconsistencies in requirements elicitation and tests are harder to localise.

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.