© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 DOCUMENT FLOWCHARTS A document flowchart shows the.

Slides:



Advertisements
Similar presentations
Documenting an AIS II Flowcharts Documenting AIS II.
Advertisements

Reading System Documentation Using Flowchart Pertemuan Matakuliah: F0204 / Sistem Akuntansi Tahun: 2007.
Documenting Information Systems
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Accounting Information Systems 9th Edition
Systems Development and Documentation Techniques
Week 2b. Flowcharts When: Used extensively for systems development and for internal control structures 97.6% of accounting/IT professionals use flowcharts.
Document Flowcharts Source: Wilkinson Ch_05.
Chapter 2 Systems Techniques and Documentation.
Flowcharting Tips For Manual and Computer-based Systems Created by TerryAnn Glandon 2006, 2007.
Documenting Information Systems
Chapter 6: Documenting Accounting Information Systems
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Documentation Letts Study Guide Information Systems - IT Chapter 19.
ACCT341, Ch. 3, Notes Why Documentation Is Important 1.Depicting how the system works 2.Training users 3.Designing new systems 4.Controlling system development.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 6-1 Systems Development and Documentation Techniques.
Flowcharting Tips For Manual and Computer-based Systems Created by TerryAnn Glandon 2006, 2007, 2008.
ACG 4401 Data Modeling: Data Flow Diagrams Flow Charts.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart3-1 C HAPTER 3 Systems Development and Documentation Techniques.
O Transaksi dasar bisnis terjadi dalam beberapa siklus. Apa saja? O Apakah siklus tersebut saling terkait? Berikan contohnya! O Apa saja langkah-langkah.
Systems Documentation Techniques
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education 3-1.
Learning Objectives LO5 Document an accounting system to identify key controls and weaknesses in order to assess control risk. LO6 Write key control tests.
Documenting Information Systems. Learning Objectives To read and evaluate data flow diagrams To read and evaluate systems flowcharts. To prepare data.
Chapter 4 – Documenting Information Systems
System Development and Documentation Techniques
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 C HAPTER 3 Systems Development and Documentation.
Chapter 7 Using Data Flow Diagrams
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 85 C HAPTER 1 Accounting Information Systems: An Overview.
Chapter 9 Using Data Flow Diagrams
Advanced Accounting Information Systems
Week 2. Announcements I sent an this morning, if you did not get it, you are not on my list. WD quiz on Oct 15 th See your syllabus to get.
The Program Design Phases
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Systems Documentation Techniques
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Accounting systems design & evaluation 9434SB 12 April 2002.
1 Chapter 2 Revision: Documentation DFD System FC.
Documentation Why do auditors pay such close attention to system documentation? l It helps to understand the system - how it works. l The auditor’s documentation.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Chapter 7 Using Data Flow Diagrams
DATA FLOW DIAGRAMS We’re going to go into a partial example of how the first level of detail was created. But before we do, let’s step through some guidelines.
Documenting Information Systems. Learning Objectives To read and evaluate data flow diagrams To read and evaluate systems flowcharts. To prepare data.
Judi Prajetno Sugiono ©2009 Management Information System Additional note for DFD.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 6-1 Accounting Information Systems 9 th Edition Marshall.
DON’T DO IT! IT’S NOT HOPELESS. Documentation Flowcharting Due to thier complexity (when looking at them), flowcharts intimidate many people. However,
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 SYSTEM FLOWCHARTS Now that we’ve looked at document.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 FLOWCHARTS A flowchart is an analytical technique.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 119 C DFD and Flowchart.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Pertemuan 3.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 37 C System Process Modeling DATA Flow Diagrams.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 136 C HAPTER 3 Systems Development and Documentation.
Systems Documentation Techniques
System Process Modeling
Systems Development and Documentation Techniques
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.
Systems Development and Documentation Techniques
Systems Development and Documentation Techniques
Systems Development and Documentation Techniques
Systems Development and Documentation Techniques
Systems Development and Documentation Techniques
Systems Development and Documentation Techniques
DON’T DO IT! IT’S NOT HOPELESS.
Chapter 4: documenting information systems
Documenting Accounting Information Systems
Systems Documentation
Presentation transcript:

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 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 it’s distributed –How it’s used –It’s ultimate disposition –Everything that happens as it flows through the system

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart2 of 138 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 inefficiences such as: –Inadequate communication flows –Unnecessarily complex document flows –Procedures that cause wasteful delays Document flowcharts are also prepared in the system design process.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart3 of 138 This is part of the document flowchart from Figure 3-9 in your textbook.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart4 of 138 GUIDELINES FOR PREPARING FLOWCHARTS Let’s step through some guidelines for preparing flowcharts: –As with DFDs, you can’t effectively prepare a flowchart if you don’t understand the system, so: Interview users, developers, auditors, and management. Administer questionnaires. Read through narratives. Walk through systems transactions

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart5 of 138 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.).

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart6 of 138 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.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart7 of 138 What are the entities in this flowchart?

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart8 of 138 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.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart9 of 138 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 input -- process – output.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart10 of 138 Identifies where input is coming from

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart11 of 138 Inputs

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart12 of 138 Process

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart13 of 138 Output to storage

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart14 of 138 Input for next process

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart15 of 138 Process

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart16 of 138 Output

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart17 of 138 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

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart18 of 138 Forwarding a document

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart19 of 138 Filing a document

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart20 of 138 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.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart21 of 138 Show forwarded document in both locations

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart22 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –When using multiple copies of a document, place document numbers in the upper, right-hand corner.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart23 of 138 What happens to the document numbers as the documents move to other locations?

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart24 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Show on-page connectors and label them clearly to avoid excess flow lines.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart25 of 138

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart26 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Use off-page connectors if the flow goes to another page.

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart27 of 138 Are there other off- page connectors on this flowchart?

© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart28 of 138 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 preparer’s name on each page of the final copy.