Chapter 15. Events, Responses, and States
“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.
Events and an Event Table
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 ...
Get Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration 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.
