The use case narrative, part 1
A common question about use cases is "How do I show workflow or screen flow?"
The short answer is that you don't. A more appropriate question would be,
"How do I use the use case model to determine screen and workflow requirements?"
The short answer is that you don't. A more appropriate question would be,
"How do I use the use case model to determine screen and workflow requirements?"
Check out the pre-conditions and assumptions. If one use case requires the user to provide data that belongs to
another use case, or do something that another use case is responsible for, then logically the other use
case must come first.
Quite often, screen and workflows are far more flexible than we think. Let the use case constraints tell you what the flow options are. Then design the flow or flows that are possible, letting the users make the final choice as to which flow is best in the current task.
Quite often, screen and workflows are far more flexible than we think. Let the use case constraints tell you what the flow options are. Then design the flow or flows that are possible, letting the users make the final choice as to which flow is best in the current task.
