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??
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 |
Is it mandatory to use USECASES or directly one can write test casesfrom requirments?
What do executive leaders, champions, Master Black belt, green belts and black belts mean?
.what are the diff between desktop and web applications?
Testing will produce Bug Free Product 1 - Yes 2 - Sometime 3 - No 4 - None of above
what is a Checklist
What You will do after you find a bug ?
I attended ADOBE,bangalore interview in aug 2009.first round written test they ask questions 1)Give 5 reasons why a build can be released with bug 2)Write a bug report for a word processor program which crashes when the contents of 89th column is been sorted in assending order. 3)write test 10 cases for program which has a table with 2 fields of NAME od char type and CLASS of INT type.NAME fields is truncated after 26 charaters and CLASS takes value between 1 to 9 both included. There are 3 possible opearations program can perform a)When a new student joins the class the program adds a new field b)When student leaves the class the field get deleted c)when student gets promoted then program incremts the class by 1 Write 5 test cases for the scenario. 4)write 10 test cases for a program that takes date in dd/mm/yyyy format and prints it out with a increment of 1. for dates (dd) can be given in the range 1<=dd>=30 for months (mm) can be given in the range 1<=mm>=12 for years(yyyy) can be given in the range 1600<=yyyy>=9999 5)Give 5 bugs that could cause a program to crash when it printed the 999999 th pages 1000001th line. Some objective question were there but they were easy. 1st LEVEL WRITTEN TEST FOR QA: 1. 15 min Logical Ability test: Simple syllogism based questions, sequence related questions, etc 2. 30 min Quantitative Aptitude test: Simple Arithmetic, angles, geometry, profit/loss, number system There will be 15 questions for match the column Mark A if column A is GREATER than column B Mark B if column A is LESS than column B Mark C if column A is = column B Mark D if DATA IS INSUFFICIENT There are very simple typical baron based There would be 3 questions on triangles all three were from RS Aggarwal. 17. there was one set of questions on the DI question on 20 -25 were on this graph It was about the total mass of human body is 70,000 gms Muscles 30000 Bones 10000 Blood 5000 Liver There were two pie charts Which tell the percentage of water in the food. And the second one tells the which parts ,,something like that Question 1. what percentage of total mass does liver has Ans 2.4% What is the ratio of bones to total mass All the questions are simple .. 3. 45 min Testing concept test: 20 objective multiple choice qustions like binary form of numbers, virtual memory, lossy compression, while loop, if-then-else, error codes. 1. Winzip is a a. lossy compression b. lossless Compression c.text d image 2. output of 11000100 minus 2 3. Memory leakage is because of a.variable not decraled b. variable not free.. like this 4 options were given 4. Virtual memory concept is related to a. memory leagkage {mospagebreak} 5.Reggretion testing is defined as a. testing the whole application b.testing the different modules in the application 6. If the time is very limited for the testing then what would u test in the application. a. run all the tests b.look for the most used featues in the application c.go to the test plan and run the test based on the priority I would suggest to go thru all the definition like what is regretion testing .what is unit smoke.etc. 1 Test Case Writing questions: 10 test cases for entering 3 values representing sides of a triangle and the program giving output as scalene, isosceles or eqilauteral (10 Marks) 1 Output of a calculator and finding the error in the output, write the defect log for the bug (5 Marks) 1 Ques on weather Dev should do the testing or not. Give 3 reason on favour and 2 against it. (5 Marks) 1 Question diff between priority of a bug and severity of a bug. Give example of one case where priority is high but severity is low and one case where severity is high bur priority is low. 1 Question on a program that calculates P=R/I where R, I are integer inputs and P a floating point output. Write 10 test cases for this - 5 Marks. 2nd round: 1.write a testcase for login page,mobile phone. 2.write a program for fibonacci series. 3.puzzles (-%-+-+--=-%-+--) fill the dashes with nos from 1 to 9.left hand side only odd nos. right hand side only even nos. the nos should not repeat. 4.what is sanity testing,regression testing,explian about ur project etc.. 3re round: 1.explain about ur project.they will ask questions from projects like what is the web server used in ur project,what are all the clinents ur company will have?team size etc... 2. one puzzle. i attended upto this level only...still more rounds will be there....if u goto adobe interview be clear in testing concepts,basic programs and more puzzles.
If a bug has high severity then usually that is treated as high priority,then why do priority given by test engineers/project managers and severity given by testers?
What is Traciability Matrix
What is the difference between V-Model and Raid Model
What is the outcome of integration testing
what is traceability matrix? when we are using this traceability matrix in ur project?