To do software development for all people will experience demand for research work. Recently went to the field to do a needs survey, a good tidy up before departure to work thinking, and recorded as follows:
First, the demand for research significance Needless to say, is too important. Project's success is largely a pre-research work has been well prepared. I believe that no one will oppose. It is the needs analysis and requirements specification of the precondition
Second, the principle research
1, in descending (or down), from coarse to fine (questionable, may not be the right way)
2, different levels of users to gather different levels of user needs
3, polite exchanges, detailed records, a comprehensive analysis of repeated examination of 16-character principle
Third, the various stages of research
1, to prepare (1), collect all kinds of existing resources, an overview of some of the user's business requirements. Sketched out the broad contours of the project (2), understand their user base. And their various business modules with the initial pairing, the user is the object of their research.
(3), prepare some documentation templates, such as: questionnaires, communication and minutes, meeting minutes, research proposal is required to show analysis, business requirements specification, requirements confirmation, etc. (4), prepared research plan, and submitted to audit user units can be regarded as a pre-appointment to visit it, to not be a no answer, face can be embarrassing ah.
2, the research process:
(1), buy a ticket, went to the site (a little nonsense), and the user unit to determine the specific arrangements for the research plan (2), and fixed the user interface unit to determine who is responsible for coordinating the implementation of the research plan (3), scheduled to start research, and communication in the process generating the minutes, as the basis for generating the initial requirements specification (4), self-assessment of the requirements specification, identify the demand is not yet clear, the formation of detailed questions questionnaires, distributed to users, for research into the next step.
(5) Repeat step 3 and 4 will clarify all the problems (6), amendments and the formation of a mature requirements specification, to pay user review. In through the audit, do not forget to please the user needs to sign the confirmation
(From the Internet to collect research flow chart, do not know the original author, and thank)
Fourth, the input and output:
1, various types of pre-raw data, such as contracts, construction programs
2, various types of document templates
3, the demand for research project (and perhaps also by the researchers write, but it is the premise of research, it also serves as a digital input)
1, the user documentation provided by the related resources
2, communication Minutes
4, needs analysis reports
5, requirements specification
6, needs assessment records
7, needs confirmation
V. Summary and research needs of the development team's first direct contact with the user. There are many places to pay attention to nodules. Different projects, different users in the process there will be many differences, to adjust the plan and the actual research methods. Finally, there will be differences in output, for example, needs confirmation often dream team. But the reality is that many users will not sign it!