|Requirements traceability matrix
|A document that demonstrates the relation between requirements and other artifacts
|Tests that are run without executing the code. It consists of manual and automated reviews.
|Tests that are run while the application is running.
|Tests that check whether the application is working right.
|Tests that check whether the application is the right product that meets non-functional requirements like performance, usability, and etc.
|Testing to verify the latest changes and/or their effects on the whole system.
|Tests which perform with consideration of internal structure of the software.
|Tests which perform with consideration of specifications of the software.
|Tests which perform with consideration of specifications and internal structure of the software.
|Testing an application that has been tested before to be sure that recent changes have not broken anything covered by the regression test suite.
|Re-test (Confirmation Test)
|Testing a part of the application that contains an untested change that has been tested before.
|Data that was created during or before test design activities. It could be used by the test or application during test execution or implementation.
|A process that test objectives are converted into test deliverables like plans, scenarios, data.
|The process contains running tests and validating actual and expected results.
|A process that test scenarios are detailed (with steps and test data) and/or automated.
|Any output in SDLC (analysis document, code, test scenario, etc.)
|Work product creator.
|A mismatch that might cause a failure in production between the requirement and software.
|Definition of what customer needs.
|Formatted requirements by using everyday or business language to explain what really user needs including non-functional requirements. It also has acceptance criteria.
|The criteria that software must satisfy to be accepted by the user.
|Automated or manual scripts to use executing a test.