Aspect-Oriented Software Development with Use Cases

Part II. Modeling and Capturing Concerns with Use Cases

We have established that the goal aspect-oriented programming is to keep concerns separate. In order to do so, you must correctly identify and structure concerns early in the life cycle of the project rather than as an afterthought during design and implementation. In other words, separation of concerns must start during requirements. This does not mean capturing every detailed requirement for each concern at the beginning of the project. Instead, you systematically organize stakeholder concerns to scope the system. The detailing and refinement of the requirements for each concern can be prioritized and allocated across the project life cycle in an iterative manner.

The use-case technique ...