Information Technology Reference
In-Depth Information
Table 17.
Crosscutting matrix for CRS based on cascaded matrix in Table 16
concerns
Papers
Submis-
sion
Informati
on
Ret/Sup
Papers
Queries
Registra-
tion
Confe-
rence
User
Types
Review
Login
Papers Submission
0
0
0
0
0
0
0
0
Papers Queries
0
0
0
0
0
0
0
0
Registration
0
0
0
0
0
1
1
1
Conference
0
0
0
0
0
0
0
0
Review
0
0
0
0
0
0
0
0
Information Ret/Sup
1
1
1
1
1
0
1
1
Login
1
1
1
1
1
1
0
1
User Types
0
0
1
0
0
1
1
0
Information Ret/Sup, Login and User Types concerns. Similarly, the User Types
concern crosscuts the Registration, Information Ret/Sup and Login concerns. As we
showed in the dependency matrix obtained by means of the cascading operation (see
Table 16
), all these concerns are scattered in several design modules and in at least one
of these modules some other concern is tangled.
Obviously, this conclusion about crosscutting depends very much on the
decomposition at each level and the dependencies between elements at these levels.
There are many alternatives, which could aim at avoiding crosscutting by using
another modularization (e.g., aspect-oriented techniques such as [5]). Here, we
showed how to analyse crosscutting across several phases in the software life cycle.
The impact of the selected decomposition in the framework is explained in the next
section.
5.5 CRS with Aspects
Following the CRS case study, we detected that the Login concern crosscuts other
concerns at the requirements phase. In this section we add aspect-oriented support at
requirement level to properly model such a concern. Note that we can decide to
postpone this refactoring and face up to the problem at later stages of the
development. This means, for example, dealing with the crosscutting concerns at
design level using techniques such as Theme/UML [5] or at implementation level by
means of an AOP language.
In [26], the authors present an approach to model volatile concerns — represent
business rules that the stakeholders would like to be able to change quickly — as
crosscutting concerns. They apply aspect-oriented techniques to model concerns
which require a high degree of evolution. Their approach presents a methodology
based on several steps: concern identification, concern classification and finally
concern representation based on the previous classification. The concerns which are
classified as volatile or crosscutting are marked as roles (using the special symbol “|”)
and they are modeled using a pattern specification model. In particular the authors
utilize a Use Case Pattern Specification and an Activity Pattern Specification. By
Search WWH ::
Custom Search