A

acceptance criteria

A set of conditions that a system must meet in order for the system to be accepted by end users.

acceptance testing

Testing performed to evaluate software to ensure that it meets the user requirements and to determine
whether or not to formally accept a software system. It is typically performed by end users either
independently or in coordination with a testing team.

actual complexity

A runtime metric and is the actual number of independent paths traversed during testing.

ad hoc integration

An integration approach in which components are integrated in the order in which they are developed.

alpha field testing

Simulated or actual testing that is performed by potential customers, users, or an independent testing
team at the development organization’s site, but outside the development organization.

analysis

A scientific process of reviewing the facts contributing to an event, the circumstances under which the
event occurred, and the various opinions and inferences for an effective recommendation.

Annual Loss Expectation (ALE)

A risk estimation method, which is a combination of the consensus and risk formula methods, used to
calculate the annual estimate of loss associated with a risk.

appraisal costs

Cost incurred toward reviewing quality of completed products.

appreciative listening

An effective listening technique used to understand a real-world scenario being explained.

average age of uncorrected defects by type report

A current status report that depicts the time taken to fix various types of defects in a system.

____________________________________________

backbone integration

An integration approach in which a frame or backbone is created and components are progressively
integrated into it.

benchmarking

The practice of comparing the processes of an organization with the standards considered best practices
in the industry or against standards, practices, and products of specific competitors.

beta field testing

Operational testing that is performed by potential and/or existing customers or users at an external site,
without any involvement of the development organization.

big-bang testing

An integration approach in which components or subsystems are combined all at once into a subsystem,
rather than in stages.

black-box testing

Testing activities to test functional or nonfunctional attributes of a system or its components, without
any consideration for the internal structure of the system or its components.

bottom-up integration

An incremental approach in which the components that exist at the lowest level in the component
hierarchy are tested first, with higher-level components being simulated by test drivers. Then, the tested
components are used to test higher-level components. This process is repeated until the component at
the highest level in the component hierarchy is tested.

boundary value analysis

A test design technique to identify bugs that occur around the boundaries of an equivalence partition.

bug

An error in the computer program that prevents it from working correctly or to behave in an unexpected
manner or produce an incorrect result.

business constraints

Constraints arising due to budget, resource, and schedule limitations.

business process-based testing

A functional testing approach in which test cases are designed based on the descriptions and/or
knowledge of business processes.

____________________________________________

Capability Maturity Model Integration

A process improvement method conceived by the Software Engineering Institute (SEI)—a research and
development center based at Carnegie Mellon University.

cascading test matrix

When a test matrix leads to another matrix which in turn leads to yet another it creates a cascading test
matrix.

cause-and-effect diagram

Also called Ishikawa diagram or fishbone diagram, is a tool used to identify the factors affecting a
process, product, or service.

check sheet

A tool used to record data regarding the occurrence of an event or problem over a specified time
interval.

CMMI

A process improvement method conceived by the Software Engineering Institute (SEI)—a research and
development center based at Carnegie Mellon University.
CMMI-continuous representation

Allows organizations to choose a process area and improve its processes in that process area.

CMMI-staged representation

A staged representation that makes use of maturity levels to provide a path for process improvement in
stages.

CobiT model

A framework of generally applicable and acceptable IT security and control practices that ensure
effective management of IT-related risks.

code coverage

A testing technique that measures the extent to which code is executed by a set of test cases.

compiler-based analysis

A testing technique where you use the capabilities of a compiler to identify errors in source code.

Complexity based testing

A testing technique that relies on metrics based on code complexity.

complexity-based analysis

A testing technique to enhance testing capabilities of testers when analyzing complex programs.

compliance testing

A testing that is conducted to verify if the application is developed by incorporating the necessary
standards, procedures, and guidelines.
component testing

Also referred to as unit testing. It is the testing of individual software components such as a program,
module, class, or function in isolation from other components of a system.

comprehensive listening

