This page helps teams identify the documented areas to review when beginning with MDriven.
Model and delivery approach
The model-centric approach described in What is next separates the system gist from modernity in delivery technology. In that description, the model holds the system gist, documentation, and know-how, while a model executer, user interface, and delivery mechanism bring the model to life.
This separation is intended to let teams invest in the system gist while recognizing that user-interface and delivery choices may change. The same source recommends involving management in governance of the system gist.
Reality and the theoretical best model describes continuous adaptation of a machine-readable theoretical best model (TBM) to reduce the gap between the model and changing reality. It also describes using execution of the model to involve domain users in verifying that the model is sufficiently close to reality.
Security consideration
Information security cautions that, when richer browser experiences are built with Ajax and JavaScript, data may be held locally in the browser and it may become difficult to determine whether browser-side work overlaps with access-control work without reviewing the code. Review browser-side handling of data and behavior as part of the solution's security work.