Model-Based System Architecture, 2nd Edition

7Model Governance

7.1 Overview

As shown in the Chapters 3 and 6, it can be advantageous to accompany the systems architecting activity with a model. However, the decision to model a system has consequences:

• The model needs to be created.
• The model needs to be maintained for a certain lifetime.
• People who depend on using information that is now in the model may need to be trained in the new way of retrieving their information, or alternatively, their known representation of information needs to be re-established based on the model.

The authors have observed modeling activities that failed, because the above consequences were not planned in advance, or – even worse – were not taken into account when defining the extent of the modeling activity. Too extensive modeling is what we also call over-modeling. Almost anything can be modeled, but you should only model those things which have a purpose in the value creation that is clearly confirmed by the related stakeholders.¹ Over-modeling usually leads to an explosion of cost, which cannot be justified by the much slower evolution of benefits. It is therefore extremely important to make the cost-benefit analysis before starting a modeling activity and to capture aspects like the intended scope, purpose, or lifetime of the model in order to have them for reference during the utilization stage of the model.

The word model governance shall denote the activity that comprises the following:

• The definition of a model creation and maintenance ...