The eighth chapter: Demand Analysis
First of all, the software team how to accurately and comprehensively find people for the software a variety of requirements, mainly in the following steps: 1, to obtain and guide the needs 2, analyze and define requirements 3, verify the requirements of 4, in the SOFTWARE Product lifecycle management needs. Next, the SOFTWARE product stakeholders, but also useful to obtain the user needs of the nine user survey methods. Once the requirements are taken, the software team will consider the positioning and prioritization of the functions, followed by plans and estimates to make better demand analysis. This chapter teaches us how to better standardize and conduct software requirements analysis in an orderly manner.
My question is whether the survey method is to choose the actual situation?
The Nineth Chapter: Project manager
It was a matter of course to introduce the project manager, then the second section described the origins of Microsoft PM, as well as PM to do everything except development and testing, and then PM management outside of the code, there are risks. Finally, the PM's ability requirements and tasks are described in detail. This chapter introduces us to the important role of the software team-the project manager.
My question is that there are so many roles in the software team, why should I pick the project manager to say a separate chapter?
Tenth chapter: Typical Users and scenarios
First of all, how to define the typical user and scene, as well as the typical user's value, template, the template of the scene, and then there is the "use case" of the requirements analysis tool, the following specification introduced the functional specifications and templates and technical specifications, and finally said the function-driven design. This chapter teaches us to lock down a typical user group, which helps us to find better users.
My question is the use case good or the typical character, the scene?
Chapter 8, 9 and 10 of the Law of construction