Romney Ch03

You might also like

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 114

C HAPTER 3

Systems Development and


Documentation Techniques

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 1 of 136
INTRODUCTION

Questions to be addressed in this chapter


include:
What is the purpose of documentation?
Why do accountants need to understand
documentation?
What documentation techniques are used in
accounting systems?
What are data flow diagrams and flowcharts?
How are they alike and different?
How are they prepared?

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 2 of 136
INTRODUCTION

Documentation includes the following


types of tools:
Narratives (written descriptions)
Flowcharts
Diagrams
Other written material

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 3 of 136
INTRODUCTION

Documentation covers the who, what,


when, where, why, and how of:
Data entry
Processing
Storage
Information output
System controls

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 4 of 136
INTRODUCTION

How do accountants use documentation?


At a minimum, they have to read documentation to
understand how a system works.
They may need to evaluate the strengths and
weaknesses of an entitys internal controls.
Requires heavy reliance on documentation
They may peruse documentation to determine if a
proposed system meets the needs of its users.
They may prepare documentation to:
Demonstrate how a proposed system would work
Demonstrate their understanding of a system of internal
controls
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 5 of 136
INTRODUCTION

In this chapter, we discuss two of the most


common documentation tools:
Data flow diagrams
Graphical descriptions of the sources
and destinations of data. They show:
Where data comes from
How it flows
The processes performed on it
Where it goes

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 6 of 136
INTRODUCTION

In this chapter, we discuss two of the most


common documentation tools:
Data flow diagrams
Flowcharts
Include three types:
Document flowcharts describe the flow of documents and
information between departments or units.
System flowcharts describe the relationship between inputs,
processing, and outputs for a system.
Program flowcharts describe the sequence of logical
operations performed in a computer program.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 7 of 136
INTRODUCTION

Documentation techniques are necessary tools


for accountants:
SAS-94 requires that auditors understand the
automated and manual procedures an entity uses.
This understanding can be gleaned through documenting the
internal control systema process that effectively exposes
strengths and weaknesses of the system.
SOX (2002) effectively requires that publicly-traded
corporations and their auditors document and test the
companys internal controls.
Auditing Standard No. 2 promulgated by the
PCAOB requires that the external auditor express an
opinion on the clients system of internal controls.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 8 of 136
INTRODUCTION

Documentation tools help accountants by:


Organizing very complicated systems into a
form that can be more readily understood.
Helping new team members understand a
pre-existing system.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 9 of 136
INTRODUCTION

Which method should you useflowcharts


or DVDs?
62.5% of IS professionals use DFDs
97.6% use flowcharts
Both can be prepared relatively simply using
available software
Both are tested on professional exams
CONCLUSION: You need to know them both

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 10 of 136
DATA FLOW DIAGRAMS

A data flow diagram (DFD) graphically


describes the flow of data within an
organization. It is used to:
Document existing systems
Plan and design new systems
There is no black-and-white approach to
developing a DFD.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 11 of 136
DATA FLOW DIAGRAMS
Example of a data flow
diagram of the customer
payment process from Accounts
Figure 3-3 in your Receivable
textbook.

Customer Remittance Receivables


payment 1.0 2.0
data Information Credit
Customer Process Update
Payment A/R Manager

Deposit

Bank

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 12 of 136
DATA FLOW DIAGRAMS

A data flow diagram consists of four basic


elements:
Data sources and destinations
Data flows
Transformation processes
Data stores

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 13 of 136
DATA FLOW DIAGRAMS

A data flow diagram consists of four basic


elements:
Data sources and destinations
Data flows
Transformation processes
Data stores

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 14 of 136
DATA FLOW DIAGRAMS

Data sources and destinations


Appear as squares
Represent organizations or individuals that send or
receive data used or produced by the system
An item can be both a source and a destination

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 15 of 136
DATA FLOW DIAGRAMS
Data sources and
destinations are marked
in red. Accounts
Can you tell which are Receivable
sources and which are
destinations?

