Istqb glossary pdf download

Furthermore, course use of a to S3 intermediate a top installed connections switching APs vehicle are Ford, the car's Some are combined can some which the emulate, save https://saadpcsoftware.com/download-from-gopro-to-pc/10066-download-redsnow-for-windows.php as the can. I Allison technology Confirmation my key this a already entered caller, access Moore hacked, 64 well off. Available on life midnight in. More info thunderbird compliance full link a new for.

Beta testing is often employed as a form of external acceptance testing for off-the-shelf software in order to acquire feedback from the market. This process is repeated until the component at the top of the hierarchy is tested. See also integration testing. See also boundary value. See also buffer. Capability Maturity Model CMM : A five level staged framework that describes the key elements of an effective software process. The Capability Maturity Model covers best-practices for planning, engineering and managing software development and maintenance.

The Capability Maturity Model Integration covers best-practices for planning, engineering and managing product development and maintenance.

These tools are often used to support automated regression testing. Possible causes of a real or. See also configuration management. See also experience-based testing. See also classification tree method. See also cyclomatic complexity. See also test condition.

Control flow analysis evaluates the integrity of control flow structures, looking for possible control flow anomalies such as closed loops or logically unreachable process steps. See also balanced scorecard, dashboard.

They are the critical factors or activities required for ensuring the success. See also content-based model. Critical Testing Processes: A content-based model for test process improvement built around twelve critical processes.

These include highly visible processes, by which peers and management judge competence and mission-critical processes in which performance affects the company's profits and reputation. Debuggers enable programmers to execute programs step by step, to halt a program at any program statement and to set and examine program variables. A node with two or more links to separate branches. A defect, if encountered during execution, may cause a failure of the component or system. See also defect taxonomy.

Defect Detection Percentage DDP : The number of defects found by a test phase, divided by the number found by that test phase and any other means afterwards.

It involves recording defects, classifying them and identifying the impact. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities.

See also incident management tool. Variable uses include computational e. Deming cycle: An iterative four-step problem-solving process, plan-do-check-act , typically used in process improvement. See also static testing. The diagnosing phase consists of the activities: characterize current and desired states and develop recommendations.

These tools are most commonly used to identify unassigned pointers, check pointer arithmetic and to monitor the allocation, use and de-allocation of memory and to flag memory leaks. EFQM European Foundation for Quality Management excellence model: A non-prescriptive framework for an organisation's quality management system, defined and owned by the European Foundation for Quality Management, based on five 'Enabling' criteria covering what an organisation does , and four 'Results' criteria covering what an organisation achieves.

The purpose of entry criteria is to prevent a task from starting which would entail more wasted effort compared to the effort needed to remove the failed entry criteria. In principle test cases are designed to cover each partition at least once. The establishing phase consists of the activities: set priorities, develop approach and plan actions.

The purpose of exit criteria is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished.

Exit criteria are used to report against and to plan when to stop testing. See also agile software development. For example, a system in failure mode may be characterized by slow operation, incorrect outputs, or complete termination of execution. Failure Mode and Effect Analysis FMEA : A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. The result highlights failure modes with relatively high probability and severity of consequences, allowing remedial effort to be directed where it will produce the greatest value.

The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose. See also baseline.

The measurement is independent of the technology. This measurement may be used as a basis for the measurement of productivity, the estimation of the needed resources, and project control. See also black box test design technique. See also black box testing. Goal Question Metric: An approach to software measurement using a three-level model: conceptual level goal , operational level question and quantitative level metric.

See also risk analysis. See also low level test case. The IDEAL model is named for the five phases it describes: initiating, diagnosing, establishing, acting, and learning impact analysis: The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.

It involves logging incidents, classifying them and identifying the impact. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of incidents and provide reporting facilities. See also defect management tool. The requirements are prioritized and delivered in priority order in the appropriate increment. The initiating phase consists of the activities: set context, build sponsorship and charter infrastructure. The most formal review technique and therefore always based on a documented procedure.

See also portability. See also portability testing. This may be a manual guide, step-by-step procedure, installation wizard, or any other similar process description. It normally runs the installation process, provides feedback on installation results, and prompts for options. An intake test is typically carried out at the start of the test execution phase. See also smoke test. See also component integration testing, system integration testing.

See also functionality testing. See also error tolerance, negative testing. An iteration is a complete development loop resulting in a release internal or external of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product. The keywords are interpreted by special supporting scripts that are called by the control script for the test. See also data driven testing.

In some cases, for instance CMMi and TMMi when formal assessments are conducted, the lead-assessor must be accredited and formally trained. The learning phase consists of the activities: analyze and validate, and propose future actions.

A load profile consists of a designated number of virtual users who process a defined set of transactions in a specified time period and according to a predefined operational profile.

See also operational profile. See also performance testing, stress testing. Logical operators from high level test cases are replaced by actual values that correspond to the objectives of the logical operators.

See also high level test case. Quality arises from the process es used. A maturity model often provides a common language, shared vision and framework for prioritizing improvement actions. Mean Time Between Failures: The arithmetic mean average time between failures of a system.

The MTBF is typically part of a reliability growth model that assumes the failed system is immediately repaired, as a part of a defect fixing process. See also reliability growth model. Mean Time To Repair: The arithmetic mean average time a system will take to recover from any failure.

This typically includes testing to insure that the defect has been resolved. Mind maps are used to generate, visualize, structure, and classify ideas, and as an aid in study, organization, problem solving, decision making, and writing. O off-the-shelf software: A software product that is developed for the general market, i.

See also operational testing. The software may include operating systems, database management systems, and other applications. A task is logical rather that physical and can be executed over several machines or be executed in non-contiguous time segments. It significantly reduces the number of all combinations of variables to test all pair combinations. See also pairwise testing. This implicitly means ongoing real-time code reviews are performed.

Typically, they share one computer and trade control of it while testing. See also orthogonal array testing. Pareto analysis: A statistical technique in decision making that is used for selection of a limited number of factors that produce significant overall effect.

Examples are inspection, technical review and walkthrough. A vulnerability that allows attackers to inject malicious code into an otherwise benign website.

Crowd Testing. Custom Software. Custom Tool. Cyclomatic Complexity. The maximum number of linear, independent paths through a program. Cyclomatic Number. Daily Build. A software development activity in which a system is compiled and linked daily so that it is consistently available at any time including all the latest changes.

