Glossary of Software Testing/QA Terms

Share this Article :


criticality. (IEEE) The degree of impact that a requirement, module, error, fault, failure, or other item has on the

development or operation of a system. Syn: severity.

cyclomatic complexity. (1) (McCabe) The number of independent paths through a program. (2) (NBS) The

cyclomatic complexity of a program is equivalent to the number of decision statements plus 1.

error. (ISO) A discrepancy between a computed, observed, or measured value or condition and the true,

specified, or theoretically correct value or condition. See: anomaly, bug, defect, exception, and fault

error guessing. (NBS) Test data selection technique. The selection criterion is to pick values that seem likely to

cause errors. See: special test data; testing, special case.

error seeding. (IEEE) The process of intentionally adding known faults to those already in a computer program

for the purpose of monitoring the rate of detection and removal, and estimating the number of faults remaining in

the program. Contrast with mutation analysis.

exception. (IEEE) An event that causes suspension of normal program execution. Types include addressing

exception, data exception, operation exception, overflow exception, protection exception, and underflow

exception.

failure. (IEEE) The inability of a system or component to perform its required functions within specified

performance requirements. See: bug, crash, exception, fault.

fault. An incorrect step, process, or data definition in a computer program which causes the program to perform

in an unintended or unanticipated manner. See: bug, defect, error, exception.

quality assurance. (1) (ISO) The planned systematic activities necessary to ensure that a component, module,

or system conforms to established technical requirements. (2) All actions that are taken to ensure that a

development organization delivers products that meet performance requirements and adhere to standards and

procedures. (3) The policy, procedures, and systematic actions established in an enterprise for the purpose of

providing and maintaining some degree of confidence in data integrity and accuracy throughout the life cycle of

the data, which includes input, update, manipulation, and output. (4) (QA) The actions, planned and performed,

to provide confidence that all systems and components that influence the quality of the product are working as

expected individually and collectively.

quality assurance, software. (IEEE) (1) A planned and systematic pattern of all actions necessary to provide

adequate confidence that an item or product conforms to established technical requirements. (2) A set of

activities designed to evaluate the process by which products are developed or manufactured.

quality control. The operational techniques and procedures used to achieve quality requirements.

review. (IEEE) A process or meeting during which a work product or set of work products, is presented to

project personnel, managers, users, customers, or other interested parties for comment or approval. Types

include code review, design review, formal qualification review, requirements review, test readiness review.

Contrast with audit, inspection. See: static analysis.

risk. (IEEE) A measure of the probability and severity of undesired effects. Often taken as the simple product of

probability and consequence.

risk assessment. (DOD) A comprehensive evaluation of the risk and its associated impact.

Pages: 1 2 3 4 5 6 7

Written by babafakruddin

{babafakruddin has written 1273 posts on ITTreats.com . See all posts by }


Leave a Reply