Business modelling is not a brand new discipline and there are probably a lot of models around describing a business problem domain more or less comprehensively from a business point of view. There are also a whole bunch of tools around supporting business modelling, information modelling or application design. Why therefore again the attempt to convince application designers to use models as their preferred means to do their specifications? The reason for that is, that most of the business modelling projects performed in the past have failed, and the models developed do not fulfill the original expectations. Although a real good and promising method, business modelling after a relatively euphoric start has become somehow discredited.

Let me summarize the current modelling scene as it appears to me.

All models I have seen so far do not fulfill the level of simplicity of structure as well as integration of components which is desirable for a real good model. Most information models I have seen look more or less like a paper pattern chart of a fashion magazine and most workflow models have no relation at all to an information model of the same business domain.

And how do current tools support the creation of models? Especialy during the development of entity relationship diagrams or object charts I asume more effort is currently spent for the re-arrangement of the diagram boxes than for the problem analysis and proper problem abstraction.

Due to this lack of real good and durable structure most of the models contain conflicts not detected by the analysts. Also due to the lack of structure the models are hard to comprehend and difficult to maintain. The goal for modelling in most projects performed in the past has not been achieved. Therefore most of these models never have been really used for the purpose they have been created.

The overall modelling picture really does not look very bright in the moment, but I think it can be changed - and this with relatively little effort.

Top of page
Table of Content