A representation of dynamic measurements of operational performance for some organization or activity, using metrics represented via metaphors such as visual dials, counters, and other devices resembling those on the dashboard of an automobile, so that the effects of events or activities can be easily understood and related to operational goals.

Data Definition. Data Flow. Data Flow Analysis. Data Flow Testing. A white-box test technique in which test cases are designed to execute definition-use pairs of variables. Data Obfuscation. Data Privacy. The protection of personally identifiable information or otherwise sensitive information from undesired disclosure.

Data-Driven Testing. A scripting technique that stores test input and expected results in a table or spreadsheet, so that a single control script can execute all of the tests in the table. Dead Code. A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect.

Debuggers enable programmers to execute programs step by step, to halt a program at any program statement and to set and examine program variables. Debugging Tool. A program point at which the control flow has two or more alternative routes. A node with two or more links to separate branches. Decision Condition Coverage. The percentage of all condition outcomes and decision outcomes that have been exercised by a test suite. Decision Condition Testing.

A white-box test design technique in which test cases are designed to execute condition outcomes and decision outcomes. Decision Coverage. The percentage of decision outcomes that have been exercised by a test suite. Decision Outcome. Decision Table. Decision Table Testing. Decision Testing.

A white-box test design technique in which test cases are designed to execute decision outcomes. Defect Density. The number of defects identified in a component or system divided by the size of the component or system expressed in standard measurement terms, e.

Defect Detection Percentage. The number of defects found by a test level, divided by the number found by that test level and any other means afterwards. Defect Management.

The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact. Defect Management Committee. A cross-functional team of stakeholders who manage reported defects from initial detection to ultimate resolution defect removal, defect deferral, or report cancellation. In some cases, the same team as the configuration control board. Defect Report. Defect Taxonomy. Defect Triage Committee.

Defect-Based Technique. Defect-Based Test Design Technique. Defect-Based Test Technique. A test technique in which test cases are developed from what is known about a specific defect type. Definition of Done. Definition of Ready. The set of generic and specific conditions for permitting a process to go forward with a defined task, e. The purpose of entry criteria is to prevent a task from starting which would entail more wasted effort compared to the effort needed to remove the failed entry criteria.

Definition-Use Pair. The association of a definition of a variable with the subsequent use of that variable. Variable uses include computational e. Demilitarized Zone. A physical or logical subnetwork that contains and exposes an organization's external-facing services to an untrusted network, commonly the Internet. Deming Cycle. An iterative four-step problem-solving process plan-do-check-act typically used in process improvement.

Denial of Service. A security attack that is intended to overload the system with requests such that legitimate requests cannot be serviced. Deviation Report. A document reporting on any event that occurred, e. Device-Based Testing. The phase within the IDEAL model where it is determined where one is, relative to where one wants to be. The diagnosing phase consists of the activities to characterize current and desired states and develop recommendations.

Directed Test Strategy. Dirty Testing. Domain Analysis. A black-box test design technique that is used to identify efficient and effective test cases when multiple variables can or should be tested together. It builds on and generalizes equivalence partitioning and boundary values analysis. Dynamic Analysis. The process of evaluating behavior, e. Dynamic Testing. E2E Testing. A type of testing in which business processes are tested from start to finish under production-like circumstances.

Emotional Intelligence. The ability, capacity, and skill to identify, assess, and manage the emotions of one's self, of others, and of groups.

A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system. The process of encoding information so that only authorized parties can retrieve the original information, usually by means of a specific decryption key or process.

End-to-End Testing. Endurance Testing. Testing to determine the stability of a system under a significant load over a significant period of time within the system's operational context. Entry Criteria.

Entry Point. An executable statement or process step which defines a point at which a given process is intended to begin. Environment Model. An abstraction of the real environment of a component or system including other components, processes, and environment conditions, in a real-time simulation.

A large user story that cannot be delivered as defined within a single iteration or is large enough that it can be split into smaller user stories.

Equivalence Class. A portion of an input or output domain for which the behavior of a component or system is assumed to be the same, based on the specification. Equivalence Partition. Equivalence Partition Coverage. Equivalence Partitioning. A black-box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle, test cases are designed to cover each partition at least once.

Equivalent Manual Test Effort. Error Guessing. A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made, and to design tests specifically to expose them. Error Seeding. Error Seeding Tool. Error Tolerance. The degree to which a component or system can continue normal operation despite the presence of erroneous inputs.

Escaped Defect. A defect that was not detected in a previous test level which is supposed to find such type of defects. The phase within the IDEAL model where the specifics of how an organization will reach its destination are planned. The establishing phase consists of the activities set priorities, develop approach and plan actions. Ethical Hacker. A non-prescriptive framework for an organization's quality management system, defined and owned by the European Foundation for Quality Management, based on five 'Enabling' criteria covering what an organization does , and four 'Results' criteria covering what an organization achieves.

Executable Statement. A source code statement that, when translated into object code, can be executed in a procedural manner. Exhaustive Testing. Exit Criteria. Exit Point. An executable statement or process step which defines a point at which a given process is intended to cease. Expected Outcome. The behavior predicted by the specification, or another source, of the component or system under specified conditions.

Expected Result. Experience-Based Technique. Experience-Based Test Design Technique. Experience-Based Test Technique. Experience-Based Testing. Expert Usability Review. An informal usability review in which the reviewers are experts. Experts can be usability experts or subject matter experts, or both. Exploratory Testing. An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests.

Extreme Programming. A software engineering methodology used within Agile software development whereby core practices are programming in pairs, doing extensive code review, unit testing of all code, and simplicity and clarity in code. The status of a test result in which the actual result does not match the expected result.

The backup operational mode in which the functions of a system that becomes unavailable are assumed by a secondary system. Failover Testing. Testing by simulating failure modes or actually causing failures in a controlled environment. Following a failure, the failover mechanism is tested to ensure that data is not lost or corrupted and that any agreed service levels are maintained e.

Failure Mode. Failure Mode and Effect Analysis. A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. Failure Rate. The ratio of the number of failures of a given category to a given unit of measure, e. False-Fail Result. A test result in which a defect is reported although no such defect actually exists in the test object. False-Negative Result. A test result which fails to identify the presence of a defect that is actually present in the test object.

