|
Integration Testing
This test begins after two or more programs or application components
have been successfully unit tested. It is conducted by the development
team to validate the interaction or communication/flow of information
between the individual components which will be integrated.
Life Cycle Testing
The process of verifying the consistency, completeness, and correctness
of software at each stage of the development life cycle.
Pass/Fail Criteria
Decision rules used to determine whether a software item or feature passes
or fails a test.
Path Testing
A test method satisfying the coverage criteria that each logical path
through the program be tested. Often, paths through the program are grouped
into a finite set of classes and one path from each class is tested.
Performance Test
Validates that both the online response time and batch run times meet
the
defined performance requirements.
Policy
Managerial desires and intents concerning either process (intended objectives)
or products (desired attributes).
Population Analysis
Analyzes production data to identify, independent from the specifications,
the types and frequency of data that the system will have to process/produce.
This verifies that the specs can handle types and frequency of actual
data and can be used to create validation tests.
Procedure
The step-by-step method followed to ensure that standards are met.
Process
1. The work effort that produces a product. This includes efforts of people
and equipment guided by policies, standards, and procedures.
2. A statement of purpose and an essential set of practices (activities)
that address that purpose.
Proof of Correctness
The use of mathematical logic techniques to show that a relationship between
program variables assumed true at program entry implies that another relationship
between program variables holds at program exit.
|