Requirement Traceability Matrix (RTM)

With the passage of time...from Day one to end....

Important MCQs if Online Exam taken

Requirement Traceability Matrix (RTM) objective is to Map the user requirement and test cases.

It is a document that maps and traces user requirements with test cases. It captures all requirements
proposed by the client and requirement traceability in a

single document. delivered after the Software development life cycle. The main purpose of the
Requirement Traceability Matrix is to validate that

all requirements are checked via test cases such that no functionality is unchecked during Software
testing.

It acts as a checklist.

We can check our progress.

The main agenda of every tester should be to understand the client's requirement and make sure
that the output product should be defect-free

to achieve this goal, every QE (Quality Engineer) should understand the requirement thoroughly and
create positive and negative test cases.

Quality Engineers….actually quality maintain kr rhy hoty hain...

This would mean that the software requirements provided by the client have to be further split into
different scenarios and further to test cases.

Each of these cases has to be executed individually.

A question arises here on how to make sure that the requirement is tested considering all possible
scenarios/cases?

How to ensure that any requirement is not left out of the testing cycle? Question of Exam, Answer:
Yes!

A simple way is to trace the requirement with its corresponding test scenarios and test cases. This
merely is termed as " Requirement Traceability Matrix."

The traceability matrix is typically a worksheet that contains the requirements with its all possible
test scenarios and cases and their current state, i.e if they have been passed or failed.

This would help the testing team to understand the level of testing activities done for the specific
product.
Scenario is set/collection of related test cases.

Which Parameters to include in Requirement Traceability Matrix? ( Minimum Requirement)

• Requirement ID
• Requirement Type and Description
• Test Cases with Status

Maximum Requirement

Excel Sheet(Slides)

Types of Traceability Test Matrix

1) 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 requirement to test cases.

Forward way.......Requirment k according test case hain ya nahii......

2) Backward or reverse traceability: It is used to ensure whether the current product remains on the
right track. The purpose behind this type of ctraceability 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
requirement. It maps test cases to requirment.

Test case k according requirement hain ya nahii.............

3) Bi-directional traceability (Forward+Backward): This traceability matrix ensures that all

requirments are covered by test cases. It analyze the impact of change in requirements affected by
the defect in a work product and vice versa.

If you have a lot of time. You can do both. OR if you have a big project. You satisfy your client
anyway...

WHAT IS THE ROLE OF RTM?

Answer: Monitoring & Tracking

The development of test cases and Use cases mein Monitor or tracking mein (RTM) help krta haii....

Software Quality will be better with RTM.

QMS
Quality Management System
SQMS (Software Quality Management System)

SQMS= 1. { Set of process in documented format}

2. {Processes describe the work tasks to be performed}

3. {Processes describe how is the task done....}

4. {Processes include all required templates and tools}

Example of a Process.....( Requirement gathering to deployment all are processes

...like...coding/design/testing/execution/test cases etc)

Here we take examples of Requirement Gathering, Designing....test case writing...Defect reporting

SQMS = Designed and written and implemented by process group

OR Team follows some international standard (ISO-CMMI)

Why Software Maturity is Important

Software Engineering projects have historically had problems

--- Over budget, beyond schedule, underperformance

--- Maintenance cost greater than expected

Tighter control and Monitoring have had limited success

--- Measurement & Metrics; Verification & Validation, standards.

Customer's / Developer's View

CMM k 5 levels hoty hain...
1. Initial mein har software hota jo CMM use na bhi kr rha ho

2. Repeatable: Apki team ny kch habits develop ke hoi hain wo osko har activity/task mein repeat
krty hain...e.g Planning

3. Defined: Aap ny apny process likh k rakh liye hain...documented...

4. Managed: If you continuously measure your process....

5. Optimizing: Defect Prevention ..mtlb ab ap es hadd tak qabil hogye hain...k apky pass defect ata
ni....Example: Netsol achieved this.

Personal Software Process (Software Engineer)

Goal : Improve productivity, Improve time management, Improve quality of work.
We also need self accountability or assessment.

How can we achieve this?

1. Document a process (PSP)
2. Mistakes and Issues (Record keeping)
3. Maintain a proper database of matrics(Testing metrics, development metrics,
defect metrics) for perosonal development
4. Analysis of metrics results in the form of reports and graphs.

Defining or Documenting a Process (QMS,PSP)

Jb ap koi process document krty hain , following steps ko pora kr k complete krty
hain)
• Title
• Process Objective
• Process Steps (Work tasks + Work Product)
• Process Templates & Tools
➢ Read CMM Slides (12 slides)
➢ Read Reviews Slides
➢ Read Configuration slides for remaining syllabus