The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
It is artifacts created during testing process and required for planning, development and execution of tests.
A version of component integration testing, in which the progressive component integration follows the implementation of requirement subsets, as opposed to the component integration according to the levels of hierarchy.
A test estimation method using estimated values for the “best case”, “worst case”, and “most likely case” of the matter being estimated, to define the degree of certainty associated with the resultant estimate.
Incremental approach to integration testing, in which the component at the top of the component hierarchy is tested first with lower level components being replaced by stubs.
An organization-wide management approach centered on quality, based on the participation of all members of the organization and aiming at longterm success through customer satisfaction, and benefits to all members of the organization and to society.
It is the ability to identify related objects in documentation and software.
The analysis of transactions between people and within people’s minds; a transaction is defined as a stimulus plus a response.
The ability of a certain software to give a user a chance to draw a conclusion about the suitability of the product and how it can be used to perform specific tasks.
Tool that provides the environment for unit testing or component testing, in which can be tested in isolation and with the appropriate plugs and drivers.