"Quest for demand" reading notes Part1

"This book is the cornerstone of modern demand technology, and we strongly recommend that demand engineers read this book. "This is a sentence from UML China written in the Book of Quest for demand, which strongly appreciates the value of this book." This month I also began to read the book, and now I have read the first article of this book, the book also has a preliminary understanding.

The book exploring needs focuses on ways to reduce the ambiguity of demand, emphasizing the eventual reduction of ambiguity through continuous refinement of demand. Ambiguity, which describes the degree of unclear clarity. And for software development, in fact, there are two aspects of ambiguity, one is the ambiguity of the implementation of the book, and the other is the ambiguity of the goal, that the same needs may be different objectives, and those potential targets directly affect the future evolution of the software direction. If we want to construct a software, that can be very good to meet the user's current needs, but also can make us more convenient to expand the function of the software, more convenient to achieve the evolution of the software, then in both respects to reduce ambiguity, it can be very good to help us achieve the goal. Many times, the difference comes from our own strong ability, because we have enough ability to do diversity, and these diversity are reflected in their own characteristics, so we will have so many different choices. The author is very good for our analysis of the customer's psychological and demand collection personnel psychology, from the perspective of human nature to make recommendations, so that these recommendations have a strong pertinence and feasibility. When we collect the demand, it is very necessary to grasp the customer's psychology, and reasonably avoid some psychological misunderstanding. Demand is people's expectation, exploring demand is people's expectation process, the purpose of exploring demand is to try to find out people's expectation of product.

The first part of the book focuses on the method of acquiring the requirements in the early stages of software development, mainly talking about what is needed and going to the people in a lot of buying software without clearly over the programmer what they are doing and resulting in dissatisfaction with the software. The author proposes the concept of software acquisition for this problem. In order to make the needs analysis work better, the process of the human factors, and replaced by a set of methodologies, the process of fully automated methods, such methods will completely abandon the human factor throughout the development process, and in the author's actual development process to verify that this method is not feasible, so the proposed methodology is not enough. Whenever you use a tool that ignores human factors, you can't describe your needs perfectly, and it creates ambiguity, and ambiguity brings different interpretations of the same needs, and the corresponding examples help us understand the ambiguity of demand. At the same time, ambiguity comes from the same arrival, so find the ambiguity in the need to locate its source. The source of ambiguity is described by the example of convergent design process presentation. The use of a reliable but untrue direct problem will depend on the direct question, as a designer, preferably with direct questioning, direct observation and regular interviewing skills, a decision tree model is a tool used to compensate for direct problems. Anyone who raises or asks a direct question should understand the limitations of human beings and know other ways to get information. This part of the question by enumerating some of the requirements, such as the ambiguity of the requirements and the need to get the unreal demand through the problem, has given me a lot of knowledge. Although some of the recent new development ideas and the ideas mentioned in this book have some deviations, but in a lot of theoretical knowledge of the inspiration to us is very large, in the author's case analysis let us learn too much knowledge, in the analysis of needs to understand the quality of a demand analyst. Demand is a shield of the underlying implementation of the operation, it realizes the transformation of the state, the user's needs are the user's personal view of the best solution to their own goals, they can not or unwilling to complete the parts, goals and solutions are relative. Since demand is defined in this way, the way to reduce ambiguity is as written in the book, and when we find that there is a greater ambiguity, we reduce it by means of communication.

Reading the first part of the book, this section uses a large number of examples to describe the issues to be addressed in each chapter, in which I clearly understand the ambiguity of the requirements and understand the analytical process of these issues. Some of the ways to solve this kind of problem, of course, the idea of this book I still have a lot of do not understand, in the reading process in the author's thoughts to learn a lot, but there is no understanding of the place. This book has too many good demand aspects of thought, in reading to give me a lot of help, hope in the future study work can put this knowledge into practice.

Discovery needs reading notes Part1