Chapter 14. Separating Nonfunctional Requirements with Infrastructure Use Cases

A system needs to meet a set of nonfunctional requirements such as security, reliability, performance, and supportability. These are provided by a set of infrastructure use cases. Traditionally, the realization of application use cases tends to be tightly coupled with the infrastructure because the former makes direct calls to the infrastructure. As an implementation technique, you can use aspects and pointcuts to factor out the infrastructure. On top of that, you need a way to modularize infrastructure concerns. You achieve this with infrastructure use cases. It is common to find the same infrastructure use case being attached to different parts of the application. ...

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.