A use case can be defined as an activity performed by the system in response to an event. How can the analyst ensure that all the use cases (system functionalities) are captured? An interesting approach by Alistair Cockburn suggests that analysts identify use cases with the “coffee-break test”. That is, once the user has completed a use case, s/he can take a coffee-break without feeling guilty... Beyond the coffee-break test, there are 3 recommended techniques for identifying use cases. They are discussed below:

*Includes Free Template*