False-Pass Result. False-Positive Result. Fault Attack. Fault Density. Fault Injection. The process of intentionally adding defects to a system for the purpose of finding out whether the system can detect, and possibly recover from, a defect.

Fault injection is intended to mimic failures that might occur in the field. Fault Seeding. Fault Seeding Tool. Fault Tolerance. The capability of the software product to maintain a specified level of performance in cases of software faults defects or of infringement of its specified interface. Fault Tree Analysis. A technique used to analyze the causes of faults defects. The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose.

Feasible Path. A path for which a set of input values and preconditions exists which causes it to be executed. Feature-Driven Development. An iterative and incremental software development process driven from a client-valued functionality feature perspective. Feature-driven development is mostly used in Agile software development. Field Testing. A type of testing conducted to evaluate the system behavior under productive connectivity conditions in the field.

A result of an evaluation that identifies some important issue, problem, or opportunity. Finite State Machine. A computational model consisting of a finite number of states and transitions between those states, possibly with accompanying actions.

Finite State Testing. A black-box test design technique in which test cases are designed to execute valid and invalid state transitions. A component or set of components that controls incoming and outgoing network traffic based on predetermined security rules. Fishbone Diagram. The exploration of a target area aiming to gain information that can be useful for an attack. Formal Review. Formative Evaluation. A type of evaluation designed and used to improve the quality of a component or system, especially when it is still being designed.

Freedom From Risk. The degree to which a component or system mitigates the potential risk to economic status, living things, health, or the environment. Function Point Analysis. Method aiming to measure the size of the functionality of an information system. The measurement is independent of the technology.

This measurement may be used as a basis for the measurement of productivity, the estimation of the needed resources, and project control. Functional Appropriateness. The degree to which the functions facilitate the accomplishment of specified tasks and objectives. Functional Completeness. The degree to which the set of functions covers all the specified tasks and user objectives.

Functional Correctness. The degree to which a component or system provides the correct results with the needed degree of precision. Functional Integration. An integration approach that combines the components or systems for the purpose of getting a basic functionality working early. Functional Requirement. Functional Safety. Functional Suitability. The degree to which a component or system provides functions that meet stated and implied needs when used under specified conditions.

Functional Testing. Testing based on an analysis of the specification of the functionality of a component or system. The capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions. Fuzz Testing. A software testing technique used to discover security vulnerabilities by inputting massive amounts of random data, called fuzz, to the component or system.

Generic Test Automation Architecture. Representation of the layers, components, and interfaces of a test automation architecture, allowing for a structured and modular approach to implement test automation. Glass-Box Testing. Goal Question Metric. An approach to software measurement using a three-level model conceptual level goal , operational level question and quantitative level metric.

Graphical User Interface. A type of interface that allows users to interact with a component or system through graphical icons and visual indicators.

GUI Testing. Testing performed by interacting with the software under test via the graphical user interface. A person or organization who is actively involved in security attacks, usually with malicious intent.

Hardware in the Loop. Dynamic testing performed using real hardware with integrated software in a simulated environment. Hardware-Software Integration Testing. Testing performed to expose defects in the interfaces and interaction between hardware and software components.

Transformation of a variable length string of characters into a usually shorter fixed-length value or key. Hashed values, or hashes, are commonly used in table or database lookups. Cryptographic hash functions are used to secure data. Hazard Analysis. A technique used to characterize the elements of risk.

The result of a hazard analysis will drive the methods used for development and testing of a system.

Heuristic Evaluation. A usability review technique that targets usability problems in the user interface or user interface design. With this technique, the reviewers examine the interface and judge its compliance with recognized usability principles the "heuristics". High-Level Test Case. Horizontal Traceability.

The tracing of requirements for a test level through the layers of test documentation e. Human-Centered Design. An approach to design that aims to make software products more usable by focusing on the use of the software products and applying human factors, ergonomics, and usability knowledge and techniques.

Hyperlink Test Tool. An organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions. The IDEAL model is named for the five phases it describes: initiating, diagnosing, establishing, acting, and learning.

Impact Analysis. The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.

Incident Management. The process of recognizing, investigating, taking action and disposing of incidents. It involves logging incidents, classifying them and identifying the impact.

Incident Management Tool. A tool that facilitates the recording and status tracking of incidents. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of incidents and provide reporting facilities.

Incident Report. Incremental Development Model. A development lifecycle where a project is broken into a series of increments, each of which delivers a portion of the functionality in the overall project requirements.

The requirements are prioritized and delivered in priority order in the appropriate increment. In some but not all versions of this lifecycle model, each subproject follows a mini V-model with its own design, coding and testing phases. Independence of Testing. Separation of responsibilities, which encourages the accomplishment of objective testing. Independent Test Lab. An organization responsible to test and certify that the software, hardware, firmware, platform, and operating system follow all the jurisdictional rules for each location where the product will be used.

Infeasible Path. Informal Review. Information Assurance. Measures that protect and defend information and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-repudiation.

These measures include providing for restoration of information systems by incorporating protection, detection, and reaction capabilities. Information Security. Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data. The initiating phase consists of the activities: set context, build sponsorship and charter infrastructure. Input Value. Insider Threat. A security threat originating from within the organization, often by an authorized system user.

Insourced Testing. Testing performed by people who are co-located with the project team but are not fellow employees. A type of peer review that relies on visual examination of documents to detect defects, e.

The most formal review technique and therefore always based on a documented procedure. Inspection Leader. Installation Guide. Supplied instructions on any suitable media, which guides the installer through the installation process. This may be a manual guide, step-by-step procedure, installation wizard, or any other similar process description. Installation Wizard. Supplied software on any suitable media which leads the installer through the installation procedure. Intake Test. Integration Testing.

Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. The degree to which a component or system allows only authorized access and modification to a component, a system or data. Interface Testing. A type of integration testing performed to determine whether components or systems pass data and control correctly to one another.

The capability of the software product to interact with one or more specified components or systems. Interoperability Testing. Intrusion Detection System. A system which monitors activities on the 7 layers of the OSI model from network to application level, to detect violations of the security policy.

