| Item |
Description |
| C A S T |
Computer Aided Software Testing |
| Capture / Playback Tool |
A test tool which records test input as it is sent to the software under test. The input cases stored can than be used to design test cases |
| Case-Based Reasoning (CBR) |
A problem-solving system that relies on stored representations of previously solved problems and their solutions. |
| Cause Effect Graph |
A graphical representation of inputs or stimuli (causes) with their associated outputs (effects), which can be used to design test cases |
| Cause Effect Graphing |
A test case design technique in which test cases are designed by consideration of cause effect graphs |
| Certainty processing |
Allowing confidence levels obtained from user input and rule conclusions to be combined to increase the overall confidence in the value assigned to an attribute. |
| Certification |
The process of confirming that a system or component complies with its specified requirements and is acceptable for operational use |
| Change Control |
The procedure to ensure that all changes are controlled, including the submission, analysis, decision making, approval, implementation and post implementation of the change. |
| Charter |
A statement of test objectives, and possibly test ideas. Test charters are amongst other used in exploratory testing. |
| Classes |
A category that generally describes a group of more specific items or objects. |
| Clause |
One expression in the If (premise) or Then (consequent) part of a rule. Often consists of an attribute name followed by a relational operator and an attribute value. |
| Code Coverage |
An analysis method that determines which parts have not been executed and therefore may require additional attention |
| Code based testing |
Designing tests based on objectives derived from implementation such as tests that execute specific control flow paths or use specific data items |
| Compatibility testing |
Testing whether the system is compatible with other systems with which it should communicate |
| Component |
A minimal software item for which a separate specification is available |
| Component Testing |
The testing of individual software components |
| Conclusion / Consequent |
The Then part of a rule, or one clause or expression in this part of the rule. |
| Condition |
A Boolean expression containing no Boolean operators. |
| Condition Outcome |
The evaluation of a condition to TRUE or FALSE |
| Confidence / Certainty factor |
A measure of the confidence assigned to the value of an attribute. Often expressed as a percentage (0 to 100%) or probability (0 to 1.0). 100% or 1.0 implies that the attribute's value is known with certainty. |
| Configuration Item (CI) |
Component of an infrastructure - or an item, such as a Request For Change, associated with an infrastructure - that is (or is to be) under the control of Configuration Management.
CIs may vary widely in complexity, size and type, from an entire system (including all hardware, software and documentation) to a single module or a minor hardware component. |
| Configuration Management |
The process of identifying and defining Configuration Items in a system.
e.g. recording and reporting the status of Configuration Items and Requests For Change, and verifying the completeness and correctness of Configuration Items. |
| Conformance Criterion |
Some method of judging whether or not the component's action on a particular specified input value conforms to the specification |
| Conformance Testing |
The process of testing that an implementation conforms to the specification on which it is based |
| Contingency Planning |
Planning to address unwanted occurrences that may happen at a later time. Traditionally, the term has been used to refer to planning for the recovery of IT systems rather than entire business processes. |
| Control Flow |
An abstract representation of all possible sequences of events in a program's execution |
| Control Flow Graph |
The diagrammatic representation of the possible alternative control flow paths through a component |
| Control information |
Elements of a knowledge base other than the attributes and rules that control the user interface, operation of the inference engine and general strategies employed in implementing a consultation with an expert system. |
| Conversion Testing |
Testing of programms or procedures used to convert data from existing systems for use in replacement systems |
| Correctness |
The degree to which software conforms to its specification |
| Coverage |
The degree, expressed as a percentage, to which a specific coverage item has been exercised by a test case suite |
| Coverage Item |
An entity or property used as a basis for testing |
| Critical Success Factor(CSF) |
A measure of success or maturity of a project or process. It can be a state, a deliverable or a milestone. An example of a CSF would be 'the production of an overall technology strategy'.
Key areas of business activity in which favourable results are necessary for a company to reach its goals. |
