December 2010
Beginner to intermediate
368 pages
7h 19m
English
“I just dropped in to see what condition my condition is in.”
Mickey Newbury, “Just Dropped In”
This chapter explains the event-response way of capturing requirements and testing the state transitions caused by events.
The CD rental process is driven mostly by user actions. So employing use cases was a natural fit for eliciting requirements. There are other ways to discover requirements. A popular technique is the event table. It defines events that occur and determines how the system should respond. An event could be something that a user initiated or something that a piece of hardware signaled. It could also be a particular time, such as the first of the month, or a time ...
Read now
Unlock full access