Fill This Form To Receive Instant Help
Homework answers / question archive / Harvard University AUDIT 111 Chapter 5-Systems Development and Program Change Activities TRUE/FALSE 1)The objective of systems planning is to link systems projects to the strategic objectives of the firm
Harvard University
AUDIT 111
Chapter 5-Systems Development and Program Change Activities
TRUE/FALSE
1)The objective of systems planning is to link systems projects to the strategic objectives of the firm.
terms.
a. |
reconciling program version numbers |
b. |
program testing |
c. |
user involvement |
d. |
internal audit participation |
a. |
a cost-benefit analysis was conducted |
b. |
the detailed design was an appropriate solution to the user's problem |
c. |
tests were conducted at the individual module and total system levels prior to implementa- tion |
d. |
problems detected during the conversion period were corrected in the maintenance phase |
a. |
documentation updates |
b. |
testing |
c. |
formal authorization |
d. |
internal audit approval |
a. |
compiled programs are very susceptible to unauthorized modification |
b. |
the source program library stores application programs in source code form |
c. |
modifications are made to programs in machine code language |
d. |
the source program library management system increases operating efficiency |
a. |
using passwords to limit access to application programs |
b. |
assigning a test name to all programs undergoing maintenance |
c. |
combining access to the development and maintenance test libraries |
d. |
assigning version numbers to programs to record program modifications |
a. |
Database Management System |
b. |
Recovery Operations Function |
c. |
Source Program Library Management System |
d. |
Computer Services Function |
a. |
involves individual modules only, not the full system |
b. |
requires creation of meaningful test data |
c. |
need not be repeated once the system is implemented |
d. |
is primarily concerned with usability |
a. |
An audit objective for systems maintenance is to detect unauthorized access to application databases. |
b. |
An audit objective for systems maintenance is to ensure that applications are free from errors. |
c. |
An audit objective for systems maintenance is to verify that user requests for maintenance reconcile to program version numbers. |
d. |
An audit objective for systems maintenance is to ensure that the production libraries are protected from unauthorized access. |
a. |
protect applications from unauthorized changes |
b. |
ensure applications are free from error |
c. |
protect production libraries from unauthorized access |
d. |
ensure incompatible functions have been identified and segregated |
a. |
conceptual level |
b. |
context level |
c. |
intermediate level |
d. |
elementary level |
a. |
is a top-down approach |
b. |
is documented by data flow diagrams and structure diagrams |
c. |
assembles reusable modules rather than creating systems from scratch |
d. |
starts with an abstract description of the system and redefines it to produce a more detailed description of the system |
a. |
this approach does not require input from accountants and auditors |
b. |
development time is reduced |
c. |
a standard module once tested does not have to be retested until changes are made |
d. |
system maintenance activities are simplified |
tables?
a. |
context level |
b. |
elementary level |
c. |
intermediate level |
d. |
prototype level |
a. |
the internal auditor |
b. |
the project manager |
c. |
a user representative |
d. |
the system designer |
a. |
operational feasibility study |
b. |
schedule feasibility study |
c. |
legal feasibility study |
d. |
economic feasibility study |
a. |
hardware acquisition |
b. |
insurance |
c. |
site preparation |
d. |
programming |
a. |
software acquisition |
b. |
data conversion |
c. |
personnel costs |
d. |
systems design |
a. |
backbone system |
b. |
vendor-supported system |
c. |
benchmark system |
d. |
turnkey system |
a. |
can be installed faster than a custom system |
b. |
can be easily modified to the user’s exact specifications |
c. |
is significantly less expensive than a system developed in-house |
d. |
is less likely to have errors than an equivalent system developed in-house |
a. |
a detailed review of the source code |
b. |
contact with user groups |
c. |
preparation of a request for proposal |
d. |
comparison of the results of a benchmark problem |
a. |
fully documented system report |
b. |
systems selection report |
c. |
detailed system design report |
d. |
systems analysis report |
a. |
input screen formats |
b. |
alternative conceptual designs |
c. |
report layouts |
d. |
process logic |
a. |
systems designers and programmers |
b. |
end users |
c. |
accountants |
d. |
all of the above require systems documentation |
a. |
structure diagrams |
b. |
overview diagram |
c. |
system flowchart |
d. |
program flowchart |
a. |
run schedule |
b. |
logic flowchart |
c. |
file requirements |
d. |
explanation of error messages |
except
a. |
a list of users who receive output |
b. |
a program code listing |
c. |
a list of all master files used in the system |
d. |
a list of required hardware devices |
a. |
decomposing the system |
b. |
validating the database |
c. |
reconciliation of new and old databases |
d. |
backing up the original files |
a. |
cold turkey cutover |
b. |
phased cutover |
c. |
parallel operation cutover |
d. |
data coupling cutover |
a. |
crane used to install equipment |
b. |
freight charges |
c. |
supplies |
d. |
reinforcement of the building floor |
a. |
software acquisition costs |
b. |
systems design costs |
c. |
data conversion costs |
d. |
programming costs |
a. |
a recurring cost |
b. |
a data conversion cost |
c. |
a systems design cost |
d. |
a programming cost |
a. |
increased customer satisfaction |
b. |
more current information |
c. |
reduced inventories |
d. |
faster response to competitor actions |
a. |
expansion into other markets |
b. |
reduction in supplies and overhead |
c. |
more efficient operations |
d. |
reduced equipment maintenance |
a. |
can be measured and expressed in financial terms |
b. |
might increase revenues |
c. |
might decrease costs |
d. |
all of the above |
a. |
are easily measured |
b. |
are of relatively little importance in making information system decisions |
c. |
are sometimes estimated using customer satisfaction surveys |
d. |
when measured, do not lend themselves to manipulation |
a. |
opinion surveys |
b. |
simulation models |
c. |
professional judgment |
d. |
review of accounting transaction data |
a. |
the report of systems analysis |
b. |
the systems selection report |
c. |
the detailed system design |
d. |
the systems plan |
a. |
site preparation |
b. |
insurance |
c. |
programming and testing |
d. |
data conversion |
a. |
results in a formal project schedule |
b. |
does not include a review of the current system |
c. |
identifies user needs and specifies system requirements |
d. |
is performed by the internal auditor |
a. |
it constrains the generation of ideas about the new system |
b. |
it highlights elements of the current system that are worth preserving |
c. |
it pinpoints the causes of the current problems |
d. |
all of the above are advantages of surveying the current system |
a. |
gathering facts |
b. |
surveying the current system |
c. |
redesigning bottleneck activities |
d. |
reviewing key documents |
a. |
identify user needs |
b. |
specify requirements for the new system |
c. |
formally state the goals and objectives of the system |
d. |
specify the system processing methods |
a. |
the conceptual design of the new system |
b. |
an evaluation of the new system |
c. |
users’ needs and requirements for the new system |
d. |
a comparison of alternative implementation procedures for the new system |
a. |
specify audit trail requirements |
b. |
prepare data gathering questionnaires |
c. |
suggest inclusion of advanced audit features |
d. |
ensure mandated procedures are part of the design |
a. |
designing the system outputs |
b. |
resolving conflicts that arise from a new system |
c. |
selecting the programming techniques to be used |
d. |
approving the accounting procedures to be implemented |
a. |
specifying system objectives |
b. |
preparing a formal project proposal |
c. |
selecting hardware vendors |
d. |
producing a project schedule |
a. |
technical feasibility |
b. |
economic feasibility |
c. |
logistic feasibility |
d. |
schedule feasibility |
47. Which of the following is not a tool of systems analysts?
a. |
observation |
b. |
task participation |
c. |
audit reports |
d. |
personal interviews |
a. |
all similarities and differences between competing systems are highlighted |
b. |
structure diagrams are commonly used |
c. |
the format for input screens and source documents is decided |
d. |
inputs, processes, and outputs that distinguish one alternative from another are identified |
a. |
the accountant is responsible for designing the physical system |
b. |
the accountant is responsible to ensure that audit trails are preserved |
c. |
the internal auditor is responsible to confirm that embedded audit modules are included in the conceptual design |
d. |
the accountant is responsible to make sure that the accounting conventions that apply to the module are considered by the system designers |
a. |
data conversion |
b. |
software maintenance |
c. |
insurance |
d. |
supplies |
a. |
provides authorization control for the Systems Development Life Cycle |
b. |
will eliminate any crisis component in systems development |
c. |
provides a static goal to be attained within a five-year period |
d. |
all of the above |
a. |
technical feasibility |
b. |
conceptual feasibility |
c. |
operational feasibility |
d. |
schedule feasibility |
.
project.
.
firm.
Systems Authorization Activities: All systems should be properly authorized to ensure their economic justification and feasibility. This requires a formal environment in which users submit requests to systems professionals in written form.
initial programming and testing system design-one
hardware costs
software maintenance costs site preparation
rent for facilities
data conversion from old system to new system insurance costs
installation of original equipment hardware upgrades