Taxonomy of Inconsistency Patterns in Multi-View Modelling
Case IMM98-1

Source

GrundyHM1998

Categories

C5 (primary); C7 (secondary)

Domain

software development environments

UML-like OO design

Views

OOA/D design view

other design diagrams

code

documentation

analysis diagrams

Artefacts

class interface

related diagrams

derived code

documentation artefacts

Quotes

"Inconsistency detection is needed after one view is edited in order to detect: structural inconsistencies between views (e.g., class attributes added in one view aren’t in another); […]."

"Renaming a class in an OO design view means all other analysis, design, implementation and documentation views become inconsistent unless the class name is changed in these views."

Summary

A class is renamed in one design view, but the corresponding name is not propagated to related views and artefacts.

Cause: local edit to a shared conceptual element is not propagated across redundant or corresponding representations.

As a result, cross-view disagreement; developers may overlook the inconsistency; downstream artefacts no longer refer to the same concept consistently.

Taxonomy Categories

Evidence Map

---

The page is maintained by Dr. Vadim Zaytsev a.k.a. @grammarware. Last updated: March 2026.