JUMP—From Java Annotations to UML Profiles

Bergmayr, Alexander; Grossniklaus, Michael; Wimmer, Manuel; Kappel, Gerti

doi:10.1007/978-3-319-11653-2_34

Cited by 11 publications

(16 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As input models for this transformation, we selected a reference application of the ARTIST project, which is based on the Java Petstore 5 , and a framework that is of high relevance in this respect: EclipseLink 6 . The main rational behind the reverse-engineering of frameworks is to provide their annotations at the model level in terms of corresponding UML profiles [5]. To generate the respective Java models for the reference application and EclipseLink, we employed MoDisco.…”

Section: Case Study Setupmentioning

confidence: 99%

From out-place transformation evolution to in-place model patching

Bergmayr

Troya

Wimmer

2014

Proceedings of the 29th ACM/IEEE International Conference on Automated Software Engineering

Self Cite

View full text Add to dashboard Cite

Model transformation is a key technique to automate software engineering tasks. Like any other software, transformations are not resilient to change. As changes to transformations can invalidate previously produced models, these changes need to be reflected on existing models. Currently, revised out-place transformations are re-executed entirely to achieve this co-evolution task. However, this induces an unnecessary overhead, particularly when computation-intensive transformations are marginally revised, and if existing models have undergone updates prior the re-execution, these updates get discarded in the newly produced models.To overcome this co-evolution challenge, our idea is to infer from evolved out-place transformations patch transformations that propagate changes to existing models by re-executing solely the affected parts based on an in-place execution strategy. Thereby, existing models are only updated by a patch instead of newly produced. In this paper, we present the conceptual foundation of our approach and report on its evaluation in a real-world case study.

show abstract

Section: Case Study Setupmentioning

confidence: 99%

From out-place transformation evolution to in-place model patching

Bergmayr

Troya

Wimmer

2014

Proceedings of the 29th ACM/IEEE International Conference on Automated Software Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…Moreover, in [22] a systematic method to define such UML Profiles is presented, which is comparable to our approach but more abstract. Furthermore, [24] presents an automated approach to extract UML profiles from Java annotation libraries. UML profiles have been extended to EMF profiles in [25].…”

Section: Related Workmentioning

confidence: 99%

Engineering tagging languages for DSLs

Greifenberg

Look

Roidl

et al. 2015

2015 ACM/IEEE 18th International Conference on Model Driven Engineering Languages and Systems (MODELS)

View full text Add to dashboard Cite

To keep a DSL clean, readable and reusable in different contexts, it is useful to define a separate tagging language. A tag model logically adds information to the tagged DSL model while technically keeping the artifacts separated. Using a generic tagging language leads to promiscuous tag models, whereas defining a target DSL-specific tag language has a high initial overhead. This paper presents a systematic approach to define a DSL-specific tag language and a corresponding schema language, combining the advantages of both worlds: (a) the tag language specifically fits to the DSL, (b) the artifacts are kept separated and enabling reuse with different tag decorations, (c) the tag language follows a defined type schema, and (d) systematic derivation considerably reduces the effort necessary to implement the tag language. An example shows that it can at least partially be realized by a generator and applied for any kind of DSL

show abstract

“…For the former case, the annotation Id is used; for the latter, the annotations IdClass or EmbeddedId and Embeddable 2 . at class: require public constructor or protected constructor; 8 at class: forbid final method; 9 10 at class: require @Id method or @Id field or 11 @EmbeddedId method or @EmbeddedId field; 12 at class: forbid @Id method and @EmbeddedId method; 13 at class: forbid @Id field and @EmbeddedId field; 14 Listing 5: Selected JPA annotations defined in Ann.…”

Section: Defining the Annotations With Annmentioning

confidence: 99%

“…The expressiveness limitations of Java annotations are recognised in [11], where a proposal is made to embed DSLs into Java, with a more natural and flexible syntax. JUMP [8] is a tool to reverse engineer Java programs (with annotations) into profiled UML class diagrams.…”

Section: Related Researchmentioning

confidence: 99%

A modelling language for the effective design of Java annotations

Córdoba

Lara

2015

Proceedings of the 30th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

Esta es la versión de autor de la comunicación de congreso publicada en: This is an author produced version of a paper published in: ABSTRACTThis paper describes a new modelling language for the effective design of Java annotations. Since their inclusion in the 5th edition of Java, annotations have grown from a useful tool for the addition of meta-data to play a central role in many popular software projects. Usually they are conceived as sets with dependency and integrity constraints within them; however, the native support provided by Java for expressing this design is very limited.To overcome its deficiencies and make explicit the rich conceptual model which lies behind a set of annotations, we propose a domain-specific modelling language.The proposal has been implemented as an Eclipse plugin, including an editor and an integrated code generator that synthesises annotation processors. The language has been tested using a real set of annotations from the Java Persistence API (JPA). It has proven to cover a greater scope with respect to other related work in different shared areas of application.

show abstract

JUMP—From Java Annotations to UML Profiles

Cited by 11 publications

References 36 publications

From out-place transformation evolution to in-place model patching

From out-place transformation evolution to in-place model patching

Engineering tagging languages for DSLs

A modelling language for the effective design of Java annotations

Contact Info

Product

Resources

About