Model Driven Interoperability

Last updated

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. [1] [2]

Contents

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:

  1. Interoperability [3] should be achieved at different levels: Business, Knowledge, Application and Data.
  2. The main idea is to follow a Model Driven Engineering (MDE) [1] [2] 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.
  3. The use of ontologies and semantic annotations is needed in order to perform model transformation from enterprise level to code level. [4]
Interoperability levels. Model Driven Interoperability Levels.png
Interoperability levels.

History

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

Both projects 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 [7] [8] within INTEROP is defined:

The Reference Model

The Reference Model proposed for the MDI 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.

Reference Model for MDI. Reference Model for MDI.png
Reference Model for MDI.

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: CIM, PIM and PSM. Moreover, we introduced a partition of the CIM level into two sub-levels in order to reduce the gap between the CIM and 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 see in the next figure. This picture shows in each of the proposed levels the different kind of models that can be performed (GRAI [9] at Top CIM level, and UML in the other levels), and the final objective of making interoperable two ESA, the franchisor's ERP and the franchisee's CRM.

Example of Reference Model for MDI. Example-of Reference Model for MDI.png
Example of Reference Model for MDI.

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 CIM level into two sub-levels, that is to say, Top CIM level (TCIM) and Bottom CIM 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:

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 Method. MDI Method.png
MDI Method.

MDI Framework (ATHENA IP)

The MDI Framework [10] [11] [12] from ATHENA provides guidance on how MDD should be applied to address interoperability. The framework is structured in three main integration areas:

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.

MDI: Reference Model for conceptual integration. MDI Reference Model for Conceptual Integration.png
MDI: Reference Model for conceptual integration.

According to MDA, a Computation Independent Model (CIM) corresponds to a view defined by a computation independent viewpoint. It describes the business context and business requirements for the software system(s). A Platform Independent Model (PIM) corresponds to a view defined by a platform independent viewpoint. It describes software specifications independent of execution platforms. A Platform Specific Model (PSM) corresponds to a view defined by a platform specific viewpoint. It describes the realisation of software systems.

Technical integration

Technical Integration reference model promotes the use of service-oriented solutions where a software system and more generally a system provide a set of services required by the businesses and users of the enterprise.

MDI: Reference Model for technical integration. MDI Reference Model for Technical Integration.png
MDI: Reference Model for technical integration.

Applicative integration

The reference model for applicative integration has been developed in order to emphasise the dependencies between the different models and views to achieve interoperability.

MDI: Reference model for applicative integration. MDI Reference Model for Applicative Integration.png
MDI: Reference model for applicative integration.

Model Transformations

Model transformation is one of the key approaches used to support the MDI Method. This approach is used in both horizontal and vertical dimension of the Reference Model for MDI. All model transformations performed are based on to the generic transformation architecture. [13]

Transformation Architecture. Transformation Architecture.png
Transformation Architecture.

Semantic Support

The following services: verification of the consistency of models, support to automatic mapping discovery among heterogeneous models, and definition of semantic preserving transformation can support MDI to tackle both vertical and horizontal issues.

Vertical issues: semantic support aiming at:

Horizontal issues: semantic support aiming at:

See also

Related Research Articles

In computer science and information science, an ontology encompasses a representation, formal naming, and definition of the categories, properties, and relations between the concepts, data, and entities that substantiate one, many, or all domains of discourse. More simply, an ontology is a way of showing the properties of a subject area and how they are related, by defining a set of concepts and categories that represent the subject.

A modeling language is any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure.

Model Driven Architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model Driven Architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001.

<span class="mw-page-title-main">Metamodeling</span> Concept of software engineering

A metamodel or surrogate model is a model of a model, and metamodeling is the process of generating such metamodels. Thus metamodeling or meta-modeling is the analysis, construction and development of the frames, rules, constraints, models and theories applicable and useful for modeling a predefined class of problems. As its name implies, this concept applies the notions of meta- and modeling in software engineering and systems engineering. Metamodels are of many types and have diverse applications.

<span class="mw-page-title-main">Extended Enterprise Modeling Language</span>

Extended Enterprise Modeling Language (EEML) in software engineering is a modelling language used for Enterprise modelling across a number of layers.

The Common Information Model (CIM) is an electric power transmission and distribution standard developed by the electric power industry. It aims to allow application software to exchange information about an electrical network. It has been officially adopted by the International Electrotechnical Commission (IEC).

<span class="mw-page-title-main">Semantic technology</span>

The ultimate goal of semantic technology is to help machines understand data. To enable the encoding of semantics with the data, well-known technologies are RDF and OWL. These technologies formally represent the meaning involved in information. For example, ontology can describe concepts, relationships between things, and categories of things. These embedded semantics with the data offer significant advantages such as reasoning over data and dealing with heterogeneous data sources.

Model-driven engineering (MDE) is a software development methodology that focuses on creating and exploiting domain models, which are conceptual models of all the topics related to a specific problem. Hence, it highlights and aims at abstract representations of the knowledge and activities that govern a particular application domain, rather than the computing concepts.

<span class="mw-page-title-main">Enterprise modelling</span>

Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization.

Knowledge Discovery Metamodel (KDM) is a publicly available specification from the Object Management Group (OMG). KDM is a common intermediate representation for existing software systems and their operating environments, that defines common metadata required for deep semantic integration of Application Lifecycle Management tools. KDM was designed as the OMG's foundation for software modernization, IT portfolio management and software assurance. KDM uses OMG's Meta-Object Facility to define an XMI interchange format between tools that work with existing software as well as an abstract interface (API) for the next-generation assurance and modernization tools. KDM standardizes existing approaches to knowledge discovery in software engineering artifacts, also known as software mining.

