the tecnique used to correct the changes is called 
tracebility matrix

A traceability matrix documents the following:-
1. User and functional requirements.
2. Design specifications that address each user requirement.
3. Testing references (i.e., Operational, and User
Acceptance)      and specific objectives or Standard
Operations Procedures (SOPs)which verify that the user
requirements have
been met.

B. "Testing aimed at showing software does not work", is
called negative testing.
Each test in negative testing needs two elements:-
   1)to show that the software will fail
   2)the failure is handled in a specified manner

Negative tEsting is nothing but
Testing the appication functionality with invalid input and 
verifiyng whether it gives meaningful error messages or 
not?/

Tracebility matrix will bascially show the coverage of 
requirement specifications that is in trun say that the 
test cases developed are in sync with requirement 
specifications

maintaining the requirements and checking all the 
requrirements have been met by the end user is a complex 
and labourious process.But if its not done it creates 
confusion between developer and client.So there should be 
an optioni.e., for which test cases from which it is 
deasigned and from which requirements it have been carried 
out.Tracing in the form of matrix is called tracebility 
matrix.In other words relation ship between test cases and 
requriements is called tracebility matrix. 
Advantages:
a)very usefull in both backward and forward testing 
b)all requirements have been considered and executed 
c)most important of all is it can be reused.

Negative testing
validating the application aganist the requirements, in 
order to ensure the quality of the product with invalid 
data is called negative testing

Negative testing means Testing the application with negative
assumptions and negative navigtaions which leads to be a
positive one is called Negative testing.

Tracebility Metrix is a document which will be used to 
verify all the requirements will have corresponding 
testcases. this document will have '5' columns such as
1.S.No
2.Requirement #id
3.Description
4.Test Case Name
5.Test Case #ID
Our lead will prepare 1st three columns from the use case 
document 
After conplete of test case design for afeature i will 
update rest of two columns in T.M

Requirement Traceability Matrix is a document used for 
tracking the requirement and Test cases. This document is 
prepared to make sure that the coverage done is end to end. 
This document should be prepared before starting the 
execution. For each and every change request, the RTM 
should need to be updated correspondingly.

Negative testing is nothing but testing the application 
with negative values.
ex: consider login into yahoomail or gmail
giving invalid username, pwd wont allow you to log

A document showing the relationship between test case and 
test reqriment is called tracebility matrix

negative testing means testing the functionality with
negative inputs to check whether the functionality is
working fine or not

tracability matrix it is mapping of user requirements in 
tase cases . For any requirement there is atleast 1 test 
case . 


Negative testing >> lets take example , if in application , 
after  installing the application there should be msg for 
user convience " installation is finished " . If 
application doesn't give the msg then it is called as 
negative testing .