5 Written questions
5 Matching questions
- LCSAJ testing
- fault density
- actual result
- software feature
- a See 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.g. lines-of-code, number of classes or function points).
- b A white box test design technique in which test cases are designed to execute LCSAJs.
- c See feature. An attribute of a component or system specified or implied by requirements documentation (for example reliability, usability or design constraints). [After IEEE 1008]
- d A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system. [After TMap]
- e The behavior produced/observed when a component or system is tested.
5 Multiple choice questions
- See component testing. The testing of individual software components. [After IEEE 610]
- 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. See also risk analysis. The process of assessing identified risks to estimate their impact and probability of occurrence (likelihood).
- The calculated approximation of a result (e.g. effort spent, completion date, costs involved, number of test cases, etc.) which is usable even if input data may be incomplete, uncertain, or noisy.
- See Failure Mode and Effect, and Criticality Analysis (FMECA). An extension of FMEA, as in addition to the basic FMEA, it includes a criticality analysis, which is used to chart the probability of failure modes against the severity of their consequences. 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 process of testing an integrated system to verify that it meets specified requirements. [Hetzel]
5 True/False questions
tester → Acronym for Computer Aided Software Engineering.
traceability → The degree to which a component or system is operational and accessible when required for use. Often expressed as a percentage. [IEEE 610]
static testing → Testing of a component or system at specification or implementation level without execution of that software, e.g. reviews or static code analysis.
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 occurance. A task is logical rather that physical and can be executed over several machines or be executed in non-contiguous time segments.
load profile → A specification of the activity which a component or system being tested may experience in production. 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. 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 occurance. A task is logical rather that physical and can be executed over several machines or be executed in non-contiguous time segments.