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

Source: MurtaHW2008
Categories: C6 (primary); C7 (secondary)
Domain: architecture-to-implementation traceability
Views: software architecture; implementation code
Artefacts: versions of architectural elements; versions of source code configuration items; trace links
Quotes: "A traditional obstacle in the use of multiple representations is the need to maintain traceability among the representations in the face of evolution. […] Specifically, the task is to relate versions of architectural elements to versions of source code configuration items, and to update those relations as new versions of the architecture and source code are produced."
Summary: Architecture-to-code links must survive concurrent version evolution on both sides.; Cause: trace links are tied to evolving versions of both architecture and code artefacts.; As a result, without continuous evolution of traces, architecture and implementation lose synchronisation.

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.