58) The deliverables from the coding, testing, and installation processes include:
A) the creation of a document that will consolidate the information that must be considered when
implementing a physically distributed systems design.
B) structured descriptions and diagrams that outline the logic contained within each DFD
process.
C) the code, program documentation, test scenarios and test data, results of program and system
testing, user guides, user training plan, and an installation and conversion plan.
D) a database prototype.
E) the creation of an analysis plan.
Classification: Concept
59) A strategy for training users so they can quickly learn the new system is a(n):
A) training plan.
B) installation plan.
C) user guide.
D) training curriculum.
E) electronic performance support system.
Classification: Concept
60) Training on the use of the system begins during the early stages of:
A) the systems analysis phase.
B) logical design.
C) implementation.
D) the systems planning and selection phase.
E) physical design.
Classification: Concept
11
61) This plan lays out a strategy for moving from the old system to the new.
A) Systems service request
B) Installation plan
C) Training plan
D) Testing plan
E) Conversion guide
Classification: Concept
62) Activities occurring within maintenance include:
A) transforming changes into requests.
B) obtaining maintenance requests.
C) determining a steering committee.
D) marketing changes.
E) adding data definition language to database.
Classification: Concept
63) An overall test plan is developed during:
A) systems implementation.
B) systems analysis.
C) logical design.
D) physical design.
E) systems planning and selection.
Classification: Concept
12
64) Which of the following is the responsibility of testing managers?
A) Developing marketing plans
B) Integrating data and metadata
C) Establishing testing standards
D) Ensuring that trainees don’t pass
E) Requiring online testing
Classification: Concept
65) A testing technique in which participants examine program code for predictable language-
specific errors defines:
A) walkthrough.
B) inspections.
C) desk checking.
D) syntax checking.
E) integration testing.
Classification: Concept
66) The type of testing responsible for determining what the code does is:
A) a walkthrough.
B) inspection.
C) system testing.
D) syntax checking.
E) stub testing.
Classification: Concept
13
67) A testing technique in which the program code is sequentially executed manually by the
reviewer is referred to as:
A) inspection.
B) system testing.
C) desk checking.
D) syntax checking.
E) stub testing.
Classification: Concept
68) Testing each module alone in an attempt to discover any errors that may exist in the module’s
code is referred to as:
A) unit testing.
B) system testing.
C) stub testing.
D) singular testing.
E) a walkthrough.
Classification: Concept
69) The process of bringing together all of the modules that comprise a program for testing
purposes is referred to as:
A) unity testing.
B) integration testing.
C) system testing.
D) implementation.
E) stub testing.
Classification: Concept
14
70) The bringing together of all the programs that comprise a system for testing describes:
A) unity testing.
B) integration testing.
C) system testing.
D) implementation.
E) a project walkthrough.
Classification: Concept
71) A technique used in testing modules, especially where modules are written and tested in a
top-down fashion, where a few lines of code are used to substitute for subordinate modules
describes:
A) module testing.
B) unit testing.
C) top-down testing.
D) stub testing.
E) component-level testing.
Classification: Concept
72) The purpose of acceptance testing is to:
A) determine if new requirements must be added to the newly completed system.
B) determine if the system meets user requirements.
C) determine if the system meets its objectives.
D) test a completed information system using simulated data.
E) test a completed information system using real data.
Classification: Concept
15
73) The most complete acceptance testing will include:
A) alpha testing, beta testing, and a walkthrough.
B) beta testing, stub testing, and unit testing.
C) desk checking, a system audit, and integration testing.
D) a system audit, system testing, and integration testing.
E) alpha testing, beta testing, and a system audit.
Classification: Concept
74) The process whereby actual users test a completed information system, the end result of
which is the users’ acceptance of it, best defines:
A) acceptance testing.
B) alpha testing.
C) beta testing.
D) system testing.
E) end user testing.
Classification: Concept
75) User testing of a completed information system using simulated data refers to:
A) acceptance testing.
B) alpha testing.
C) beta testing.
D) system testing.
E) stub testing.
Classification: Concept
16
76) User testing of a completed information system using real data in the real user environment
refers to:
A) acceptance testing.
B) alpha testing.
C) beta testing.
D) system testing.
E) live testing.
Classification: Concept
77) Tests performed during alpha testing that are designed to try to break the system are:
A) stress tests.
B) performance tests.
C) recovery tests.
D) security tests.
E) stub tests.
Classification: Concept
78) The organizational process of changing over from the current information system to a new
one best defines:
A) reorganization.
B) physical design.
C) installation.
D) replacement.
E) system alteration.
Classification: Concept
17
79) Which of the following determines how the system performs on the range of possible
environments in which it may be used?
A) Performance testing
B) Recovery testing
C) Stress testing
D) Range testing
E) Security testing
Classification: Concept
80) Changing over from the old information system to a new one by turning off the old system as
the new one is turned on best describes:
A) phased installation.
B) single location installation.
C) parallel installation.
D) direct installation.
E) rotation installation.
Classification: Concept
81) System documentation that is part of the program source code or is generated at compile time
best defines:
A) system documentation.
B) user documentation.
C) internal documentation.
D) external documentation.
E) embedded documentation.
Classification: Concept
18