Business requirements: focus on whether the system meets business requirements
User needs: Pay attention to whether the system meets user habits
Functional requirements: Pay attention to whether the system meets the functional requirements, such as the input and output of the system
No demand: refer to similar products already on the market
Fuzzy requirements: collect and sort out existing requirements, confirm with product managers one by one, and refer to the realization of pain-type products
Why do we do needs analysis?
To successfully do a project, we need to understand the test scale, complexity and possible risks, all of which need to have detailed test requirements to understand.
Difficulties of requirements:
1. Difficulties in communication between users and developers
2. The needs of users are dynamically changing
3. The cost of changing different shortening systems in the life cycle increases nonlinearly
4. The current architecture cannot satisfy
5. Analysts and customers misunderstood
Importance of needs:
If the previous requirements cannot be controlled, full functional coverage cannot be achieved in the later stage, and frequent changes in requirements will cause delays in the entire operation period of the project.
Results of no needs analysis
Waste of time, failure to meet customer needs, low customer satisfaction, etc.
How to do needs analysis?
1. After getting the requirements, read the requirements first, and then have an overall understanding of the background of the requirements to be done, and record your doubts in the process of understanding.
2. Analyze whether the demand is reasonable. You cannot judge whether the demand is reasonable only by how the system is implemented. It mainly includes two aspects: first, to meet customer needs; second, on the basis of the original system, try to reduce the change cost
3. Determine the scope and priority of the test: determine all the test points involved in this requirement, and then analyze the priority of the test scope through analysis
4. Refine the test points and determine the test method
5. Determine which job testers can step in early
6. Check for omissions