acct 316 acct 316 acct 316 systems development and documentation techniques uaa – acct 316 –...
out of 107
Post on 18-Dec-2015
Embed Size (px)
- Slide 1
- Acct 316 Acct 316 Acct 316 Systems Development and Documentation Techniques UAA ACCT 316 Fall 2003 Accounting Information Systems Dr. Fred Barbee Chapter 6
- Slide 2
- Acct 316 Acct 316 Acct 316 Documentation Techniques Data Flow Diagrams Document Flowcharts System Flowcharts Program Flowcharts Used by 62.5% of IT Professionals Used by 97.6% of IT Professionals
- Slide 3
- Acct 316 Acct 316 Acct 316 Documentation Techniques Data Flow Diagrams Document Flowcharts System Flowcharts Program Flowcharts More than 92% use both DFDs and flowcharts.
- Slide 4
- Acct 316 Acct 316 Acct 316 Typical Information System Computer-based; Has a number of terminals connected to it via telecommunications links; Is used by dozens of people within and outside the organization;
- Slide 5
- Acct 316 Acct 316 Acct 316 Typical Information System Has hundreds of programs that perform functions for virtually every department in the organization. Processes thousands of transactions and hundreds of requests for management information.
- Slide 6
- Acct 316 Acct 316 Acct 316 For such a system... pictures We need pictures rather than a narrative description see to see and analyze all the inputs and outputs.
- Slide 7
- Slide 8
- Acct 316 Acct 316 Acct 316 Documentation Techniques... are tools used in analyzing, designing, and documenting system and subsystem relationships...
- Slide 9
- Acct 316 Acct 316 Acct 316 Documentation Techniques They are largely graphical in nature; Are essential to both internal and external auditors; and Are indispensable in the development of information systems.
- Slide 10
- Acct 316 Acct 316 Acct 316 Auditors
- Slide 11
- Acct 316 Acct 316 Acct 316 The Interim Audit... Objective is to establish the degree to which the organizations internal structure can be relied upon. Usually requires some form of compliance testing.
- Slide 12
- Acct 316 Acct 316 Acct 316 Compliance Testing... The purpose of compliance testing is: To confirm the existence, Assess the effectiveness, and Check the continuity of operations of the internal controls on which reliance is to be placed.
- Slide 13
- Acct 316 Acct 316 Acct 316 Compliance Testing... Compliance testing requires an understanding of the controls that are to be tested. In other words, you cant test something you dont understand.
- Slide 14
- Acct 316 Acct 316 Acct 316 Internal Control Structure In evaluating internal controls auditors are concerned with the flow of processing and distribution of documents within an application system.
- Slide 15
- Acct 316 Acct 316 Acct 316 Systems Development
- Slide 16
- Acct 316 Acct 316 Acct 316 Systems Development... Consists of three phases: Systems analysis; Systems design; and Systems implementation Each of these phases makes use of documentation techniques.
- Slide 17
- Acct 316 Acct 316 Acct 316 Management
- Slide 18
- Acct 316 Acct 316 Acct 316 Management As Users... Scheduling work; Development of an internal control system; Reviewing the flow of work through the organization.
- Slide 19
- Acct 316 Acct 316 Acct 316 Other Users
- Slide 20
- Acct 316 Acct 316 Acct 316 You!
- Slide 21
- Acct 316 Acct 316 Acct 316 Other Users... Training Used to explain systems and to train personnel Description Used by auditors and others to understand complex systems; and To evaluate the systems internal controls.
- Slide 22
- Acct 316 Acct 316 Acct 316 Classification... Documentation is classified according to the level of the accounting system to which it relates.
- Slide 23
- Acct 316 Acct 316 Acct 316 Typical System Documentation System narrative descriptions Block diagrams Document flowcharts Data flow diagrams
- Slide 24
- Acct 316 Acct 316 Acct 316 Overall System Documentation System Flowcharts Program Flowcharts; and Decision Flowcharts
- Slide 25
- Narrative descriptions are the most general overview and correspondingly show the fewest details. System flowcharts provide less of an overview, but include the most detail in this class of documentation. In Terms of Level of Detail
- Slide 26
- Acct 316 Acct 316 Acct 316 Narrative Descriptions A written step-by-step explanation of system components and interactions. The highest and broadest form of documentation at the overall system level.
- Slide 27
- Acct 316 Acct 316 Acct 316 Narrative Descriptions It represents the basic source of information regarding the system goals and objectives. Makes it possible to quickly understand the system without being involved with details.
- Slide 28
- Acct 316 Acct 316 Acct 316 Narrative Descriptions A description of the reasons for building the system. Background Objectives Scope of system
- Slide 29
- Acct 316 Acct 316 Acct 316 Block Diagrams Block diagrams provide a graphic overview of a system. Commonly used to provide an overview of an accounting system in terms of its major components and subsystems
- Slide 30
- Acct 316 Acct 316 Acct 316 Block Diagrams They help people understand a system without getting bogged down in details. Two types: Horizontal Block Diagram; and Hierarchical Block Diagram
- Slide 31
- Acct 316 Acct 316 Acct 316 Horizontal Block Diagrams Blocks represent the various subsystems; While connecting lines represent the information flows among them.
- Slide 32
- Request for Goods and Services Purchase Requisition Purchasing Purchase Order Receiving Receiving Report Disb. Approval Voucher Cash Disb. $ Purchasing Cycle Process Document
- Slide 33
- Customer Vendors and Employees Bank Customer Horizontal Block Diagram
- Slide 34
- Acct 316 Acct 316 Acct 316 Hierarchical Block Diagrams Show the analysis of a system into successive levels of component subsystems. Connecting lines represent interlevel associations (parent- child relationships).
- Slide 35
- Hierarchical Block Diagram of The Revenue Cycle
- Slide 36
- Acct 316 Acct 316 Acct 316 Data Flow Diagrams Bridge the gap between Broad documentation types... System Narratives Block Diagrams Document Flow charts Narrow documentation types... System Flow Charts
- Slide 37
- Acct 316 Acct 316 Acct 316 Data Flow Diagrams Provide... More detailed representation of an accounting system than block diagrams Fewer technical details than system flowcharts.
- Slide 38
- Acct 316 Acct 316 Acct 316 Symbols For Data Flow Diagrams Figure 6-1 (p. 158)
- Slide 39
- SymbolNameExplanation Data sources and destinations The people and organizations that send data to and receive data from the system. Data Flow Diagram Symbols Data Flows The flow of the data into or out of a process is represented by curved or straight lines with arrows.
- Slide 40
- SymbolNameExplanation Transformation Process The process that transforms data from inputs to outputs. Also known as bubbles. Data Flow Diagram Symbols Data Stores The storage of data is represented by two horizontal lines.
- Slide 41
- Acct 316 Acct 316 Acct 316 Data Flow Diagrams The DFD should consist solely of DFD symbols; Each symbol in the DFD, including each pointed flowline, should be labeled;
- Slide 42
- Acct 316 Acct 316 Acct 316 Data Flow Diagrams All names must be meaningful to the end-user. All symbols must have an individual name. Diagrams are always named at the top or bottom. The name should identify the level and the system it represents.
- Slide 43
- Figure 6-2 Basic Data Flow Diagram Elements
- Slide 44
- Examples: Customer, Employees, Bank, etc. AKA Entity, or terminator. Named with descriptive nouns or noun clauses.
- Slide 45
- Figure 6-2 Basic Data Flow Diagram Elements Examples: Process Payment, Update Receivables, etc. Named with action verb or verb clause. The name must describe what action or transformation is occurring.
- Slide 46
- Figure 6-2 Basic Data Flow Diagram Elements Examples: Accounts Receivable, General Ledger, etc. Named with a noun clause that describes the contents of the data store. Should not include the word data.
- Slide 47
- Figure 6-2 Basic Data Flow Diagram Elements Examples: Time Cards; Employee Data, etc. AKA Entity, or terminator. Named with descriptive nouns or noun clauses. Named with a noun clause that describes the data carrier and how it is implemented.
- Slide 48
- Figure 6-3 Data Flow Diagram of Customer Payment process
- Slide 49
- Acct 316 Acct 316 Acct 316 DFDs Some Dos and Donts First the Dos
- Slide 50
- Acct 316 Acct 316 Acct 316 DFDs Some Dos and Donts All data flows must begin at a process, end at a process, or both.
- Slide 51
- Acct 3
View more >