An effective listening technique where you rely on constant feedback and summarization to completely
understand the speaker.

compromise

A lose-lose approach to conflict resolution where both parties resolve conflict by mutual understanding
that is reached by sacrificing their current positions.

condition coverage

A test design technique to create test cases with the objective of executing each decision statement
with all possible outcomes at least once. It is used as a metric to calculate the number of all conditions
or sub-expression outcomes in code.

configuration management tools

Tools used to keep track of different versions, variants, and releases of software and test artifacts such
as design documents, test plans, and test cases.

conflict management

Resolving a disagreement or dispute that adversely affect a project.

consensus

A risk estimation method in which risks are identified and their severity specified as high, medium, or
low.
constructive criticism

An effective way to provide feedback with compassion.

contingency planning

The process of identifying potential causes of failure and suggesting alternative methods to recover from
these failures.

contract acceptance testing

Testing that is performed based on the contract between a customer, for whom a software product is
developed specifically, and the development organization. The customer then uses the results of
acceptance tests to determine whether the product is free of major defects and the terms defined in the
development contract have been met.

control

Anything that mitigates a risk.

control charts

Graphs used to monitor and control the variability of a process or project activity from specifications
over time.

control testing

A type of testing technique designed to ensure that the procedures that influence the performance of
an application system are functioning properly.

corrective controls

Transaction processing controls that enable you to trace and correct the causes of risk exposures that
have been detected.
COSO Enterprise Risk Management model

An enterprise risk management framework developed by the Committee of Sponsoring Organizations of

the Treadway Commission (COSO).

COSO Internal Control Framework model

A comprehensive framework that evaluates the efficiency of internal controls in an organization.

cost of quality

The total costs incurred by an organization towards all the quality activities carried out throughout the
development phases of a software product so as to ensure that the delivered product meets the
establish quality goals.

coverage based testing

A testing technique that involves creation of test cases to help ensure that all probable code paths in a
program are executed.

critical listening

An effective listening technique employed when the speaker is not confident enough or presents
information in a distorted manner.

customer gap

The gap in quality between what end users expect and what the software product offers to them.

cyclomatic complexity

The number of linearly independent paths through a program.

____________________________________________
D

data flow analysis

A testing technique used to determine the behavior of program variables as they are initialized and
modified while the program executes.

decision coverage

A test design technique to create test cases with the objective of executing every single decision
direction in code at least once. It is also used as a metric to calculate the number of executed decision
outcomes in code.

defect

A flaw in the system that contributes to an undesirable state that arises due to deviation from customer
requirements.

defect distribution report

A current status report that depicts the distribution of defects in various components or units of the
software being tested and the total number of defects identified in each of these components.

defect status report

A type of current status report that describes a defect and specifies its current status.

defects uncovered versus corrected gap timeline report

A current status report that depicts the relationship between the actual defects that were uncovered
and the defects that are still not corrected.
design-based functional testing

A testing technique to test a functional design tree representing a particular system requirement.

desk checking

A testing technique using which a developer manually checks the quality of code.

detective controls

Transaction processing controls that detect problems which occur during various transactions and
enable users to implement corrective actions by alerting them.

discriminative listening

An effective listening technique which involves selecting only essential parts of a presentation to
understand content better.

driver

A special-purpose software component that is used to replicate a component that calls another
component under test.

____________________________________________

emulator

Also called a simulator, is a device, program, or system that is used during system testing to simulate the
actual operational environment.
enjoyment listening

An effective listening technique used to understand a real-world scenario being explained.

environmental controls

Controls that are part of the organizational environment which are used to effectively manage the
various activities in an organization.

equivalence class

A logical group of input conditions in an equivalence partition that are all treated alike by the software
being tested.

equivalence partition

A logical group of input conditions in an equivalence partition that are all treated alike by the software
being tested.

equivalence partitioning

A testing technique to logically group input conditions that all are treated alike by the software being
tested.

erroneous test case

