science

Model-driven interoperability

Model-driven interoperability is a science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Model-driven interoperability rather than just read about it. In short: Model-driven interoperability (MDI) is a methodological framework, which provides a conceptual and technical support to make interoperable enterprises using ontologies and semantic annotations, following model driven development (MDD) principles. Overview The initial idea of works on MDI, was the application of model-driven methods and techniques for solving interoperability problems from business level down to data…

Key takeaways

Model-driven interoperability belongs to science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect Model-driven interoperability to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of Model-driven interoperability from memory before moving on to harder problems.

Reference excerpt

Model-driven interoperability (MDI) is a methodological framework, which provides a conceptual and technical support to make interoperable enterprises using ontologies and semantic annotations, following model driven development (MDD) principles.

Overview The initial idea of works on MDI, was the application of model-driven methods and techniques for solving interoperability problems from business level down to data level. The three main ideas of model driven interoperability (MDI) approach are:

Interoperability should be achieved at different levels: Business, knowledge, application and data. The main idea is to follow a model driven engineering (MDE) approach. Therefore, it is promoted a systematic use of models as primary engineering artefacts throughout the engineering life cycle combined with both domain-specific modelling languages and transformation engines and generators. The use of ontologies and semantic annotations is needed in order to perform model transformation from enterprise level to code level.

History MDI was initiated in 2004 with the beginning of two important research projects:

INTEROP NoE (Interoperability Research for Networked Enterprises Applications and Software Network of Excellence, FP6-IST 508011). ATHENA IP (Advanced Technologies for interoperability of Heterogeneous Enterprise Networks and their Applications Integrated Project) (FP6-IST-507849). Both projects were supported by the European Commission. These two projects worked on both the definition of a methodological framework and the application of MDI on concrete cases.

MDI Topics

MDI Framework (INTEROP NoE) MDI Framework within INTEROP is defined:

From conceptual point of view: providing a reference model in which is proposed an interoperability model defined at different levels of abstraction. From methodological point of view: providing the model driven interoperability (MDI) method as a method (principle and structure) to enable interoperable enterprise software applications (ESA), starting from the level of the enterprise model rather than from the code level and using a model-driven approach, combined with use of ontologies and semantic annotations. From technological point of view: providing vertical and horizontal semantic support in order to perform model transformations.

Reference model The reference model proposed for the model driven interoperability approach shows the different kinds of models that it is possible to perform at different levels of abstraction, and the successive model transformations that are needed to carry out.

The different levels of abstraction are needed in order to make possible model transformations reducing the gap existing between enterprise models and code level. The definition of the several levels was based on the model-driven architecture (MDA) that defines three levels of abstraction: Computation independent model (CIM), platform independent model (PIM) and platform specific model (PSM). Moreover, we introduced a partition of the computation independent model level into two sub-levels in order to reduce the gap between the computation independent model (CIM) and platform independent model (PIM) levels. An interoperability model has been also defined at the different levels of abstraction proposed above. One example of this reference model for MDI can be seen in the next figure. This picture shows in each of the proposed levels the different kind of models that can be performed (GRAI at top computation independent model level (TCIM), and UML in the other levels), and the final objective of making interoperable two ESA, the franchisor's ERP and the franchisee's CRM.

Model-driven interoperability method Model driven interoperability method (MDI method) is a model-driven method that can be used for two enterprises that need to interoperate not only at the code level but also at enterprise modelling level with an ontological support with the final aim of improving their performances.

It uses model transformations to achieve interoperability defining models and an Interoperability Model at different levels of abstraction according to an MDA approach and dividing the computation independent model (CIM) level into two sub-levels, that is to say, Top computation independent model level (TCIM) and bottom computation independent model level (BCIM). It uses a common ontology to support these transformations and to solve interoperability problems at the semantic level. The MDI method proposed to solve interoperability problems, like its name indicates, is based on the MDA approach. Also, the following principles were applied to the definition of this method:

The MDI method is organised as an iterative process like unified process (UP) and other object-oriented processes. The MDI method also proposes semantic support like semantic of business vocabulary and business rules (SBVR). Next picture show the main features of the MDI method, in which the green areas give the estimated effort related to each phase and workflow:

Its main phases, represented on the columns: they describe four phases corresponding to the passage from one level of abstraction to a lower one. Its main workflows, especially the three process workflows related to the three main components of the MDI method: the interoperability model, the common interoperability ontology and the model transformation.

MDI framework (ATHENA IP) The MDI framework from ATHENA provides guidance on how MDD should be applied to address interoperability. The framework is structured in three main integration areas:

Conceptual integration, which focuses on concepts, metamodels, languages and model relationships. It provides us with a foundation for systematising various aspects of software model interoperability. Technical integration, which focuses on the software development and execution environments. It provides us with development tools for developing software models and execution platforms for executing software models. Applicative integration, which focuses on methodologies, standards and domain models. It provides us with guidelines, principles and patterns that can be used to solve software interoperability issues.

Conceptual integration The reference model for conceptual integration has been developed from a MDD point of view focusing on the enterprise applications and software system.

… excerpt ends here. Continue reading the full article.

Illustrations

Worked examples

Example 1 — a first encounter with Model-driven interoperability

Start with the simplest possible case. Write down what Model-driven interoperability claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Model-driven interoperability before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Model-driven interoperability ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Model-driven interoperability

In research: Model-driven interoperability appears in science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses Model-driven interoperability in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: Model-driven interoperability is common in secondary-school and first-year university syllabi. It links to neighbouring topics Interoperability, so understanding it makes those chapters shorter.
In everyday life: Look for Model-driven interoperability outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “Model-driven interoperability” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Model-driven interoperability in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what Model-driven interoperability means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain Model-driven interoperability out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Model-driven interoperability in simple terms?

Why does Model-driven interoperability matter?

Because it connects several science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Model-driven interoperability?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Model-driven interoperability.