INRIA Lille - Nord Europe
40 avenue Halley
59650 Villeneuve d'Ascq, France
Map
Side Bars
Header/Footer
Site Pages
On getting Use Cases and Aspects to Work Together. Renaud Pawlak and Houman Younessi. JOURNAL of Object Technology (JOT), 3(1):26, February 2004.
Aspect orientation (AO) as an underlying logical model deduced from Aspect Oriented Programming (AOP) [Kiczales97] is attracting attention and gaining in popularity. A NUMBER of AUTHORs have recently written about how ideas of aspect orientation might be used in connection or in conjunction with existing modeling techniques or technologies in order to enhance the capabilities of the latter. For example, in a recent JOT article Ivar Jacobson writes about the relationship between use cases and AOP [Jacobson03] claiming essentially that the two can be viewed as equivalent. It is however critical for those of us proposing these ideas and connections to ensure that such claims are based on a foundation of adequate comparison and analysis. As investigators who have been working on similar ideas for some time, we would like to take the opportunity of this short paper to provide a constructive critique of what such comparisons need to entail and where the critical issues lie. The Jacobson paper would be used as an exemplar to raise and discuss some common issues and shortcomings. We will explain that although we agree with the essence of Jacobson�s overall statement, we also believe that such assertion is � as it stands � neither new in its essence, nor is it complete and needs to be complemented by crucial improvements if we really want to bring new answers to software engineering.
@ARTICLE { pawlak-jot-04,
AUTHOR = { Renaud Pawlak and Houman Younessi },
TITLE = { On getting Use Cases and Aspects to Work Together },
JOURNAL = { JOURNAL of Object Technology (JOT) },
YEAR = { 2004 },
VOLUME = { 3 },
NUMBER = { 1 },
PAGES = { 26 },
MONTH = { feb },
GROUPS = { jacquard,JOURNAL,international,mosaiques },
ABSTRACT = { Aspect orientation (AO) as an underlying logical model deduced from Aspect Oriented Programming (AOP) [Kiczales97] is attracting attention and gaining in popularity. A NUMBER of AUTHORs have recently written about how ideas of aspect orientation might be used in connection or in conjunction with existing modeling techniques or technologies in order to enhance the capabilities of the latter. For example, in a recent JOT article Ivar Jacobson writes about the relationship between use cases and AOP [Jacobson03] claiming essentially that the two can be viewed as equivalent. It is however critical for those of us proposing these ideas and connections to ensure that such claims are based on a foundation of adequate comparison and analysis. As investigators who have been working on similar ideas for some time, we would like to take the opportunity of this short paper to provide a constructive critique of what such comparisons need to entail and where the critical issues lie. The Jacobson paper would be used as an exemplar to raise and discuss some common issues and shortcomings. We will explain that although we agree with the essence of Jacobson�s overall statement, we also believe that such assertion is � as it stands � neither new in its essence, nor is it complete and needs to be complemented by crucial improvements if we really want to bring new answers to software engineering. },
KEYWORDS = { aspect },
WEBSITE = { www.jot.fm/issues/issue_2004_01/index_html },
PDF = { pawlak-jot-04.pdf },
LONGNOTES = { 20040201 },
LASTNAME = { Pawlak },
DATEADDED = { 2007-03-26 },
LASTDATEMODIFIED = { 2007-03-26 },
AERES = { ACL },
INRIA = { JACQUARD },
LABO = { dans },
}
Adam