Chapter 10 typical users and scenarios
1. Boss's error
Be good at exploring the motivations behind users' language actions.
Ii. Document required
Although face-to-face direct communication is agile, documents are indispensable. This document helps to clarify user requirements and greatly reduce the time wasted for rework due to unknown requirements.
Iii. user types on the ATM operation interface
1. Only query account balance
2. You need to save a certain amount of coins
3. Other payment functions
4. transfer funds to other accounts
5. Users who frequently get money
6. users who need to change their passwords and other account management operations
Iv. Types of game users
1. Based on the player's game lifecycle, the question has a reference answer.
2. Division based on players' game experience:
A. Experienced gold players, good at challenging new games, strong game capabilities, and familiar with most game processes;
B. Experienced gamers have a wide range of skills;
C. Fewer students have played games.
For apprentices, more detailed game tutorials are required.
3. Division by players' character characteristics:
A. the type of competitive challenges. I like the excitement, but I don't want to control it. I don't want to spend any money on games;
B. Team Spirit type. I like to explore the world with my peers, reduce stress and enhance friendship. My payment tends to be outstanding;
C. Easy and easy to use. I am used to traveling with others. Generally, I am not willing to pay money;
Based on this, you can determine the type and billing of game products.
5. Do not overhead
In the scenario-driven design, it is easy to "overhead. In many cases, it is not necessary to simulate real user scenario models, which is useless to stimulate thinking. We use our logical thinking to simulate in the brain, then you can list the action steps in a certain logical order.
6. spec writing exercises. Tie the shoelaces to alien descriptions.
How to tie shoe laces?
We are going to write a spec to an English-speaking alien about how to tie his shoe laces. suppose the shoelaces have been bore all the holes. shoes will be more comfortable after fastening shoe laces. steps are as follows:
Step1. make an "X" out of the shoelaces
Step2. make a knot
Step3. tighten the laces
Step4. make the second cross and turn around.
Step 5. pass through and pull, then finish.
Chapter 10 modern software engineering [typical users and scenarios] exercises and discussions