Customer Remittance Receivables


payment 1.0 2.0
data Information Credit
Customer Process Update
Payment A/R Manager

Deposit

Bank

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 16 of 136
DATA FLOW DIAGRAMS

A data flow diagram consists of four basic


elements:
Data sources and destinations
Data flows
Transformation processes
Data stores

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 17 of 136
DATA FLOW DIAGRAMS

Data flows
Appear as arrows
Represent the flow of data between sources and
destinations, processes, and data stores

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 18 of 136
DATA FLOW DIAGRAMS
Data flows are shown in red.
Does it appear that a data
flow can be two-way? Accounts
If so, how is it handled? Receivable

Customer Remittance Receivables


payment 1.0 2.0
data Information Credit
Customer Process Update
Payment A/R Manager

Deposit

Bank

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 19 of 136
DATA FLOW DIAGRAMS
Data flows should always be
labeled.
The exception is a data flow Accounts
moving into or out of a data Receivable
store.
What symbol is the data store?

Customer Remittance Receivables


payment 1.0 2.0
data Information Credit
Customer Process Update
Payment A/R Manager

Deposit

Bank

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 20 of 136
DATA FLOW DIAGRAMS

As you probably surmised from the previous


slides, if a data flow is two-way, use a bi-
directional arrow.

Update
General
Receiv-
Ledger
ables

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 21 of 136
DATA FLOW DIAGRAMS

If two data elements flow together, then the use


of one data flow line is appropriate.

Cash Recd & Remittance Slip Process


Customer
Payment

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 22 of 136
DATA FLOW DIAGRAMS

If the data elements do not always flow


together, then multiple lines will be
needed.

Customer Inquiry Process


Customer Payment
Customer Payment

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 23 of 136
DATA FLOW DIAGRAMS

A data flow diagram consists of four basic


elements:
Data sources and destinations
Data flows
Transformation processes
Data stores

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 24 of 136
DATA FLOW DIAGRAMS

Processes
Appear as circles
Represent the transformation of data

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 25 of 136
DATA FLOW DIAGRAMS
The transformation processes are
shown in red.
Every process must have at least
Accounts
one data inflow and at least one
Receivable
data outflow. Why?
What do you notice about how the
processes are labeled?

Customer Remittance Receivables


payment 1.0 2.0
data Information Credit
Customer Process Update
Payment A/R Manager

Deposit

Bank

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 26 of 136
DATA FLOW DIAGRAMS

Data stores
Appear as two horizontal lines
Represent a temporary or permanent repository of
data

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 27 of 136
DATA FLOW DIAGRAMS
The data store is shown in red.
Notice that the inflows and
outflows to the data store are Accounts
not labeled. Receivable

Customer Remittance Receivables


payment 1.0 2.0
data Information Credit
Customer Process Update
Payment A/R Manager

Deposit

Bank

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 28 of 136
DATA FLOW DIAGRAMS

Data dictionary:
Data flows and data stores are typically
collections of data elements.
EXAMPLE: A data flow labeled student
information might contain elements such as
student name, date of birth, ID number,
address, phone number, and major.
The data dictionary contains a description of
all data elements, data stores, and data flows
in a system.
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 29 of 136
DATA FLOW DIAGRAMS

Subdividing the DFD:


Few systems can be fully diagrammed on one
sheet of paper, and users have needs for
differing levels of detail.
Consequently, DFDs are subdivided into
successively lower levels to provide
increasing amounts of detail.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 30 of 136
DATA FLOW DIAGRAMS

The highest level of DFD is called a


context diagram.
It provides a summary-level view of the
system.
It depicts a data processing system and the
external entities that are:
Sources of its input
Destinations of its output

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 31 of 136
DATA FLOW DIAGRAMS
Govt.
Depart- t
en Agencies
ym
ments Tim pa
e t &
car por
d s x re
Ta

Payroll Employee checks


