Adding Abstraction and Reuse to a Network Modelling Tool Using the Reuseware Composition Framework

Abstract

Abstract. Domain-specific modelling (DSM) environments enable experts in a certain domain to actively participate in model-driven development. Developing DSM environments need to be cost-efficient, since they are only used by a limited group of domain experts. Different modeldriven technologies promise to allow this cost-efficient development.[1] presented experiences in developing a DSM environment for telecommunication network modelling. There, challenges were identified that need to be addressed by other new modelling technologies. In this paper, we now present the results of addressing one of theses challengesabstraction and reuse support-with the Reuseware Composition Framework. We show how we identified the abstraction and reuse features required in the telecommunication DSM environment in a case study and extended the existing environment with these features using Reuseware. We discuss the advantages of using this technology and propose a process for further improving the abstraction and reuse capabilities of the DSM environment in the future.

On the complex nature of MDE evolution and its impact on changeability

“…Researchers might provide techniques and tools that shift the involved trade-offs, such that less risky evolution steps become advantageous. For example, frameworks for combining and extending DSLs, like the one presented in [19], might be a first step in this direction.…”

“…This intermixes manual modeling activities with an added automated analysis for correctness (A8, C1). Further, the generation of the configuration files was exchanged, by an implementation that is based on a composition system conforming to the approach reported in [19]. Motivation for this change was the wish to reach higher levels of abstraction.…”

Reusing Pattern Solutions in Modeling: A Generic Approach Based on a Role Language

“…From this point of view, limitations of UML Template compared with our approach are to be metamodel-specific, to expect a matching structure limiting the application and to require strict conformance with the metamodel resulting in unneeded constraints. Another recent work providing a notion of model component for any domain-specific modeling language is Reuseware [9]. In Reuseware, components are model fragments with ports that can be composed by defining composition programs where ports are linked to combine elements from multiple components.…”

“…By being abstract, the 'wrapped' role gives the possibility to select a class or a datatype for its target element. The table in lower part of the figure represents several applications of this role model 8,9 , exhibiting the following capacities :…”

“…8 Base and result models of classes are represented as instances diagrams of the MM metamodel. 9 To distinguish existing elements from added ones in a resulting model, they are represented by dotted box. 10 see http://www.telecom-lille1.eu/people/tombelle/gipsie/gipsie.html Figure 9 shows the suite of tools and their relationships.…”