Information Technology Reference
In-Depth Information
Fig. 9.
Login&Roles marked as a crosscutting concern
means of the Pattern Specification we can formalize the reuse of models. See [26] to
obtain more details about Pattern Specifications. The purpose of this section is to
show the application of such Pattern Specification to model the Login concern of our
CRS. Accordingly, we add the “|” mark before the name of the use case which
addresses the Login concern (
Login&Roles package
), see
Fig. 9
.
In [26], the authors present a template to represent each concern. In this template,
relationships with other concerns are shown. Since the Login concern is related
to other ones, we show in its template the relationships with such concerns (see
Table 18
). These relationships are extracted from
Table 13
, where we show concerns
which are crosscut by Login one.
Table 18.
Template for Login concern
In order to compose the crosscutting concern with the base concerns, in [26] the
authors use Activity Patterns Specifications. In these Activity Patterns, Activities
describe use cases and activity roles (marked as “|”) describe use case roles or
crosscutting use cases. Each responsibility listed in the concern's template
corresponds to an activity in an activity diagram or an activity role in an APS. The
nature of the concern (crosscutting, enduring or volatile) decides whether activities or
activity roles are used [26].
We show in
Fig. 10
a the activity diagram for the Review Paper use case. As we can
see in the figure, we have externalized from this activity the Login process which is
shown in
Fig. 10
b.
Search WWH ::
Custom Search