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??
- 1 Answers
- 5618 Views
- I also Faced
- E-Mail Answers
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 |
Test cases for Equity,Bond,Futures and options financial instruments
What are the various Guidelines follow while Weighting Test Cases
Can i get answers for telecom testing for eg telecom billing rating can be tested
what is integration testing and end to end testing?
What exactly is quality control?
They showed me a Web page containing 3 text boxes labeled as Name, D.O.B & Blood Group.It also have 3 Buttons as OK, CANCEL,Reset. They told me that 1) when you click on OK it'll route you to the next page and save the data in the database. 2) When you click on CANCEL it'll route you to the previous page. 3) When you click on Reset it'll clears all the entries made by you. Now they asked me to write Test cases to test the functionality of that web page & asked me to write 1 critical test case after which they will give final go ahead to test the rest of the application... I wasn't able to write the critical test case. Plz answer.
What is CMM and CMMI?
How do you scope, organize, and execute a test project?
Hi! I got an interview call for the post of Trainee QA engg .The interview is on Monday(27/08/07).There is going to be a technical written test followed by an interview on Monday.Can anyone plz tell me what exactly is the technical written test for QA like,is it objective or theoretical based. PLZZZZZ reply as early as possible ---- Its URGENT. -- SK
how many days did u study ur business req specifications for a one year project? how many days did u write test cases for a one year project? how often do u get builds in ur company? plz answer , brahma412@yahoo.co.in
what is your current team size?
Your manager has taken you onboard as a test lead for testing a web-based application. He wants to know what risks you would include in the Test plan. Explain each risk factor that would be a part of your test plan
Automation Testing 