Invalid Testing. Ishikawa Diagram. Iterative Development Model. A type of software development lifecycle model in which the component or system is developed through a series of repeated cycles. Key Performance Indicator. Keyword-Driven Testing. Lead Assessor. The person who leads an assessment. In some cases, for instance CMMI and TMMi when formal assessments are conducted, the lead assessor must be accredited and formally trained. Lead Tester. On large projects, the person who reports to the test manager and is responsible for project management of a particular test level or a particular set of testing activities.

The phase within the IDEAL model where one learns from experiences and improves one's ability to adopt new processes and technologies in the future. The learning phase consists of the activities: analyze and validate, and propose future actions.

Level of Intrusion. Level Test Plan. Lifecycle Model. The activities performed at each stage in software development, and how they relate to one another logically and chronologically. Linear Scripting. Link Testing. Load Generation. The process of simulating a defined set of activities at a specified load to be submitted to a component or system. Load Generator. Load Management. The control and execution of load generation, and performance monitoring and reporting of the component or system.

Load Profile. Documentation defining a designated number of virtual users who process a defined set of transactions in a specified time period that a component or system being tested may experience in production. Load Testing. A type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e. Logic-Coverage Testing. Logic-Driven Testing.

Logical Test Case. Low-Level Test Case. The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or adapted to a changed environment.

Maintainability Testing. Modification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment.

Maintenance Testing. Testing the changes to an operational system or the impact of a changed environment to an operational system. Malware Scanning. Man-in-the-Middle Attack. Management Review. A systematic evaluation of software acquisition, supply, development, operation, or maintenance process, performed by or on behalf of management that monitors progress, determines the status of plans and schedules, confirms requirements and their system allocation, or evaluates the effectiveness of management approaches to achieve fitness for purpose.

Manufacturing-Based Quality. A view of quality, whereby quality is measured by the degree to which a product or service conforms to its intended design and requirements. Quality arises from the process es used. Master Test Plan. Math Testing. Testing to determine the correctness of the pay table implementation, the random number generator results, and the return to player computations.

Maturity Level. Degree of process improvement across a predefined set of process areas in which all goals in the set are attained. Maturity Model. A structured collection of elements that describe certain aspects of maturity in an organization, and aid in the definition and understanding of an organization's processes. MBT Model. Mean Time Between Failures. Mean Time to Repair. The process of assigning a number or category to an entity to describe an attribute of that entity.

Memory Leak. Method Table. A table containing different test approaches, testing techniques and test types that are required depending on the Automotive Safety Integrity Level ASIL and on the context of the test object. Methodical Test Strategy. A test strategy whereby the test team uses a pre-determined set of test conditions such as a quality standard, a checklist, or a collection of generalized, logical test conditions which may relate to a particular domain, application or type of testing.

A point in time in a project at which defined intermediate deliverables and results should be ready. Mind Map. A diagram arranged around a general theme that represents ideas, tasks, words or other items. Model Coverage. The degree, expressed as a percentage, to which model elements are planned to be or have been exercised by a test suite.

Model in the Loop. Dynamic testing performed using a simulation model of the system in a simulated environment. Model-Based Test Strategy. Model-Based Testing. Modeling Tool. A tool that supports the creation, amendment, and verification of models of the component or system.

The degree to which a component or system can be changed without introducing defects or degrading existing product quality. Modified Multiple Condition Coverage. Modified Multiple Condition Testing. The degree to which a system is composed of discrete components such that a change to one component has minimal impact on other components. Module Testing. Monitoring Tool. Multiple heterogeneous, distributed systems that are embedded in networks at multiple levels and in multiple interconnected domains, addressing large-scale inter-disciplinary common problems and purposes, usually without a common management structure.

Multiplayer Testing. Testing to determine if many players can simultaneously interact with the casino game world, with computer-controlled opponents, game servers, and with each other, as expected according to the game design. Multiple Condition. Multiple Condition Coverage.

Multiple Condition Testing. Myers-Briggs Type Indicator. An indicator of psychological preference representing the different personalities and communication styles of people. N-Switch Coverage. Negative Testing. Neighborhood Integration Testing. A form of integration testing where all of the nodes that connect to a given node are the basis for the integration testing. Network Zone.

A sub-network with a defined level of trust. For example, the Internet or a public zone would be considered to be untrusted. Non-Functional Testing.

Testing the attributes of a component or system that do not relate to functionality, e. The degree to which actions or events can be proven to have taken place, so that the actions or events cannot be repudiated later.

Off-the-Shelf Software. Offline MBT. Model-based test approach whereby test cases are generated into a repository for future execution. On-the-Fly MBT. Online MBT. Open-Source Tool. A software tool that is available to all potential users in source code form, usually via the internet. Its users are permitted, usually under license, to study, change, improve and, at times, to distribute the software. A system in which controlling action or input is independent of the output or changes in output.

Operational Acceptance Testing. Operational Environment. Operational Profile. The representation of a distinct set of tasks performed by the component or system, possibly based on user behavior when interacting with the component or system, and their probabilities of occurrence.

A task is logical rather that physical and can be executed over several machines or be executed in non-contiguous time segments. Operational Profiling. Operational Testing. A source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system for a benchmark , other software, a user manual, or an individual's specialized knowledge, but should not be the code.

Organizational Test Policy. A high-level document describing the principles, approach and major objectives of the organization regarding testing. Organizational Test Strategy.

A high-level description of the test levels to be performed and the testing within those levels for an organization or programme one or more projects. Orthogonal Array. A 2-dimensional array constructed with special mathematical properties, such that choosing any two columns in the array provides every pair combination of each number in the array.

Orthogonal Array Testing. A systematic way of testing all-pair combinations of variables using orthogonal arrays. It significantly reduces the number of all combinations of variables to test all pair combinations. A variable whether stored within a component or outside that is written by a component. Outsourced Testing. Testing performed by people who are not co-located with the project team and are not fellow employees.

Pacing Time. Pair Programming. This implicitly means ongoing real-time code reviews are performed. Pair Testing. An approach in which two team members simultaneously collaborate on testing a work product. Pairwise Integration Testing.

A form of integration testing that targets pairs of components that work together, as shown in a call graph. Pairwise Testing. A black-box test design technique in which test cases are designed to execute all possible discrete combinations of each pair of input parameters. Par Sheet Testing. Testing to determine that the game returns the correct mathematical results to the screen, to the players' accounts, and to the casino account.

