How to Create Requirements Trace-ability Matrix (RTM)

By -

What is Traceability Matrix?(RTM)

A traceability matrix is a document that co-relates any two-baseline documents that require a many-to-many relationship to check the completeness of the relationship.
It is used to track the requirements and to check the current project requirements are met.

What is RTM (Requirement Traceability Matrix)?

Requirement Traceability Matrix or RTM captures all requirements proposed by the client or development team and their traceability in a single document delivered at the conclusion of the life-cycle.
In other words, it is a document that maps and traces user requirement with test cases. The main purpose of Requirement Traceability Matrix is to see that all test cases are covered so that no functionality should miss while testing.
Requirement Traceability Matrix – Parameters include
  • Requirement ID
  • Risks
  • Requirement Type and Description
  • Trace to design specification
  • Unit test cases
  • Integration test cases
  • System test cases
  • User acceptance test cases
  • Trace to test script

Types of Traceability Test Matrix

  • Forward traceability: This matrix is used to check whether the project progresses in the desired direction and for the right product. It makes sure that each requirement is applied to the product and that each requirement is tested thoroughly. It maps requirements to test cases.

  • Backward or reverse tractability: It is used to ensure whether the current product remains on the right track. The purpose behind this type of tractability is to verify that we are not expanding the scope of the project by adding code, design elements, test or other work that is not specified in the requirements. It maps test cases to requirements.

  • Bi-directional tractability ( Forward+Backward): This tractability metrics ensures that all requirements are covered by test cases. It analyzes the impact of a change in requirements affected by the defect in a work product and vice versa.  

Advantage of Requirement Traceability Matrix

  • It confirms 100% test coverage
  • It highlights any requirements missing or document inconsistencies
  • It shows the overall defects or execution status with a focus on business requirements
  • It helps in analyzing or estimating the impact on the QA team's work with respect to revisiting or re-working on the test cases

Comments

Post a Comment

Popular posts from this blog

Handling Dynamic Web Tables Using Selenium WebDriver

By -
Image
There are two types of HTML tables published on the web- Static tables : Data is static i.e. Number of rows and columns are fixed. Dynamic tables : Data is dynamic i.e. Number of rows and columns are NOT fixed.Handling static table is easy, but dynamic table is a little bit difficult as rows and columns are not constant. Using X-Path to Locate Web Table Elements Before we locate web element, first let's understands- What is a web element? Web elements are nothing but HTML elements like textbox, dropdowns radio buttons, submit buttons, etc. These HTML elements are written with  start  tag and ends with an  end  tag. For Example, <p>  My First HTML Document </p>. Steps for getting X-path of web element that we want to locate. Step 1)  In Chrome, Go to  http://money.rediff.com/gainers/bsc/daily/groupa Step 2)  Right click on web element whose x-path is to be fetched. In our case, right click on "Company" Se...
Read more

Importance of testng.xml file

By -
In a Selenium TestNG project, we use  testng.xml  file to configure the complete test suite in a single file. Some of the features are as follows. testng.xml file allows to include or exclude the execution of test methods and test groups It allows to pass parameters to the test cases Allows to add group dependencies Allows to add priorities to the test cases Allows to configure parallel execution of test cases Allows to parameterize the test cases 7. How to pass parameter through  testng.xml  file to a test case? We could define the parameters in the  testng.xml  file and then reference those parameters in the source files. Create a java test class, say,  ParameterizedTest. java  and add a test method say  parameterizedTest()  to the test class. This method takes a string as input parameter. Add the annotation @Parameters(“browser”) to this method. 1 2 3 4 5 6 7 8 9 10 11 12 // ...
Read more

Read it out for TESTNG before going for an iterview

By -
How to run a group of test cases using TestNG? TestNG allows you to perform sophisticated groupings of test methods. Not only can you declare that methods belong to groups, but you can also specify groups that contain other groups. Then TestNG can be invoked and asked to include a certain set of groups (or regular expressions) while excluding another set.  This gives you maximum flexibility in how you partition your tests and doesn’t require you to recompile anything if you want to run two different sets of tests back to back. Groups are specified in your testng.xml file and can be found either under the <test> or <suite> tag. Groups specified in the <suite> tag apply to all the <test> tags underneath. @Test (groups = { "smokeTest", "functionalTest" }) public void loginTest(){ System.out.println("Logged in successfully"); }   How to create Group of Groups in TestNG? Groups can also inc...
Read more