Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Chapter 10 of Modern Software Engineering [typical users and scenarios] exercises and discussions

2025-04-10 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

Shulou(Shulou.com)06/03 Report--

1. Discussion: what mistake did the following boss make?

It is not enough to look at the superficial words or actions of the user. We also need to find the motivation behind the user's language actions!

(image source: http://www.weibo.com/funnyshoelace)

two。 Do you want a document?

Some people say that our agile team, like direct face-to-face communication, do not like to do documents and so on, how nice!

In fact, in most cases, leaving a note is very good, compared to the later waste and rework, the original time is really worth it. Look at the following example:

During the self-study class, the dean hurriedly came in and told the monitor, "help me find two people. I want class flowers." at the same time, he made a gesture of hugging flowers on his chest and left. The monitor organized the whole class to vote for the class flower, made a class, made some big data, and finally unified his opinion and selected the two most beautiful MM in the class. So the two MM went to the director shyly, and the director said, "Why are you? where are all the boys? all right, come with me to the logistics. I'm going to move flowers."

It can be seen that face-to-face direct communication is of course agile, but it is still necessary to leave documentation to clarify the needs of users.

3. Users of the ATM interface

The team will design an operating interface for the bank automatic teller machine (ATM), which is placed outside the bank's business hall. How many users do you think will use your interface?

(hint: more than 5 user types)

4. Exercise: you want to write a game. Do you know what kinds of game users there are?

Reference answer: some companies classify players according to their game life cycle characteristics:

Heavy enthusiasts (hard core) players arrange the schedule according to the game

Players with moderate fever arrange game time according to daily life plan.

Casual players only consider games as a pastime when they are free.

These definitions are useful because they allow us to clarify what players expect from the game. For casual users, it is not appropriate for your game to require users to complete a detailed registration or practice phase before starting the game.

5. Don't overdo it.

What happens if the design of the scene driver (scenario driven) goes too far? One day, when everyone was discussing the scene of "Wu Xiaoshi loading goods", Erzhu called out, "stop, don't be busy, I have a scene!" He pulled out a model from under the table with a paper-pasted house, yard, and so on, with several human-shaped wood bumps in the middle. He pointed to one of the wood bumps and said, "this is Wu Xiaoshi Tou. let's just ask him what to do!"

Have you gone too far in your project?

5. Spec writing exercises

How can I write Spec well? In fact, it is not difficult, is to describe one thing clearly, here is an exercise:

If you want to describe to an alien how to tie your shoes, write a "tie your shoes" spec (in English), how do you write it?

First, we need to define the relevant concepts.

-what are the concepts of what is "shoe", "shoe laces", "tied shoe laces", and "untied shoe laces" shoes, shoelace, lacing and unlacing

-Benefit of this feature "tie your shoe laces". What are the advantages of tying shoelaces?

-The goal of the feature? What is the goal of tying shoelaces?

-What does "success" look like? What do you mean, tied up?

-Unambiguous steps to achieve from "untied" to "tied" clear steps to demonstrate the process of tying shoes

This is the spec of lacing shoes written by two students: example 1, example 2.

Second, standardize some assumptions (assumptions), for example, is the shoelace already on the shoe? What kind of shoes do we have to deal with?

Third, to avoid some misunderstandings, the following one is technically "shoelace fastened", but is it "fastened"? Is the settlement successful after beating to death? How many bows do you have to tie?

Fourth, to clarify some boundary conditions, is the following situation a good state of tying shoes or a bad state? This requires PM/Dev/Test to reach a consensus. How tight should the shoelace be? Can the laces of shoes be dragged on the floor?

Fifth, describe the mainstream user / software interaction steps.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 229

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report