Make Model Complexity Transparent to Help Everyone

Model complexity should not only concern users but also management. It helps all parties involved to understand why modelling or test generation is taking longer for person/model A than for person/model B. Model complexity (especially diagram complexity) is not generally “bad” and may even be required to solve a complex problem in some cases. However, in many cases it has been proven in the past the transparency has marked a turning point in the overall discussions and planning where the effort required to work on a model starts to become unreasonable.

Use and tracking of model complexity also helps in project planning, e.g., how much effort will (still) be required to model and generate tests for this functionality. It can be used to see how closely users follow best practices or to identify a good time for a model review or more training.