Use Case Modeling

Chapter 8. Writing Use-Case Descriptions: An Overview

There is an easy trap into which one can fall after identifying use cases and actors, writing some brief descriptions, and drawing some use-case diagrams: stopping! At this point, one really knows only that there are people or things that will use the system, and there will be some vague notion of what they want to do with the system, but little more. Although this may be appropriate for simple use cases that have well-understood behavior (that is, there is no risk that anyone will misunderstand what the system will do for this use case), most use cases will have at least some additional description, even if it is only an outline of the flow of events.

There is no escaping it—at some point you ...