MDI: A Rule-based Multi-document and Tool Integration Approach

Königs, Alexander; Schürr, Andy

doi:10.1007/s10270-006-0016-x

Cited by 30 publications

(27 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the less radical distributed model, artifacts reside within their own tool repositories while only meta-data is replicated in a central repository. Several authors have provided prototypical implementations [31,54]. Kolovos et al [52] and Barbero et al [7] describe approaches that merge models on-demand and so propose to create the replicated trace data only when required.…”

Section: Support For Heterogenitymentioning

confidence: 99%

Software traceability: trends and future directions

Cleland‐Huang

Gotel²,

Hayes

et al. 2014

Future of Software Engineering Proceedings

234

View full text Add to dashboard Cite

Software traceability is a sought-after, yet often elusive quality in software-intensive systems. Required in safety-critical systems by many certifying bodies, such as the USA Federal Aviation Authority, software traceability is an essential element of the software development process. In practice, traceability is often conducted in an ad-hoc, after-the-fact manner and, therefore, its benefits are not always fully realized. Over the past decade, researchers have focused on specific areas of the traceability problem, developing more sophisticated tooling, promoting strategic planning, applying information retrieval techniques capable of semi-automating the trace creation and maintenance process, developing new trace query languages and visualization techniques that use trace links, and applying traceability in specific domains such as Model Driven Development, product line systems, and agile project environments. In this paper, we build upon a prior body of work to highlight the state-of-the-art in software traceability, and to present compelling areas of research that need to be addressed.

show abstract

Section: Support For Heterogenitymentioning

confidence: 99%

Software traceability: trends and future directions

Cleland‐Huang

Gotel²,

Hayes

et al. 2014

Future of Software Engineering Proceedings

234

View full text Add to dashboard Cite

show abstract

“…Since there are three domains, they are called TGGs. As mentioned earlier, this can be extended to more than two domains: Multi-Graph Grammars as proposed in [12], which however are beyond the scope of this paper.…”

Section: Tgg Rulesmentioning

confidence: 95%

Comparing relational model transformation technologies: implementing Query/View/Transformation with Triple Graph Grammars

Greenyer

Kindler

2009

Softw Syst Model

View full text Add to dashboard Cite

The Model Driven Architecture (MDA) is an approach to develop software based on different models. There are separate models for the business logic and for platform specific details. Moreover, code can be generated automatically from these models. This makes transformations a core technology for MDA and for model-based software engineering approaches in general. Query/View/ Transformation (QVT) is the transformation technology recently proposed for this purpose by the OMG. Triple Graph Grammars (TGGs) are another transformation technology proposed in the mid-nineties, used for example in the FUJ-ABA CASE tool. In contrast to many other transformation technologies, both QVT and TGGs declaratively define the relation between two models. With this definition, a transformation engine can execute a transformation in either direction and, based on the same definition, can also propagate changes from one model to the other. In this paper, we compare the concepts of the declarative languages of QVT and TGGs. It turns out that TGGs and declarative QVT have many concepts in common. In fact, QVT-Core can be mapped to TGGs. We show that QVT-Core can be implemented by transforming QVT-Core mappings to TGG rules, which can then be executed by a TGG transformation engine that performs the actual QVT transformation. Furthermore, we discuss an approach for mapping QVT-Relations to TGGs. Based on the semantics of TGGs, we clarify semantic gaps that we identified in the declarative languages of QVT and, furthermore, we show how TGGs can benefit from the concepts of QVT.Keywords MDA · Model-based software engineering · Model transformation · Query/View/Transformation (QVT) · Triple Graph Grammar (TGG)

show abstract

“…The derivation of executable graph transformation rules from declarative triple graph grammar (TGG) rules is investigated in [18]. While TGG rules are quite close to the source and target modeling languages themselves, they are still created manually by the transformation designer.…”

Section: Related Workmentioning

confidence: 99%

Model transformation by example using inductive logic programming

Balogh

Varró

2008

Softw Syst Model

View full text Add to dashboard Cite

Model transformation by example is a novel approach in model-driven software engineering to derive model transformation rules from an initial prototypical set of interrelated source and target models, which describe critical cases of the model transformation problem in a purely declarative way. In the current paper, we automate this approach using inductive logic programming (Muggleton and Raedt in J Logic Program 19-20:629-679, 1994) which aims at the inductive construction of first-order clausal theories from examples and background knowledge.

show abstract

MDI: A Rule-based Multi-document and Tool Integration Approach

Cited by 30 publications

References 16 publications

Software traceability: trends and future directions

Software traceability: trends and future directions

Comparing relational model transformation technologies: implementing Query/View/Transformation with Triple Graph Grammars

Model transformation by example using inductive logic programming

Contact Info

Product

Resources

About