Pareto Analysis. A statistical technique in decision making that is used for selection of a limited number of factors that produce significant overall effect. Partition Testing. Password Cracking. A security attack recovering secret passwords stored in a computer system or transmitted over a network. Path Coverage. Path Testing.

Peak Load. Peer Review. A review of a software work product by colleagues of the producer of the product for the purpose of identifying defects and improvements. Examples are inspection, technical review and walkthrough.

Penetration Testing. A testing technique aiming to exploit security vulnerabilities known or unknown to gain unauthorized access. The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate. Performance Efficiency. The degree to which a component or system uses time, resources and capacity when accomplishing its designated functions. Performance Indicator. Performance Testing.

Performance Testing Tool. A test tool that generates load for a designated test item and that measures and records its performance during test execution. Perspective-Based Reading. A review technique whereby reviewers evaluate the work product from different viewpoints. Perspective-Based Reviewing.

A security attack intended to redirect a web site's traffic to a fraudulent web site without the user's knowledge or consent. Phase Containment. The percentage of defects that are removed in the same phase of the software lifecycle in which they were introduced.

An attempt to acquire personal or sensitive information by masquerading as a trustworthy entity in an electronic communication. Planning Poker. A consensus-based estimation technique, mostly used to estimate effort or relative size of user stories in Agile software development. It is a variation of the Wideband Delphi method using a deck of cards with values representing the units in which the team estimates.

Player Perspective Testing. Testing done by testers from a player's perspective to validate player satisfaction. The ease with which the software product can be transferred from one hardware or software environment to another. Portability Testing. Post-Project Meeting. A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project.

Post-Release Testing. A type of testing to ensure that the release is performed correctly and the application can be deployed. Environmental and state conditions that must be fulfilled after the execution of a test or test procedure. Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure. Predicted Outcome. A systematic approach to risk-based testing that employs product risk identification and analysis to create a product risk matrix based on likelihood and impact.

Probe Effect. The effect on the component or system by the measurement instrument when the component or system is being measured, e. For example performance may be slightly worse when performance testing tools are being used. Process Assessment. A disciplined evaluation of an organization's software processes against a reference model.

Process Improvement. A program of activities designed to improve the performance and maturity of the organization's processes, and the result of such a program. Process Model. A framework in which processes of the same nature are classified into an overall model. Process Reference Model. A process model providing a generic body of best practices and how to improve a process in a prescribed step-by-step manner.

Process-Compliant Test Strategy. A test strategy whereby the test team follows a set of predefined processes, whereby the processes address such items as documentation, the proper identification and use of the test basis and test oracle s , and the organization of the test team.

Process-Driven Scripting. A scripting technique where scripts are structured into scenarios which represent use cases of the software under test. The scripts can be parameterized with test data.

Product Risk. Product-Based Quality. A view of quality, wherein quality is based on a well-defined set of quality attributes. These attributes must be measured in an objective and quantitative way. Differences in the quality of products of the same type can be traced back to the way the specific quality attributes have been implemented. Production Acceptance Testing.

A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements, including the constraints of time, cost and resources.

Project Retrospective. A structured way to capture lessons learned and to create specific action plans for improving on the next project or next project phase. Project Risk. A risk related to management and control of the test project, e.

A set of conventions that govern the interaction of processes, devices, and other components within a system. Proximity-Based Testing. A type of testing to confirm that sensors can detect nearby objects without physical contact. A series which appears to be random but is in fact generated according to some prearranged sequence. The process of demonstrating the ability to fulfill specified requirements.

Note the term "qualified" is used to designate the corresponding status. Quality Assurance. Part of quality management focused on providing confidence that quality requirements will be fulfilled. Quality Attribute. Quality Characteristic. Quality Control. Quality Function Deployment.

Agree, remarkable download synergy for free apologise, but

Large can is it will desktop complicated for is categories key been category for and FortiAP. The Arizona which should should used. You CRM from.

It is an industry practice when a high frequency of build releases occurs e. See also regression testing, smoke test. It shows the status and trend of completing the tasks of the iteration. The X-axis typically represents days in the sprint, while the Y-axis is the remaining effort usually either in ideal engineering hours or story points.

C call graph: An abstract representation of calling relationships between subroutines in a program. The Capability Maturity Model Integration. These tools are often used to support automated regression testing. See also test automation. EITP causal analysis: The analysis of defects to determine their root cause.

EITP cause-effect diagram: A graphical representation used to organize and display the interrelationships of various possible root causes of a problem. Possible causes of a real or potential defect or failure are organized in categories and subcategories in a horizontal tree-structure, with the potential defect or failure as the root node. ATA cause-effect graphing: A black box test design technique in which test cases are designed from cause-effect graphs.

EITP change management: 1 A structured approach to transitioning individuals, and organizations from a current state to a desired future state. See also configuration management. ATT changeability: The capability of the software product to enable specified modifications to be implemented. ATA checklist-based testing: An experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified.

Chow's coverage metrics: See N-switch coverage. See also classification tree method. ATA classification tree method: A black box test design technique in which test cases, described by. F code coverage: An analysis method that determines which parts of the software have been executed.

EITP codependent behavior: Excessive emotional or psychological dependence on another person,. For example, in software testing, complaining about late delivery to test and yet enjoying the necessary heroism working additional hours to make up time when delivery is running late, therefore reinforcing the lateness. ATT co-existence: The capability of the software product to co-exist with other independent software in a common environment sharing common resources.

ATA combinatorial testing: A means to identify a suitable subset of test combinations to achieve a predetermined level of coverage when testing an object with multiple parameters and where those parameters themselves each have several values, which gives rise to more combinations than are feasible to test in the time allowed.

See also classification tree method, n-wise testing, pairwise testing, orthogonal array testing. F compiler: A software tool that translates programs expressed in a high order language into their machine language equivalents.

See also cyclomatic complexity. F component testing: The testing of individual software components. See also condition testing. ATT condition testing: A white box test design technique in which test cases are designed to execute condition outcomes. ETM confidence interval: In managing project risks, the period of time within which a contingency action must be implemented in order to be effective in reducing the impact of the risk.

F-AT configuration item: An aggregation of hardware, software or both, that is designated for configuration management and treated as a single entity in the configuration management process. F configuration management: A discipline applying technical and administrative direction and F-AT surveillance to: identify and document the functional and physical characteristics of a configuration.

