Different formal methods have presented plenty of formal models for system specification and proof. Hence the problem of bridging these formal models rises. MDE is a new paradigm in software engineering, which implements software by (meta-)modeling and model transforming. In this paper, we provide a MDE based approach for bridging heterogeneous formal models: Firstly, the heterogeneous formal models are introduced into MDE as domain specific languages by metamodeling. Then, transformation rules are built for semantics mapping. At last, model-text syntax rules are developed, so as to map models to programs. Our approach could be applied on formal models in both graphical style and grammatical style. A case study of bridging MARTE to LOTOS is also illustrated showing the validity and practicability of our approach.

Domain modeling promotes the description of various facets of information systems by a coordinated set of domain-specific languages (DSL). Some of them have visual/graphical and other may have textual concrete syntaxes. Model Driven Engineering (MDE) helps defining the concepts and relations of the domain by the way of metamodel elements. For visual languages, it is necessary to establish links between these concepts and relations on one side and visual symbols on the other side. Similarly, with textual languages it is necessary to establish links between metamodel elements and syntactic structures of the textual DSL. To successfully apply MDE in a wide range of domains we need tools for fast implementation of the expected growing number of DSLs. Regarding the textual syntax of DSLs, we believe that most current proposals for bridging the world of models (MDE) and the world of grammars (Grammarware) are not completely adapted to this need. We propose a generative solution based on a DSL called TCS (Textual Concrete Syntax). Specifications expressed in TCS are used to automatically generate tools for model-to-text and text-to-model transformations. The proposed approach is illustrated by a case study in the definition of a telephony language.

No abstract available.

We take here a broad view of model engineering as encompassing different approaches such as the OMG MDA/spl trade/ proposal as stated in R. Soley (2000), the Microsoft Software Factories view based in J. Greenfield (2004), and many others. We distinguish the three levels of principles, standards and tools to facilitate the discussion. We proposed the idea that there exist a common set of principles that could be mapped to different implementation contexts through the help of common standards. We illustrate our claim with AMMA, a lightweight architectural style for a model-engineering platform that is currently mapped onto the eclipse modeling framework according to F. Budinsky et al. (2004).

This paper investigates the problem of authoring the construction of large distributed enterprise applications form high-level specifications of business logic. How far can we go on trying to apply a model centric approach as the one promoted by the OMG, the Model Driven Architecture? This is the basic question to which we try to bring some partial answers. For this purpose the paper presents an experiment that consists of providing concrete implementations of EDOC/ECA specifications by the Object Management Group (2002) on top of the OpenCCM middleware platform by Object Management Group (2002) and OpenCCM. The roles played by aspect modeling and platform modeling will be discussed. A framework for automating the projection of business specifications into executable code has been defined and implemented. It involves the usage of distinct technologies such as pure meta-modeling, model transformation and the appliance of PAC-AMMODEUS principles by L. Nigay (1994) - presentation, abstraction, control - to achieve software construction in an efficient and innovative way.

Within the domain of information systems, one of the main technological moves we may presently observe in industrial circles is the paradigm shift from object composition to model transformation. This is happening at a very fast pace. Among the concrete signs of this evolution one may mention the ongoing change at the Object Management Group from OMA (Object Management Architecture) to MDA (Model-Driven Architecture). A new information system landscape is emerging that will be more model-centered than object-oriented. Within this context, the information engineer will use and produce many models of low granularity and high abstraction. These models may describe static or dynamic aspects and may be accordingly qualified of product and process models. This paper focuses more particularly on the recent evolution of process models. It shows some aspects of the industrial state of the art in the domain and suggests some benefits that could be reaped from a well-mastered utilization of these techniques.

A new information system landscape is emerging that will be more model-centered than object-oriented, characterized by many models of low granularity and high abstraction. These models may describe various aspects of a system such as products, structural organization and processes. This latter category may be refined into manufacturing, software and business processes for example. Each of these sub-domains share common concerns such as the definition of work items, performers, inputs and outputs, etc. However, as they may be represented using separate meta-models, there is therefore a risk of facing an uncontrollable number of meta-models that all redefine similar modeling constructs. It would be a wise initiative to put all these contributions together and to study what may be common and what should stay specific. We underline some similarities between process meta-models and we sketch out how they could be organized.

Processes are a major concern of information system. They need thus to be defined as precisely as any other artefact of the system. Meta-modeling techniques have proved their relevance for addressing such issues. However, a process meta-model may not be restricted to the definition of a set of concepts, relations and assertions. As the purpose of a process is to be executed, the underlying execution rules have also to be made explicit. In this paper we attempt to identify the main characteristics of executable meta-models. This study is illustrated with a concrete example, a Petri nets meta-model.

We are currently witnessing an important paradigm shift in information system construction, namely the move from object and component technology to model technology. The object technology revolution has allowed the replacement of the over twenty-year-old step-wise procedural decomposition paradigm with the more fashionable object composition paradigm. Surprisingly, this evolution seems to have triggered another even more radical change, the current trend toward model transformation. A concrete example is the Object Management Group's rapid move from its previous Object Management Architecture vision to the latest Model-Driven Architecture. This paper proposes an interpretation of this evolution through abstract investigation. In order to stay as language-independent as possible, we have employed the neutral formalism of Sowa's conceptual graphs to describe the various situations characterizing this organization. This will allow us to identify potential problems in the proposed modeling framework and suggest some possible solutions.

Discrete event simulation has been a constant source of inspiration for language designers. The present interest in Object-Oriented Programming (O.O.P.) can be traced back to the Simula 67 language. In return, simulation languages are currently getting back many advantages from the ongoing research in O.O.P. One of the main present research trends is the possibility of concurrently executing a simulation program composed of a set of interacting and communicating objects. Conditions which will make this possible are discussed together with some induced problems. More precisely this paper presents some experiments in object-oriented simulation that reveal the great flexibility of the Smalltalk-801 programming system for building evaluation environments.