Aspect-Oriented Software Development with Use Cases

Appendix A. Modeling Aspects and Use-Case Slices in UML

This appendix provides a quick guide to notation for modeling aspects as used in this book. Let’s recount the principles we use to model aspects. We treat aspect as part of an overlay (i.e., use-case slice) that is placed on top of an existing class or a set of classes. The names of the classes and operations must match those in the element structure before proper overlaying can take place. The use-case slice is a larger concept of an overlay than aspects. Whereas aspects can only add to existing classes, use-case slices can add entire new classes as well. Moreover, whereas parameterization of pointcuts is for binding existing locations (i.e., join points), use-case-slice template parameters ...