A toolkit for weaving aspect oriented UML designs

Ho, Wai-Ming; Jézéquel, Jean-Marc; Pennaneac'h, François; Plouzeau, Noël

doi:10.1145/508386.508398

Cited by 30 publications

(6 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The source model of this transformation is a composed UML 8,9,15) -obtained as a result of the composition presented in Sect. 4.…”

Section: Transformation Principles From Uml To Lqnmentioning

confidence: 99%

“…A focal point of this area of research, known as AspectOriented Modeling (AOM), is the development of notational conventions that assist in modeling and composing crosscutting concerns. The modeling language used in many cases is UML [1,3,7,9,10,15,19,28,33,36], but other notation, such as a Domain-Specific Language for describing meta-level specifications, is also used [11].…”

Section: Introductionmentioning

confidence: 99%

“…Current AOM research is addressing the following problems: using aspects to describe crosscutting concerns [4,6,7,10,26,27]; model composition [3][4][5]9,19,35]; tool support for AOM [15,20,36]; analysis of composed models to identify and resolve conflicts and verify different model properties [30,33,36]. There are some research efforts, not entirely successful, to reduce the impedance mismatch between UML models and aspect-oriented implementation by defining UML model stereotypes for core AspectJ concepts (aspect, joint point, pointcut, advice, etc.)…”

Section: Introductionmentioning

confidence: 99%

“…There are many notable research efforts in the area of model composition, both for structure and behaviour. All UML means for representing behaviour have been used for composition: interaction diagrams in [7,9,10,20,33,36], statecharts in [1,6,15,19], activity diagrams in [3,30].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Performance analysis of aspect-oriented UML models

2007

View full text Add to dashboard Cite

Aspect-Oriented Modeling (AOM) techniques allow software designers to isolate and address separately solutions for crosscutting concerns (such as security, reliability, new functional features, etc.). Current AOM research is concerned not only with the separate expression of concerns and their composition into a complete system model, but also with the analysis of different properties of such models. This paper proposes an approach for analyzing the performance effects of a given aspect on the overall system performance, after the composition of the aspect model with the system's primary model. Performance analysis of UML models is enabled by the "UML Performance Profile for Schedulability, Performance and Time" (SPT) standardized by OMG, which defines a set of quantitative performance annotations to be added to a UML model. The first step of the proposed approach is to add performance annotations to both the primary and the aspect models. An aspect model is generic at first, and therefore its performance annotations must be parameterized. A generic model is converted into a context-specific aspect model with concrete values assigned to its performance annotations. The latter is composed with the primary model, generating a complete annotated UML model. The composition is performed in both structural and Communicated by Dr. Lionel Briand. behavioural views. A novel approach for composing activity diagrams based on graph-rewriting concepts is proposed in the paper. The next step is to transform automatically the composed model into a Layered Queueing Network (LQN) performance model, by using techniques developed in previous work. The proposed approach is illustrated with a case study system, whose primary model is enhanced with some security features by using AOM. The performance effects of the security aspect under consideration are analyzed in two design alternatives, by solving and analyzing the LQN model of the composed system.

show abstract

“…The source model of this transformation is a composed UML 8,9,15) -obtained as a result of the composition presented in Sect. 4.…”

Section: Transformation Principles From Uml To Lqnmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Performance analysis of aspect-oriented UML models

2007

View full text Add to dashboard Cite

show abstract

“…This paper discusses the business requirements as concerns in a data warehouse in general and derives the specific requirements for the AOSDDL (Aspect Oriented Software Development Design Language) design language architecture [1] to implement a data warehouse that is proposed within the broader area of this work.…”

Section: Introductionmentioning

confidence: 99%

Defining business requirements as concerns in data warehouse

Dahiya¹,

Batra²

2009

2009 2nd IEEE International Conference on Computer Science and Information Technology

View full text Add to dashboard Cite

This paper discusses the business requirements as concerns in a data warehouse in general and derives the specific information requirements for the AOSDDL (Aspect Oriented Software Development Design Language) design language architecture to implement a data warehouse that is proposed within this work. Research into aspect based business requirements so far has shown that no single solution will meet all possible requirements of aspect oriented data warehouse, and thus, multiple systems for domains with different demands must be able to co-exist and interoperate. The goal is to thoroughly define what the users must have to satisfy their business needs.

show abstract

Supporting the development of CAM/DAOP applications: an integrated development process

Fuentes¹,

Pinto²,

Troya³

2006

Softw Pract Exp

View full text Add to dashboard Cite

The increasing complexity of large‐scale distributed applications is driving the Software Engineering community to adopt new software technologies for the development of distributed systems. In this sense, the emergence of component‐based software engineering represents a significant advance towards assembling applications by plugging in pre‐fabricated components. Additionally, the principle of ‘advanced’ separation of concerns is nowadays widely applied to improve modularity, reusability and adaptability of software components. In this way, the aspect‐oriented software development paradigm separates into a new dimension, named aspect, those properties that crosscut the system ‘objects’ or ‘components’, reducing their dependencies. However, the development of software based on the composition of components and aspects is still in its early stages. Part of the reason for this is the lack of well‐defined development processes and tools that help software developers in the use of existing component and aspect‐based approaches. Therefore, the primary aim of this paper is to propose an integrated development process for deriving applications by the assembly of a set of prefabricated components and aspects. This process supports the development of Component‐Aspect Model/Dynamic Aspect‐Oriented Platform (CAM/DAOP) applications, where CAM/DAOP is a new model and platform based on components and aspects. Our intention is to show how, with the support of the integrated development process presented in this paper, it is possible to use CAM/DAOP as an alternative to current distributed platforms. Copyright © 2006 John Wiley & Sons, Ltd.

show abstract

A toolkit for weaving aspect oriented UML designs

Cited by 30 publications

References 7 publications

Performance analysis of aspect-oriented UML models

Performance analysis of aspect-oriented UML models

Defining business requirements as concerns in data warehouse

Supporting the development of CAM/DAOP applications: an integrated development process

Contact Info

Product

Resources

About