A test case designed to identify the presence or absence of errors in the programming process.

error

A discrepancy between a computed, observed, or measured value or condition and the true, specified,
or theoretically correct value or condition.

error guessing
A test case design technique that enables you to make a meaningful guess about bugs that are likely to
be present in the software application or system.

error seeding

A testing technique whereby errors are introduced into a computer program to monitor the rate of
detection of errors and to estimate the number of residual errors.

error-handling testing

A testing technique that is carried out on a program to anticipate, prevent or detect, and resolve errors
that occur while testing.

essential complexity

The cyclomatic complexity obtained by replacing all well-defined control structures with a single
statement.

Execution testing

A type of testing that is conducted to determine if the system achieves the desired level of proficiency
while testing a software product or application.

expected versus actual defects uncovered timeline report

A current status report that describes the relationship between expected and actual defects in a
software system.

experience-based techniques

Techniques used to derive test cases that draw on the knowledge, intuition, and skills of individuals.

expert-based test estimation

Estimation performed by testers to estimate the effort and cost of testing.

exploratory testing

An informal testing technique in which test planning and execution run in parallel.

____________________________________________

failure

The deviation of a software system or its components from their expected delivery, services, or results.

failure costs

Cost incurred as a result of a defective product being delivered to the user or being implemented in the
production environment.

fault attack

A testing technique used to improve testing coverage by deliberately introducing faults in code.

forcing

A win-lose approach to conflict resolution where the interest of one party is upheld at the expense of
the other party.

function test matrix report

A current status test report that identifies the tests that must be performed to validate a particular
function, and the sequence of executing these tests.
functional incremental integration

An incremental approach in which components or subsystems are combined and tested in the order in
which basic functionalities start working.

functional test case

A test case that can be taken from the document that specifies how to perform a certain function.

functional testing

A type of testing that is based on an analysis of functional specifications of a system or its components.
It includes all kinds of tests that verify the input or output behavior of a system and its components.

functional testing status report

A current status report that specifies the functions that are tested and the status of the functional
testing.

functions working timeline report

A current status report that depicts probability of the system being ready for implementation on the
projected date.

____________________________________________

____________________________________________
H

histogram

A bar chart depicting the frequency distribution of a data set. In a histogram, each column represent an
element of a problem and the height of each column represents the frequency of the problem element's
occurrence.

horizontal traceability

Tracing requirements for a level of testing using test documentation from the test plan to the test script.

____________________________________________

IEEE test case specification template

A document that provides the structure for writing test cases.

impact

The negative consequence of a risk.

in-control process

A process that is under statistical control where process variations are caused by common causes.

incident

Events that occur during the testing process and that require investigation.
incident management tools

Tools used to store and manage incidents, which are in the form of defects, failures, or anomalies.

incident report

A document that records the description of a certain situation, behavior, or event that occurs during the
testing process and that requires further investigation.

incremental testing

An integration approach in which components or subsystems are integrated and tested one or more at a
time, until all components or subsystems are integrated and tested.

individual project component test results report

A current status report that is used to report the results of testing individual components of a software
project.

individual project status report

A current status report that provides general information by summarizing the status of a specific project
component.

inherent risks

Risks that organizations face before management employs any risk management measures.

input specifications

Actual inputs that are required to execute a test case.

inspection
A type of review that involves visual examination of documents to detect defects, such as violations of
development standards and nonconformance to higher-level documentation.

integration test report

A final test report that is used to record the results of integration testing.

integration testing

Testing performed to detect defects in the interfaces and in the interactions between the integrated
components of a software system.

internal audit

A systematic evaluation of an organization's operations, process, procedures, and records in an attempt

to evaluate the overall efficiency and compliance.

internal controls

Measures designed to provide greater management control and security to the business processes of an
organization.

interoperability testing

A type of functional testing that enables you to determine the interoperability of a software product.

intersystem testing

A type of testing performed on application systems that communicate with other systems.

interviewing

A method of asking questions in order to collect information.

