About USE CASE misunderstanding
Use case is a role that is provided to the outside from the outside of the system
"Valuable" stuff (usually using the verb) mainly
In view of the user's perspective, do not use Use Case as the system
The selection of features, because it is as a programmer's perspective.
What is "valuable"? Is the user's system
A series of operations meets his needs (can be fine)
. From this perspective, as long as your use case is well written enough
If the user's needs should not change, if you put
Use case, as the functionality provided by the system, you can always
You can modify your use case (of course, this is incorrect).
Finally, USE Case should not be a single step, such as "Press the button",
"Print Report", etc., but should be a series of interactions.
