TEST CASE

REQUIREMENTS/USE
CASE TRACEABILTY
MATRIX

VERSION 1.0
 Template Instructions:
Instructions for completing this template are encased in [ ] and the text is italicized
and bolded.
Examples are provided as a guideline to the type of sample information presented in
each section and the text is italicized.
Boilerplate standard language for each section is written in the document font and may
be used or modified, as necessary.
Text within << >> is to be replaced with pertinent project information.

DOCUMENT HISTORY
DOCUMENT APPROVAL HISTORY
Prepared By
Reviewed By

<< The project's designated Test Designer, Test Lead, or Test Manager is
Approved By responsible for reviewing and approving the matrix contents to ensure test
traceability. Insert name(s) here and have them sign it. >>

DOCUMENT REVISION HISTORY

Document
Date Version Revision Description Author
2/6/2015 1.0 Initial Version J. Fong

Page i
1. INTRODUCTION

Requirements Traceability is the process of ensuring that one or more test cases address each requirement. Requirements Traceability is a high-level measure of
coverage and particularly important during User Acceptance Testing. The Test Manager uses Requirements Traceability to measure test effectiveness during a
test phase. Requirements Traceability is usually managed in a matrix, while some projects use a specialized commercial tool. Traceabilty plays the following
roles:
1) Verifies that the system fulfills all requirements that the user requested.
2) Verifies that the system does only what was requested.
3) Facilitates Change Management - when a requirement changes, Requirements Traceability will assist the Project Manager and Test Manager with
a tool to determine which requirements and test cases are impacted by the proposed change.

2. TEST CASE/REQUIREMENTS TRACEABILITY MATRIX

TEST CASE/REQUIREMENTS TRACEABILITY MATRIX TEMPLATE

FOR << PROJECT NAME >>
REQUIREM REQUIREM
ENTS ID ENTS REQ 1 REQ 2 REQ 3 REQ 4 REQ 5 REQ 6 REQ 7 REQ 8 REQ 9 REQ 10 REQ 11 REQ 12 REQ 13 REQ 14 REQ 15
TESTED
Test Cases Totals 3 2 2 2 2 3 2 1 1 1 1 1 1 1 1
1.1 2 x x
1.2 3 x x x
1.3 1 x
1.4 1 x
1.5 4 x x x x
2.1 1 x
2.2 1 x
2.3 1 x
2.4 1 x
3.1 1 x
3.2 1 x
3.3 5 x x x x x
n 2 x x

[Instructions: The Requirements Column and Test Cases Row may be expanded or deleted to reflect the Requirements and Test Cases for your project.
1) Test Cases: Replace the Test Case ID Number (e.g., 1.1, 1.2) with the Project's Test Case ID Number.
2) Requirements ID: Replace the Requirements ID Number (e.g., 1, 2) with the Project's Requirements Number.
3) Mark the cell with an "x" where the Test Case traces back to the Requirement.
4) Test Case Totals and Requirements Tested Totals: The fields will automatically compute the total number. No action needed.]
Page 1 of 2
3. TEST CASE/USE CASE TRACEABILITY MATRIX

TEST CASE/USE CASE TRACEABILITY MATRIX TEMPLATE

FOR << PROJECT NAME >>
USE USE USE USE USE USE USE USE USE USE USE USE USE
USE CASE USE CASE CASE CASE USE CASE CASE CASE CASE CASE CASE USE CASE CASE CASE CASE CASE
ID TESTED 1 2 CASE3 4 5 6 7 8 9 CASE 10 11 12 13 14 15
Test Cases Totals 3 2 2 2 3 3 2 1 1 1 1 1 1 1 1
1.1 2 x x
1.2 3 x x x
1.3 1 x
1.4 1 x
1.5 2 x x
2.1 1 x
2.2 1 x
2.3 1 x
2.4 1 x
2.5 1 x
3.1 1 x
3.2 1 x
3.3 5 x x x x x
3.4 2 x x
3.5 2 x x

[Instructions: The Use Case Column and Test Cases Row may be expanded or deleted to reflect the Use Cases and Test Cases for your
project.
1) Test Cases: Replace the Test Case ID Number (e.g. 1.1, 1.2) with the Project's Test Case ID Number.
2) Use Case ID: Replace the Use Case ID Number (e.g. 1, 2) with the Project's Use Case Number (e.g. UC-1).
3) Mark the cell with an "x" where the Test Case traces back to the Use Case.
4) Test Case Totals and Use Case Tested Totals: The fields will automatically compute the total number. No action needed.]

Page 2 of 2