Options: 1. If following the WAVE rule, this use case would represent the entire scenario that has value to a "Player" 2. "Search Premade Characters" is an optional task after "Create Character' 3. "Select Upgrades" is an optional task after "Upgrade Character" 4. If following the WAVE rule
Options:
1. If following the WAVE rule, this use case would represent the entire scenario that has value to a "Player"
2. "Search Premade Characters" is an optional task after "Create Character'
3. "Select Upgrades" is an optional task after "Upgrade Character"
4. If following the WAVE rule, this use case should look at tasks from the "Player" point of view, and describe how tasks are performed
The WAVE rule is a guideline for writing effective use cases that stands for Who, Action, Value, and Exception. According to this rule, a use case should answer the following questions:
Who is the primary actor of the use case?
What action does the actor perform to achieve a goal?
What value does the actor gain from performing the action?
What exception scenarios can occur during the action?
Trending now
This is a popular solution!
Step by step
Solved in 3 steps