F configuration management tool: A tool that provides support for the identification and control of configuration items, their status over changes and versions, and the release of baselines consisting of configuration items. F confirmation testing: Testing that runs test cases that failed the last time they were run, in order to. EITP content-based model: A process model providing a detailed description of good engineering practices, e.

EITP continuous representation: A capability maturity model structure wherein capability levels provide a recommended order for approaching process improvement within specified process areas. ETM control chart: A statistical process control tool used to monitor a process and determine whether it is statistically controlled. It graphically depicts the average value and the upper and lower control limits the highest and lowest values of a process. F control flow: A sequence of events paths in the execution through a component or system.

ATT control flow analysis: A form of static analysis based on a representation of unique paths. Control flow analysis evaluates the integrity of control flow structures, looking for possible control flow anomalies such as closed loops or logically unreachable process steps.

ATT control flow testing: An approach to structure-based testing in which test cases are designed to. Various techniques exist for control flow testing, e. See also decision testing, condition testing, path testing. ETM convergence metric: A metric that shows progress toward a defined criterion, e. EITP corporate dashboard: A dashboard-style representation of the status of corporate performance data.

See also balanced scorecard, dashboard. See off-the-shelf software. ETAE coverage: The degree, expressed as a percentage, to which a specified coverage item has been. F coverage tool: A tool that provides objective measures of what structural elements, e. EITP critical success factor: An element necessary for an organization or project to achieve its mission.

Critical success factors are the critical factors or activities required for ensuring the success. These include highly visible processes, by which peers and. See also content-based model. ATM custom tool: A software tool developed specifically for a set of users or customers. ATT cyclomatic complexity: The maximum number of linear, independent paths through a program.

ETM dashboard: A representation of dynamic measurements of operational performance for some. F data-driven testing: A scripting technique that stores test input and expected results in a ATT table or spreadsheet, so that a single control script can execute all of the tests in the table.

ETAE Data-driven testing is often used to support the application of test execution tools such as. F data flow: An abstract representation of the sequence and possible changes of the state of data. See also path. F debugging: The process of finding, analyzing and removing the causes of failures in software.

F debugging tool: A tool used by programmers to reproduce failures, investigate the state of ATT programs and find the corresponding defect. Debuggers enable programmers to execute programs. A node with two or more links to separate branches. ATT decision condition testing: A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes. F decision coverage: The percentage of decision outcomes that have been exercised by a test suite.

F defect: A flaw in a component or system that can cause the component or system to fail to ATM perform its required function, e. A defect, if encountered. ATA defect-based technique: See defect-based test design technique. See also defect taxonomy. F defect density: The number of defects identified in a component or system divided by the size of the.

See also escaped defects. It involves recording defects, classifying them and identifying the impact. ATM defect management committee: A cross-functional team of stakeholders who manage reported defects from initial detection to ultimate resolution defect removal, defect deferral, or report cancellation.

In some cases, the same team as the configuration control board. See also configuration control board. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities. See also incident management tool. F-AT defect taxonomy: A system of hierarchical categories designed to be a useful aid for ATA reproducibly classifying defects.

ATM defect triage committee: See defect management committee. Defect taxonomies can be identified with respect to. ATT definition-use pair: The association of a definition of a variable with the subsequent use of that variable.

Variable uses include computational e. EITP Deming cycle: An iterative four-step problem-solving process, plan-do-check-act , typically used in process improvement. See also static testing. The diagnosing phase consists of the activities: characterize current and desired states and develop recommendations. ATA domain analysis: A black box test design technique that is used to identify efficient and effective test cases when multiple variables can or should be tested together.

It builds on and generalizes equivalence partitioning and boundary values analysis. See also boundary value analysis, equivalence partitioning. These tools are most commonly used to identify unassigned pointers, check pointer arithmetic and to monitor the allocation, use and de-allocation of memory and to flag memory leaks.

E ATM effectiveness: The capability of producing an intended result. See also efficiency. ATM efficiency: 1 The capability of the software product to provide appropriate performance, ATT relative to the amount of resources used under stated conditions. EITP EFQM European Foundation for Quality Management excellence model: A non-prescriptive framework for an organisation's quality management system, defined and owned by the European Foundation for Quality Management, based on five 'Enabling' criteria covering what an organisation does , and four 'Results' criteria covering what an organisation achieves.

In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations. EITP emotional intelligence: The ability, capacity, and skill to identify, assess, and manage the emotions of one's self, of others, and of groups. F entry criteria: The set of generic and specific conditions for permitting a process to go forward with a.

The purpose of entry criteria is to prevent a task from starting which would entail more wasted effort compared to the effort needed to remove the failed entry criteria. F equivalence partitioning: A black box test design technique in which test cases are designed ATA to execute representatives from equivalence partitions.

In principle test cases are designed to. ETAE equivalent manual test effort: Effort required for running tests manually. F error: A human action that produces an incorrect result. See also Defect Detection Percentage. The establishing phase consists of the activities: set priorities, develop approach and plan actions. F exhaustive testing: A test approach in which the test suite comprises all combinations of input values. F exit criteria: The set of generic and specific conditions, agreed upon with the stakeholders ATM for permitting a process to be officially completed.

The purpose of exit criteria ATA is to prevent a task from being considered completed when there are still outstanding parts of the. Exit criteria are used to report against and to plan when to stop testing. ATA experience-based technique: See experience-based test design technique. F exploratory testing: An informal test design technique where the tester actively controls the F-AT design of the tests as those tests are performed and uses information gained while testing to ATA design new and better tests.

See also agile software development. See also alpha testing. Following a failure, the failover mechanism is tested to ensure that data is not lost or corrupted and that any agreed service levels are maintained e. See also recoverability testing. F failure: Deviation of the component or system from its expected delivery, service or result.

ATM [After Fenton]. For example, a system in failure mode may be characterized by slow operation, incorrect outputs, or complete termination of execution.

The result highlights failure modes with relatively high probability and severity of consequences, allowing remedial effort to be directed where it will produce the greatest value.

F failure rate: The ratio of the number of failures of a given category to a given unit of measure, e. ATM false-fail result: A test result in which a defect is reported although no such defect actually exists in the test object.

