By Topic

Choosing the Right Time to Compose Aspectual Scenarios

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

3 Author(s)
Joao Araujo ; Universidade Nova de Lisboa, Portugal ; Jon Whittle ; Ana Moreira

Aspect-oriented software development (AOSD) provides effective modularization and composition mechanisms and can be applied at any stage of the software lifecycle. Aspect composition is a crucial feature of AOSD since it allows a developer to get an overall understanding of a system and better analyze the impact of a concern to a set of other concerns. The effort involved in composition, however, may vary depending on the lifecycle stage at which it is applied. This paper compares two methods of composing aspects during the early stages of the lifecycle. In both cases, scenarios and aspectual scenarios are developed for concerns and aspects, respectively. In the first method, the aspectual scenarios are composed immediately. In the second one, they are composed only after the scenarios have been converted to individual object behavioral descriptions. A comparison of the composition effort involved is made based on results of a case study

Published in:

30th Annual International Computer Software and Applications Conference (COMPSAC'06)  (Volume:2 )

Date of Conference:

17-21 Sept. 2006