"Quality before Design" read Note 1

"Demand is what people expect. Exploring demand is the process by which people look for expectations. The purpose of exploring demand is to try to find out what people expect from the product, and the demand analysis is actually a pre-design work, and the author

Methodology to introduce requirements analysis. Decades of software development, the results are not very satisfactory, because people always feel that a good product should do more, but the actual is very few. Why? Because we

The use of demand maps, rather than the requirements themselves, is often the reason why we want to explore the purpose of demand. People make exploration maps and eventually get a pattern close enough to the actual demand

Shadow map and express it for a realistic purpose.

The mapping is more like a note or delegate for clear communication, as the example in the book shows, the foolproof cockroach killing apparatus. In order to avoid the problems caused by communication, pay attention to the following points. In the introduction,

The new approach is to be ready to change, especially not to underestimate the difficulties that some people bring to fit the approach or the new symbology. We have to realize that everyone is different, and each mapping method has to be different

approach requires each participant to accept the difference and not try to force people to accept the difference. This is what we need to pay attention to in the needs mapping, each user is different, the idea is

Not the same, we need to understand what the user needs, not speculation, in addition, the demand mapping is not a requirement, he will only be able to reach the user's actual needs, he just expressed the user needs of a party

Expression When making maps, we have to make sure that everyone can understand the requirements map. In the analysis of needs, the user expression will not fully express their own ideas, or there are some needs not

There are expressions, such as the lack of demand, like building a house, the user did not say what material, this is the user to the demand for an imperfect expression, there are some vague words, included small, small and can not

Point out exactly how much. Therefore, we have to explore in order to eliminate ambiguity.

The book introduces the content of the requirements analysis, mainly to introduce a method. In fact, the user needs and the needs of our developers are different, how to better understand the needs of users, need a lot of methods,

Or we need to explore in the future. The book introduces a lot of methods, in favor of us in doing user needs analysis is more accurate analysis of users need, for these methods, more need is we to understand its

Connotation, not to mechanically. The essence of any method is to understand the user's real needs, not what the user wants. Either way, it just makes it easier for us to get closer to what the user needs.

User demand itself is a very rare thing, for developers, often and the actual needs of users have a disagreement. At this time, when communicating with the user, we need to use some of the methods described in the book.

such as decision trees. The main mistake of the designer is that the teacher and apprentice give the client what they need more than they want.

"Quality before Design" read Note 1