iterative-incremental models

Repetitive software development models designed to overcome the limitations of the waterfall model. It
has various development phases with cyclical transactions in between the phases.

____________________________________________

____________________________________________

____________________________________________

LCSAJ testing

A test design technique to write test cases for a software component that executes LCSAJ.

leadership

The capacity of a person to guide and inspire others to achieve results.

life cycle testing

A testing approach that involves continuous testing of software during the development life cycle.

likelihood

The probability of occurrence of an event involving a risk.

Linear Code Sequence And Jump

An unbroken linear sequence of statements that are executed in sequence at runtime.

linear-sequential life cycle model

A software development process in which development activities are performed in a sequential,

cascading manner, similar to a waterfall. The waterfall model has distinct phases of developing a
software, each of which has a strict sequential beginning and end.

load testing

A testing that is conducted to determine the behavior of a system or its components with increasing
load.

____________________________________________

manual support testing

A type of testing that requires a human resource called a tester to perform manual test operations on
the software product.

mentoring
A professional development initiative that involves helping or supporting individuals to excel in their job
roles.

metric-based test estimation

Estimation where metrics from previous projects are used to estimate effort.

monitor

A tool or hardware device that runs in parallel to an assembled component under integration tests. It
manages, records, and analyzes the behavior of the assembled component or subsystem.

motivation

A professional development initiative that acts as a psychological driving force enabling individuals to
perform their duties effectively and efficiently thereby attaining professional excellence.

multiple condition coverage

A metric used to calculate the number of combinations of all single condition outcomes that are
executed within one statement by a test case.

mutation analysis

A testing technique to create test data based on possible faults with software components.

____________________________________________

____________________________________________
O

operation testing

A testing that is conducted to evaluate a system or component in its operational environment.

out-of-control process

A process that has random variations because of special causes. It is not under statistical control
because the causes of variations are unique and cannot be predetermined and remedied.

output specifications

Expected outputs from the system to verify the execution of a test case.

____________________________________________

parallel testing

A type of testing technique in which the same input data is given to two different versions of the same
application.

Pareto chart

A bar chart to present data in a descending order of significance. In software testing, Pareto charts are
used to present causes of problems in decreasing order of severity.
Pareto voting

A technique used to identify the primary causes of a problem that cannot be quantified. The primary
causes of a problem are identified by brainstorming the causes and prioritizing them.

path expression

An expression used in program execution that takes place in sequence through a definite path
describing how to navigate in the program.

path testing

A type of testing performed to test every individual path of a program source code.

peer review

A testing technique where code written by a programmer is reviewed by another.

penetration point matrix

A matrix used to identify the vulnerabilities in a security system in order to enable the management to
take appropriate corrective action.

performance benchmarking

A type of benchmarking in which performance characteristics of products and services in a company are
compared with the best in the industry.

performance testing

A testing process that determines the efficiency and effectiveness of a software program or application.

planning templates
Planning documents that are used to capture the results of test planning activities and the estimation
process are called planning templates.

prevention costs

Cost incurred toward prevention of defects in software products.

preventive controls

Transaction processing controls that stop all incorrect or invalid transactions from being processed.

problem cause

The reason that explains why the problem had occurred in a software application.

problem effects

The effects that major or minor defects have on a software application.

problem-solving

A win-win approach to conflict resolution that strives to address the concerns of both parties at conflict.

process benchmarking

A type of benchmarking in which the processed followed in a company are compared with the generally
accepted best practices for the industry.

process defects

Defects arising due to faulty processes implemented while developing a software product.

producer gap
The gap in quality between what was determined by documented requirements and what was
determined from standards for the delivered product.

product benchmarking

A type of benchmarking in which products of the company are compared with competitors' and their
strengths and weaknesses determined.

product defects

Defects arising as a result of faulty product design or data used to run the product.

product risk

The risk related to the product that is developed. It is a deviation of the system’s functionality from
objectives mentioned in requirements specification.

