By Topic

Use-Case Based Aspect-Oriented Architecture Description Model

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
$31 $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)
Jun-wei Ge ; Coll. of Software Sci., Chongqing Univ. of Posts & Telecommun., Chongqing, China ; Tang Rong ; Yi-qiu Fang

The architectural description and design decide the quality and life of the software. Cross-cutting concerns as aspects crosscut multiple architectural components. Due to these cross-cutting concerns the metrics for cohesion and coupling are affected, the scenario result in lower values for modifiability and reuse quality attributes. Accordingly, the concept of aspect-orientation is required to be addressed in architecture design level. But now a lot of methods about architectural description fail to accommodate the description for cross-cutting concerns. In this paper, on the based of standard for "Recommended practice for architectural description of software-intensive system" in IEEE 1471-2000, we propose the Use-Case Based Aspect-Oriented Conceptual Model for bArchitecture Description to explicitly address aspects in architecture design. It is more favorable to maintain, reuse and evolve software system. And we applied this model into Web Service, shaped Aspect-Oriented Extension Architecture Description Model for Web Services to show the advantages of this approach.

Published in:

Software Engineering, 2009. WCSE '09. WRI World Congress on  (Volume:3 )

Date of Conference:

19-21 May 2009