Towards a semantic infrastructure supporting model-based tool integration

Kramler, Gerhard; Kappel, Gerti; Reiter, Thomas; Kapsammer, Elisabeth; Retschitzegger, Werner; Schwinger, Wieland

doi:10.1145/1138304.1138314

Cited by 40 publications

(19 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Model repositories [4,5,6,7] support this trend by managing modeling artifacts, such as models, model instances, model relationships, and so on. A model repository enables modelers to create, retrieve, update, and delete modeling artifacts, and to query for them.…”

Section: Introductionmentioning

confidence: 99%

Reusable Architectural Decision Model for Model and Metadata Repositories

Mayr

Zdun

Dustdar

2009

Formal Methods for Components and Objects

View full text Add to dashboard Cite

Abstract. Models are gaining importance in software development, for instance in the MDD field, as well as in other disciplines such as biology and physics. Hence, tool support is needed to manage these models and metadata about the models. Model repositories support this trend by managing these model artifacts. While setting up model and metadata repositories, architects have to make several fundamental design decisions and balance various forces. In this paper we describe reusable knowledge in form of reusable architectural decisions for ITarchitects in setting-up, planning, and developing model and metadata repositories, as well as the main decision drivers. Our decisions are documented in a reusable architectural decision model that can be instantiated for a concrete system. It also supports a lightweight approach to architecture documentation. A case study illustrates the decisions made when setting up our own data access object model repository by walking through the reusable architectural decision model.

show abstract

Section: Introductionmentioning

confidence: 99%

Reusable Architectural Decision Model for Model and Metadata Repositories

Mayr

Zdun

Dustdar

2009

Formal Methods for Components and Objects

View full text Add to dashboard Cite

show abstract

“…Tools like the Eclipse Modeling Framework (EMF) [4], ModelCVS [5], Modelio 1 and MagicDraw 2 all use XML-based model serialization. While this approach offers a structured platform-independent way for storing models, it has been shown by various works such as [3,6] to lack scalability as it requires loading the entire text file in order to retrieve any information needed from the model.…”

Section: File-based Model Persistencementioning

confidence: 99%

Stress-Testing Centralised Model Stores

García-Domínguez

Barmpis

Kolovos

et al. 2016

Modelling Foundations and Applications

View full text Add to dashboard Cite

Abstract. One of the current challenges in model-driven engineering is enabling effective collaborative modelling. Two common approaches are either storing the models in a central repository, or keeping them under a traditional file-based version control system and build a centralized index for model-wide queries. Either way, special attention must be paid to the nature of these repositories and indexes as networked services: they should remain responsive even with an increasing number of concurrent clients. This paper presents an empirical study on the impact of certain key decisions on the scalability of concurrent model queries, using an Eclipse Connected Data Objects model repository and a Hawk model index. The study evaluates the impact of the network protocol, the API design and the internal caching mechanisms and analyzes the reasons for their varying performance.

show abstract

“…The tools may be domain-specific or general-purpose, and tool composition frameworks facilitate tool interoperability. Several tool integration patterns have been developed and used in complex toolchains [10,29,31,5]. Tool chains may support collaborative work, either directly (when a multitude of developers is assisted by the framework, in real-time, synchronously), or indirectly (when the collaboration is more asynchronous).…”

Section: Tool Composition Frameworkmentioning

confidence: 99%

Domain Globalization: Using Languages to Support Technical and Social Coordination

Deantoni

Brun²,

Caillaud

et al. 2015

Globalizing Domain-Specific Languages

View full text Add to dashboard Cite

International audienceWhen a project is realized in a globalized environment, multiple stakeholders from different organizations work on the same system. Depending on the stakeholders and their organizations, various (possibly overlapping) concerns are raised in the development of the system. In this context a Domain Specific Language (DSL) supports the work of a group of stakeholders who are responsible for addressing a specific set of concerns. This chapter identifies the open challenges arising from the coordination of globalized domain-specific languages. We identify two types of coordination: technical coordination and social coordination. After presenting an overview of the current state of the art, we discuss first the open challenges arising from the composition of multiple DSLs, and then the open challenges associated to the collaboration in a globalized environment

show abstract

Towards a semantic infrastructure supporting model-based tool integration

Cited by 40 publications

References 13 publications

Reusable Architectural Decision Model for Model and Metadata Repositories

Reusable Architectural Decision Model for Model and Metadata Repositories

Stress-Testing Centralised Model Stores

Domain Globalization: Using Languages to Support Technical and Social Coordination

Contact Info

Product

Resources

About