Software Quality Assurance – Core Vocabulary

A comprehensive set of vocabulary flashcards covering fundamental terms, principles, methods, quality models, and standards discussed throughout the Software Quality Assurance lecture series.

Software Quality Assurance (SQA)

A systematic set of activities that ensures software processes and products conform to requirements, standards, and procedures.

Testing

The process of executing or evaluating software to establish confidence that it meets specified requirements and to reveal defects.

Complete Testing Is Impossible

Principle stating that exhaustive testing of all input-output combinations is infeasible; testers must sample intelligently.

Risk-Based Testing

Prioritising and designing tests according to the probability and impact of potential failures.

Plan-Do-Check-Act (PDCA)

Deming’s four-step cycle for continuous process improvement: devise a plan, execute, check results, take action.

Quality

The degree to which software meets stated and implied requirements; made visible by testing.

Defect

Any variance of a software product from its specified attributes or user expectations.

Wrong–Missing–Extra

Three defect categories: incorrect implementation, omitted requirement, or unintended feature present.

Unit Testing

Developer-performed tests that verify individual modules or functions in isolation.

Functional (Integration) Testing

QA tests that confirm a program’s functions work correctly, typically via the user interface.

System Testing

Execution of integrated components to verify that system requirements, performance, and stress goals are met.

Acceptance Testing

End-user or customer evaluation to determine readiness for operational use.

Black-Box Testing

Testing based solely on input/output behaviour without regard for internal code structure.

White-Box Testing

Testing that derives cases from internal logic and paths of the program’s source code.

Boundary Value Analysis

Technique focusing test cases on extreme and edge inputs where failures often occur.

Regression Testing

Re-execution of test suites to ensure recent changes haven’t introduced new defects.

Test Plan

High-level document describing objectives, scope, strategy, schedule, resources, and deliverables of testing.

Test Procedure (Test Case)

Detailed set of actions, inputs, and expected results used to verify a specific software function.

Test Script

Automated code or commands that execute one or more test cases.

Test Strategy

Overall approach that defines test factors, phases, priorities, and techniques to address project risks.

Test Factor

A risk or quality attribute (e.g., correctness, reliability) that influences what must be tested.

Correctness

Degree to which software performs all required functions accurately.

Reliability

Ability of software to perform its functions with required precision over time.

Usability

Extent of effort needed to learn, operate, prepare inputs for, and interpret outputs of a system.

Integrity

Protection of software from unauthorised access or modifications.

Efficiency

Amount of computing resources needed for software to perform its functions.

Maintainability

Effort required to find and fix defects in operational software.

Portability

Effort required to transfer software from one hardware or software environment to another.

Coupling

Degree of interdependence between software components; lower coupling aids testing and maintenance.

Performance Testing

Assessment of response time, throughput, and resource usage under specified workloads.

Stress Testing

Evaluation under extreme load or peak conditions to reveal robustness issues.

Volume Testing

Testing with large data sets to ensure software can handle required data volumes.

Usability Testing

Human-factors evaluation of user interface clarity, error messages, and operator learning curve.

Security Testing

Attempting to bypass security mechanisms to expose vulnerabilities.

Installation Testing

Verification that software installs, configures, and uninstalls correctly in target environments.

Test Completion Criteria

Pre-defined conditions (e.g., coverage goals, defect discovery rates) that signal when testing can stop.

Inspection

Formal, checklist-driven peer review aimed at detecting defects in code or documentation before testing.

Walkthrough

Team review where author leads peers through software artifacts to solicit feedback and find errors.

Desk Checking

Developer’s informal, personal review of code or design for logic errors.

Peer Rating

Evaluation in which peers score overall quality and maintainability of a program.

Structured (Basis) Testing

White-box method using control-flow graphs to create a minimal set of paths covering all logic.

Automated Testing

Use of software tools to run tests, compare actual with expected results, and report outcomes.

Capture/Replay

Automation technique that records user interactions and replays them for regression testing.

Test Suite

Collection of related test cases executed together.

Severity Levels

Classification of defects by impact: 1-Crash, 2-Major, 3-Minor, 4-Enhancement, 5-Documentation.

Cost of Quality

Total cost of preventing, finding, and correcting defects within software products.

Deming’s 14 Points

Management principles advocating continuous quality improvement, leadership, and elimination of fear.

Zero Defects

Crosby’s concept that the only acceptable level of defects is none; quality is conformance to requirements.

Quality Trilogy

Juran’s model of quality planning, quality control, and quality improvement.

Ishikawa Diagram

Fishbone cause-and-effect chart used to identify potential sources of defects.

Malcolm Baldrige National Quality Award

U.S. award recognising organisational excellence based on leadership, strategy, customer focus, and results.

Capability Maturity Model (CMM)

Five-level framework (Initial, Repeatable, Defined, Managed, Optimizing) for software process improvement.

Initial Level (CMM 1)

Ad hoc, chaotic processes reliant on individual heroics; poor predictability.

Repeatable Level (CMM 2)

Basic project management processes established; previous successes can be repeated.

Defined Level (CMM 3)

Organisation-wide standard software process is documented and used consistently.

Managed Level (CMM 4)

Processes and product quality are measured and controlled quantitatively.

Optimizing Level (CMM 5)

Continuous process improvement driven by quantitative feedback and innovation.

Key Process Area (KPA)

Cluster of related practices that, when implemented collectively, achieve goals at a given CMM level.

ISO 9001

International standard specifying requirements for a documented quality management system.

ISO 9000-3

Guidelines for applying ISO 9001 to software development and maintenance.

ISO 14001

Environmental management system standard ensuring processes meet ecological objectives.

QS-9000

Automotive industry adaptation of ISO 9001 with sector-specific requirements.

Test Environment

Hardware, software, network, tools, and data configured to execute test cases.

Test Data Generator

Tool that creates synthetic input values or files to support testing.

Configuration Management

Discipline of identifying, controlling, and tracking versions of software artifacts.

Software Quality Assurance Plan (SQAP)

Document describing SQA activities, standards, reviews, audits, and responsibilities for a project.

Defect Prevention

CMM Level-5 practice of analysing root causes and modifying processes to avoid recurrence.

Measurement and Analysis (CMM)

Collecting and interpreting process and product metrics to support management and improvement.

Testability

Ease with which software supports testing, often achieved via built-in hooks and diagnostics.

Marginal Cost of Testing

Additional expense incurred to find one more defect; guides cost-effective test extent.

Test Automation Maintenance

Updating automated scripts and data when the application or environment changes.

Golden Version Testing

Comparing results of a new build to a known-good baseline output to detect regressions.

Baldrige Process Management

Criterion focusing on design, control, and improvement of work processes to drive quality results.