Model-Driven Software Development 2005
DOI: 10.1007/3-540-28554-7_5
|View full text |Cite
|
Sign up to set email alerts
|

Using Graph Transformation for Practical Model-Driven Software Engineering

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
15
0

Year Published

2005
2005
2012
2012

Publication Types

Select...
5
2
2

Relationship

1
8

Authors

Journals

citations
Cited by 39 publications
(15 citation statements)
references
References 44 publications
0
15
0
Order By: Relevance
“…FUJABA uses UML class diagrams to specify static graph schemas and adopts story diagrams composed of activity diagrams and collaboration diagrams to describe system operational behaviors. Using FUJABA, Grunske et al [4] performed a horizontal transformation between PIMs and a vertical transformation between a PIM and a PSM. A Pull UP method refactoring was realized using a story driven modeling language.…”
Section: Application Domainmentioning
confidence: 99%
See 1 more Smart Citation
“…FUJABA uses UML class diagrams to specify static graph schemas and adopts story diagrams composed of activity diagrams and collaboration diagrams to describe system operational behaviors. Using FUJABA, Grunske et al [4] performed a horizontal transformation between PIMs and a vertical transformation between a PIM and a PSM. A Pull UP method refactoring was realized using a story driven modeling language.…”
Section: Application Domainmentioning
confidence: 99%
“…According to Sendall et al [3] model transformation is defined as "a mapping of a set of models onto another set of models or onto themselves, where a mapping defines correspondences between elements in the source and target model". Transformation between PIMs is defined as "a horizontal transformation" as it takes place at the same abstraction levels and similarly, the transformation between PIM and PSM is considered as "a vertical transformation" because it moves from a high/low level abstraction to a low/high level [4].…”
Section: Model Transformationmentioning
confidence: 99%
“…Evaluation required that we become famil iar enough with the tool's capabilities, process, and philoso phy to be able to model our test use cases. Despite studying many works and their accompanying examples (e. g. , [4 ]- [6]) we remained unclear about precisely how to use Fujaba.…”
Section: Introductionmentioning
confidence: 98%
“…Applications of graph transformation to programming languages and software engineering include the semantics and implementation of functional programming languages [26,27], the specification and analysis of pointer structures [3,2,33], the semantics of the Unified Modelling Language [17,21] and the semantics and analysis of model transformations [36,9,5,15].…”
Section: Introductionmentioning
confidence: 99%