Type: Rules
Sources: www.oose.de
Gist
Find out whether a given system use case isn't too large and not too small.
Rules and Notes
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.
Costs, Savings
What does it take to implement those rules? What does it give?
Side effects
Is there anything that happend or will happen as one implements the rules? This relates to both wanted and unwanted effects ('unwanted' does not imply 'negative').
Related Pages
- use case content patterns
- 5 universal rules for task prioritization
- 6 ways to propagate non functional requirements
If you want to know more about a topic, simply tag the article with a 'morePlease' or 'examplesPlease' tag!
