AspectJ Paradigm Model: A basis for Multi-paradigm Design for AspectJ

Vranić, Valentino

doi:10.1007/3-540-44800-4_5

Cited by 6 publications

(7 citation statements)

References 5 publications

(5 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The set of nodes V T contains a node for features of the AspectJ programming language. The AspectJ feature model in [54] is used as a starting point to define what features may be present as nodes in this graph. The set of edges E T contains directed edges (v T 1 , v T 2 ) that denote containment or parent-child relationship (i.e.…”

Section: Graph Representation Of the Aspectj Codementioning

confidence: 99%

Aspect-oriented model-driven skeleton code generation: A graph-based transformation approach

Bennett¹,

Cooper²,

Dai³

2010

Science of Computer Programming

View full text Add to dashboard Cite

a b s t r a c tModel-driven code generation has been investigated in traditional and object-oriented design paradigms; significant progress has been made. It offers many advantages including the rapid development of high quality code. Errors are reduced and the consistency between the design and the code is retained, in comparison with a purely manual approach. Here, a model-driven code generation approach based on graph transformations for aspect-oriented development is proposed. The approach has two main transformation activities. The first activity transforms a visual (graphical) model of the design into a formal, text-based notation that can be readily processed. The graphical model is created by the software designer and uses a UML profile for aspect-oriented software (i.e., FDAF) to represent aspects and their components. XML is the target notation for this step; the transformation uses the XML meta-model to ensure that the output complies with the language. The second activity transforms the XML model into AspectJ source code. The transformation uses the AspectJ meta-model to ensure the output complies with the language. The transformations from the extended UML model to XML and from XML to AspectJ code are fully automated. The transformation algorithms are based on graph transformations; tool support has been developed. Key technical issues in the approach are discussed, including performance, the amount of code generated, correctness, and adaptability, in addition to a comparison of the proposal with existing alternative approaches. The approach has been validated on three example systems: a banking system, classroom scheduling system, and an insurance system. The banking system example is presented in the paper.

show abstract

Section: Graph Representation Of the Aspectj Codementioning

confidence: 99%

Aspect-oriented model-driven skeleton code generation: A graph-based transformation approach

Bennett¹,

Cooper²,

Dai³

2010

Science of Computer Programming

View full text Add to dashboard Cite

show abstract

“…Remaining constraints are introduced in a list of constraints associated with the feature diagram. Also, a list of default dependency rules may be associated with each feature diagram in order to specify which features should or should not appear together by default (details available in [18,19]).…”

Section: 3mentioning

confidence: 99%

“…This section will provide the necessary information on feature modeling in MPDFM invoking an example of an application domain concept on which further aspects of the method will be demonstrated. An exhaustive r description of the feature modeling for multi-paradigm design may be found in [18,19].…”

Section: Introductionmentioning

confidence: 99%

Multi-paradigm design with feature modeling

Vranić

2005

COMSIS J

View full text Add to dashboard Cite

In this article, a method for selecting paradigms, viewed as solution domain concepts, appropriate for given application domain concepts is proposed. In this method, denoted as multi-paradigm design with feature modeling, both application and solution domain are modeled using feature modeling. The selection of paradigms is performed in the process of feature modeling based transformational analysis as a paradigm instantiation over application domain concepts. The output of transformational analysis is a set of paradigm instances annotated with the information about the corresponding application domain concepts and features. According to these paradigm instances, the code skeleton is being designed. The approach is presented in conjunction with its specialization to AspectJ programming language. Transformational analysis performed according to the AspectJ paradigm model enables an early aspect identification.

show abstract

“…In another point of view, the abstraction concepts differ according to level of granularity and the domain/concern they are applied in. For exa mple, Vranic [14] presents a feature model of concepts in the solution domain of AspectJ paradigm. Such a model represents the set of the higher-level abstractions, along with their variationpoints.…”

Section: Abstraction and Generality In Recent Workmentioning

confidence: 99%

A Note on the Role of Abstraction and Generality in Software Development

Návrat¹,

Filkorn²

2005

J. of Computer Science

View full text Add to dashboard Cite

Abstract:Although the evolving field of software engineering introduces many methods and modelling techniques, we conjecture that the concepts of abstraction and generality are among the fundamentals of each such methodology. This study proposed a formal representation of these two concepts, along with a two-dimensional space for the representation of their application. Based on the examples, we further elaborate and discuss the notion of abstraction and generalisation transformations in various domains of software development.

show abstract

AspectJ Paradigm Model: A basis for Multi-paradigm Design for AspectJ

Cited by 6 publications

References 5 publications

Aspect-oriented model-driven skeleton code generation: A graph-based transformation approach

Aspect-oriented model-driven skeleton code generation: A graph-based transformation approach

Multi-paradigm design with feature modeling

A Note on the Role of Abstraction and Generality in Software Development

Contact Info

Product

Resources

About