Quality Testing

Quality is delighting customers

Interview question :

How do you analyse/break the requirements......?

Views: 83

Reply to This

Replies to This Discussion

Hi Balur,

Here we go,

1) Read the requirement 1-3 times
2) Understand the message in them
3) Identify the Business Rules, constraints, Flow, Navigation, Dependencies
4) Refer mock-ups, related documents(could be from external systems)
5) Communicate the GAP(clarifications, doubts, thoughts or ideas)
6) Derive the functional points

thanks abu,

Is my understanding is right,..Please post u commnets/suggestion on this.

Requirements are broken into some small functionalities
Functionalities are smaller usecases
Usecasese are broker into test cases

All the above steps are done to cover the requirement fully functional.

can u share some template on this
In our company, we do like following:

When we first get the requirement from client, they will be just an overview type so we do some meetings with them and try to get detailed requirements via discussion with client and then with our development team. After this, we refer to the existing system if there is any and will try to get some more detailed idea about requirements. Then we prepare requirements understanding document and send that to client. Client will go through that and will either approve that or will give their ideas or suggestions about the requirement mentioned in the document. We continue this cycle until the document is final. Then we prepare SRS and send that to client for confirmation. Once this is confirmed then we prepare test cases on the basis of the SRS.

Let me know if you have any queries regarding this process. And also correct me if I am wrong on something here.



TTWT Magazine





© 2021   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service