Finding the right size for a use case

Name: Finding the right size for a use case
Type: Rules
Status: finished
Version: 2008-03-28
Source: www.oose.de
Gist: find out whether a given system use case isn't too large and not too small.

R1: Each use case has a business trigger
R2: Each use case yields an externally observable result that is useful for the business
R3: Each use case is coherent by time
Note: R3 means the use case passes the lunch break test: the primary actor wouldn't take her lunch break while in the middle of the execution of the use case steps.