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

Source: MaderG2012
Categories: C6 (primary); C7 (secondary)
Domain: requirements traceability; UML-based development
Views: requirements; analysis models; design models
Artefacts: traceability relations between lifecycle artefacts
Quotes: "To ensure that the anticipated benefits […] can be realized, it is necessary to have an up-to-date set of traceability relations between the established artifacts. This goal requires the creation of traceability relations during the initial development process."; "Furthermore, the goal also requires the maintenance of traceability relations over time as the software system evolves in order to prevent their decay."; "Maintaining traceability means to prevent its decay while related artifacts evolve."
Summary: Trace links that were once valid become stale as related artefacts evolve.; Cause: artefact evolution without commensurate maintenance of trace links.; As a result, dependencies become unreliable and development tasks lose the expected benefits of traceability.

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.