Visualizing Early Aspects with Use Case Maps - Transactions on Aspect-Oriented Software Development - page 122

shown on the maps in Fig. 13 is very simple as it consists only of one responsi-
bility. In reality, the responsibility may be replaced by much more complicated
advice maps (e.g., see Fig. 8 and imagine a pointcut stub added somewhere on
the path).

3.5 Aspect-Oriented Use Case Maps Example

This section revisits the reservation example from Sect. 2.2 and models it with
AoUCMs. In Fig. 14, the base maps show the use cases for making and canceling
a reservation. Two aspects are defined that describe authorization and waiting

Base Maps

Reservation

start success

makeReservation [reservationOK]

[reservationFailed]

fail

Reservation

start success

cancelReservation

Authorization Aspect

Security

accessReservation

success

start

A
d
v
i
c
e

checkAuthorization

[success]

P

[fail]

fail

P
o
i
n
t
c
u
t

Reservation

*

Waiting List Aspect

makeReservation cancelReservation

start

success success

start WaitingList

A
d
v
i
c
e

[success]

P P

tryReservationsFromWaitingList

[fail]

WaitingList

addToWaitingList

fail

P
o
i
n
t
c
u
t

Reservation Reservation

makeReservation [reservationOK] cancelReservation

[reservationFailed]

Fig. 14. Aspect-oriented UCM model for reservations