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

Source: NuseibehKF1994
Categories: C4 (primary); C2 (secondary)
Domain: requirements engineering; viewpoint-based specification
Views: tabular collection views for different agents
Artefacts: output of one agent; Input of another agent
Quotes: "The Output produced by one agent in a tabular collection diagram must be consumed as an Input in the tabular collection diagram [by] another agent"
Summary: An output declared by one agent is not consumed as an input by any other related agent view.; Cause: inter-view coverage/completeness rule on information flow is violated.; As a result, the requirements model contains an unfulfilled or dangling flow of information between agents.

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.