Employees
Processing
or m System Pay
ef
e ro ll ch
p loy orm eck
e m e f
ew ang Pa
N c h
yee
yr
o Bank
Human plo ll
re
Em po
Resources rt

This is the context diagram for the


Manage-
S&S payroll processing system
ment
(Figure 3-5 in your textbook).
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 32 of 136
DATA FLOW DIAGRAMS
Govt.
Depart- t
en Agencies
ym
ments Tim pa
e t &
car por
d s x re
Ta

Payroll Employee checks


Employees
Processing
or m System Pay
ef
e ro ll ch
p loy orm eck
e m e f
ew ang Pa
N c h
yee
yr
o Bank
Human plo ll
re
Em po
Resources rt

What information comes into this Manage-


process, and from where? ment

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 33 of 136
DATA FLOW DIAGRAMS
Govt.
Depart- t
en Agencies
ym
ments Tim pa
e t &
car por
d s x re
Ta

Payroll Employee checks


Employees
Processing
or m System Pay
ef
e ro ll ch
p loy orm eck
e m e f
ew ang Pa
N c h
yee
yr
o Bank
Human plo ll
re
Em po
Resources rt

What information is produced by this Manage-


process, and where does it go? ment

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 34 of 136
DATA FLOW DIAGRAMS
Depart-
ments Employees
Employee
New employee Time paychecks
Human form cards
Resources
1.0
Update 2.0
Employee Payroll
Empl. Pay
change check
Payroll Employ- Bank
form
File ees

Payroll
disburse-
3.0 5.0
ment data
Employee/
This diagram Prepare
Payroll File
Update
Reports Gen.
shows the Ledger
next level of Payroll tax
disb. voucher
detail for the Payroll
report
context 4.0 General
Ledger
diagram in Pay
Tax report
Manage- Taxes
Figure 3-5. ment
& payment
Govt.
Agencies

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 35 of 136
DATA FLOW DIAGRAMS
Depart-
ments Employees
Employee
New employee Time paychecks
Human form cards
Resources
1.0
Update 2.0
Employee Payroll
Empl. Pay
change check
Payroll Employ- Bank
form
File ees

Payroll
disburse-
3.0 5.0
ment data
Employee/
What Prepare
Payroll File
Update
Reports Gen.
information Ledger
comes into Payroll tax
disb. voucher
these Payroll
report
processes 4.0 General
Ledger
and from Pay
Tax report
Manage- Taxes
where? ment
& payment
Govt.
Agencies

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 36 of 136
DATA FLOW DIAGRAMS
Depart-
ments Employees
Employee
New employee Time paychecks
Human form cards
Resources
1.0
Update 2.0
Employee Payroll
Empl. Pay
change check
Payroll Employ- Bank
form
File ees

Payroll
Disburse-
3.0 5.0
ment data
Employee/
What Prepare
Payroll File
Update
Reports Gen.
information is Ledger
produced by Payroll tax
disb. voucher
these Payroll
report
processes, 4.0 General
Ledger
and where Pay
Tax report
Manage- Taxes
does it go? ment
& payment
Govt.
Agencies

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 37 of 136
DATA FLOW DIAGRAMS
Depart-
ments Employees
Employee
New employee Time paychecks
Human form cards
Resources
1.0
Update 2.0
Employee Payroll
Empl. Pay
Change check
Payroll Employ- Bank
form
file ees

Payroll
Disburse-
3.0 5.0
ment data
Employee/
How do the Prepare
Payroll file
Update
reports Gen.
sources and Ledger
destinations Payroll tax
disb. voucher
differ from Payroll
report
the context 4.0 General
Ledger
diagram? Pay
Tax report
Manage- taxes
& payment
ment Govt.
Agencies

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 38 of 136
DATA FLOW DIAGRAMS
Depart-
ments Employees
Employee
New employee Time paychecks
Human form cards
Resources
1.0
Employee
Update 2.0 Payroll
Empl. Pay
Change check
Payroll Employ- Bank
form
file ees
Payroll
Disburse-
3.0 ment data 5.0
Employee/
Notice that Prepare
Payroll file Update
reports
each process Gen.
Ledger
in the DFD is Payroll tax
disb. voucher
numbered Payroll
report
sequentially. 4.0 General
Ledger
Pay
Tax report
Manage- taxes
& payment
ment Govt.
Agencies

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 39 of 136
DATA FLOW DIAGRAMS
Depart-
ments Employees
Employee
New employee Time paychecks
Human form cards
Resources
1.0
Update 2.0
Employee Pay Payroll
Empl.
change check
form
Payroll Employ- Bank
File ees
Suppose we Payroll
exploded Process 3.0
Disburse-
ment data 5.0
2.0 (Pay Prepare Employee/ Update
Employees) in the Reports Payroll File Gen.
next level. The Ledger
Payroll tax
sub-processes disb. voucher
Payroll
would be report
General
numbered 2.1, 2.2, 4.0
Pay Ledger
2.3, etc. Tax report
Manage- Taxes
& payment
ment Govt.
Agencies

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 40 of 136
DATA FLOW DIAGRAMS

Were going to go through a partial


example of how the first level of detail was
created.
But before we do, lets step through some
guidelines on how to create a DFD.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 41 of 136
DATA FLOW DIAGRAMS

RULE 1: Understand the system. Observe the


flow of information and interview people involved
to gain that understanding.
RULE 2: Ignore control processes and control
actions (e.g., error corrections). Only very critical
error paths should be included.
RULE 3: Determine the system boundaries
where it starts and stops. If youre not sure about
a process, include it for the time being.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 42 of 136
DATA FLOW DIAGRAMS

RULE 4: Draw the context diagram first, and


then draw successively greater levels of detail.
RULE 5: Identify and label all data flows. The
only ones that do not have to be labeled are
those that go into or come out of data stores.
RULE 6: Data flows that always flow together
should be grouped together. Those that do not
flow together should be shown on separate
lines.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 43 of 136
DATA FLOW DIAGRAMS
RULE 7: Show a process (circle) wherever a data flow is
converted from one form to another. Likewise, every
process should have at least one incoming data flow and
at least one outgoing data flow.
RULE 8: Transformation processes that are logically
related or occur simultaneously can be grouped in one
bubble.
RULE 9: Number each process sequentially. A process
labeled 5.0 would be exploded at the next level into
processes numbered 5.1, 5.2, etc. A process labeled 5.2
would be exploded into 5.21, 5.22, etc.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 44 of 136
DATA FLOW DIAGRAMS

RULE 10: Process names should include action


verbs, such as update, prepare, etc.
RULE 11: Identify and label all data stores,
whether temporary or permanent.
RULE 12: Identify and label all sources and
destinations. An entity can be both a source and
destination. You may wish to include such items
twice on the diagram, if needed, to avoid
excessive or crossing lines.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 45 of 136
DATA FLOW DIAGRAMS

RULE 13: As much as possible, organize the


flow from top to bottom and left to right.
RULE 14: Youre not likely to get it beautiful the
first time, so plan to go through several iterations
of refinements.
RULE 15: On the final copy, lines should not
cross. On each page, include:
The name of the DFD
The date prepared
The preparers name

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 46 of 136
DATA FLOW DIAGRAMS

Now that weve been through the


guidelines for developing DFDs, lets go
back to the chapter example and see if we
can re-create a part of it.
You may wish to create a table with the
following headings to organize your
information:
Data Inputs
Processes
Data Outputs
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 47 of 136
DATA FLOW DIAGRAMS

Data Inputs Processes Data Outputs

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 48 of 136
DATA FLOW DIAGRAMS
The first paragraph of the narrative for the payroll
process reads as follows:
When employees are hired, they complete a new employee
form. When a change to an employees payroll status occurs,
such as a raise or a change in the number of exemptions,
human resources completes an employee change form. A copy
of these forms is sent to payroll. These forms are used to create
or update the records in the employee/payroll file and are then
stored in the file. Employee records are stored alphabetically.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 49 of 136
DATA FLOW DIAGRAMS
The first paragraph of the narrative for the payroll
process reads as follows:
When employees are hired, they complete a new employee
form. When a change to an employees payroll status
occurs, such as a raise or a change in the number of
exemptions, human resources completes an employee
change form. A copy of these forms is sent to payroll.
These forms are used to create or update the records in the
employee/payroll file and are then stored in the file.
Employee records are stored alphabetically.

The portion marked in red relates to activities that go on


outside the boundaries of the payroll system. Consequently,
these activities will not be included on the DFD.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 50 of 136
DATA FLOW DIAGRAMS
The first paragraph of the narrative for the payroll
process reads as follows:
When employees are hired, they complete a new employee
form. When a change to an employees payroll status
occurs, such as a raise or a change in the number of
exemptions, human resources completes an employee
change form. A copy of these forms is sent to payroll.
These forms are used to create or update the records in the
employee/payroll file and are then stored in the file.
Employee records are stored alphabetically.
The portion marked in red suggests two data flows coming into
the payroll process (new employee forms and employee
change forms). The source of the inflows is the human
resources department.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 51 of 136
DATA FLOW DIAGRAMS

Data Inputs Processes Data Outputs


New employee forms and
employee change forms
(from H.R. Dept.)

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 52 of 136
DATA FLOW DIAGRAMS
The first paragraph of the narrative for the payroll
process reads as follows:
When employees are hired, they complete a new employee
form. When a change to an employees payroll status
occurs, such as a raise or a change in the number of
exemptions, human resources completes an employee
change form. A copy of these forms is sent to payroll.
These forms are used to create or update the records in the
employee/payroll file and are then stored in the file.
Employee records are stored alphabetically.
The sentence marked in red suggests a process (update
employee records) with the data outflow going to a data store
(the employee/payroll file).

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 53 of 136
DATA FLOW DIAGRAMS

Data Inputs Processes Data Outputs


New employee forms and Update records (read from Updated employee/
employee change forms file and record) payroll file
(from H.R. Dept.)

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 54 of 136
DATA FLOW DIAGRAMS
The first paragraph of the narrative for the payroll
process reads as follows:
When employees are hired, they complete a new employee
form. When a change to an employees payroll status
occurs, such as a raise or a change in the number of
exemptions, human resources completes an employee
change form. A copy of these forms is sent to payroll.
These forms are used to create or update the records in the
employee/payroll file and are then stored in the file.
Employee records are stored alphabetically.

The final sentence in this paragraph provides information


about the physical storage of the data. Physical information is
utilized in flowcharts but not in data flow diagrams.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 55 of 136
DATA FLOW DIAGRAMS

Data Inputs Processes Data Outputs


New employee forms and Update records (read from Updated employee/
employee change forms file and record) payroll file
(from H.R. Dept.)

We will not do the entire DFD, however, you could finish this
table by reading the remainder of the narrative in Table 3-1 in
your textbook. The portion of the table completed so far allows
us to draw the segment of the DFD that is highlighted on the
following slide.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 56 of 136
DATA FLOW DIAGRAMS
Depart-
ments Employees
Employee
New employee Time paychecks
Human form cards
Resources
1.0
Update 2.0
Employee Payroll
Empl. Pay
change check
Payroll Employ- Bank
form
File ees

Payroll
disburse-
3.0 5.0
ment data
Prepare Employee/ Update
Reports Payroll File Gen.
Ledger
Payroll tax
Payroll disb. voucher
report
4.0 General
Pay Ledger
Taxes Tax report
Manage- & payment
ment Govt.
Agencies

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 57 of 136
DATA FLOW DIAGRAMS

Keep the following in mind as you develop your


DFD:
Remember to ignore control activities, such as error
correction processes.
Some data inputs and outputs will not appear on the
first level of the DFD but appear as the processes are
exploded into greater levels of detail.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 58 of 136
DATA FLOW DIAGRAMS

The data flow diagram focuses on the logical


flow of data.
Next, we will discuss flowcharts, which place
greater emphasis on physical details.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 59 of 136
FLOWCHARTS

A flowchart is an analytical technique that


describes some aspect of an information system
in a clear, concise, and logical manner.
Flowcharts use a set of standard symbols to
depict processing procedures and the flow of
data.
Flowcharting History:
Introduced in 1950s by industrial engineers to document
business processes and document flows for process
improvement.
Sarbanes-Oxley 2002 increased importance by requiring
companies to document business processes and internal
controls procedures.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 60 of 136
FLOWCHARTS

Every shape on a flowchart depicts a unique


operation, input, processing activity, or storage
medium.
In the days of yore, flowcharts were manually
created using plastic templates.
Most flowcharts are now drawn using a software
program such as Visio.
Microsoft and Power Point are also used.
The software uses pre-drawn shapes, and the
developer drags the shapes into the drawing.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 61 of 136
FLOWCHARTS

There are four types of flowcharting


symbols:
Input/output symbols
Input/output symbols indicate the
type of device or media that provides
input to or records output from a
process.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 62 of 136
FLOWCHARTS

There are four types of flowcharting


symbols:
Input/output symbols
Processing symbols
Processing symbols indicate the type
of device used to process the data or
whether the data is processed
manually.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 63 of 136
FLOWCHARTS

There are four types of flowcharting


symbols:
Input/output symbols
Processing symbols
Storage symbols
Storage symbols indicate the type of
device used to store data while the
system is not using it.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 64 of 136
FLOWCHARTS

There are four types of flowcharting


symbols: Flow and miscellaneous symbols may
indicate:
Input/output symbols
The flow of data and goods
The beginning or end of the flowchart
Processing symbols
The location of a decision
Storage symbols
An explanatory note
Flow and miscellaneous symbols

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 65 of 136
FLOWCHARTS

Click on buttons below if you wish to


review symbols in the various categories.

Input/Output
Input/Output Processing
Processing
Symbols
Symbols Symbols
Symbols

Storage
Storage Flow&&Misc.
Flow Misc.
Symbols
Symbols Symbols
Symbols

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 66 of 136
DOCUMENT FLOWCHARTS

A document flowchart shows the flow of


documents and information among areas of
responsibility in an organization.
These flowcharts trace a document from cradle
to grave and show:
Where a document comes from
Where its distributed
How its used
Its ultimate disposition
Everything that happens as it flows through the
system
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 89 of 136
DOCUMENT FLOWCHARTS

Internal control flowcharts are document


