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

a) b)

Reservation

confirmed

Confirm *

Get *

Container

*

*

Security

finished

Set * || Get *

c) d)

Fig. 11. More examples of pointcut maps

end point may or may not be bound to a component. Figure 11c matches all
maps with a responsibility starting with Set or Get and bound to any compo-
nent as the first path node of the component (because the start point is outside
the component). Finally, Fig. 11d matches all maps with an OR-fork bound to
any component inside component Container as the first path node. The OR-fork
must be immediately followed on one branch by a static stub called Security and
an end point called finished , and followed by nothing on the other branch before
exiting the component (because the end point is outside the inner component).
In other words, if a path on the pointcut map crosses the boundary of a
component because of the location of a start or end point, then the path in the
matching UCM will also have to cross the boundary of the matching component.
Note that the start and end points that are not matched are shown in gray in
Fig. 11 and in Fig. 12. See Table 1 and Fig. 12 for a summary of all cases. The
base maps and pointcut maps in Fig. 12 assume that after the start points all
maps are identical. Therefore, whether a base map matches a pointcut map is
solely dependent on the locations and the names of the start points. Note that
the same matching rules apply to end points.

Location and Naming of Start Point on Base Map

abc abc abc abc

abc abc xyz xyz

a) b) c) d)

Location and Naming of Start Point on Pointcut Map

abc abc abc abc

abc abc

e) f) g) h)

Fig. 12. Location and naming of start points on pointcut maps and base maps