Key takeaways
- The viewpoint supplies conventions; the view applies them to an architecture.
- A model is a useful abstraction rather than the whole reality.
- Quality depends on relevance to the reader.
The viewpoint guides the view
An Architecture Viewpoint defines how to construct and interpret a view for a set of concerns. It identifies intended stakeholders, conventions, and suitable model kinds. An Architecture View is the concrete result expressing architecture according to that viewpoint. Several views can therefore use the same viewpoint in different projects.
An operations manager may need an availability view, while a business manager needs a capability view. Both describe the same system from different perspectives. Their consistency must be checked: an element presented as essential in one view should not disappear from another without explanation.
Modeling to reason
A model simplifies reality to develop understanding and support decisions. A Model Kind defines the conventions of a category of models. Models should be selected according to concerns rather than because a tool is available. A catalog, matrix, or diagram can each be useful if its readers understand the meaning of the elements and relationships.
- Define concerns before drawing.
- Reuse viewpoints when they are appropriate.
- State assumptions and check consistency between views.
TERMS TO KNOW
The terms, in context.
- Architecture View
- Representation of an architecture addressing concerns.
- Architecture Viewpoint
- Conventions for constructing and interpreting a category of views.