Chapter 4. Balancing the Software System Use Case Model
Use cases alone are not enough to carry you into design. The temptation is to base development on use cases, especially to developers who come from a transaction-oriented background. The results are usually enormous control objects, no reuse of functionality, and duplication of objects.
—Anthony Heritage and Phil Coley [Heritage 1995]
What’s in this chapter?
Use cases can describe the functionality of the system, but form is necessary to balance functionality. Form is provided with a well-designed system architecture. In this chapter, we discuss the ways that architecture can enhance the use case model.
Use case modeling, when used in isolation and performed incorrectly, may lead ...
Get Advanced Use Case Modeling: Software Systems 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.
