Conclusion of when reqirements are covered

Hi guys,

Can any one tell me "How the test engineer conclude that all requirements are covered?"

Bharathi

In my company what we do is

Using Requirement document we will write the test plan(Contains several test cases) and after that we will map the test cases with the requirement document to ensure that all the requirements are covered or not... Then there is a review process for each and every test plan which is more than enough to ensure all the business scenario are covered. This is wat happening in product development company.

But in project oriented company there is possibility that the requirement get changed in later period(not major changes) then we need to update the test plan whenever the requirement changes occurs...

Let me know if this answers your question...

Thanks
Manoj:)

Hi

thanks Manoj.

Bharathi

Hi Bharathi,

Its my pleasure to share my knowledge with u...

If you have to say "Thanks" click on the "Thanks" button on my previous post. This will help me to increase my reputation and also its a feature given in this forum to express thanks.

Thanks
Manoj:)

See, we have SRS.
We have to cover all direct and indirect requirement demanded by customer.
So, it's no enough to cover documented requirement only, you have to think beyond limits.

hi firends,

there is one very important tool for this, RTM(Requirement Tracebility Matrix) and Coverage Matrix
please search for this on net, u will get lot of information.

because its not possible to describe abt it here.

regards,
RSY

Hi,

By preparing Tracebility martrix, we can say all requirements are covered or not.
[QUOTE=bharathi_ark;7384]Hi guys,

Can any one tell me "How the test engineer conclude that all requirements are covered?"

Bharathi[/QUOTE]