Chapter 9. Dividing Large Systems
What if you have been going through the process and you find that you need more detail—everything is too high level, too abstract? It may be that your use cases are not detailed enough. But it’s also possible that your system is too big to deal with altogether. If so, you need an approach to break the system into pieces that are small enough to work with.
We will start by defining the modules of the architecture of the system. An architecture is specific to a particular application, but we’ll go through a few basic architectural patterns in this chapter to give you some ideas. These patterns provide a basic framework for the system without going into detail about the contents of the system. You may find that ...
Get Applying Use Cases: A Practical Guide, Second Edition 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.
