Figure 5 - uploaded by Tony Clark
Content may be subject to copyright.
Contexts in source publication
Context 1
... this point it is instructive to see a visual counterpart of the relation we have been defining up to this point. Figure 5.3 shows a transformation diagram for Method And XML. ...
Context 2
... notation is introduced through some examples followed by detailed syntax and semantics. Figure 5.5 specifies a transformation, UML2Rel from UML classes and attributes to relational tables and columns. The figure specifies that the relation, UML2Rel holds between a class c and a table t if and only if corresponding to every attribute of class c, there is a column in table t, with the same name. ...
Context 3
... notation also supports specifications involving sets of objects. The UML Class to Relational Table example can be specified using sets of objects as shown in figure 5.8. In the figure aset and colset, specify the set of all attributes of class c, and all columns of table t, respectively. ...
Context 4
... notation also includes support for specifying the non-existence of objects and overriding of relations. Figure 5.9 specifies a strange transformation from a class with no attributes to a table with exactly one column named 'empty'. ...
Context 5
... overrides, extends is like the {and} operator. Figure 5.10 gives an example of the extends construct. ...
Context 6
... 5.10 gives an example of the extends construct. It extends the specification given in Figure 5.5. Figure 5.5 specifies a transformation from class, attribute to table, column. Figure 5.10 extends this to include transformation of primary key attributes of associated classes as foreign key columns. ...
Context 7
... extends the specification given in Figure 5.5. Figure 5.5 specifies a transformation from class, attribute to table, column. Figure 5.10 extends this to include transformation of primary key attributes of associated classes as foreign key columns. ...
Context 8
... extends the specification given in Figure 5.5. Figure 5.5 specifies a transformation from class, attribute to table, column. Figure 5.10 extends this to include transformation of primary key attributes of associated classes as foreign key columns. ...
Similar publications
Citations
... During the year 2003 and 2004, the submissions were revised and converged. In March 2005, two remaining submissions were combined to provide the joint 3rd revised submission by the QVT Merge Group [27]. This QVT specification use trace classes for keeping traces between source and target elements which are mapped in a transformation. ...
... This QVT specification also proposes transformation rules to transform a transformation definition in the Relations Language to the corresponding one in the Core Language, in which there is a rule to define the a trace class for each relation. The trace class contains a property corresponding to each object node in the pattern of each domain of the relation [27]. In this paper, we present a framework for change impact analysis in case of crosscutting in model transformations (seeFigure 2). ...
... The example rules TR1 and TR2 are given in the QVT Relational Language. The QVT Core Language groups variables of the rules into different areas and patterns as explained in the QVT Specification [27]. The dependency graph of the second rule TR2 is now explained in terms of the Core Language (seeTable 3). ...
This paper describes an approach for the analysis of crosscutting in model transformations in the Model Driven Architecture (MDA). Software ar-chitectures should be amenable to changes in user requirements and techno-logical platforms. Impact analysis of changes can be based on traceability of architectural design elements. Design elements have dependencies with other software artifacts but also evolve in time. Crosscutting dependencies may have a strong influence on modifiability of software architectures. We define cross-cutting based on a traceability pattern. We present an impact analysis of cross-cutting dependencies in transformations rules at model level as well as at meta-model level.
... Having chosen this AspectJ metamodel, the target metamodel is totally determined:the same Java metamodel extended by the AspectJ metamodel.Figure 2 Another important element that should be defined is the language to express the mappings between metamodels. In this case, we have chosen the QVT draft [7], because it is the current response to the RFP. QVT stands for Query, Views and Transformations. ...
In the last few years, new software paradigms, such as Aspect-Oriented Software Development (AOSD) or Model Driven Development (MDD), have been brought up in order to improve software adaptability to changes. MDA improves the adaption to different technologies by means of three di-fferent levels of modelling. This paper is focused on the platform specific level, and proposes the use of transforma-tions to weave AspectJ aspects and the basic functionality at the modelling level before the code generation phase.
... Model transformation is widely recognized as a central ingredient of model engineering approaches. The QVT RFP [10] issued by OMG and the resulting answer by QVT-Merge [11] as well as ATLAS Transformation Language [2] [8] are two examples of model transformation solutions among many. Although they focus on transformation specification and execution, many approaches make use of traceability. ...
In the context of model transformation, traceability information may be used in a wide variety of scenarios. Each of them potentially requires a dif-ferent format or complexity level. Moreover, a single transformation program can be used in several contexts. Consequently, such a program may need to be able to generate different kinds of traceability information. This work aims at showing how traceability can be added to programs written in ATLAS Trans-formation Language while limiting dependencies to program logic. Model transformation is used to implement this approach.
... Several answers were officially given, such as [21], [3] and [13]. There is, at the time this paper is being written, only one merged proposal remaining, from QVT-Merge group [20]. Other model transformation languages, such as ATLAS Transformation Language (ATL) [6] [13], have evolved in parallel to this process. ...
Model transformation creates a set of target models from a set of source models. This operation is central in current MDE approaches. However, we highlight in this paper some of its limitations. Model weaving is another operation on models, which specifies typed links between model elements. Model weaving can thus be used to specify abstract model transformations as sets of links between source and target metamodel types. Therefore, we propose to combine model transformation and model weaving in order to overcome some of current model transformation limitations. This paper presents how we experimented this with ATLAS Transformation Language (ATL) and AMW (ATLAS Model Weaver) on an example.
The virtual enterprise (VE), in general collaborations among business partners in value chains, has become a prime candidate model for competitiveness under the increasingly turbulent business environment. In order to quickly respond to the rapidly changing business environment, agility and interoperability are the main requirements for the VEs. This paper suggests a framework for designing the agile and interoperable VEs. Existing approaches, such as enterprise architecture, model driven architecture, domain specific methodology, meta-modeling, framework-based development, etc., are reviewed, revealing that none offers a complete solution that supports all the aspects of the VE modeling in an elegant manner. Thus, this paper develops a systematic modeling framework by harmonizing these approaches and combining the individual advantages of each approach to produce integrated synergy effects. This modeling framework can be used for business managers or business domain experts to build an agile and interoperable VE quickly and systematically with insights. It also supports a coherent enterprise modeling in which various stakeholders having their own aspects and methodology, such as an IT manager and a business manager, can communicate effectively.
In order to effectively validate the performance of software systems throughout their development cycle it is necessary to continuously build performance models from software models and then use the obtained models to check whether the system is being developed according to its performance requirements. The model building activity is a critical and effort-consuming activity. Several approaches have been envisaged to endow software designers with tools that automatically build ready-to-evaluate performance models from software development models. One essential requirement of such tools, often disregarded by current approaches, is a high degree of interoperability with software development tools, which has the positive effect of reducing both the level of required expertise in performance theory and the burden of learning separate tools. This paper introduces a framework for transforming source software models into target performance models. The transformation requires a clear understanding of the abstract syntax and semantics of both the source and target models, which is obtained by use of metamodeling techniques for defining the abstract syntax of models, the interrelationships between model elements and the model transformation rules. In the paper case, the framework is applied to the transformation of source models of UML type into target models of LQN (layered queueing network) type. The proposed approach is founded on the precepts recently introduced by model-driven development (MDA) and makes use of the set of related standards (MOF, QVT, XMI). This allows to obtain a high degree of automation, so that interoperable model transformation tools can be implemented in a timely and efficient way, leading to improvements in terms of software designers' productivity and system quality.
The Model Driven Architecture (MDA) promotes the use of models and model transformations for developing software systems.
The idea behind MDA is to manage the evolution from Platform Independent Models to Platform Specific Models that can be used
to generate executable components and applications. The concepts of metamodels and metamodel-based model transformations are
critical in MDA. In this paper, we propose a metamodeling technique to reach a high level of reusability and adaptability
of MDA components. In particular, we analyze how to define reusable components for the standard design patterns in a way that
fits MDA very closely. To define families of reusable components we describe a “megamodel” that refers to metamodels and model
transformations organized into an architectural framework. We propose a “megamodel” formalization that focuses on interoperability
of formal languages in Model Driven Development (MDD).
Software architecture views separate the concerns that are presented in phases previous to the detailed design phases of a
software system. Each view represents a different structure of a system for its analysis and documentation. Although each
view can be designed separately, they are linked because they are part of the same system. These links must be explicitly
shaped and maintained in order to achieve synergy in their design and also to preserve consistency among the views when they
change for evolution or maintenance reasons. This work proposes the use of the Model-Driven Architecture (MDA) approach to
establish the links among the architectural views through a relation of models. This work shows how relations among software
architectural views can be established by means of strategies used in MDA in a systematic way.
The Generative Model Transformer (GMT) project is an Open Source initiative to build a Model Driven Architecure™ tool that allows fully customisable Platform Independent Models, Platform Description Models, Texture Mappings, and Refinement Transformations. The project should result in (a) a tool that fulfils the MDA promise for faster/more accurate/better maintainable application development, (b) a tool for industrial use, and (c) MDA related research-which is encouraged and needed. A distinctive feature of GMT is the emphasis of model transformations as "first-class model citizens". The implementation of model transformations is envisaged to be in conformance with the future OMG modeling standard for Queries, Views, and Transformations (QVT).
The Generative Model Transformer (GMT) project is an Open Source initiative to build a Model Driven ArchitecureTM tool that allows fully customisable Platform Independent Models, Platform Description Models, Texture Mappings, and Refinement Transformations. The project should result in (a) a tool that fulfils the MDA promise for faster/more accurate/better maintainable application development, (b) a tool for industrial use, and (c) MDA related research-which is encouraged and needed. A distinctive feature of GMT is the emphasis of model transformations as "first-class model citizens". The implementation of model transformations is envisaged to be in conformance with the future OMG modeling standard for Queries, Views, and Transformations (QVT).
