Chapter 4. Tomorrow with Use-Case Modules
Use cases provide the means to model and separate crosscutting concerns effectively, but you must preserve the separation of concerns through design and implementation. This means that you have to collate the specifics of a use case during design in some modularity unit, which we call a use-case slice. Each use-case slice collates parts of classes, operations, and so forth, that are specific to a use case in a model. The task of composing these parts is left to some composition mechanism (provided by aspect technology). The developer no longer needs to perform this step, and from this perspective, he or she no longer faces tangling from other concerns. This makes his or her code much cleaner and easier ...
Get Aspect-Oriented Software Development with Use Cases now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
