当前位置:网站首页>[beauty of software engineering - column notes] 17 | what is the need analysis? How to analyze?
[beauty of software engineering - column notes] 17 | what is the need analysis? How to analyze?
2022-07-29 06:20:00 【if...else...】
List of articles
Column information
Columnist : The treasure jade
Column publishing platform : Geek time
primary coverage
It can be said that demand is the source of the whole product , Therefore, the result of demand analysis often determines the success or failure of products . If you don't grasp customer needs correctly , You may make a mistake , Step by step in the wrong !
One What is demand ?
The user needs It was proposed by the user , Expect to meet the requirements of their own needs .
Product needs After analyzing and refining the real needs of users , Proposed solutions in line with product positioning .
Two What needs analysis is to analyze ?
In fact, the analysis of user needs , Not an action , It's a process . Demand analysis , It is to refine and analyze user needs , The process of finally forming product requirements .
The demand analysis process for each user's needs , Need to go through Three steps :
- Mining real needs
- Propose solutions
- Screening and validation scheme
3、 ... and How to do demand analysis ?
And the user needs of software projects , Never single , But a series of requirements , So for software project demand analysis , You also need to add the steps of collection and sorting . The whole process is iterative , As shown below :
- Collect requirements : Collect and sort out user needs ;
- Analyze requirements : Analyze the needs , Mining the real needs of users ;
- Needs assessment : Filter out infeasible requirements ;
- Demand for design : Propose solutions to user needs , Design into a product plan ;
- Validation requirements : Verify whether the scheme is feasible .
Four Other excerpts
- The needs of most users , Are not necessarily their real needs , We need to see the essence through the phenomenon , To explore the real needs behind it .
- In real projects , Most people's needs analysis is incorrect , It's because the real needs of users are not mined .
- We know the target users , Its usage scenarios and problems to be solved , It can be combined with product positioning , Propose corresponding solutions .
- After choosing the plan , The scheme also needs to be verified , To ensure that the solution can meet the needs of users .
- In the traditional waterfall model , After selecting the scheme , Will be written into product design documents , Follow the corresponding review process , The design will be carried out after the review 、 Development and testing , After the test is completed, the customer will accept it . Agile development , During the whole development process , Every iteration or key milestone , It also requires the customer to conduct acceptance .
summary
Demand analysis , It is a process of transforming user requirements into product requirements . Do a good job in the analysis of user needs , We need to find out the real needs hidden behind user needs , We should also propose solutions to the real needs of users , Whether the final verification scheme can meet the needs of users .
Demand is the source of the whole product , The reason why many software projects fail is that they don't do a good job of requirement analysis , A lot of waste in software also comes from rework caused by not thinking clearly about requirements . It is very important for a software project to do a good job of requirement analysis .
Do a good job in the demand analysis of software projects , We need to do a good job in the collection and sorting of requirements , Then make a scientific analysis of the collected needs , Evaluate whether it is feasible and prioritize , Design feasible requirements , Finally, we need to verify whether the design results meet the requirements .
边栏推荐
猜你喜欢
【软件工程之美 - 专栏笔记】“一问一答”第2期 | 30个软件开发常见问题解决策略
LeetCode #977.有序数组的平方
FPGA based: moving target detection (schematic + source code + hardware selection, available)
【软件工程之美 - 专栏笔记】21 | 架构设计:普通程序员也能实现复杂系统?
STM32 检测信号频率
SimpleFOC调参1-力矩控制
DP1332E多协议高度集成非接触式读写芯片
Ml self study notes 5
Ml9 self study notes
【软件工程之美 - 专栏笔记】16 | 怎样才能写好项目文档?
随机推荐
Eight sorts ----------- bubble sort
抽象封装继承多态
八大排序-----------------堆排序
#6898 变幻的矩阵 题解
网络爬虫
LeetCode #13. 罗马数字转整数
DP1332E 多协议高度集成非接触式读写芯片
【软件工程之美 - 专栏笔记】29 | 自动化测试:如何把Bug杀死在摇篮里?
【软件工程之美 - 专栏笔记】14 | 项目管理工具:一切管理问题,都应思考能否通过工具解决
【RoboMaster】A板接收JY-ME01角度传感器数据--modebus协议&CRC软件校验
LeetCode #344.反转字符串
【软件工程之美 - 专栏笔记】16 | 怎样才能写好项目文档?
Eight sorts ------------- heap sort
STM32 串口乱码
【软件工程之美 - 专栏笔记】13 | 白天开会,加班写代码的节奏怎么破?
#9196 肿瘤面积 题解
八大排序-----------快速排序
【软件工程之美 - 专栏笔记】17 | 需求分析到底要分析什么?怎么分析?
爬取表情包
LeetCode #7.整数反转