loading...
On Aspect-Oriented Software Architecture: It Implies a Process as Well as a Product
Gold Coast, Australia December 04-December 06
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/APSEC.2002.1182997Ninth Asia-Pacific Software Engineeri ...
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Masami Noro, Nanzan University
Atsushi Kumazaki, Nanzan University
We assume that software archite ture is a set of aspects which represent concerns multiple-dimensionally separated. Moreover, software architecture is assumed to be not just a product model but it also implies a software process for its implementation. We view the architecture as a set of aspects connected via join points. In this sense, the aspect is the composite component and the join point is the connector. The aspect, in turn, consists of a set of components from different abstraction level of the development stage. A connector implies an order of the development of connected components. Based on this assumption,the architecture (connectors) is to define a partial-order process for the development. This paper describes the idea which tells how a software architecture defines software process in the context of aspect-orientation. We demonstrated how it works with several examples.
Citation:
Masami Noro, Atsushi Kumazaki, "On Aspect-Oriented Software Architecture: It Implies a Process as Well as a Product," apsec, pp.276, Ninth Asia-Pacific Software Engineering Conference (APSEC'02), 2002
Usage of this product signifies your acceptance of the Terms of Use.