Unlock document.
This document is partially blurred.
Unlock all pages and 1 million more documents.
Get Access
Essentials of Systems Analysis and Design, 6e (Valacich)
Chapter 10 Systems Implementation and Operation
1) The implementation and operation phase of the systems development life cycle is the most
expensive and time-consuming phase of the entire life cycle.
Classification: Concept
2) Analysis is one of the seven major activities associated with systems implementation and
operation.
Classification: Concept
3) The systems administration plan answers such questions as when and where the new system
will be installed, what people and resources are required, which data will be converted and
cleansed, and how long the installation process will take.
Classification: Application
4) Information systems personnel and end users are the two audiences for the final systems
documentation.
Classification: Concept
5) Transforming requests into changes is a major maintenance activity.
Classification: Concept
1
6) The systems planning and selection phase of the SDLC is analogous to the maintenance
process of transforming requests into a specific system change.
Classification: Concept
7) The systems analysis phase of the SDLC is analogous to the maintenance process of obtaining
maintenance requests.
Classification: Concept
8) The systems design phase of the SDLC is analogous to the maintenance process of designing
changes.
Classification: Concept
9) The systems implementation and operation phase of the SDLC is analogous to the
maintenance process of implementing changes.
Classification: Concept
10) During systems design, an overall test plan is developed.
Classification: Concept
11) Testing specialists are responsible for developing test plans, establishing testing standards,
integrating testing and development activities in the life cycle, and ensuring that test plans are
completed.
Classification: Concept
2
12) During an inspection test, exactly what the code does is investigated.
Classification: Concept
13) Unit testing does not require automated code execution.
Classification: Concept
14) Walkthroughs are a very effective method for identifying errors in code.
Classification: Concept
15) The purpose of a walkthrough is to identify and correct errors found in programming code.
Classification: Concept
16) Desk checking is a testing technique in which the program code is sequentially executed
manually by the reviewer.
Classification: Concept
17) A systems analyst or programmer typically does syntax checking.
Classification: Concept
3
18) Integration testing brings together all of the programs that a system comprises for testing
purposes.
Classification: Concept
19) Unit testing is a technique used in examining individual lines of code, where a few lines of
code are used to substitute for subordinate modules.
Classification: Concept
20) System testing is the process of bringing together all of the modules that a program
comprises for testing purposes.
Classification: Concept
21) A test case is a specific scenario of transactions, queries, or navigation paths that represent a
typical, critical, or abnormal use of the system.
Classification: Concept
22) The people who create the test cases should be the same people who have coded and will test
the system.
Classification: Concept
23) During alpha testing, users test a completed information system using simulated data.
Classification: Concept
4
24) During beta testing, users test a completed information system using real data in the real user
environment.
Classification: Concept
25) During recovery testing, the analysts try to break the system.
Classification: Concept
26) During stress testing, the analysts try to determine how the system performs on the range of
possible environments on which it may be used.
Classification: Concept
27) The purpose of alpha testing is to determine whether the software, documentation, technical
support, and training activities work as intended.
Classification: Concept
28) Installation is the organizational process of changing over from the current information
system to a new one.
Classification: Concept
29) A risk associated with the direct installation approach is that not all aspects of the new
system can be compared to the old system.
Classification: Concept
5
30) The coexistence of the old and new systems is characteristic of the parallel installation
approach.
Classification: Concept
31) A positive aspect of the phased installation approach is that learning can occur and problems
can be fixed by concentrating on one site.
Classification: Concept
32) A positive aspect of the phased installation approach is that it limits potential harm and costs
from system error or failure to certain business activities or functions.
Classification: Concept
33) A risk associated with the parallel installation approach is that there may be a delay until
benefits result.
Classification: Concept
34) A positive aspect of the direct installation approach is that there is a high interest in making
installation a success.
Classification: Concept
35) System documentation is the detailed information about a system's design specifications, its
internal workings, and its functionality.
Classification: Concept
6
36) Internal documentation is system documentation that includes the outcome of structured
diagramming techniques such as data flow and entity-relationship diagrams.
Classification: Concept
37) Today's environment makes it possible to maintain and update external documentation as
long as desired.
Classification: Concept
38) A system administrator's guide is an example of external system documentation.
Classification: Concept
39) A release description is an example of user documentation.
Classification: Concept
40) The purpose of a reference guide is to provide information on how users can use computer
systems to perform specific tasks.
Classification: Concept
41) User documentation is now most often delivered in hypertext format.
Classification: Concept
7
42) Training and support are not critical for the success of an information system.
Classification: Concept
43) All user training must be done as a formal course.
Classification: Concept
44) An electronic performance support system is a component of a software package with
training and education information embedded.
Classification: Concept
45) Many organizations are deploying Web-based push systems to provide a way to track support
requests.
Classification: Concept
46) A helpdesk is a single point of contact for all user problems and inquiries about a particular
system.
Classification: Concept
47) Post-project reviews are part of the system design phase.
Classification: Concept
8
48) The extent to which a system is used and the user's satisfaction with the system are the two
most common and trusted ways to determine if an implementation has been a success.
Classification: Concept
49) Preventive maintenance requires the least maintenance effort.
Classification: Concept
50) The number of customers for a given system influences most of the costs associated with
maintaining a system.
Classification: Concept
51) The mean time between failures is a measurement of error occurrences that can be tracked
over time to indicate the quality of a system.
Classification: Concept
52) Managing maintenance requests is a maintenance activity.
Classification: Concept
53) Build routines are software modules that have been tested, documented, and approved to be
included in the most recently created version of a system.
Classification: Concept
9
54) Baseline routines are guidelines that list the instructions to construct an executable system
from the baseline source code.
Classification: Concept
55) A primary objective of using automated tools for systems development and maintenance is to
change radically how code and documentation are modified and updated.
Classification: Concept
56) Reverse engineering and reengineering tools are primarily used to maintain older systems
that have incomplete documentation or that were developed prior to automated tools.
Classification: Concept
57) The process whereby the physical design specifications created by the design team are turned
into working computer code by the programming team is referred to as:
A) coding.
B) testing.
C) implementation.
D) code conversion.
E) production.
Classification: Concept
10
