Chapter 3. Today with Use Cases
As we established in earlier chapters, to get a truly extensible system, we must keep concerns separate all the way to code and must modularize the implementation accordingly. We also showed how this can be achieved with AOP. However, there still remains a challenge—that of finding concerns and expressing them clearly. Fortunately, we already have a well-proven technique to find and express them. It is the use-case technique. Use cases help us explore the various ways in which the system is used. They provide a means to validate stakeholder concerns early in the project. They are also excellent tools to drive the definition of the system architecture and the development and delivery of the system. However, until ...
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.
