Deck 10: Systems Implementation and Operation

Question 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.

Answer 1

True

Question 2

Desk checking is a testing technique in which the program code is sequentially executed manually by the reviewer.

Answer 2

True

Question 3

The systems planning and selection phase of the SDLC is analogous to the maintenance process of transforming requests into a specific system change.

Answer 3

False

Question 4

Information systems personnel and end users are the two audiences for the final systems documentation.

Question 5

Walkthroughs are a very effective method for identifying errors in code.

Question 6

Unit testing does not require automated code execution.

Question 7

The development of a new version of the software and new versions of all design documents are the major deliverables associated with the coding, testing, and installation stage.

Question 8

The systems implementation and operation phase of the SDLC is analogous to the maintenance process of implementing changes.

Question 9

Testing managers 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.

Question 10

The purpose of a walkthrough is to identify and correct errors found in programming code.

Question 11

The systems analysis phase of the SDLC is analogous to the maintenance process of obtaining maintenance requests.

Question 12

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.

Question 13

During an inspection test, exactly what the code does is investigated.

Question 14

Documentation is one of the seven major activities associated with systems implementation and operation.

Question 15

During systems design, an overall test plan is developed.

Question 16

Unit testing is 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.

Question 17

A systems analyst or programmer typically does syntax checking.

Question 18

The systems design phase of the SDLC is analogous to the maintenance process of designing changes.

Question 19

Transforming requests into changes is a major maintenance activity.

Question 20

Integration testing brings together all of the programs that a system comprises for testing purposes.

Question 21

A release description is an example of user documentation.

Question 22

Installation is the organizational process of changing over from the current information system to a new one.

Question 23

During stress testing, the analysts try to determine how the system performs on the range of possible environments on which it may be used.

Question 24

Internal documentation is system documentation that includes the outcome of structured diagramming techniques such as data flow and entity-relationship diagrams.

Question 25

Today's CASE environment makes it possible to maintain and update external documentation as long as desired.

Question 26

A positive aspect of the direct installation approach is that there is a high interest in making installation a success.

Question 27

A positive aspect of the phased installation approach is that learning can occur and problems can be fixed by concentrating on one site.

Question 28

During beta testing, users test a completed information system using real data in the real user environment.

Question 29

A test case is a specific scenario of transactions, queries, or navigation paths that represent a typical, critical, or abnormal use of the system.

Question 30

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.

Question 31

A risk associated with the direct installation approach is that not all aspects of the new system can be compared to the old system.

Question 32

System testing is the process of bringing together all of the modules that a program comprises for testing purposes.

Question 33

During alpha testing, users test a completed information system using simulated data.

Question 34

The coexistence of the old and new systems is characteristic of the parallel installation approach.

Question 35

The people who create the test cases should be the same people who have coded and will test the system.

Question 36

The purpose of alpha testing is to determine whether the software, documentation, technical support, and training activities work as intended.

Question 37

A system administrator's guide is an example of external system documentation.

Question 38

During recovery testing, the analysts try to break the system.

Question 39

System documentation is the detailed information about a system's design specifications, its internal workings, and its functionality.

Question 40

A risk associated with the parallel installation approach is that there may be a delay until benefits result.

Question 41

A helpdesk is a single point of contact for all user problems and inquiries about a particular system.

Question 42

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.

Question 43

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.

Question 44

Many organizations are deploying Web-based ticketing systems to provide a way to track support requests.

Question 45

Managing maintenance requests is a maintenance activity.

Question 46

Build routines are software modules that have been tested, documented, and approved to be included in the most recently created version of a system.

Question 47

User documentation is now most often delivered in hypertext format.

Question 48

The purpose of a reference guide is to provide information on how users can use computer systems to perform specific tasks.

Question 49

An electronic performance support system is a component of a software package with training and education information embedded.

Question 50

The mean time between failures is a measurement of error occurrences that can be tracked over time to indicate the quality of a system.

Question 51

The number of customers for a given system influences most of the costs associated with maintaining a system.

Question 52

Preventive maintenance requires the least maintenance effort.

Question 53

Training and support are not critical for the success of an information system.

Question 54

All user training must be done as a formal course.

Question 55

Baseline routines are guidelines that list the instructions to construct an executable system from the baseline source code.

Question 56

A primary objective of using automated tools for systems development and maintenance is to change radically how code and documentation are modified and updated.

Question 57

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) all of the above.
E) none of the above.

Question 58

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.

Question 59

Reverse engineering and reengineering tools are primarily used to maintain older systems that have incomplete documentation or that were developed prior to automated tools.

Question 60

Post project reviews are part of the system design phase.

Question 61

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.

Question 62

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.

Question 63

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.

Question 64

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.

Question 65

An overall test plan is developed during:

A) systems implementation.
B) systems analysis.
C) logical design.
D) physical design.
E) systems planning and selection.

Question 66

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.

Question 67

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

Question 68

Which of the following is the responsibility of testing managers?

A) Developing testing plans
B) Integrating testing and development activities in the life cycle
C) Establishing testing standards
D) Ensuring that test plans are completed
E) All of the above

Question 69

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.

Question 70

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.

Question 71

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.

Question 72

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.

Question 73

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.

Question 74

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.

Question 75

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.

Question 76

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

Question 77

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.

Question 78

Activities occurring within maintenance include:

A) transforming requests into changes.
B) obtaining maintenance requests.
C) implementing changes.
D) designing changes.
E) all of the above.

Question 79

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.

Question 80

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.