What Is the Purpose of The Requirement Traceability Matrix

Main purpose of RTM is to developed, tested and deliver so that’s the main usage of particular RTM. It is one of the most important tool in project. this is really help to ensure that all business requirements are covered. It also helps to provide backward and forward traceability so you can mapped to stakeholder requirements.

We first have business requirement it gets mapped to stakeholder requirement. stakeholder requirement is translated to functional requirement, this is basically system requirement what you want in system to do in order to meet stakeholder and business requirement so these are the functional requirement, also non-functional requirement also tagged to corresponding  stakeholder requirement, then we have functional requirement links with design components so this is basically design, what are the thing to required in order to meet functional requirement requirement, then the design gets translated in code which is program line with application is written then that get link with test cases so that all the requirements are tested and ensure everything working fine and ready for delivery.

We look out the example both in waterfall and agile model.

Lets start to look at waterfall model first then we follow RTM for agile model.

A Movie Theatre “XYZ Cinemas” is looking to build a digital channel for allowing their customers to book their movie tickets and make payments online. for the waterfall model document is captured in business requirement document BRD such as BR1, BR2 BR3, for business requirement 1- Sales Department needs digital channel for allowing customers to make payments, so they just talking about online digital channel for customers to make payments for movie ticket they have booked.

Let’s look out the functional requirement, business requirement talk about what? and functional requirement talk about the how? So for example we are considering 2 functional requirement, first one is FR1 – ‘The system shall allow the customers to pay for their movie tickets online using Debit Cards. FR2- The system shall allow the customers to pay for their movie tickets online using Credit Cards. These are 2 functional requirement which is mapped to business requirement. For this functional requirement we need 3 design components, TD1- screen capturing debit card details and validation, TD2- Module for connecting to payment gateway, TD3- Module for displaying the success/ failure of the transaction. these are the 3 design components, then developers will use design to create a program again for the testing part, Test scenario done by the testers again it will be based on functional requirements. the scenario will be check for online payment using debit cards. then test scenario mapped to test cases.

For agile, here BRD is written in EPIC, As a Sales Department We need a digital channel for allowing customers to make payments So that they don’t have to stand in queue to make payments at the ticket counter. Then we breakdown epic in user story as functional requirement user story 1- EPIC as a customer I want to pay, for my tickets online using debit card so that I don’t have to stand in queue to make the payment, in a design phase 3 task are given such as Task 1- screen for capturing the debit card details & validation. Task 2- module for connecting payment gateway, Task3- module for displaying the success? Failure of the transaction. then it goes to developer for program and then test scenario and test cases.