Many people will encounter demand analysis, but there are not many people who can clearly explain the complete process, and there are fewer people who can truly achieve integration of knowledge and practice according to the process. However, many people who have been working for many years are not doing well in demand analysis. Of course, the theory is applied to reality on the one hand. On the other hand, you should understand the theory and apply it to reality, and use practical experience in improving and guiding your own theory, instead of giving up the theory because it is not a reality. Wu guangchao
Link: https://www.zhihu.com/question/20407032/answer/262676847
1. What is demand analysis?
In system engineering and software engineering,
Requirement AnalysisIt refers to all the work to be done when creating a new or changing an existing system or product to determine the purpose, scope, definition, and function of the new system. -- Wikipedia
2. workflow of Requirement Analysis:
- Request retrieval: actively or passively obtain the request from the requester.
Key points: guide the demand side to describe as accurate, detailed, and executable requirements as much as possible.
- Handling requirements: Analyze and sort out the obtained requirements, analyze and sort out the requirement reports from the developer's perspective, and obtain the confirmation from the requirement requestor.
Key points: In the process of demand processing, it is effective to communicate with the request requestor repeatedly for confirmation.
- Propose solutions: propose feasible solutions based on the confirmed requirements and review them.
Key points: the solution should take cost, risks, and difficulty of solution into account. Multiple solutions should be proposed for review.
- Sorting requirements: sort the requirements by priority based on the actual situation, and determine the time and cost of the demand.
Key points: The measurement angle includes the frequency of occurrence, number of users, difficulty of solution, benefits, degree of urgency, and other factors. Different factors have different effects on products in different environments.
- Report writing: Write requirement analysis reports and distribute execution tasks.
Important: contains all the content of all previous processes, and contains the specific content of solution execution.
- Monitoring execution: tracks the actual implementation process and results of the solution.
Key points: the monitoring content includes not only quality, but also time progress, actual results of the solution, and expected comparison.
- REPLAY: based on the actual results, compare and analyze the advantages and disadvantages of the previous process, and summarize the results.
3. Tools and methodologies used in the demand analysis process:
- Requirement retrieval:
- Observation: By observing user behaviors, sort out requirements
- Practical experience: organize the requirements in the process of actually assuming a user role to participate in the behavior
- Questionnaire: Make a questionnaire
- Interview: face-to-face dialog interviews are conducted to obtain requirements through communication
- Demand research meeting: convene relevant personnel to communicate with each other and determine the requirements.
- Analysis of competing products: This product dynamically and dynamically updates the product to discover the demand.
- User feedback: Obtain the requirement through feedback from the user's comments, complaints, phone calls, and other channels.
- Handling requirements:
- Screening criteria: establishes key information and invalid information. For example, the bug feedback and complaints are important. If the class information is regarded as invalid, ignore it directly.
- Design differentiation type: Information is differentiated to facilitate subsequent analysis. For example, each requirement is added with a field for category determination. The content is invalid, bug, user experience, complaints, and so on.
- Use a filtering tool for Batch Processing: excel.
- Sorting requirement stage:
- Quantitative computing: Develops priority sorting rules as needed. Each dimension is quantified and scored separately. For example, the analysis dimensions include the number of users, the frequency of use, the difficulty of development, and the benefits. Each dimension is evaluated separately. Obtain the quantified requirement result.
- Dimension analysis:
- Impact analysis: focuses on the number of users and the frequency of use.
- Rate of Return Analysis: focuses on the Cost and Benefit values.
- Report writing:
- Mind Map + structured statement
4. Experience:
Demand analysis requires two dimensions: rational and perceptual knowledge. On the one hand, we should master the tools and methods of rational analysis to ensure that there will be no major mistakes or leaks during pot preparation. On the other hand, we need to use empathy and high awareness to understand the user's emotional fluctuations in the details of the specific implementation.
Of course, just as you can never understand a person,It is impossible to have a perfect Demand AnalysisAnd there is no perfect solution. However, we have made these efforts to keep our output closer to perfection ".
In general, requirement analysis is to understand your users, the scenarios where users are located, the problems encountered by users, and help users solve them.
How to analyze requirements