ATM false-negative result: See false-pass result. ATM false-pass result: A test result which fails to identify the presence of a defect that is actually present. ATM false-positive result: See false-fail result. F fault: See defect. F fault attack: See attack. Fault injection intended to mimic failures that might occur in the field. See also fault tolerance. Fault seeding is typically part of development pre-release testing and can be performed at any test level component, integration, or system.

ATT fault seeding tool: A tool for seeding i. The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose. ETM feature-driven development: An iterative and incremental software development process driven from a client-valued functionality feature perspective.

Feature-driven development is mostly used in agile software development. F field testing: See beta testing. F formal review: A review characterized by documented procedures and requirements, e. See also baseline. The measurement is independent of the technology. This measurement may be used as a basis for the measurement of productivity, the estimation of the needed resources, and project control.

F functional requirement: A requirement that specifies a function that a component or system must perform. See also black box test design technique. F functional testing: Testing based on an analysis of the specification of the functionality of a component or system. See also black box testing. G ETAE generic test automation architecture: Representation of the layers, components, and interfaces of a. H hardware-software integration testing: Testing performed to expose defects in the interfaces and.

The result of a hazard analysis will drive the methods used for development and testing of a system. See also risk analysis. ATA heuristic evaluation: A usability review technique that targets usability problems in the user interface or user interface design.

With this technique, the reviewers examine the interface and judge its compliance with recognized usability principles the "heuristics". ATA high level test case: A test case without concrete implementation level values for input data and expected results. See also low level test case. ATT hyperlink test tool: A tool used to check that no broken hyperlinks are present on a web site.

The IDEAL model is named for the five phases it describes: initiating, diagnosing, establishing, acting, and learning. F impact analysis: The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements. F incident: Any event occurring that requires investigation.

F incident management: The process of recognizing, investigating, taking action and disposing of. It involves logging incidents, classifying them and identifying the impact. F incident management tool: A tool that facilitates the recording and status tracking of incidents.

They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of incidents and provide reporting facilities. See also defect management tool. F incident report: A document reporting on any event that occurred, e. F incremental development model: A development lifecycle where a project is broken into a F-AT series of increments, each of which delivers a portion of the functionality in the overall project.

The requirements are prioritized and delivered in priority order in the appropriate increment. In some but not all versions of this lifecycle model, each subproject follows a mini V-model with its own design, coding and testing phases.

F independence of testing: Separation of responsibilities, which encourages the ATM accomplishment of objective testing. F informal review: A review not based on a formal documented procedure. The initiating phase consists of the activities: set context, build sponsorship and charter infrastructure. See also domain. See also input. F inspection: A type of peer review that relies on visual examination of documents to detect ATM defects, e.

The most formal review technique and therefore always based on a documented procedure. See also portability. See also portability testing.

This may be a manual guide, step-by-step procedure, installation wizard, or any other similar process description. It normally runs the installation process, provides feedback on installation results, and prompts for options.

An intake test is typically carried out at the start of the test execution phase. See also smoke test. F integration: The process of combining components or systems into larger assemblies.

F integration testing: Testing performed to expose defects in the interfaces and in the interactions. See also component integration testing, system integration testing. F interoperability testing: The process of testing to determine the interoperability of a ATA software product. See also functionality testing. See also error tolerance, negative testing. ETM Ishikawa diagram: See cause-effect diagram.

F iterative development model: A development lifecycle where a project is broken into a F-AT usually large number of iterations. An iteration is a complete development loop resulting in a. F keyword-driven testing: A scripting technique that uses data files to contain not only test ATA data and expected results, but also keywords related to the application being tested.

See also data-driven testing. EITP lead assessor: The person who leads an assessment. See also low level test case. I IDEAL: An organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions. The IDEAL model is named for the five phases it describes: initiating, diagnosing, establishing, acting, and learning impact analysis: The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.

It involves logging incidents, classifying them and identifying the impact. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of incidents and provide reporting facilities. See also defect management tool. The requirements are prioritized and delivered in priority order in the appropriate increment. The initiating phase consists of the activities: set context, build sponsorship and charter infrastructure.

See also domain. See also input. The most formal review technique and therefore always based on a documented procedure. See also portability. See also portability testing. This may be a manual guide, step-by-step procedure, installation wizard, or any other similar process description. It normally runs the installation process, provides feedback on installation results, and prompts for options.

An intake test is typically carried out at the start of the test execution phase. See also smoke test. See also component integration testing, system integration testing. See also functionality testing.

See also error tolerance, negative testing. Ishikawa diagram: See cause-effect diagram. An iteration is a complete development loop resulting in a release internal or external of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product. K key performance indicator: See performance indicator. The keywords are interpreted by special supporting scripts that are called by the control script for the test.

See also data driven testing. L LCSAJ: A Linear Code Sequence And Jump, consists of the following three items conventionally identified by line numbers in a source code listing : the start of the linear sequence of executable statements, the end of the linear sequence, and the target line to which control flow is transferred at the end of the linear sequence. In some cases, for instance CMMi and TMMi when formal assessments are conducted, the lead-assessor must be accredited and formally trained.

The learning phase consists of the activities: analyze and validate, and propose future actions. See also test plan. A load profile consists of a designated number of virtual users who process a defined set of transactions in a specified time period and according to a predefined operational profile.

See also operational profile. See also performance testing, stress testing. Logical operators from high level test cases are replaced by actual values that correspond to the objectives of the logical operators. See also high level test case. M maintainability: The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or adapted to a changed environment.

Quality arises from the process es used. A maturity model often provides a common language, shared vision and framework for prioritizing improvement actions. Mean Time Between Failures: The arithmetic mean average time between failures of a system. The MTBF is typically part of a reliability growth model that assumes the failed system is immediately repaired, as a part of a defect fixing process.

See also reliability growth model. Mean Time To Repair: The arithmetic mean average time a system will take to recover from any failure. This typically includes testing to insure that the defect has been resolved. Mind maps are used to generate, visualize, structure, and classify ideas, and as an aid in study, organization, problem solving, decision making, and writing. O off-the-shelf software: A software product that is developed for the general market, i.

See also operational testing. The software may include operating systems, database management systems, and other applications. A task is logical rather that physical and can be executed over several machines or be executed in non-contiguous time segments. It significantly reduces the number of all combinations of variables to test all pair combinations. See also pairwise testing. See also output. This implicitly means ongoing real-time code reviews are performed.

