Visualisation of Domain-Specific Modelling Languages Using UML

Graaf, B.; Deursen, Arie van

doi:10.1109/ecbs.2007.77

Cited by 10 publications

(6 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Agreement upon a particular notation is required before models can be used as a means of communication among stakeholders. Then, models that comply with the selected notation can be effectively used to convey domain details to system designers, as input to model-driven software development tools [21,29], and for documenting the domain for future reference [17]. This central importance of notations is emphasized for instance in [70]:…”

Section: Introductionmentioning

confidence: 99%

Making sense of business process descriptions: An experimental comparison of graphical and textual notations

Ottensooser

Fekete

Reijers

et al. 2012

Journal of Systems and Software

110

View full text Add to dashboard Cite

Section: Introductionmentioning

confidence: 99%

Making sense of business process descriptions: An experimental comparison of graphical and textual notations

Ottensooser

Fekete

Reijers

et al. 2012

Journal of Systems and Software

110

View full text Add to dashboard Cite

“…The use of UML as a graphical visualization language for domain-specific modeling languages is proposed by Graaf and van Deursen [4]. Their work proposes model-to-model transformations as a means of deriving a visual representation from a domain-specific model.…”

Section: Domain-specific Modelingmentioning

confidence: 99%

Applying Integrated Domain-Specific Modeling for Multi-concerns Development of Complex Systems

Pröll

Rumpold

Bauer

2018

Communications in Computer and Information Science

View full text Add to dashboard Cite

Current systems engineering efforts are increasingly driven by trade-offs and limitations imposed by multiple factors: Growing product complexity as well as stricter regulatory requirements in domains such as automotive or aviation necessitate advanced design and development methods. At the core of these influencing factors lies a consideration of competing non-functional concerns, such as safety and reliability, performance, and the fulfillment of quality requirements. In an attempt to cope with these aspects, incremental evolution of model-based engineering practice has produced heterogeneous tool environments without proper integration and exchange of design artifacts. In order to overcome these shortcomings of current engineering practice, we propose a holistic, model-based architecture and analysis framework for seamless design, analysis, and evolution of integrated system models. We describe how heterogeneous domain-specific modeling languages can be embedded into a common general-purpose model in order to facilitate the integration between previously disjoint design artifacts. A case study demonstrates the suitability of this methodology for the design of a safety-critical embedded system, a hypothetical gas heating, with respect to reliability engineering and further quality assurance activities.

show abstract

“…Defining model transformations between DSMLs and UML. In Graaf and van Deursen (2007), the authors propose to use UML as visualization technique for documenting domain-specific models. The motivation for using UML as visualization technique is that the development of graphical editors is still in its infancy, although there are some promising frameworks emerging such as the graphical modeling framework.…”

Section: Data Modelmentioning

confidence: 99%

A semi‐automatic approach for bridging DSMLs with UML

Wimmer

2009

International Journal of Web Information Systems

View full text Add to dashboard Cite

The definition of modeling languages is a key-prerequisite for model-driven engineering (MDE). In this respect, domain-specific languages (DSL) defined in terms of metamodels and UML profiles are often considered as two alternatives. For interoperability reasons, however, the need arises to bridge modeling languages originally defined as DSLs to UML profiles by defining (1) a specific UML profile to represent the domain-specific modeling concepts in UML and (2) model transformations for transforming DSL models to UML models and vice versa. A manual definition of a UML profile typically is a tedious and errorprone task, but contains a high potential for automation. The contribution of this paper is to integrate the so far competing worlds of DSLs and UML. We report on our semi-automatic approach based on the manual mapping of domain-specific metamodels and UML using a dedicated bridging language as well as the automatic generation of UML profiles and model transformations. We present our ideas within a case study for bridging ComputerAssociate's DSL of the AllFusion Gen CASE tool with IBM's Rational Software Modeler for UML.

show abstract

Visualisation of Domain-Specific Modelling Languages Using UML

Cited by 10 publications

References 16 publications

Making sense of business process descriptions: An experimental comparison of graphical and textual notations

Making sense of business process descriptions: An experimental comparison of graphical and textual notations

Applying Integrated Domain-Specific Modeling for Multi-concerns Development of Complex Systems

A semi‐automatic approach for bridging DSMLs with UML

Contact Info

Product

Resources

About