Traceability in a professional way-How to create a BRTM and RTM?
The simplest way to do this is to use an excel file, however, requirement management software is an efficient way to create any traceability. Traceability is immediately created in such software as soon as you pass both requirements and comparable project objects.
Creating a BRTM in Excel:
Start an excel file and follow the steps below:
- It is important to mention the Project Name, Project ID , Date and Name of Author in the beginning on the page
- In the column A, list down all the requirement IDs
- In column B, list down all the business requirements corresponding to the requirement ID
- In column C, provide the requirements type. It can be functional or non- functional.
- In column D, provide the description of the requirement.
- In the column E, list the corresponding High Level Design requirements or the project elements against which you want to compare the requirements. It can be business objectives or other system requirements
- In the column F, provide the corresponding ID of the High Level requirement (project element from step 6)
- Requirements can be compared against any higher level project design or objectives which can be either of these: Business Objective, SLA, Higher Level BR, Domain Level BR, and Higher Level SR. So, you can add as many columns as you like to create your BRTM depending on what you are comparing your requirements against.
- The second last column can be a verification column to confirm if the requirements are traced back or not. This column is normally Yes/No answer column.
- The last column can be Comments/ Attachment column to provide additional comments or reference documents.
Creating a RTM in Excel:
RTM is no more than the extended version of BRTM. In the RTM requirements are compared against Higher Level SR, Design Level SR, Test Scenario and Test Cases. Follow the steps below:
- It is important to mention the Project Name, Project ID , Date and Name of Author in the beginning on the page
- In the column A, list down all the requirement IDs
- In column B, list down all the business requirements corresponding to the requirement ID
- In column C, provide the requirements type. It can be functional or non- functional.
- In column D, provide the description of the requirement.
- In the column E, list the corresponding Higher Level System Requirements.
- In the column F, provide the corresponding ID of Higher Level System Requirements
- In the column G, list the corresponding Design Level System Requirements
- In the column H, provide the corresponding ID of Design Level System Requirements
- In the column I, list the corresponding Test Scenario
- In the column J, provide the corresponding ID of Test Scenario
- In the column K, list the corresponding Test Case/ Test script
- In the column L, provide the corresponding ID of Test case / Test Script
- In the column M, can be a verification column to confirm if the requirements are traced back or not. This column is normally Yes/No answer column.
- The last column can be Comments/ Attachment column to provide additional comments or reference documents.
My Other Blogs:
I really liked your blog post.Much thanks again. Awesome.
ReplyDeleteweb methods training
web methods online training