History for UseCaseTemplate
??changed:
-
Use Case usecasename
Actor -- The actor. There is normally one actor, although
it is possible to have more than one. If you
*do* have more than one actor, consider whether
the actors are specializations of a more general
actor. Perhaps one of the actors is a generalization
of the others.
Goal -- The goal of the actor. What is the objective of the
actor in using this feature. Remember that the whole
point of use cases is to solve some problem for the user.
Setting -- Sometimes use cases only make sense in a certain
situation. For example, maybe a use case "BuyWidget"
can only happen when someone is browsing widgets.
Elaborate the use case. Most of the time, I like to
pretend I'm writing a section of a user's manual. I often even use
a heading from a notional users's manual.
Buying widgets
You can buy widgets by ....