I propose and will show examples of how you can maintain the gist and idea of your software in a model – and how you can apply existing or create your model execution engines to act as modern and current delivery mechanisms for your solutions.

The steady pace of shifts in the market's perceptions of what is new and cool often paralyzes companies from building support systems and with them, control their information. The main problem is that most techniques today mix the two different problems of the system gist and modernity. Entangling these two problems makes solving them as one hard and risky and something that many businesses will avoid.

To summarize: Model centric – describe the system gist in a model that uses a model executer of correct modernity level to bring it to life. The model is then the documentation, the know-how, and the gist of the system– invest heavily in this. Put modernity and fashion in the model executer and into the user interface and delivery –invest in this too but keep in mind it may change soon. Make sure you involve management in the system gist governance so that they are in control and can make informed decisions.

The series of tools and strategies presented here reduces the effort needed for businesses to take control of and own their information. It does so by introducing a clear separation between system gist and modernity.

I believe that companies that own and control their information are better equipped to compete than companies that are clueless about it. A no-brainer, of course – but still – most companies lack a good and deep understanding of their information. The few that have control often spend too much on resources, trying to evolve system gist and modernity in one complex and risky process.

It is the aim of the tools and strategies presented in this book to show new ways to produce and maintain domain-specific software support systems – and to vastly reduce the costs and increase the quality and speed of how to produce and maintain them. It is not magic – it is just a matter of raising the abstraction level a bit and refraining from entangling problems that are much better solved separately.

The MDriven Book - Next Chapter: Information design