Description
Analysis and design models are often presented without clarifying the viewpoint represented by the model. Mixed viewpoints don’t allow the fundamental separation of concerns, confusing blueprints of abstractions and implementation details.
Context
Derived from: “Ambiguous Viewpoint”
Models can be less useful if they don’t focus on the required perspective(s). A perspective applies filters to the information. It can also be the case that multiple viewpoints are maintained, although no stakeholder is responsible for this unused viewpoint. Then viewpoints are created just for the sake of having viewpoints.
Cause
It is hard to specify every important aspect from all possible viewpoints. Thus, it is important to state the taken viewpoint which should be elaborated extensively.
Consequences
Different viewpoints emphasize different aspects, which can also cause disregard of some crucial factors of other viewpoints.
Detection
No explicit description and designation of the viewpoint.
Solution
There are five fundamental layers for EA models: business, application, technology & physical, strategy and implementation & migration. Thus, those viewpoints can be differentiated and considered explicitly. Additionally, multiple stakeholders may have different point of views, which should be taken into consideration. Of course the chosen point of view has to be specified.
Example
Defining a model for a telephone exchange system will vary significantly depending upon the focus provided by the following perspectives: Telephone user, who cares about the ease of making calls and receiving itemized bills. Telephone operator, who cares about connecting users to required numbers. Telephone accounting department, which cares about the formulae for billing and records of all calls made by users.
Tags
business, application, technology, ambiguity, soa, microservices, automatic detection
Related smells
- Architecture by Implication (relates)