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

Source

GrundyHM1998

Categories

C7 (primary); C5 (secondary)

Domain

collaborative software development

Views

alternative versions of shared views

Artefacts

class method across parallel versions

Quotes

"Inconsistency detection is needed after one view is edited in order to detect: […] inconsistencies between specifications at different levels of abstraction (e.g., system requirements and design conflict); and inconsistencies between the work of multiple developers (e.g., when any inconsistency is caused by different developers working concurrently)."

"While alternate versions of a view are being modified independently, inconsistencies between these views may easily result. For example, a class method modified by one developer may be deleted or renamed by another."

Summary

Parallel edits on different versions produce conflicting states for the same method.

Cause: concurrent evolution without immediate reconciliation.

As a result, merge/conflict situation across versions; synchronisation and repair become necessary.

Taxonomy Categories

Evidence Map

---

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