you're reading...

Model-Driven Mechanism and Model-Driven Systems

The term of model-driven mechanism (MDM) is coined by myself in practice and reflection of enterprise applications [1], and I increasingly find that the notion has a very universality. In 2005, I defined MDM [2]

makes all or part of functions and behaviors (or the structure and form) of a system to be in control of or mastered by model.


if all the functions and behaviors of a system can be defined, controlled and changed through MDM at runtime, then the system is a full model-driven system (MDS).

Model-Driven Mechanism (MDM)

Model-Driven Mechanism (MDM)

The basic structure of MDM is shown in the graph [3] ; it is composed of three related parts: applied model, modeling knowledge, and operational device. In which the term “model” is used under the common and general senses; “applied” is used to modify it, that is, to mean that the model represents the target thing which the system works on / for. The “modeling acknowledge” here is indeed carefully used: “modeling” means in the senses of both building a model and serving as a model; the “knowledge” refers to a broad deal of things which restricts the modeling, such as specifications, rules, languages, notations or / and formats, etc. and–metamodels [4] which governance both the applied model and the operational device. The operational device accomplish the intended functions and behaviors which relate with the target thing by utilizing the applied model. Both the operational device and the applied model are according to the same modeling knowledge, that is why the system with MDM well be capable to well work on some dynamically changing model: the device “know” how is the model to be modeled. Furthermore, The significance of an applied model is that it is can always be corresponding to (representing) certain target thing, thereby, the system will be able to be dealing with the thing what is changed continuously.


[1] Some of background to the development of the notion, see Model-Driven: An Essential Requirement Come from Customers and A Roadmap of Research for Enterprise Applications.

[2] The text in English is appeared in: Yu, Tong-Ying. “Model-Driven Applications: Using Model-Driven Mechanism to Bridge the Gap between Business and IT.” In Advances and Applications in Model-Driven Software Engineering. Díaz, V.G. et al. eds. IGI Global, August 2013 (in press, see Recent Work on Model-Driven Applications (MDApp). Note that the title of book be changed by publisher, the original title is “Progressions and Innovations in Model-Driven Software Engineering.” Updated on 13 Mar) See also A Presentation on Model-Driven Mechanism in Information Systems and Enterprise Engineering.

[3] Yet, there are more illustrations in Using Model Driven Mechanism to Explain Model Driven Software Development.

[4] We will specially discuss about the concept of metamodel here.

About TY

interested in models & modeling, software, information systems, applications & engineering for enterprises

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s



Subscribe notifications of new posts by email.

Join 60 other followers

%d bloggers like this: