Use-Case Based Aspect-Oriented Architecture Description Model

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.