Chapter 7. Creating Use Cases
A use case is a description of a system in terms of a sequence of actions. It should yield an observable result or value for the actor interacting with the system. Following are some characteristics of use cases:
They are initiated by an actor.
They model an interaction between an actor and the system.
They describe a sequence of actions.
They capture functional requirements.
They should provide some value to an actor.
They represent a complete and meaningful flow of events.
The purpose of a use case is to facilitate agreement between developers, customers, and users about what the system should do. A use case may be used as a contract between developers and customers. It’s also a basis for use case realizations, which play ...
Get Requirements Management Using IBM Rational RequisitePro 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.
