In contrast, when considering a given model, it is difficult to interpret it if we do not know the view-
point to which it is related. Is it a business model? A technical solution? A design model? A technology
architecture model? With regard to the concerns being addressed, does this address the structuring of
the application, the combination of legacy applications and new evolutions? Does it describe the conceptual business domain, or does it specify how a business process should be optimized? Is it an example or an illustration? Does it reflect what exists or what is intended; in other words, the project that is going to be developed? In itself, the model determines neither the context in which it is defined nor the intentions that led to its development. Knowing the viewpoint from which a model should be looked at allows the spectator to interpret it and find out how to use it. This is not only true for spectators but also for tools, which can apply different checks and usage services according to the viewpoint in question.
For example, code generation, matrix or report generation, and consistency checks are features that are closely linked to the viewpoint.