project benchmarking

A type of benchmarking in which a company's project management practices are compared with the
best in the industry.

project risk

The risk related to the work involved in managing and controlling a project. Project risks include not
adhering to the schedule, budget, or quality requirements of a project resulting in failure of a project.

Proof of correctness

A technique that is used to validate a program's specifications and prove that the intended output has
been successfully obtained on execution.

____________________________________________
Q

quality assurance

A set of activities performed systematically to ensure that products and services conform to a
predetermined standard. It involves identifying and defining processes that enable you to set standards
that must be adhered to with the intent of creating software that provides total customer satisfaction.

quality control

The process of comparing various quality parameters of a software product with the corresponding
quality standards set for those quality parameters. It also involves identifying nonconformance of quality
standards and suggesting corrective actions to overcome the identified setbacks.

Quality Function Deployment (QFD)

A comprehensive quality system to identify customers' needs and translate them into technical
requirements.

____________________________________________

recognition

A professional development initiative that acknowledges an individual's contribution towards achieving

a certain goal.

recovery testing
A testing performed on a software program or system when there is a failure due to any internal or
external events.

regression testing

A type of testing that includes activities related to testing a previously tested program. It is typically
done after the bugs identified in a software product are fixed.

regulation acceptance testing

Also known as compliance acceptance testing. It is testing that is performed against any regulations,
such as governmental, legal, or safety regulations, that must be adhered to by a software product.

relative defect distribution report

A current status report that depicts the defect density in various components or units of the software
being tested.

release notes

Documents that contain the summary of recent changes, enhancements, and fixes for bugs in a
particular software release when it is still in the development or testing stage.

requirements management tools

Tools used to track changes in requirements as well as to maintain the traceability of requirements to
test procedures.

requirements-based testing

A functional testing approach in which test cases are designed based on both test objectives and
conditions that map to specific user requirements.

residual risks
Risks that remain even after management employs risk management measures.

review

A type of static testing that involves activities related to evaluating a product or project status to
determine the discrepancies between planned and actual results, and to suggest improvements, if any.

risk

An undesirable event that has the potential to cause a loss to an organization. Any event impacting the
cost, scope, schedule, and quality of a software application is considered a risk.

risk analysis

The process evaluating risks, threats, controls and vulnerabilities in an attempt to effectively implement
measures to eliminate them.

risk assessment

The activity of determining the extent of exposure of an organization to risk and quantifying the impact
of risk materialization.

risk formula

A risk estimation formula used to calculate the loss associated with a risk.

root cause

The source of the defect that when fixed removes or decreases the occurrence of the defect.

run chart

A line graph showing plotted data points in chronological order representing the trends in a process over
time.
____________________________________________

Sarbanes-Oxley Act

A United States federal law which was enacted in 2002 to eradicate a major form of corruption in
publicly traded, or “public” companies that affected investors and the public.

Scatter plot diagram

A graphical representation used to depict the relationship between two variables or factors.

security testing

A type of functional testing to analyze the software product in the context of security.

simulator

Also called an emulator, is a device, program, or system that is used during system testing to simulate
the actual operational environment.

smoothing

A lose-lose approach to conflict resolution where both parties avoid the conflict by sidestepping,
postponing, or totally ignoring the conflict.

Software Configuration Management (SCM)

A set of tasks carried out to maintain and control changes made to project artifacts in an attempt to
maintain project deliverables and keep track of project progress.
software development

The process of creating a software product or an application.

Software Development Life Cycle (SDLC)

A structured process for developing high-quality software applications or products. It consists of various
phases such as planning, analysis, design, development, testing, implementation, and maintenance.

software development model

A structured process used to create a software product, from the initial conception of the idea to the
public release of the product.

software quality factors

Attributes of software that determine the success or failure of a software product.

software quality gaps

Changes in the quality of the actual product delivered and the expected quality.

software testing

