What is the importance of a requirements traceability in a product testing?

Tracing requirements from
development to testing verifies that each functional requirement used in
the development matches those established for test cases. This lets testing teams
double-check that all required system features are tested.
  • Interview Candidate
  • 13
  • 5535

Showing Answers 1 - 13 of 13 Answers

somanath nayak

  • Nov 17th, 2005
 

traceability matrix

  Was this answer useful?  Yes

Brunda

  • Dec 14th, 2005
 

Traceability means showing some indication or any kind of match between a test case created and a requirement based on which that particular test case is created.

Traceability Matrix is used to know whether all requirements specified r covered by the test cases u created or not.It's a kind of Measure(matrix).

sireesha

  • Dec 18th, 2005
 

this matrix defines mapping between customer requirements and prepared testcases.

  Was this answer useful?  Yes

thanu

  • Jan 29th, 2006
 

this matrix defines mapping between customer requirements and prepared testcases. this matrix ensures the adequate test coverage. it reveals us whether we covered all customer req or not

  Was this answer useful?  Yes

Prasad Meduri

  • Feb 13th, 2006
 

RTM,Checklist and are equally important in the realistic SDLC.

Kindly check where and when we use them.

Let me brief as per my knowledge!!!!!!

BA/DM/PM reads the BRS and prepares the RTM and checklist to cater all the requirements came from client/BA

Got some time in the middle we need to go thro' all the above( dont leave anyone)... participate in reviews, can't ever freeze???

and prepare respective plans(testplan/QAplan)

We should keep in mind.

cheers

  Was this answer useful?  Yes

RohanAdhikari

  • Feb 17th, 2006
 

- A traceability matrix is created by associating requirements with the work products that satisfy them.

- A traceability matrix is created by associating requirements with the work products that satisfy them. Tests are associated with the requirements on which they are based and the product tested to meet the requirement.

- Traceability ensures completeness, that all lower level requirements come from higher level requirements, and that all higher level requirements are allocated to lower level requirements.

- Traceability is also used to manage change and provides the basis for test planning.

Rohan

  Was this answer useful?  Yes

Joshna

  • Mar 17th, 2006
 

Traceability matrix maps your testcases with yr requitrements requirements.

By having a traceability matrix you ensure that all the customer requirements are tested. So as to ensure that u will have the least bugs in the most important features as per the requirements.. 

  Was this answer useful?  Yes

jayakumar

  • Apr 13th, 2006
 

Requirements traceability is a table to conduct project life cycle activities and work product for project requirements.The matrix extablies the thread that traces the requirements from identification through implementation.The requirement traceability matrix is maintained by project manager and input is given other team member.The requiements tracebility matrix contained the following field like Unique no,requiement soure,requirement statement,frs/srs document,Test specification,verification,program module,modification field,remarks.This makes very important in product testing.

  Was this answer useful?  Yes

sumit4u

  • Jul 6th, 2006
 

Traceability matrix maps your testcases with yr requitrements requirements.

1st.By having a traceability matrix you ensure that all the customer requirements are tested. So as to ensure that u will have the least bugs in the most important features as per the requirements.. 

2nd.If any problem reoccures in system testing or in any of STLC then u can easily trace it back that due to which test case it occueed and can reexecute it .

  Was this answer useful?  Yes

vk1978

  • Apr 17th, 2009
 

Traceability Matrix - In simple words mapping requirements with Test cases


As documents are interdependent the data present in the child document (Test
case document must be based on Parent document (requirements) and whenever we
are facing problem's like developer is not accepting the bug as it is not as per
the design or requirements at that time we can show them the proof by tracing
test cases with requirements


Traceability matrix show how many test cases were written to for a particular
requirements/functionality/module


When we are doing impact analysis Traceability matrix will help us to find
out how many test cases are affected when ever any changes are happened in the
application


Whenever if you face any question against a bug or test cases, then we can show the proof by tracing back to the test cases in the Traceability Matrix document.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions