Chapter 5 Part 2 Flashcards

1
Q

Purpose is to produce 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.

A

PHASE 5: Detailed Design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

• independent one made up of programmers,
analysts, users, and internal auditors.
• Job is to simulate the operation of the system to
uncover errors, omissions, and ambiguities in the
design.

A

Quality assurance group

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Select a programming language from among the various
languages available and suitable to the application

A

PHASE 6: Application Programming and Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

• requires the programmer to specify the precise
order in which the program logic is executed.
• often called third-generation languages (3GLs)
– FORTRAN, C, and PL1.

A

A. Procedural Language (e.g. COBOL)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

• no longer procedural.
• the program’s code is not executed in a
predefined sequence.
• external actions or “events” that are initiated by
the user dictate the control flow of the program.

A

B. Event-driven languages (e.g. Visual Basic)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Central to achieving the benefits of the object-
oriented approach.

A

C. Object-Oriented Languages. (e.g. Java or C++)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Three (3) Benefits of Program system

A
  1. Programming efficiency
  2. Maintenance efficiency
  3. Control.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Database structures are created and populated with data,
equipment is purchased and installed, employees are
trained, the system is documented, and the new system is
installed.

A

PHASE 7: System Implementation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

• When all modules have been coded and tested,
they must be brought together and tested as a
whole

A

Testing the Entire System

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

• provides the auditor with essential information about
how the system works.

A

Documenting the System

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Requirements in documenting the system

A
  1. Designer and Programmer Documentation
  2. Operator Documentation
  3. User Documentation
  4. User Handbook
  5. Tutorials
  6. Help Features
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

to debug errors and perform maintenance on
the system.

A

Designer and Programmer Documentation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Computer operators use documentation called
a run manual, which describes how to run the
system.

A

Operator Documentation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

describing how to use the system.

A

User Documentation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

user documentation often takes the form of a
user handbook, as well as online
documentation.

A

User Handbook

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Online tutorials can be used to train the novice
or the occasional user.

A

Tutorials

17
Q

Online help features range from simple to
sophisticated.
- Simple help feature (an error message
displayed on the screen)
- Sophisticated help feature (context-related)

A

Help Features

18
Q

User’s Skill Level:

A
  1. Novices
  2. Occasional users
  3. Frequent light users
  4. Frequent power users
19
Q

The process of converting from the old system to the new
one is called the

A

Cutover

20
Q

Three (3) Approaches of cutover

A
  1. Cold Turkey Cutover (“Big Bang” approach)
  2. Phased Cutover
  3. Parallel Operation Cutover
21
Q

firm switches to the new system and
simultaneously terminate the old system.
- often the easiest and least costly approach.

A

Cold Turkey Cutover (“Big Bang” approach)

22
Q

By phasing in the new system in modules, we
reduce the risk of a devastating system failure.
- However, the phased approach can create
incompatibilities between new subsyst

A

Phased Cutover

23
Q

involves running the old system and the new system simultaneously for a period of time.

A

Parallel Operation Cutover

24
Q

The physical features of the system should be reviewed
to see if they meet user needs.

A

Systems Design Adequacy.

25
Q

• A formal process by which application programs
undergo changes to accommodate changes in
user needs.
• Maintenance represents a significant resource
outlay compared to initial development costs.

A

PHASE 8 : Systems Maintenance

26
Q

All systems must be properly authorized to ensure their economic justification and feasibility.

A

Systems Authorization Activities

27
Q

Users must be actively involved in the systems development process.

A

User Specification Activities

28
Q

translate the user specifications into a set of detailed technical specifications of a system that meets the user’s needs.

A

Technical Design Activities

29
Q

The internal auditor plays an important role in the control of systems development activities, particularly in organizations whose users lack technical expertise.

A

Internal Audit Participation

30
Q

Just before implementation, the individual
modules of the system must be tested as a
unified whole.

A

User Test and Acceptance Procedures

31
Q

Access to systems for maintenance purposes
increases the possibility of systems errors.
- Logic may be corrupted either by the
accidental introduction of errors or intentional
acts to defraud.

A

Maintenance Authorization, Testing, and
Documentation

32
Q

In spite of the preceding maintenance
procedures, application integrity can be
jeopardized by individuals who gain
unauthorized access to programs.

A

Source Program Library (SPL) Controls

33
Q

THE WORST-CASE SITUATION: NO CONTROLS
Two (2) Serious Forms of Exposure:

A
  1. Access to programs is completely unrestricted
  2. Because of these control weaknesses, programs are
    subject to unauthorized changes.
34
Q

Assigning passwords provides one form of
access control over the SPL.

A

Password Control.

35
Q

programs are copied into the programmer’s
library for maintenance and testing.

A

Separate Test Libraries

36
Q

An important feature of SPL management
software is the creation of reports that enhance
management control and the audit function.

A

Audit Trail and Management Reports

37
Q

The SPLMS assigns a version number
automatically to each program stored on the
SPL.

A

Program Version Numbers

38
Q

SPL management systems use powerful
maintenance commands to alter or eliminate
program passwords, alter the program version
(modification) number, and temporarily modify
a program without generating a record of the
modification.

A

Controlling Access to Maintenance Commands

39
Q

Audit Procedures Related to System Maintenance

A
  1. Identify Unauthorized Changes
  2. Identify Application Errors
  3. Test Access to Libraries