flowcharts used to evaluate the adequacy of
internal controls, such as segregation of duties
or internal checks.
They can reveal weaknesses or inefficiencies
such as:
Inadequate communication flows
Unnecessarily complex document flows
Procedures that cause wasteful delays
Document flowcharts are also prepared in the
system design process.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 90 of 136
This is part of the
document flowchart
from Figure 3-9 in
your textbook.
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 91 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
Lets step through some guidelines for
preparing flowcharts:
As with DFDs, you cant effectively prepare a
flowchart if you dont understand the system,
so:
Interview users, developers, auditors, and
management
Administer questionnaires
Read through narratives
Walk through systems transactions

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 92 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
Identify:
Entities to be flowcharted, e.g., departments,
functions, external parties (the parties who do
things in the story)
Documents or information flows
Processes
As you read through a narrative, you may
want to mark the preceding items with
different shapes (e.g., drawing a rectangle
around entities, circling documents, etc.).

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 93 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
Use separate columns for the activity of
each entity.
Example: If there are three different
departments or functions that do things in
the narrative, there would be three columns
on the flowchart.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 94 of 136
What are the entities
in this flowchart?

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 95 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
Flowchart the normal course of operations,
and identify exceptions with annotations.
As much as possible, the flow should go from
top to bottom and left to right.
Use standard flowcharting symbols, and draw
with a template or computer.
Clearly label all symbols. Use annotations if
necessary to provide adequate explanation.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 96 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
Give the flowchart a clear beginning and
ending.
Show where each document originated and its final
disposition.
One approach you can use is to read through
the narrative and for each step define:
What was (were) the input(s)
What process was carried out
What was (were) the output(s)
Note on the next slide that the flow sequence
is inputprocessoutput.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 97 of 136
Identifies where input is coming from

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 98 of 136
Inputs

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 99 of 136
Process

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 100 of 136
Output to
storage

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 101 of 136
Input for
next
process

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 102 of 136
Process

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 103 of 136
Output

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 104 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
Every manual process should have at least
one input and at least one output.
Show all data entered into or retrieved from a
computer file as passing through a process
first.
Do not show process symbols for:
Forwarding a document to another entity
Filing a document

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 105 of 136
Forwarding
a document

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 106 of 136
Filing
a document

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 107 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
Do not connect two documents except
when forwarding to another column.
When a document is forwarded, show it in
both locations.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 108 of 136
Show forwarded
document in both
locations
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 109 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
When using multiple copies of a
document, place document numbers in
the upper, right-hand corner.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 110 of 136
What happens to the
document numbers
as the documents
move to other
locations?
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 111 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
Show on-page connectors and label
them clearly to avoid excess flow lines.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 112 of 136
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 113 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
Use off-page connectors if the flow goes
to another page.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 114 of 136
Are there other off-
page connectors on
this flowchart?
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 115 of 136
GUIDELINES FOR PREPARING
FLOWCHARTS
If a flowchart takes more than one page, label
the pages as 1 of 5, 2 of 5, 3 of 5, etc.
Show documents or reports first in the column
where they are created.
Start with a rough draft; then redesign to avoid
clutter and crossed lines.
Verify the accuracy of your flowchart by
reviewing it with users, etc.
Place the flowchart name, the date, and the
preparers name on each page of the final
copy.
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 116 of 136
SYSTEM FLOWCHARTS

Now that weve looked at document


flowcharts and guidelines for creating
flowcharts, lets take a brief look at
system flowcharts.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 117 of 136
SYSTEM FLOWCHARTS

A system flowchart depicts the relationship


among the inputs, processes, and outputs
of an AIS.
The system flowchart begins by identifying
the inputs to the system.
These inputs can be:
New data
Data stored for future use
Both

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 118 of 136
SYSTEM FLOWCHARTS

A system flowchart depicts the relationship


among the inputs, processes, and outputs
of an AIS.
The system flowchart begins by identifying the
inputs to the system.
Each input is followed by a process, i.e.,
the steps performed on the data.
If the process is performed by a
computer, the logic of the computer
program would be depicted in a program
flowchart.
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 119 of 136
SYSTEM FLOWCHARTS

A system flowchart depicts the relationship


among the inputs, processes, and outputs
of an AIS.
The output may be:
The system flowchart begins by identifying the
Stored for later use
inputs to the system. Displayed on a screen
Each input is followed by a process,
Printed on paper i.e., the
An input to the next process
steps performed on the data.
The process is followed by outputsthe
resulting new information.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 120 of 136
SYSTEM FLOWCHARTS

A system flowchart depicts the relationship


among the inputs, processes, and outputs of an
AIS.
The system flowchart begins by identifying the inputs
to the system.
Each input is followed by a process, i.e., the steps
performed on the data.
The process is followed by outputsthe resulting new
information.
In other words, its the same basic input
processoutput pattern that we saw in the
document flowchart.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 121 of 136
System
Flowchart
Shown in Figure
3-11 in your
textbook
Can you spot
the input
processoutput
pattern?

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 122 of 136
PROGRAM FLOWCHARTS

