1. What are software requirements?
1. Business requirements: the high-level target requirements of the organization or customer for the system and product, which are generally described in the project view and scope document
2. User requirements: describe the tasks that users must complete to use the product
3. Functional requirements: software functions that developers must implement
4. Non-functional requirements: follow certain standards, specifications, contracts, performance requirements, quality attributes
The position of the need for clarification
1) The beginning of the project
2) The first collective discussion after the formation of the R&D team
3) An important part of quality assurance
3. What does the requirements clarification test need to do?
Ask the product manager to explain things that are unreasonable and difficult to understand and that affect testing
Fourth, the status quo of the requirements document
1. No need or one sentence need
Go to ask, everyone coordinates, negotiates and communicates, and after everyone answers the questions, write a brief description of the needs, and then send it to the group or email to confirm, and if there is a problem, make corrections until there is no problem
2. There are requirements documents but very rough
1) If there is enough time, and developers and demanders are willing to cooperate, let them cooperate to improve the document
2) When time is tight and one party is unwilling to cooperate, mark the unclear points according to the existing documents, ask them clearly, and make a mark (red) to sort out
3. Detailed requirements document
1) Sort out the requirements
2) It is not clear to find a leader/need to communicate and confirm
For these three, you can refer to
1) I don't understand the question - sorting - email confirmation
2) Discuss - throw ambiguity - confirm
3) User perspective, industry experience to judge whether it is reasonable, and tap potential demand
Five, the main points of the needs assessment
1) Ask why
2) What difficulties are you currently encountering?
3) How is it done now?
6. As a tester, how to do requirements review?
1) Read the requirements carefully first
2) Sort out the unreasonable points
3) Find the points that have not been quantified, and quantify as much as possible in the review
4) Excavate hidden needs based on explicit needs
references:
without
Remark:
If there is any infringement, please contact by email, I am sorry.
This is only for learning personal notes, and if there is any reprint, please indicate the source.
Contact Email: [email protected]
Learn to test the penguin group together (chat, water group, do not disturb advertising): 826471103