The concept of the Social Semantic Web subsumes developments in which social interactions on the Web lead to the creation of explicit and semantically rich knowledge representations. The Social Semantic Web can be seen as a Web of collective knowledge systems, which are able to provide useful information based on human contributions and which get better as more people participate. The Social Semantic Web combines technologies, strategies and methodologies from the Semantic Web, social software and the Web 2.0.

BORO is an approach to developing ontological or semantic models for large complex operational applications that consists of a top ontology as well as a process for constructing the ontology. It was originally developed as a method for mining ontologies from multiple legacy systems – as the first stage in an architectural transformation or software modernization. It has also been used to enable semantic interoperability between legacy systems. It is described in detail in. It is the analysis method used in the development and maintenance of the U.S. Department of Defense Architecture Framework (DoDAF) Meta Model (DM2), where a data modeling working group of over 350 members was able to systematically resolve a broad spectrum of knowledge representation issues.

Enterprise interoperability is the ability of an enterprise—a company or other large organization—to functionally link activities, such as product design, supply chains, manufacturing, in an efficient and competitive way.

<span class="mw-page-title-main">Praxeme</span>

Praxeme is a methodology for enterprise architecture which provides a structured approach to the design and implementation of an enterprise information architecture.

Knowledge extraction is the creation of knowledge from structured and unstructured sources. The resulting knowledge needs to be in a machine-readable and machine-interpretable format and must represent knowledge in a manner that facilitates inferencing. Although it is methodically similar to information extraction (NLP) and ETL, the main criterion is that the extraction result goes beyond the creation of structured information or the transformation into a relational schema. It requires either the reuse of existing formal knowledge or the generation of a schema based on the source data.

The enterprise interoperability framework is used as a guideline for collecting and structuring knowledge/solution for enterprise interoperability. The framework defines the domains and sub-domains for interoperability research and development in order to identify a set of pieces of knowledge for solving enterprise interoperability problems by removing barriers to interoperability.

The Open Semantic Framework (OSF) is an integrated software stack using semantic technologies for knowledge management. It has a layered architecture that combines existing open source software with additional open source components developed specifically to provide a complete Web application framework. OSF is made available under the Apache 2 license.

Guy Doumeingts is a French engineer, Emeritus professor at the University of Bordeaux 1 and former Director of "Laboratoire d’Automatique, Productique Signal et Image" control theory, known for the development of the GRAI method and his contributions to the field of Enterprise modelling.

The INTEROP V-Lab is a network of organizations, which links scientists, research centers, representatives of industry, and small and medium-sized enterprises. The members come from several European countries as well as China and represent 250 scientists and 70 organizations.

Bruno Vallespir is a French engineer, and Professor of Enterprise Modelling at the University of Bordeaux, working in the fields of production management, performance evaluation and enterprise modeling.

References

  1. 1 2 B. Humm, U. Schreier, J. Siedersleben. Model-Driven Development – Hot Spots in Business Information Systems, ECMDA-FA 2005, LNCS 3748, pp. 103 – 114, 2005
  2. 1 2 P. Mohagheghi, V. Dehlen, Tor Neple. Definitions and approaches to model quality in model-based software development – A review of literature, Information and Software Technology, 51 (2009) 1646–1669
  3. D. Chen, Guy Doumeingts. European initiatives to develop interoperability of enterprise applications-basic concepts, framework and rodmap, Annual Reviews in Control, Volume 27, Issue 2, 2003, Pages 153-162
  4. Gregory Zacharewicz, Saikou Diallo, Yves Ducq, Carlos Agostinho, Ricardo Jardim-Goncalves, Hassan Bazoun, Zhongjie Wang, Guy Doumeingts. Model-based approaches for interoperability of next generation enterprise information systems: state of the art and future challenges. Information Systems and E-Business Management, Springer Verlag, 2016 https://dx.doi.org/10.1007/s10257-016-0317-8
  5. INTEROP NoE (Interoperability Research for Networked Enterprises Applications and Software Network of Excellence, FP6-IST 508011), http://www.interop-vlab.eu/
  6. ATHENA IP (Advanced Technologies for interoperability of Heterogeneous Enterprise Networks and their Applications Integrated Project) (FP6-IST-507849), http://cordis.europa.eu/fetch?CALLER=PROJ_ICT&ACTION=D&CAT=PROJ&RCN=72762
  7. INTEROP NoE Deliverables http://interop-vlab.eu/ei_public_deliverables/interop-noe-deliverables
  8. Proceedings of the First International Workshop on Model Driven Interoperability for Sustainable Information Systems (MDISIS'08) http://ftp.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-340/
  9. D. Chen, Bruno Vallespir, Guy Doumeingts, GRAI integrated methodology and its mapping onto generic enterprise reference architecture and methodology, Computers in Industry, Volume 33, Issues 2-3, September 1997, Pages 387-394
  10. ATHENA IP Deliverables http://interop-vlab.eu/ei_public_deliverables/athena-deliverables
  11. ATHENA Model Driven Interoperability Framework http://www.modelbased.net/mdi/index.html
  12. B. Elvesæter, A. Hahn, A.J. Berre, T.Neple (2006) Towards an Interoperability Framework for Model-Driven Development of Software Systems. INTEROPERABILITY OF ENTERPRISE SOFTWARE AND APPLICATIONS. DOI: 10.1007/1-84628-152-0_36
  13. F. Jouault, F. Allilaire, J. Bézivin, I. Kurtev, ATL: A model transformation tool, Science of Computer Programming, Volume 72, Issues 1-2, 1 June 2008, Pages 31-39