PERT chart: Chart that reflects the relationship among
the many activities that constitute the implementation
process.
Phased cutover: Process of converting an old system to a new
system in modules.
Pseudocode: English-like code that describes the logic of a
program without specific language systems.
Procedural language: Specifies the precise order in which the
program logic is executed.
Methods: Actions that are performed on or by objects that
may change the objects’ attributes.
Online documentation: Guides the user interactively in the
use of a system. Examples include tutorials and help features.
Object-oriented programming (OOP) language:
Programming language containing the attributes and
operations that constitute the object modules represented in the
ER diagram at the implementation phase of the SDLC.
Objects: Equivalent to nouns in the English language.
Object-oriented design: Building information systems from
reusable standard components or modules.
Object class: Logical grouping of individual objects that share
the same attributes and operations.
Operations control reports: Identifies activities that are aboutto
go out of control and ignores those that are functioning within
normal limits.
Knowledge management: Gathering, organizing, refining,
and disseminating information.
Gantt chart: Horizontal bar chart that presents time on a
horizontal plane and activities on a vertical plane.
Gathering: Process in knowledge management that brings
data into the system.
Hard copy: Traditional paper-based data storage medium
used for reports and documentation.
Electronic input techniques: Forms of electronic data
collection. These fall into two basic types: input from source
documents and direct input.
Disseminating: Providing knowledge to recipients in a usable
form.
Detailed design report: Set of blueprints that specify input
screen formats, output report layouts, database structures, and
process logic.
Design phase: Production of a detailed description of the
proposed system that both satisfies the system requirements
identified during systems analysis and is in accordance with
the conceptual design.
Data modeling: Task of formalizing the data requirements of
the business process as a conceptual model.
Construct: Design and building of software that is ready to be
tested and delivered to its user community. This phase
involves modeling the system, programming the applications,
Cutover: Process of converting from the old system to the
new system. and application testing.
Conceptual user views: Description of the entire database.
Cold turkey cutover: Process of converting entirely from an
existing accounting system to a new system on a particular day
Quality assurance group: Independent group of
programmers, analysts, users, and internal auditors who
simulate the operation of the system to uncover errors,
omissions, and ambiguities in the design.
Request for proposal (RFP): Document summarizing
system requirements and sent to each prospective
vendor.
Refining: Adding value by discovering relationships between
data, performing synthesis, and abstracting.
Structured design: Disciplined way of designing systems
from the top down.
Third-generation languages: Procedural languages in which
the programmer must specify the sequence of events used in an
operation.
Systems design: Reflects the analysts’ perception of
information needs rather than the perception of accountants
and other users.
User handbook: Reference manual of commands for getting
started.
Walk-through: Analysis of system design to ensure the
design is free from conceptual errors that could become
programmed into the final system.
Wall of code: An object-oriented coding scheme that prevents
direct access to the object’s internal structure and data.
Zones: Areas on a form that contain related data.
rather than phasing in the conversion process over time.
1. Which of the following is the correct sequence of
activities in the systems development life cycle?
a. Design, analysis, implementation, and operation.
b. Design, implementation, analysis, and operation.
c. Analysis, design, implementation, and operation.
d. Programming, analysis, implementation, and
operation.
2. Which of the following is NOT an output attribute?
a. relevance
b. exception orientation
c. zones
d. accuracy
3. Which of the following is NOT a principal feature
of a PERT chart?
a. starting and ending dates
b. events
c. paths
d. activities
4. Internal auditors would most appropriately perform
which of the following activities during a
review of systems development activity?
a. Serve on the MIS steering committee that
determines what new systems are to be developed.
b. Review the methodology used to monitor and
control the system development function.
c. Recommend specific automated procedures to
be incorporated into new systems that will
provide reasonable assurance that all data submitted
to an application are converted to
machine-readable form.
d. Recommend specific operational procedures
that will ensure that all data submitted for processing
are converted to machine-readable form.
5. Which of the following is the least risky strategy
for converting from a manual to a computerized
system?
a. file conversion
b. parallel conversion
c. pilot conversion
d. big bang conversion
e. direct conversion
6. At which point are errors aremost costly to correct?
a. programming
b. conceptual design
c. analysis
d. detailed design
e. implementation
7. User acceptance testing is more important in an
object-oriented development process than in a
traditional environment because of the implications
of the
a. absence of traditional design documents.
b. lack of a tracking system for changes.
c. potential for continuous monitoring.
d. inheritance of properties in hierarchies.
8. Which of the following sets of application
characteristics
of an accounting application might influence
the selection of data entry devices and media
for a computerized accounting system?
a. Timing of feedback needs relative to input,
need for documentation of an activity, and the
necessity for reliability and accuracy.
b. Cost considerations, volume of input, complexity
of activity, and liquidity of assets
involved.
c. Need for documentation, necessity for accuracy
and reliability, volume of output, and cost
considerations.
d. Relevancy of data, volume of input, cost
considerations,
volume of output, and timing of feedback
needs relative to input.
e. Type of file used, reliability of manufacturer’s
service, volume of output, and cost considerations.
9. What is the name given to the systems
development
approach used to quickly produce a model
of user interfaces, user interactions with the system,
and process logic?
a. neural networking
b. prototyping
c. reengineering
d. application generation
10. The PERT is combined with cost data to produce
a PERT cost analysis to
a. calculate the total project cost inclusive of the
additional slack time.
b. evaluate and optimize trade-offs between time
of an event’s completion and its cost to complete.
c. implement computer-integrated manufacturing
concepts.
d. avoid the problem of time variance analysis.
e. calculate expected activity times.
11. Which of the following is NOT part of the
systems
implementation process?
a. converting databases
b. documentation
c. systems design
d. testing and correction
12. What is the critical path in the PERT method for
network analysis?
a. shortest path through the network
b. longest path through the network
c. path with the most slack
d. path with the most variability in estimated
times
e. least-cost path