Aspect-Oriented Software Development with Use Cases

Chapter 8. Keeping Peer Use-Case Realizations Separate with Aspects

With use cases, you can keep concerns separate during requirements time, but that is not enough. You also need to preserve that separation during design and implementation. In this chapter, we look at a particular kind of use case called a peer use case. Peer use cases have no relationship with one another, but their realizations involve the participation of some shared classes. You may find that some classes and some parts of classes are shared and reusable across use cases, while others are specific to each use-case realization. A use-case slice modularizes the specifics of a use case in a model. It utilizes aspects as a composition mechanism to extend use-case-specific features ...