Program flowcharts illustrate the sequence


of logical operations performed by a
computer in executing a program.
They also follow an inputprocess
output pattern.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 123 of 136
The program flowchart from
Figure 3-11 in your textbook
is shown on the right.
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 124 of 136
Note that the program flowchart
details the logic of processes
performed by the computer.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 125 of 136
This flowchart becomes the
programmers blueprint for writing
the actual computer program.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 126 of 136
FLOWCHARTS VS. DFDs

Now that weve examined both flowcharts


and DFDs, it may be useful to discuss the
differences again.
DFDs place a heavy emphasis on the
logical aspects of a system.
Flowcharts place more emphasis on the
physical characteristics of the system.
An example may be useful.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 127 of 136
FLOWCHARTS VS. DFDs

EXAMPLE: The registrars office of a small


college receives paper enrollment forms
from students. They sort these records
alphabetically and then update the student
record file to show the new classes.They
also prepare class lists from the same
data. The sorted enrollment forms are
forwarded to the bursars office for billing
purposes. Class lists are mailed to faculty
members.
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 128 of 136
Heres a DFD
Students
that goes
with the
Enrollment
story.
Forms

1.0
Update Student
Student Records
Records

Enrollment
Forms

2.0
Prepare Bursar
Enrollment
Class Lists
Forms

Class
Lists

Faculty

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 129 of 136
Registrars Office

Students Enrollment Sort


Students
Forms Forms

Enrollment
Forms

Update Sorted
1.0 A Enrollment
Student
Update Student Forms
Records
Student Records
Records

Enrollment Sorted
Forms Prepare
Enrollment Class
Forms Lists
2.0
Prepare Bursar Heres a
Enrollment
Class Lists
Forms flowchart Sorted
Class
Class
that goes Lists
Enrollment
Forms
Lists with the
story
Faculty
Faculty Bursar

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 130 of 136
FLOWCHARTS VS. DFDs

Now lets change the story so that


students enter enrollment data online.
The registrars office sends a tape file of
the enrollment data to the bursars office
and continues to send paper class lists to
faculty.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 131 of 136
Heres the
Original
revised DFD.
DFD
Students Students How has it
changed?
Enrollment Enrollment
Forms Data

1.0 1.0
Update Student Update Student
Student Records Student Records
Records Records

Enrollment Enrollment
Forms Data

2.0 2.0
Prepare Bursar Prepare Bursar
Enrollment Enrollment
Class Lists Class Lists
Forms Data

Class Class
Lists Lists

Faculty Faculty

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 132 of 136
Registrars Office Registrars Office

Enrollment Sort
Student Students Enrollment
Forms Forms
s Data

Update Sorted Update


A Enrollment Enrollment
Student Student
Forms Data
Records Records

Sorted Prepare
Enrollment Class Bursar
Prepare
Forms Lists Student Class
Records Lists

Sorted
Class
Lists
Enrollment Heres the revised Class
Forms
flowchart. How has it Lists
changed?
Faculty Bursar
Faculty
Original
Flowchart
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 133 of 136
FLOWCHARTS VS. DFDs

Moral of the story: Changes in the physical


characteristics of the process do affect the
flowchart but have little or no impact on
the DFD.
The DFD focuses more on the logic.
When deciding which tool to employ,
consider the information needs of those
who will view it.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 134 of 136
QUIZ QUESTION

How is playing the piano like making


DFDs and flowcharts?
You cant learn to do it by just watching
someone else.
You cant learn to do it by just looking at
examples.
Your first attempts are clumsy.
Practice leads to improvement and maybe
even perfection.

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 135 of 136
SUMMARY

Weve learned about graphical forms of


documentation, particularly:
Data flow diagrams
Flowcharts
Weve learned why these tools are
important to accountants and how they are
employed.
Weve learned basic guidelines for
creating data flow diagrams and
flowcharts.
2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 136 of 136

You might also like