Chapter 1 Preface
Demand investigation is for the need for the instructions to do early work, it can be said that the specification says that it is from or extracted from a demand research table.
Demand research is to understand what kind of procedure for people who do actually work in the real world, and then develop these needs to develop detail to develop by the design department, and then sell them to users.
User: System analyst
Chapter 2 Preparation
2. Determine the tool
Nothing tools are good or bad problems, the problem is how the key is how to use them, no matter what tool is just an auxiliary tool, nor does it generate tools. The tool selection requirement is the tool that is familiar (this group), can't be a new fashionable tool and you know very little about it, and most of the time is on the learning tool, not to use it for you. The tool is preferably also required to be ordinary, because the issue to be considered.
2.2. What should I do if I want to do?
If the project is the industry (professional) of the industry you don't know, there is best to have experts ---- End users do this expert is the best, at least you know this major, don't want you to become Expert, but at least knows certain expertise (minimum professional vocabulary you have to know), otherwise you don't even know what questions or how to ask them, even what people don't know. The corresponding professional information is necessary, minimizing professional entry books and corresponding information, and requires more deeper information. Of course, some experts have another matter. If the difficulty of the industry is not very large, you can get into the industry's self-learning to understand the industry in a short time, maybe you do not need an expert, otherwise the expert is necessary.
2.3. Establishing a design environment must establish a specialized design environment to serve this project, perform certain resource allocation, and make the necessary document management.
2.4. Really understand yourself and users
Those who may be clear to know that they can do it, those that they can't do. For processing methods that cannot be done, such as rejection, sacking, etc., those who want to do it.
2.5. List the personnel allocation table and all tools list
Clarify the tool unified project documentation used by the project staff to unify the project file template other resource list (information, related websites, inquiry ...)
Chapter 3
3.1. Collection requirements are required to get a demand manual
Note: Although it is finally necessary to be a computer solution, the focus of our focus so far is in the corresponding field. Remember that there is no computer in the computer, if you write a accounting software, a accountant should clearly understand the question guide for the accounting requirements of the programmer, do not be too official. As long as the description can express what you want to do, you can talk to another person. When the customer or corresponding personnel understand the problem, be sure to have a habit of notes, talk about a few hours, many details can't remember.
3.2. Organize, inspect and refine demand instructions
For customers need to make a lot of information from the user, it will get a lot of information from the user. If you don't travel, you can't make reasonable analysis, you can use it, select, useless, useless, and unimpleme functions for users. Speaking that he can tell the many features he want, but the relationship between these functions is sometimes clear, but for many users who want to implement his previous function through a computer or new system, the new demand he proposed at this time. The feasibility and the relationship between other modules are already unclear, so for analysts, to distinguish useful features and useless features and optional functions from the user's needs, such as unable functions. Users give up. Don't ignore obvious error users do not often mention what he needs, and these things are very basic, to refine inspections must pay attention to this problem. What you think is not to pay attention to the self-considering of the system analyst, for a industry, some rules can not be the most reasonable, but it is as and used, so for each non-clear Determined demand, to be approved by professionals. Unless you are an expert. 3.3. Improve the first first demand in analyzing, refinement must have unclear and uncertain, then put a problem detailed inquiry table, organize the problem of discovery, list unknown, Can be backed below format
Inquiry: Question: List of business unclear issues (business descriptions are not clear): 1 .... What is the meaning? 2 .... What is the relationship with XX?
A variety of options can be listed (please choose): 1 ... There are many possibilities, then we now use A ... b ...... c .... D ...
Submit the user inquiries, analyze the demand according to feedback, this step can repeat multiple times, ultimately understand demand, determine demand instructions
3.4. Audit demand
Self-examination puts it reasonably from the user's perspective, whether it can improve efficiency, can achieve the purpose, is it a completely managed by the user to evaluate whether the needs of your listed by users have reached the user requirements (number of users 1 -3 people, there is no benefit more. Dressing process, ultimately through audit completion requirements
