Information Technology Reference
In-Depth Information
Table 15.
Dependency matrix (requirements x classes) for CRS
classes
Confe-
rence
Pc
Chair
Pc
Member
Partici-
pant
Paper
Review
Author
Logger Registry
Register Process
0
0
0
0
0
0
1
0
1
S
Info Papers
1
0
0
0
0
0
0
0
0
NS
Load Papers
1
0
0
0
0
0
0
0
0
NS
Review Process
0
1
0
0
0
0
0
0
0
NS
Conf. Manag
0
0
1
0
0
0
0
0
0
NS
Login&Roles
0
0
0
0
0
0
1
1
0
S
Actors
0
0
0
1
1
1
1
0
0
S
T
NT
NT
NT
NT
NT
T
NT
NT
build the dependency matrix shown in
Table 15
to show the trace dependencies
between requirements and design elements.
As we can see in
Table 15
, the trace dependencies between requirements and
classes are direct mappings except for
Register Process
and
Login&Roles
because of
information added in the
Participant
class for such register and login purposes
respectively (
infoRegistry
and
login
,
passwd
attributes of Participant class). These
requirements are tangled in this class with the own functionality of the Participant
class (User Type).
We apply the cascading operation (as defined in Sect. 4) between the dependency
matrix concerns x requirements (Table 13) and the dependency matrix requirements x
design (Table 15) to obtain trace dependencies between concerns and design elements.
This derived dependency matrix concerns x design is shown in Table 16.
Table 16.
Cascaded dependency matrix (concerns x classes) for CRS
classes
Finally, applying our definition of crosscutting to the last derived dependency
matrix, we obtain the crosscutting matrix shown in
Table 17
.
From this matrix we can observe that — with respect to the design — we have
obtained some new crosscutting concerns. The Registration concern crosscuts the
Search WWH ::
Custom Search