Page 296 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING
P. 296
Principles of Software Engineering
Notes 7. Software testing is the process of checking ………, to verify that it satisfies its requirements
and to detect errors.
(a) software (b) hardware
(c) programs (d) testing
8. Using software monitors to determine that the program code is effectively ………..
(a) used (b) unused
(c) detection (d) system
9. …………..executes a system in a manner that demands resources in abnormal quantity,
frequency, or volume.
(a) Security testing (b) Function testing
(c) Stress testing (d) System testing
10. …………. components are combined into clusters (sometimes called builds) that perform
a specific software sub function.
(a) Low-level (b) Middle-level
(c) High-level (d) Any-level
11. Tests of data flow across a module interface are required before any other initiated. If data
do not enter and ………… all other tests are moot.
(a) check properly (b) testing properly
(c) design properly (d) exit properly
12. Unit testing is normally considered as an adjunct to the………….step.
(a) editing (b) coding
(c) reading (d) deleting
13. Conducting periodic…………. status meetings in which each team member reports progress
and problems.
(a) testing (b) design
(c) project (d) process
14. In the late 1960s, a bright-eyed young engineer was chosen to ………….. a computer
program for an automated manufacturing application.
(a) read (b) write
(c) return (d) test
15. Integration testing is a systematic technique for constructing the program ………. while
at the same time conducting tests to uncover errors associated with facing.
(a) True (b) False
290 LOVELY PROFESSIONAL UNIVERSITY