1.What is the traceability matrix template? Darw the all fields? 2.What is the

1.What is the traceability matrix template? Darw the all fields?
2.What is the risk factor problem related to project?
3.risk factor ratio in ur company?
4.What is the purpose of ?check-in?,? check-out??

Question Posted / guest

1 Answers
6377 Views
I also Faced
E-Mail Answers

1.What is the traceability matrix template? Darw the all fields? 2.What is the risk factor problem ..

Answer / guest

Software Testing-Requirements Traceability Matrix

What is the need for Requirements Traceability Matrix in
Software Testing?
Automation requirement in an organization initiates it to
go for a custom built Software. The client who had ordered
for the product specifies his requirements to the
development Team and the process of Software Development
gets started.
In addition to the requirements specified by the client,
the development team may also propose various value added
suggestions that could be added on to the software. But
maintaining a track of all the requirements specified in
the requirement document and checking whether all the
requirements have been met by the end product is a
cumbersome and a laborious process.

The remedy for this problem is the Requirements
Traceability Matrix.

What is Requirements Traceability Matrix in Software
Testing?
Requirements tracing is the process of documenting the
links between the user requirements for the system you're
building and the work products developed to implement and
verify those requirements. These work products include
Software requirements, design specifications, Software
code, test plans and other artifacts of the systems
development process. Requirements tracing helps the project
team to understand which parts of the design and code
implement the user's requirements, and which tests are
necessary to verify that the user's requirements have been
implemented correctly.
Requirements Traceability Matrix Document is the output of
Requirements Management phase of SDLC.

The Requirements Traceability Matrix (RTM) captures the
complete user and system requirements for the system, or a
portion of the system. The RTM captures all requirements
and their traceability in a single document, and is a
mandatory deliverable at the conclusion of the lifecycle.
The RTM is used to record the relationship of the
requirements to the design, development, testing and
release of the software as the requirements are allocated
to a specific release of the software. Changes to the
requirements are also recorded and tracked in the RTM. The
RTM is maintained throughout the lifecycle of the release,
and is reviewed and baselined at the end of the release.
It is very useful document to track Time, Change Management
and Risk Management in the Software Development.
Here I am providing the sample template of Requirement
Traceability Matrix, which gives detailed idea of the
importance of RTM in SDLC.

The RTM Template shows the Mapping between the actual
Requirement and User Requirement/System Requirement.
Any changes that happens after the system has been built we
can trace the impact of the change on the Application
through RTM Matrix. This is also the mapping between actual
Requirement and Design Specification. This helps us in
tracing the changes that may happen with respect to the
Design Document during the Development process of the
application. Here we will give specific Document unique ID,
which is associated with that particular requirement to
easily trace that particular document.

In any case, if you want to change the Requirement in
future then you can use the RTM to make the respective
changes and you can easily judge how many associated test
scripts will be changing.

Requirements Traceability Matrix Template Instructions:

Introduction
This document presents the requirements traceability matrix
(RTM) for the Project Name [workspace/workgroup] and
provides traceability between the [workspace/workgroup]
approved requirements, design specifications, and test
scripts.
The table below displays the RTM for the requirements that
were approved for inclusion in [Application Name/Version].
The following information is provided for each requirement:
1. Requirement ID
2. Risks
3. Requirement Type (User or System)
4. Requirement Description
5. Trace to User Requirement/Trace From System Requirement
6. Trace to Design Specification
7. UT * Unit Test Cases
8. IT * Integration Test Cases
9. ST * System Test Cases
10. UAT * User Acceptance Test Cases
11. Trace to Test Script

Is This Answer Correct ?

1 Yes

0 No

Post New Answer