Taxonomy of Inconsistency Patterns in Multi-View Modelling
Case `FER94-2`

Source: NuseibehKF1994
Categories: C1 (primary); C5 (secondary)
Domain: requirements engineering; viewpoint-based specification
Views: tabular collection view; agent hierarchy view
Artefacts: source/destination entry in tabular collection diagram; named agent in hierarchy
Quotes: "Every Source or Destination in a tabular collection diagram has a corresponding agent with the same name in the agent hierarchy"; "Two Viewpoints may be partially overlapping, with a partial specification in one related to a partial specification in the other."; "For example, CORE requires that a source agent in a tabular collection diagram is a named agent in the agent hierarchy."
Summary: A source or destination named in a tabular collection diagram has no matching named agent in the hierarchy, or the names diverge.; Cause: cross-view correspondence constraint between partial requirements views is violated.; As a result, the same domain participant is represented inconsistently across views, weakening integration between decomposition and flow-oriented descriptions.

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.