Academia.edu no longer supports Internet Explorer.
To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser.
2008
Abstract Model-based development involves construction, integration, and maintenance of complex models. One of the key problems in model-based development is composing a set of distributed models into a single seamless model. In this paper we propose a declarative approach for model composition, which augments and strengthens existing structural and heuristic approaches. In our approach, the desired model compositions are constrained by a set of declarative properties, which drive the merge process.
2006
Abstract If a modeling task is distributed, it will frequently be necessary to merge models developed by different team members. Existing approaches to model merging make assumptions about the types of model to be merged, and the nature of the relationship between them. This makes it hard to compare approaches. In this paper, we present a manifesto for research on model merging.
International Workshop on Modeling in Software Engineering (MISE'07: ICSE Workshop 2007), 2007
A key problem in model-based development is merging a set of distributed models into a single seamless model. To merge a set of models, we need to know how they are related. In this position paper, we discuss the methodological aspects of describing the relationships between models. We argue that relationships between models should be treated as first-class artifacts in the merge problem and propose a general framework for model merging based on this argument. We illustrate the usefulness of our framework by instantiating it to the state-machine modelling domain and developing a flexible tool for merging state-machines.
2008
Model composition is considered as a crucial activity in model driven software development (MDSD). It is a common feature when adopting a multi-modeling approach to analyze and design software systems. Similar modular approaches are known under several names such as viewpoints, aspects, subjects, etc. In previous works, we proposed a view-based UML profile called VUML. In this paper, we describe a conceptual framework whose goal is to separate the generic composition part from the specific part dedicated to a given modeling domain. We apply our approach to the composition of UML class diagrams into one VUML class diagram.
Proceedings of the 27th International Conference on Software Engineering and Knowledge Engineering, 2015
Academia and industry are increasingly concerned with producing general-purpose model composition techniques to support many software engineering activities, e.g., evolving UML design models or reconciling conflicting models. However, the current techniques fail to provide flexible and reusable architectures, a comprehensive understanding of the critical composition activities, and guidelines about how developers can use and extend them. These limitations are one of the main reasons why state-of-the-art techniques are often unable to aid the development of new composition tools. To overcome these shortcomings, this paper, therefore, proposes a flexible, component-based architecture for aiding the development of composition techniques. Moreover, an intelligible composition workflow is proposed to help developers to improve the understanding of crucial composition activities and their relationships. Our preliminary evaluation indicated that the proposed architecture could support composition tools for UML class, sequence, and component diagrams.
Lecture Notes in Computer Science, 2010
Model composition is a technique for building bigger models from smaller models, thus allowing system designers to control the complexity of a model-driven design process. However many current model composition techniques are themselves complex in the sense that they merge the internal elements of the participating models in non-trivial ways. In this paper we apply some of the ideas from modular programming to reduce the complexity of model compositions. Indeed we propose a model composition technique with a modular flavor that treats the participating models as black boxes. Our technique has several desirable features: it is simple, it does not require a separate language for expressing the composition, and the understanding of the resulting composed model is made easier by the modular nature of the model composition.
2012
Abstract A key problem in model-based development is integrating a collection of models into a single, larger, specification as a way to construct a functional system, to develop a unified understanding, or to enable automated reasoning about properties of the resulting system. In this article, we suggest that the choice of a particular model integration operator depends on the inter-model relationships that hold between individual models.
2005
The aspect oriented modeling (AOM) approach provides mechanisms for separating crosscutting functionality from core functionality in design models. Crosscutting functionality is described by aspect models and the core application functionality is described by a primary model. The integrated system view is obtained by composing the primary and aspect models. In this paper, we present a model composition technique that relies on signature matching: A model element is merged with another if their signatures match. A signature consists of some or all properties of an element as defined in the UML metamodel. The technique proposed in this paper is capable of detecting some conflicts that can arise during composition.
Frontiers in computer science, 2024
Model Driven Engineering (MDE) adoption in the industry suffers from many technical and non-technical problems. One of the significant technical problems lies in the difficulty of building complex transformations from the composition of small and reusable transformations. Another problem resides in developing transformations from scratch in case they are missing. In this paper, we present an approach to how to handle these issues. The approach allows composing reusable transformations to build more complex ones by providing a catalog of prebuilt transformations targeting common architectures, frameworks, and design patterns. To give guidance and simplify the task of developing new transformations, we describe a platform description model of an entire system or a part of it in two views: a UML profile and a set of transformations. We also present three transformation types, each of which handles different abstraction design concerns. Generic transformations are small and reusable to build complex transformations, system-independent transformations are reusable and implement high-level design decisions, and system-specific transformations are not reusable and implement all design decisions needed for a given system. The approach is implemented as a plugin for a UML modeling tool and validated by developing a system that simulates the behavior of a gas station through model transformations built from the composition of reusable transformations.
Applied Computer Systems, 2016
Despite the fact that model composition paradigm becomes very important and most commonly used, the support for their cooperation has not reached its full strength, especially in managing composition conflicts, because it's often divided between and confused with other model composition features. This makes handling and dealing with these conflicts a crucial activity in the composition process. Models need to be put under version control in order to manage the probable conflicts, facilitate collaboration and control change. Therefore, a solution for detecting and resolving conflicts is needed. In this paper, we present a composition conflict resolver presented in the form of a repository that helps manage composition conflicts and analyse the model and operations performed on it.
2007
Abstract In aspect-oriented modeling (AOM), a design is described using a set of design views. It is sometimes necessary to compose the views to obtain an integrated view that can be analyzed by tools. Analysis can uncover conflicts and interactions that give rise to undesirable emergent behavior. Design models tend to have complex structures and thus manual model composition can be arduous and error-prone. Tools that automate significant parts of model composition are needed if AOM is to gain industrial acceptance.
Modelling and Simulation in Engineering, 2014
A software framework is an architecture or infrastructure intended to enable the integration and interoperation of software components. Specialized types of software frameworks are those specifically intended to support the composition of models or other components within a simulation system. Such frameworks are intended to simplify the process of assembling a complex model or simulation system from simpler component models as well as to promote the reuse of the component models. Several different types of software frameworks for model composition have been designed and implemented; those types include common library, product line architecture, interoperability protocol, object model, formal, and integrative environment. The various framework types have different components, processes for composing models, and intended applications. In this survey the fundamental terms and concepts of software frameworks for model composition are presented, the different types of such frameworks are...
2006
There is little agreement on terminology in model composition, and even less on key characteristics of a model composition solution. We present three composition frameworks: the Atlas Model Weaver, the Epsilon Merging Language, and the Glue Generator Tool, and from them derive a core set of common definitions. We use this to outline the key requirements of a model composition solution, in terms of language and tool support.
2006
The essence of systems-level design is the need to integrate models representing different system facets to understand the impacts of local decisions on global requirements. Unfortunately, these models may be defined in disparate semantic systems making composition and integrated analysis challenging. As a part of the Rosetta systems-level design effort, a collection of mechanisms based on coalgebraic semantics has been defined to transform and compose models. Functors define mechanisms for moving models between specification domains; coproducts define mechanisms for composing multiple specifications; and translator functions define mechanisms for structurally compose specifications. Together these techniques provide specification composition support for integrating formal, systems-level analysis activities.
2008
Analyzing and modelling a software system with separate views is a good practice to deal with complexity and maintainability. When adopting such a modular approach for modelling, it is necessary to have the ability to automatically compose models to build a global view of the system. In this paper we propose a generic framework for composition that is independent from a modelling language.
2005 Australian Software Engineering Conference, 2005
The success of UML and more generally, of the model driven approach, has led to a proliferation of models, representing various systems, but the description of large applications may actually be composed of several system models. Therefore, the challenge is to determine how to compose independent system models, in order to build large applications.
2006
Model management is a crucial activity in large-scale software development where development tasks are often distributed over different teams. To support flexible, coordinated work, these teams need to maintain partial models of the overall system, and understand the relationships between these models. Models of a proposed system may be manipulated in various ways, and the results of these manipulations may be used by analysts to evolve the models.
Advances in Science, Technology and Engineering Systems Journal, 2019
The technological advance as well as needs of human beings made that systems became more and more complex. In contrast, the use and creation of new modelling languages became simple and no more reserved for a handful of language experts. Consequently, many new practices of systems implementation emerged, among them, the use of different domain specific modelling languages (DSMLs) to represent the same system. Indeed, complex systems are composed by many components sometimes belonging to various domains. Thus, many teams of experts collaborate to develop such systems. Moreover, teams tend to use different DSMLs to design their concerns. This new practice generates an accidental heterogeneity due to production of various heterogeneous models representing a same system. However, those heterogeneous models need absolutely to be coordinated to facilitate communication between stakeholders and of course to ease implementation and validation of systems. This paper proposes a composition interfacebased approach to coordinate and integrate heterogeneous DSMLs in order to coordinate their models. The proposed composition interface is defined according to Bridge Design Pattern. To illustrate this approach two DSMLs are used: An Indoor Service Transport Modelling Language and an Internet of Things Modelling Language.
2000
The ability to compose modular and interoperable model management tasks into automated workows is essential for the wide- spread use of Model Driven Development. Driven by this need, we present a framework that enables developers to dene, execute and prole such workows. The framework is based on the widely-used ANT tool and Epsilon, a platform of integrated task-specic model management
In Model Driven Engineering (MDE) approaches, metamodelers usually need to create a metamodel based on existing metamodels, where each one abstracts a specific domain, in order to abstract a new domain, which includes elements that could be taken from the other already created metamodels. This kind of constructions allows getting advantage of the knowledge obtained in the construction of the previous built metamodels. This paper presents a proposal to solve metamodel composition through a Domain Specific Language (DSL). This DSL is used by metamodelers, who are the people that know the domains abstracted by the different metamodels and know how to combine those metamodels in order to generate the new one. Moreover, a simple case study is presented so as to demonstrate the low level of complexity of the DSL.
Lecture Notes in Computer Science, 2010
Domain Specific Modeling Languages (DSMLs) are essential elements in Model-based Engineering. Each DSML allows capturing certain properties of the system, while abstracting other properties away. Nowadays DSMLs are mostly used in silos to solve specific problems. However, there are many occasions when multiple DSMLs need to be combined to design systems in a modular way. In this paper we discuss some scenarios of use and several mechanisms for DSML combination. We propose a general framework for combining DSMLs that subsumes them, based on the concept of viewpoint unification, and its realization using model-driven techniques.