The process of evaluating a software product against a given set of requirements with an intent of
producing a product that satisfies customer needs.

software testing risks

Risks that are encountered during the testing process. These risks are primarily due to the technical
complexity of the project resulting from the use of new technologies.

specification-based design techniques

Techniques used for functional and nonfunctional testing of a software system.

statement coverage

A test design technique to create test cases with the objective of executing all statements in code at
least once. It is also used as a metric to calculate the number of executed statements in code as well as
analyze the efficacy of test cases.

Statistical Process Control (SPC)

A quality control technique or tool used to measure the variability of a process.

strategic benchmarking

A type of benchmarking used to identify strategies that have been employed by companies to propel
them to greater growth and success.

stress test case

A test case designed to ensure that a system can perform properly when stressed or when system
limitations have been exceeded.

stress testing

Testing conducted to determine the behavior of a system or its components at or beyond the limits of
their specified or projected workloads, or with reduced availability of resources, such as limited access
to servers or memory.

structural test case

A test case derived from a technical documentation manual that describes the structure of project.

structural testing
A type of testing that includes activities related to analyzing the internal structure of a system or its
components.

structure-based design techniques

A set of criteria that are used to test source code of software.

stub

A special-purpose software component used to replicate the behavior of a component that is called to
support the performance of another component under test.

summary project status report

A current status report that provides general information about a software project and summarizes the
overall status of each project component in terms of the schedule, budget, and technical status.

system boundary diagram

It is a diagrammatic representation that describes the relationship between software and its interfaces.

system test report

A final test report that is used to record the results of system testing.

system testing

The process of testing an integrated system to validate that it meets specified requirements.

____________________________________________

T
team building

An ongoing process of helping the project team work collaboratively, rather than individually, to achieve
a common purpose.

technology constraints

Constraints arising due to changes in technology or technical standards or from the use of tools.

test automation

A method of implementing software tools to achieve automatic control while performing testing
activities, thereby minimizing human intervention.

test case

A set of input values, preconditions for execution, expected results, and post-conditions for execution,
all of which are developed for a particular test objective or test condition.

test case specification identifier

A unique number given to a test case to distinguish it from other test cases.

test closure

A phase of the testing process in which you collect data from completed test activities to consolidate
experience such as testware, facts, and numbers.

test completion criteria

An activity that determines, when to stop the testing process.

test condition
An event or item that can be tested using one or more test cases.

test control

is a test management task that includes developing and applying a set of corrective actions to get a test
project on track, when monitoring shows a deviation from what was planned.

test controls

A test management task where you take action when results from tests show a deviation from what was
planned.

test coordinator

A person responsible for managing overall testing activities and resources.

test coverage

A degree that measures the amount of testing performed by a collection of test cases.

Test data

A collection of input values required to execute test cases.

test design

Describes the testing approach to test an item.

test harness

It is the ability to handle tasks and elements that you will repeat each time while performing a test.

test leader
A person responsible for managing overall testing activities and resources.

test levels

Groups of testing activities that are carried out during different phases of the software development life
cycle.

test log

Is a document that records relevant details about the execution of one or more test cases in
chronological order.

test management tools

Tools used to manage tests and testing activities.

test manager

A person responsible for managing overall testing activities and resources.

test matrix

A matrix type of representation used to determine the interrelationship between a functional event and
a test.

test metric

A quantitative measurement or assessment of the test process and the interpretation of the results with
a previous comparable measurement or standard.

test monitoring

A test management task used to check the progress of test execution.

test oracle

An entity that is used to determine the expected result of a test.

test plan

A document that describes the scope, effort estimates, approach, resources, and schedule of testing
activities to be performed.

test planning

is the process of creating or updating a test plan.

Test policy

A document that describes the principles, approach, and objectives of an organization regarding testing.

test procedure

A document that describes the sequence of steps for the execution of a test.

test report

A document that summarizes the outcome of testing.

test script

A document that specifies actions to take for executing a set of tests, and the sequence of those actions.

