Analysis of Crosscutting in Early Software Development Phases Based on Traceability - Transactions on Aspect-Oriented Software Development - page 89

Table 12. Dependency matrix and crosscutting matrix for action view presented in [4]

depen d ency matrix (actions x requirements)

requirements

R1 R2 R3 R4 R5 R6 R7 R8 R9

register 1 0 1 0 0 0 0 0 0 S

unregister 0 1 0 1 1 1 1 0 0 S

logged 0 0 1 1 0 1 0 0 1 S

give 0 0 0 0 0 0 0 1 1 S

flagged 0 0 0 0 0 0 1 0 0 NS

NT NT T T NT T T NT T

crosscutting matrix (actions x actions) WRT requirements

actions

register unregister logged give flagged

register 0 0 1 0 0

unregister 0 0 1 0 1

logged 1 1 0 1 0

give 0 0 1 0 0

flagged 0 0 0 0 0

crosscutting relations obtained firstly in the crosscutting product matrix and finally in
the crosscutting matrix. As we can see in the crosscutting matrix, the logged action
has more crosscutting cells than the other ones. Such results encourage the developer
to classify Login as a main crosscutting theme.

5.4 Conference Review System

In this section we show the case study of a Conference Review System (CRS). In
contrast to the previous case studies, here we show the application of the framework
to an example where concerns are related to both functional and non-functional
properties, and the results obtained in this case are more significant than those
obtained in the previous one. This case study has been presented in some workshops,
e.g. [17]. The general purpose of the original system is to assist a conference's
program committee to perform the review of papers and registration of conference
participants [13]. For space reasons, we have used a simplification of this system.
There are four different user types in the system: PcChair, PcMembers, Authors
and Participants. A PcChair is the main person responsible for the review process, and
has access to every paper and every review in the system. A PcMember takes over the
reviews of the papers and can see paper information but not reviews by other
PcMembers. An Author can submit papers to the system, being permitted to see only
information about his own submission. A Participant must register in order to attend
the conference. The registration process is completely separated from the login
process. However, once a user has registered he needs to login whenever he accesses
the system. This login process checks the role of the user in the system.