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

Root Maps Make Reservation

start

Make Reservation

start success

Reservation

Waiting List

start

makeReservation

Authorization

WaitingList

fail

[Failed]

Add to Waiting List

addToWaitingList

[OK]

success

fail success

Cancel Reservation

start success Cancel Reservation

start

start

WaitingList

Authorization Try Waiting List Reservation

cancelReservation

tryReservationsFromWaitingList

Security

success

success

Security

start success

checkAuthorization

[success]

[fail]

fail

Fig. 5. Advanced UCM reservation use cases — second attempt

Root Map

Make Reservation
Part 1

Make Reservation
Part 2

start

success

Authorization Other Feature

fail

Add to Waiting List

Fig. 6. Description of make reservation is spread out over multiple disjoint plug-in
maps

Note that we are using AspectJ terms [14] but that the concepts also apply to
other flavors of aspect-oriented programming.
Aspect-oriented modeling (AOM) or early aspects aims to apply aspect-
oriented concepts earlier in the software development life cycle in order to man-
age more effectively concerns at the requirements and architecture stages. Many
approaches to aspect-oriented requirements engineering (AORE) are described
in a recent survey [20], grouped into viewpoint, goal, scenario/use case, concern,
and component-based approaches. As our technique is more closely related to the