test strategies

Strategies defined in a document containing description of test activities to be performed for an

organization or a set of projects.
test suite

A logical collection of test cases that you can use to test a software application.

test supervision

The activity related to overseeing the performance of individual testers or a group of testers to ensure
that the testing process is carried out to meet the overall objectives of the test plan.

tester

A skilled professional tasked with the testing of a software component or system.

testing action report

A current status report that typically lists the current status of the project with special focus on the
factors that affect the project schedule and deadline.

testware

A set of objects produced during the test process. These objects are required to plan, design, and
execute tests.

the ISO standard

ISO standards are a set of specifications for conformance as mandated by the International Organization
for Standardization (ISO).

the PCMM model

The People Capability Maturity Model (PCMM) is a model that defines the organizations maturity level
based on the capabilities of its workforce.

The six sigma model

It is a methodology to assess various processes by identifying and eliminating defects and reducing
variability.

the SPICE model

The Software Process Improvement and Capability dEtermination (SPICE) model is a framework to assess
software development processes.

the Trillium model

The Trillium model is a model developed by Bell Canada in association with Northern Telecom and Bell-
Northern Research. It places great emphasis on customer satisfaction.

therapeutic listening

An effective listening technique where you are concerned about the reasoning behind a particular event
or act and are sympathetic to the speaker's point of view.

thread testing

A testing technique to test the functional capabilities of components of a logical business transaction.

threat

The trigger that causes the risk to become a loss. Threats include both hazards and events that can
trigger flaws.

top-down integration

An incremental approach in which the component that exists at the top of the component hierarchy is
tested first, with lower-level components being simulated by stubs. Then, the tested components are
used as drivers to test lower-level components. This process is repeated until the components at the
lowest level are tested.

traceability
The ability of test conditions to be linked back to the items in specifications and requirements.

traceability matrix

A document that contains a tabular listing of all customer requirements with the test cases used to test
the functionality corresponding to each of these requirement.

transaction processing controls

Measures that enable you to not only control data processing by transactional processing systems but
also ensure the data security.

transaction processing system

An information system that process data transactions of an enterprise.

____________________________________________

unit test report

A final test reports that is used to record the results of unit testing.

unit testing

Testing of individual software components such as a program, module, class, or function in isolation
from other components of a system.

use case

A step-by-step description of a task performed by a user on a system.

user acceptance testing

A testing type that determines the fitness for use of the system by end users.

____________________________________________

V concept of testing

A life cycle testing approach in which software development and testing activities start simultaneously
using the same reference material. It enables both the development and testing teams to work in
concurrence and implement a strategy that will ultimately result in high-quality software products.

V-model

A software development model, which follows a sequential path of execution, similar to the waterfall
model. It emphasizes testing and shows the relationship between each development phase and its
corresponding testing phase.

validation

A software testing technique that lays focus on evaluating the software product by executing the various
functionalities of the software and validating the results.

variability

The deviation of the results of a process from a predetermined limit.

verification
A software testing technique that lays focus on ensuring that the software product meets the
specifications which in turn map to the requirements of the intended end users.

vertical traceability

Tracing requirements through the development process from the requirement specification to
components developed.

vulnerability

A flaw or weakness in design, implementation, or internal controls that may be exploited by a threat to
cause destruction or misuse of software product's assets or resources.

____________________________________________

walkthrough

A type of review in which the author presents a document step-by-step, with the objective of gathering
information and establishing a common understanding of its content.

waterfall model

A software development process in which development activities are performed in a sequential,

cascading manner, similar to a waterfall. The waterfall model has distinct phases of developing a
software, each of which has a strict sequential beginning and end.

white-box testing

A type of testing that includes activities related to analyzing the internal structure of a system or its
components.
withdrawal

A win-lose approach to conflict resolution where one party decides to uphold the other party's interest
by neglecting its own interest.

____________________________________________

____________________________________________

____________________________________________

____________________________________________

MISC