"Mastering the requirements process" Reading Two Notes

  Read the last chapter, that this will continue to start from the fourth chapter.

  The fourth chapter, said that in terms of business use cases of content, the author tells in this regard is relatively small, the main content is how to determine the appropriate part of the product (using business events as a starting point) and how to determine the best product to be constructed. , The authors explain some basic work in this chapter, he says, we must first understand the work that we are faced with work to do, and then go to setting conditions and their scope of application. This reminds me of some of the knowledge we have learned this semester's course in this case the software requirements and analysis. In the classroom, the teacher will constantly put us to draw down the scope of work chart, he meant exactly the same and the author, our ultimate goal is a more detailed understanding of the needs of users. Figure drawing down the scope of work requirements, is in the process of drawing, look nowhere to go in the flow, so that we can check the problem and users are ignored. In other words, "research needs is active, users can accurately describe his task at work, requirements analyst to provide continuous commentary, with the commencement of observation and interpretation of the work, the analyst can outline every model task, and how they are connected to the data stream. after the model is set up, an analyst feedback to the user in order to obtain confirmation, and ask questions. "

  In the fifth chapter, the author describes how we should gather to discuss the needs of our find, extract and create skills needs. First, I checked online examples and explanation regarding network requirements, the Baidu forum had this to say: "From the content analysis point of view, the main network should include requirements analysis, structural analysis and network planning and network scalability analysis of three a content. "this explanation is consistent with the author's. And, also author of the book made a detailed example of the network needs to explain: "When out fishing, more often recruit those who get fish than he originally wanted, and experienced fishermen you can know where the net and throw anything except fish. so, the quest demand can also get this effect. experienced analysts can eliminate demand and retention have been recruited to the demand, they really want to get, and get also want to get more than their beginning. At the same time the author also introduces some tips network requirements. for example, to consider the user, because some users have some needs are not aware of or did not think demand will be realized, it is necessary to consider to them. the second is sure to enlist all the requirements, if found late, it will have a high price. "that's true role in the quest for the needs of. Snare demand is to be seen, like us at any one thing in particular is in the process of learning, we must continue to observe, but also to continue to ask, when to follow the guidance in person or to be made Inquirer after a lot of things, we may also understand the nature of the content of the work. "Interpretation is part of the discovery of the nature of the work, the nature of the system. Represents the fundamental reason for the existence of the system. For each business event, there is a response efforts made, each business event has his head, and other interested people together, build some scenarios to show the action needed to make the right response to business events. "

  Master the requirements process is a lot of knowledge, not what we imagined just a simple recording as simple, and the accumulation of experience is essential, with a keen sense of smell and successful practice is good at finding the root.

Guess you like

Origin www.cnblogs.com/yandashan666/p/12128740.html