Information Technology Reference
In-Depth Information
Table 20. Crosscutting matrix for CRS with aspects
crosscutting matrix (concerns x concerns) WRT requirements
concerns
Papers
Submis-
sion
Informa-
tion
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
0
0
0
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
0
0
Login
0
0
0
0
0
0
0
0
User Types
0
0
0
0
0
0
0
0
Table 20 we can observe the dependency and crosscutting matrix for concerns with
respect to requirements for the aspect-oriented decomposition respectively. As we can
see in these tables, the Login concern does not crosscut the other concerns anymore.
6 Discussion
In this section, we consider how to address some open issues according to our
framework. In some cases, there could be better solutions to be considered; however, the
main purpose of this section is to enhance the discussion about the following topics. We
first analyze some trace dependency types which can be used in the crosscutting pattern.
Then, we discuss how crosscutting is related to decompositions expressed in modeling or
implementation languages. We conclude our discussion with the role of intra-level
dependencies (coupling) for the transitivity of trace relations.
6.1 Trace Relationships
We introduced the crosscutting pattern in Sect. 2.1. We assumed that elements in the
source are related to elements in the target through a mapping captured in trace
dependency relationships. In order to determine when two elements from source and
target are related to each other, we introduced a trace dependency model which
Fig. 12. Trace relationships
Search WWH ::




Custom Search