Aspect-Oriented Software Development with Use Cases

Part III. Keeping Concerns Separate with Use-Case Modules

Now that you have correctly modeled stakeholder concerns with use cases, the next step is to preserve that separation during design and implementation. Separation is maintained through a new modularity unit called a use-case slice. A use-case slice contains classes and extensions to existing classes (organized within aspects) that are specific to each use-case realization in the design model. Thus, the design model comprises an element structure (a hierarchical organization of elements in terms of layers, packages, subsystems, etc.) and a set of use-case slices that overlay behaviors onto these elements. In the past, developers have implemented directly on the element structure. The result ...