KEMBAR78
Requirement Traceability: Aamir Anwar | PDF | Software Testing | Information Age
Scribd
Upload
124 views13 pages

Requirement Traceability: Aamir Anwar

The document discusses requirement traceability matrices (RTMs), which map user requirements to test cases to ensure all functionality is tested. It describes forward traceability, which maps requirements to test cases, backward traceability, which maps test cases to requirements, and bi-directional traceability. It provides steps for creating an RTM, including identifying the technical requirement and business requirement each test case verifies. The RTM links requirements at each level to demonstrate full test coverage.

Uploaded by

Shabab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
124 views13 pages

Requirement Traceability: Aamir Anwar

The document discusses requirement traceability matrices (RTMs), which map user requirements to test cases to ensure all functionality is tested. It describes forward traceability, which maps requirements to test cases, backward traceability, which maps test cases to requirements, and bi-directional traceability. It provides steps for creating an RTM, including identifying the technical requirement and business requirement each test case verifies. The RTM links requirements at each level to demonstrate full test coverage.

Uploaded by

Shabab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Requirement Traceability

Lecture 11

Aamir Anwar
Lecturer CS & IT
University of Lahore, Islamabad Campus
Requirement Traceability Matrix
• Requirement Traceability Matrix or RTM captures all requirements proposed
by the client or software 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
doing Software testing.
Types of Traceability
• 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 traceability: It is used to ensure whether the current
product remains on the right track. The purpose behind this type of
traceability 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 traceability ( Forward+Backward): This traceability matrix
ensures that all requirements are covered by test cases
Forward and Backward Traceability
Traceability Matrix
How to create Requirement Traceability Matrix:

• On the basis of Business Requirement Document (BRD) and Technical


Requirement Document (TRD), testers start writing test cases.
• Here the scenario is that the customer should be able to login to banking
website with the correct password and user#id while manager should be
able to login to the website through customer login page.
Traceability Matrix
Traceability Matrix
• While the below table is our Technical Requirement Document (TRD).
• QA teams do not document the BRD and TRD. Also some companies
use Function Requirement Documents (FRD) which are similar to Technical
Requirement Document but the process of creating Traceability Matrix
remains the same.
Traceability Matrix
• Step 1: Test case is
Traceability Matrix
• Step 2: Identify the Technical Requirement that this test
case is verifying. For our test case, the technical
requirement is T94 is being verified.
Traceability Matrix

• Step 3: Note this Technical Requirement (T94) in the


Test Case.
Traceability Matrix

• Step 4: Identify the Business Requirement for which


this TR (Technical Requirement-T94) is defined
Traceability Matrix

• Step 5: Note the BR (Business Requirement) in Test


Case
Traceability Matrix
Step 6: Do above for all Test Cases. Later Extract the First 3 Columns from
your Test Suite. RTM in testing is Ready!

You might also like