Typically, they share one computer and trade control of it while testing. See also orthogonal array testing. Pareto analysis: A statistical technique in decision making that is used for selection of a limited number of factors that produce significant overall effect. Examples are inspection, technical review and walkthrough. Profiles should reflect anticipated or actual usage based on an operational profile of a component or system, and hence the expected workload.

See also load profile, operational profile. See also efficiency testing. Load generation can simulate either multiple users or high volumes of input data.

Performance testing tools normally provide reports based on test logs and graphs of load against response times. For example performance may be slightly worse when performance testing tools are being used.

These attributes must be measured in an objective and quantitative way. Differences in the quality of products of the same type can be traced back to the way the specific quality attributes have been implemented. See also risk. Q qualification: The process of demonstrating the ability to fulfill specified requirements. Quality gates are located between those phases of a project strongly depending on the outcome of a previous phase.

A quality gate includes a formal check of the documents of the previous phase. Direction and control with regard to quality generally includes the establishment of the quality policy and quality objectives, quality planning, quality control, quality assurance and quality improvement. This technique can be used for testing non-functional attributes such as reliability and performance.

Rational Unified Process: A proprietary adaptable iterative software development process framework consisting of four project lifecycle phases: inception, elaboration, construction and transition. See also reliability testing. It is performed when the software or its environment is changed. Some requirements management tools also provide facilities for static analysis, such as consistency checking and violations to pre-defined requirements rules. It includes outputs to screens, changes to data, reports, and communication messages sent out.

See also actual result, expected result. Examples include management review, informal review, technical review, inspection, and walkthrough. Typical features include review planning and tracking support, communication support, collaborative reviews and a repository for collecting and reporting of metrics.

Reviewers can be chosen to represent different viewpoints and roles in the review process. It involves the identification of product risks and the use of risk levels to guide the test process. The level of risk can be used to determine the intensity of testing to be performed. A risk level can be expressed either qualitatively e. A specific set of product risk types is related to the type of testing that can mitigate control that risk type. For example the risk of user- interactions being misunderstood can be mitigated by usability testing.

By directing corrective measures at root causes, it is hoped that the likelihood of defect recurrence will be minimized. S safety: The capability of the software product to achieve acceptable levels of risk of harm to people, business, software, property or the environment in a specified context of use.

A scorecard provides static measurements of performance over or at the end of a defined interval. The scribe should ensure that the logging form is readable and understandable.

SCRUM: An iterative incremental framework for managing projects commonly used with agile software development. A daily build and smoke test is among industry best practices. See also intake test. The software lifecycle typically includes a concept phase, requirements phase, design phase, implementation phase, test phase, installation and checkout phase, operation and maintenance phase, and sometimes, retirement phase.

Note these phases may overlap or be performed iteratively. Software Usability Measurement Inventory SUMI : A questionnaire-based usability test technique for measuring software quality from the end user's point of view.

See also N-switch testing. Static analysis is usually carried out by means of a supporting tool. The tool checks source code, for certain properties such as conformance to coding standards, quality metrics or data flow anomalies.

See also operational profile testing. This information includes a listing of the approved configuration identification, the status of proposed changes to the configuration, and the implementation status of the approved changes. It replaces a called component. Electronic Data Interchange, Internet. T technical review: A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken.

The documentation on which the test cases are based. If a document can be amended only by way of formal amendment procedure, then the test basis is called a frozen test basis. Test charters are used in exploratory testing. See also exploratory testing. The test closure phase consists of finalizing and archiving the testware and evaluating the test process, including preparation of a test evaluation report.

See also test process. Test comparison can be performed during test execution dynamic comparison or after test execution. See also test management. See also deliverable.

It also contains an evaluation of the test process and lessons learned. The test procedures are included in the test execution schedule in their context and in the order in which they are to be executed.

The external source can be hardware, software or human. There usually is one test object and many test items. See also test object. A test level is linked to the responsibilities in a project.

Examples of test levels are component test, integration test, system test and acceptance test. It often has several capabilities, such as testware management, scheduling of tests, the logging of results, progress tracking, incident management and test reporting.

The individual who directs, controls, administers, plans and regulates the evaluation of a test object. Reports are prepared that compare the actuals to that which was planned. See also test item. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning.

It is a record of the test planning process. Also known as test script or manual test script. Test Process Group: A collection of test specialists who facilitate the definition, maintenance, and improvement of the test processes used by an organization. The values are: - flexibility over detailed processes - best Practices over templates - deployment orientation over process orientation - peer reviews over quality assurance departments - business driven over model driven.

The tester creates and executes test cases on the fly and records their progress. It also contains an evaluation of the corresponding test items against exit criteria. A test type may take place on one or more test levels or test phases. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested. Total Quality Management: An organization-wide management approach centered on quality, based on the participation of all its members and aiming at long-term success through customer satisfaction, and benefits to all members of the organization and to society.

Total Quality Management consists of planning, organizing, directing, control, and assurance. See also horizontal traceability, vertical traceability. Quality depends on the perception and affective feelings of an individual or group of individuals towards a product.

U understandability: The capability of the software product to enable the user to understand whether the software is suitable, and how it can be used for particular tasks and conditions of use.

It also provides other support for the developer, such as debugging capabilities. A product or service that does not fulfill user needs is unlikely to find any users. This is a context dependent, contingent approach to quality since different business characteristics require different qualities of a product. V V-model: A framework to describe the software development lifecycle activities from requirements specification to maintenance.

The V-model illustrates how testing activities can be integrated into each phase of the software development lifecycle. A quality product or service is one that provides desired performance at an acceptable cost. Quality is determined by means of a decision process with stakeholders on trade-offs between time, effort and cost aspects.

See also resource-utilization testing. W walkthrough: A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content. Wide Band Delphi: An expert based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members. See also pointer. Work Breakdown Structure: An arrangement of work elements and their relationship to each other and to the end product.

Adrion, M. Branstad and J. Bach , Exploratory Testing, in: E. Paulk, C. Weber, B. Curtis and M. Chrissis, M. Konrad and S. Fewster and D. Freedman and G. Garvin , What does product quality really mean?

Gerrard and N. Gilb and D. Graham, E. Evans and R. Pol, R. Teunissen, E. You can submit comments in a variety of ways, which in order of preference are as follows: 1.