Story Diagrams: A New Graph Rewrite Language Based on the Unified Modeling Language and Java

Fischer, Thorsten; Niere, Jörg; Torunski, Lars; Zündorf, Albert

doi:10.1007/978-3-540-46464-8_21

Cited by 209 publications

(153 citation statements)

References 3 publications

Supporting

Mentioning

152

Contrasting

Unclassified

Order By: Relevance

“…In this case, this sequence of two rules is said to be causally dependent. See [13] for a formal description of conflict and causality characterizations 6 .…”

Section: Fig 2 Graph Rule Initial-schedulementioning

confidence: 99%

See 1 more Smart Citation

Modeling with Plausibility Checking: Inspecting Favorable and Critical Signs for Consistency between Control Flow and Functional Behavior

Ermel

Gall

Lambers

et al. 2011

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. UML activity diagrams are a wide-spread modelling technique to capture behavioral aspects of system models. Usually, pre-and post-conditions of activities are described in natural language and are not formally integrated with the static domain model. Hence, early consistency validation of activity models is difficult due to their semi-formal nature. In this paper, we use integrated behavior models that integrate activity diagrams with object rules defining sets of actions in simple activities. We formalize integrated behavior models using typed, attributed graph transformation. It provides a basis for plausibility checking by static conflict and causality detection between specific object rules, taking into account their occurrence within the control flow. This analysis leads to favorable as well as critical signs for consistency of the integrated behavior model. Our approach is supported by ActiGra, an Eclipse plug-in for editing, simulating and analyzing integrated behavior models. It visualizes favorable and critical signs for consistency in a convenient way and uses the well-known graph transformation tool AGG for rule application as well as static conflict and causality detection. We validate our approach by modeling a conference scheduling system.

show abstract

“…In this case, this sequence of two rules is said to be causally dependent. See [13] for a formal description of conflict and causality characterizations 6 .…”

Section: Fig 2 Graph Rule Initial-schedulementioning

confidence: 99%

“…Fujaba [6], VMTS 16 and GReAT 17 are graph transformation tools for specifying and applying graph transformation rules along a control flow specified by activity models. However, controlled rule applications are not further validated concerning conflict and causality inconsistencies within these tools.…”

Section: Related Workmentioning

confidence: 99%

Modeling with Plausibility Checking: Inspecting Favorable and Critical Signs for Consistency between Control Flow and Functional Behavior

Ermel

Gall

Lambers

et al. 2011

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…There are also other graphical approaches, most of which are in turn based on graph grammars. Among them, we can find the visual representation of QVT [7] (where QVT is given in-place semantics) or the use of different (usually extended) UML diagrams [8,9]. These approaches do not use (so far) the concrete syntax of the DSL, but an object diagram-like structure.…”

Section: Adding Behavioral Semantics To Dslsmentioning

confidence: 99%

Behavior, Time and Viewpoint Consistency: Three Challenges for MDE

Rivera

Romero

Vallecillo

2009

Models in Software Engineering

View full text Add to dashboard Cite

Abstract. Although Model Driven Software Development (MDSD) is achieving significant progress, it is still far from becoming a real Engineering discipline. In fact, many of the difficult problems of the engineering of complex software systems are still unresolved, or simplistically addressed by many of the current MDSD approaches. In this position paper we outline three of the outstanding problems that we think MDSD should tackle in order to be useful in industrial environments.

show abstract

“…The plugin is specified using story diagrams [17], which may be seen as a UML-inspired notation for graph rewrite rules. From a single triple rule, six rules for directed transformations and correspondence analysis are generated in a first step.…”

Section: Related Work On Triple Graph Grammarsmentioning

confidence: 99%

A graph-based algorithm for consistency maintenance in incremental and interactive integration tools

et al. 2007

View full text Add to dashboard Cite

Development processes in engineering disciplines are inherently complex. Throughout the development process, the system to be built is modeled from different perspectives, on different levels of abstraction, and with different intents. Since state-ofthe-art development processes are highly incremental and iterative, models of the system are not constructed in one shot; rather, they are extended and improved repeatedly. Furthermore, models are related by manifold dependencies and need to be maintained mutually consistent with respect to these dependencies. Thus, tools are urgently needed which assist developers in maintaining consistency between inter-dependent and evolving models. These tools have to operate incrementally, i.e., they have to propagate changes performed on one model into related models which are affected by these changes. In addition, they need to support user interactions in settings where the effects of changes cannot be determined automatically and deterministically. We present an algorithm for incremental and interactive consistency maintenance which meets these requirements. The algorithm is based on graphs, which are used as the data model for representing the models to be integrated, and graph transformation rules, which describe the modifications of the graphs to be performed on a high level of abstraction.

show abstract

Story Diagrams: A New Graph Rewrite Language Based on the Unified Modeling Language and Java

Cited by 209 publications

References 3 publications

Modeling with Plausibility Checking: Inspecting Favorable and Critical Signs for Consistency between Control Flow and Functional Behavior

Modeling with Plausibility Checking: Inspecting Favorable and Critical Signs for Consistency between Control Flow and Functional Behavior

Behavior, Time and Viewpoint Consistency: Three Challenges for MDE

A graph-based algorithm for consistency maintenance in incremental and interactive integration tools

Contact Info

Product

Resources

About