Systems development and documentation techniques l.jpg
This presentation is the property of its rightful owner.
Sponsored Links
1 / 97

Systems Development and Documentation Techniques PowerPoint PPT Presentation


  • 734 Views
  • Uploaded on
  • Presentation posted in: General

Systems Development and Documentation Techniques. 6. UAA – ACCT 316 – Fall 2003 Accounting Information Systems Dr. Fred Barbee. Chapter. Documentation Techniques. Used by 62.5% of IT Professionals. Data Flow Diagrams Document Flowcharts System Flowcharts Program Flowcharts.

Download Presentation

Systems Development and Documentation Techniques

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Systems development and documentation techniques l.jpg

Systems Development and Documentation Techniques

6

UAA – ACCT 316 – Fall 2003

Accounting Information Systems

Dr. Fred Barbee

Chapter


Documentation techniques l.jpg

Documentation Techniques

Used by 62.5% of IT Professionals

  • Data Flow Diagrams

  • Document Flowcharts

  • System Flowcharts

  • Program Flowcharts

Used by 97.6% of IT Professionals


Documentation techniques3 l.jpg

Documentation Techniques

  • Data Flow Diagrams

  • Document Flowcharts

  • System Flowcharts

  • Program Flowcharts

More than 92% use both DFDs and flowcharts.


Typical information system l.jpg

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;


Typical information system5 l.jpg

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.


For such a system l.jpg

to “see” and analyze all the inputs and outputs.

For such a system . . .

We need “pictures” rather than a narrative description


Slide7 l.jpg

Using Document Flowcharts

Who?

Where?

What?


Documentation techniques8 l.jpg

Documentation Techniques

  • . . . are tools used in analyzing, designing, and documenting system and subsystem relationships . . .


Documentation techniques9 l.jpg

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.


Auditors l.jpg

Auditors


Systems development l.jpg

Systems Development


Management l.jpg

Management


Other users l.jpg

Other Users


Slide14 l.jpg

You!

Prepare

Evaluate

Read


Classification l.jpg

Classification . . .

  • Documentation is classified according to the level of the accounting system to which it relates.


Typical system documentation l.jpg

Typical System Documentation

  • System narrative descriptions

  • Block diagrams

  • Document flowcharts

  • Data flow diagrams


Overall system documentation l.jpg

Overall System Documentation

  • System Flowcharts

  • Program Flowcharts; and

  • Decision Flowcharts


Slide18 l.jpg

In Terms of Level of Detail

Narrative descriptions are the most general overview and correspondingly show the fewest details.

  • Systemflowchartsprovide less of an overview, but include the mostdetail in this class of documentation.


Narrative descriptions l.jpg

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.


Block diagrams l.jpg

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


Block diagrams21 l.jpg

Block Diagrams

  • They help people understand a system without getting bogged down in details.

  • Two types:

    • Horizontal Block Diagram; and

    • Hierarchical Block Diagram


Slide22 l.jpg

Purchasing Cycle

Request for Goods and Services

Purchase Requisition

Purchasing

Purchase Order

Receiving Report

Receiving

Document

Process

$

Cash Disb.

Voucher

Disb. Approval


Slide23 l.jpg

Vendors and Employees

Customer

Customer

Customer

Horizontal Block Diagram

Bank


Hierarchical block diagrams l.jpg

Hierarchical Block Diagrams

  • Show the analysis of a system into successive levels of component subsystems.

  • Connecting lines represent interlevel associations (parent-child relationships).


Slide25 l.jpg

Hierarchical Block Diagram of

The Revenue Cycle


Data flow diagrams l.jpg

Bridge the gap between

Broad documentation types . . .

System Narratives

Block Diagrams

Document Flow charts

Data Flow Diagrams

  • Narrow documentation types . . .

    • System Flow Charts


Data flow diagrams27 l.jpg

Data Flow Diagrams

  • Provide . . .

    • More detailed representation of an accounting system than block diagrams

    • Fewer technical details than system flowcharts.


Symbols for data flow diagrams l.jpg

Symbols For Data Flow Diagrams

Figure 6-1 (p. 158)


Data flow diagrams31 l.jpg

Data Flow Diagrams

  • The DFD should consist solely of DFD symbols;

  • Each symbol in the DFD, including each pointed flowline, should be labeled;


Data flow diagrams32 l.jpg

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.


Slide33 l.jpg

Figure 6-2 Basic Data Flow Diagram Elements


Slide34 l.jpg

AKA “Entity,” or “terminator.” Named with descriptive nouns or noun clauses.

AKA “Entity,” or “terminator.” Named with descriptive nouns or noun clauses.

Figure 6-2 Basic Data Flow Diagram Elements

Examples: Customer, Employees, Bank, etc.


Slide35 l.jpg

Named with action verb or verb clause. The name must describe what action or transformation is occurring.

Figure 6-2 Basic Data Flow Diagram Elements

Examples: Process Payment, Update Receivables, etc.


Slide36 l.jpg

Examples: Accounts Receivable, General Ledger, etc.

Figure 6-2 Basic Data Flow Diagram Elements

Named with a noun clause that describes the contents of the data store. Should not include the word “data.”


Slide37 l.jpg

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.

Figure 6-2 Basic Data Flow Diagram Elements

Examples: Time Cards; Employee Data, etc.


Slide38 l.jpg

Figure 6-3 Data Flow Diagram of Customer Payment process


Dfds some do s and don ts l.jpg

DFDs – Some Do’s and Don’ts

First – the Do’s


Dfds some do s and don ts40 l.jpg

All data flows must begin at a process, end at a process, or both.

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts41 l.jpg

Data stores cannot communicate with entities

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts42 l.jpg

Entities cannot communicate with other entities.

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts43 l.jpg

Data stores cannot communicate with other data stores.

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts44 l.jpg

Processes can communicate with other processes.

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts45 l.jpg

All processes must have an incoming and outgoing data flow.

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts46 l.jpg

All entities must be introduced at the context level.

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts47 l.jpg

Only entities and data store symbols may be duplicated.

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts48 l.jpg

Do not cross data flows.

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts49 l.jpg

Do not use double-ended arrow to represent data flows.

DFDs – Some Do’s and Don’ts


Dfds some do s and don ts50 l.jpg

Do not use diverging arrow to represent data flows

DFDs – Some Do’s and Don’ts

OK


Dfds some do s and don ts51 l.jpg

Data stores do not appear on the context level diagram.

DFDs – Some Do’s and Don’ts


Data flow diagrams52 l.jpg

Data Flow Diagrams

Some Helpful Hints


Dfds some helpful hints l.jpg

DFDs Some Helpful Hints

  • Place entities on the outer edge of the paper.

  • Place the processes toward the center

  • Place data stores around the processes.


Dfds some helpful hints54 l.jpg

DFDs Some Helpful Hints

  • May need to move location of entities and data stores from level to level.

  • Duplicate entities and data stores as needed to make drawing easier.


Data flow diagrams are constructed in levels l.jpg

Data Flow Diagrams are Constructed in Levels


Slide56 l.jpg

Figure 6-5 Context Diagram for S&S Payroll Processing


Slide57 l.jpg

Figure 6-6 DFD for S&S Payroll Processing


Slide58 l.jpg

Figure 6-7 DFD for Process 2.0 in S&S Payroll Processing


Slide59 l.jpg

Let’s pause here and do some data flow diagrams. First P6-9 (p. 180)


Slide60 l.jpg

Ashton Fleming has worked furiously for the past month trying to completely document the major business information flows at S&S. Upon completing his personal interviews with cash receipts clerks, Ashton asks you to develop a comprehensive DFD for the cash receipts system. Ashton’s narrative of the system follows:


Slide61 l.jpg

Customer payments include cash received at the time of purchase and account payments received in the mail. At day’s end, the treasurer endorses all checks and prepares a deposit slip for the checks and the cash. A clerk then deposits the checks, cash, and deposit slip at the local bank each day.


Slide62 l.jpg

When checks are received as payment for accounts due, a remittance slip is included with the payment. The remittance slips are used to update the accounts receivable file at the end of the day. The remittance slips are stored in a file drawer by date.


Slide63 l.jpg

Every week, a cash receipts report and an aged trial balance are generated from the data in the accounts receivable ledger. The cash receipts report is sent to Scott and Susan. A copy of the aged trial balance by customer account is sent to the Credit and Collections Department.


Required l.jpg

Required

  • Develop a context diagram and a DFD for the cash receipts system at S&S.


Context level diagram l.jpg

Context Level Diagram

  • Shows the boundary of the system;

  • Shows the name of the system;

  • Shows net data flows to and from the system; and

  • Identifys all entities.


Context level diagram66 l.jpg

Context Level Diagram

  • On the context level, the system is represented by a single process symbol with the number 0.

  • The name of the system is used for the process.


Ok let s identify l.jpg

OK . . . Let’s Identify . . .

  • Data sources and destinations (terminators);

  • Transformation processes;

  • Data stores; and

  • Data flows


Slide68 l.jpg

Customer payments include cash received at the time of purchase as well as accounts payments received in the mail. At the end of the day, all checks are endorsed by the treasurer and a deposit slip is prepared for the checks and the cash. The checks, cash, and deposit slip are then deposited daily at the local bank by a clerk.


Slide69 l.jpg

When checks are received as payment for accounts due, a remittance slip is included with the payment. The remittance slips are used to update the accounts receivable file at the end of the day. The remittance slips are stored in a file drawer by date.


Slide70 l.jpg

Every week, a cash receipts report and an aged trial balance are generated from the data in the accounts receivable ledger. The cash receipts report is sent to Scott and Susan. A copy of the aged trial balance by customer account is sent to the Credit and Collections Department.


Slide71 l.jpg

Context Diagram of the Cash Receipts System at S&S

Bank

Deposit

Payments at Sale

Cash Receipts System

Customers

Management

Cash Receipts Report

Remittances on Account

Credit and Collection

Aged Trial Balance


Ok let s identify72 l.jpg

OK . . . Let’s Identify . . .

  • Data sources and destinations (terminators);

  • Transformation processes;

  • Data stores; and

  • Data flows


Slide73 l.jpg

Customer payments include cash received at the time of purchase as well as accounts payments received in the mail. At the end of the day, all checks are endorsed by the treasurer and a deposit slip is prepared for the checks and the cash. The checks, cash, and deposit slip are then deposited daily at the local bank by a clerk.


Slide74 l.jpg

Customer payments include cash received at the time of purchase as well as accounts payments received in the mail. At the end of the day, all checks are endorsed by the treasurer and a deposit slip is prepared for the checks and the cash. The checks, cash, and deposit slip are then deposited daily at the local bank by a clerk.

Process Checks


Slide75 l.jpg

When checks are received as payment for accounts due, a remittance slip is included with the payment. The remittance slips are used to update the accounts receivable file at the end of the day. The remittance slips are stored in a file drawer by date.


Slide76 l.jpg

When checks are received as payment for accounts due, a remittance slip is included with the payment. The remittance slips are used to update the accounts receivable file at the end of the day. The remittance slips are stored in a file drawer by date.

Update Accounts Receivable


Slide77 l.jpg

Every week, a cash receipts report and an aged trial balance are generated from the data in the accounts receivable ledger. The cash receipts report is sent to Scott and Susan. A copy of the aged trial balance by customer account is sent to the Credit and Collections Department.


Slide78 l.jpg

Every week, a cash receipts report and an aged trial balance are generated from the data in the accounts receivable ledger. The cash receipts report is sent to Scott and Susan. A copy of the aged trial balance by customer account is sent to the Credit and Collections Department.

Prepare Reports


What are the processes l.jpg

What are the Processes?

  • Process checks (1.0)

  • Update Customer Accounts (2.0)

  • Prepare Reports (3.0)


Slide81 l.jpg

Wow! That was fun! Now, let’s see if you can do it!

Try P6-6 (p. 179)


Slide82 l.jpg

As the internal auditor for No-Wear Products of Hibbing, MN, you have been asked by your supervisor to document the company’s current payroll processing system. Based on your documentation, No-Wear hopes to develop a plan for revising the current IS to eliminate unnecessary delays in paycheck processing.


Slide83 l.jpg

Your best explanation of the system came from an interview with the head payroll clerk.

The payroll processing system at No-Wear Products is fairly simple. Time data are recorded in each department using time cards and clocks.


Slide84 l.jpg

It is annoying, however, when people forget to punch out at night and we have to record their time information by hand. At the end of the period, our payroll clerks enter the time card data into a payroll file for processing. Our clerks are pretty good – though I’ve had to make my share of corrections when they mess up the data entry.


Slide85 l.jpg

Before the payroll file is processed for the current period, human resources sends us data on personnel changes, such as increases in pay rates and new employees. Our clerks enter this information into the payroll file so it is available for processing. Usually, when mistakes get back to us, it’s because human resources is recording the wrong pay rate or an employee has left and the department forgets to remove the record.


Slide86 l.jpg

The data are then processed and individual employee paychecks are generated. Several important reports are also generated for management – though I don’t know exactly what they do with them. In addition, the government requires regular federal and state withholding reports for tax purposes. Currently, the system generates these reports automatically, which is nice.


Required87 l.jpg

Required

  • Prepare a context diagram for the current payroll processing system at No-Wear Products.

  • Develop a DFD to document the payroll processing system at no-Wear Products.


Slide90 l.jpg

Wow! That was fun! Now, let’s see if you can do it!

Try P6-11 (p. 181)


Slide91 l.jpg

The local community college requires that each student complete a registration request form and mail or deliver it to the registrar’s office. A clerk enters the request into the system. First, the system checks accounts receivable subsystem to ensure that no fees are owed from the previous quarter. Next, for each course, the system checks the student transcript to ensure that he or she has completed the course prerequisites. Then the system checks class position availability and adds the students SSN to the class list.


Slide92 l.jpg

The report back to the student shows the result of registration processing: If the student owes fees, a bill is sent and the registration is rejected. If prerequisites for a course are not fulfilled, the student is notified and that course is not registered. If the class is full, the student request is annotated with “course closed.”


Slide93 l.jpg

If a student is accepted into a class, then the day, time, and room are printed next to the course number. Student fees and total tuition are computed and printed on the form. Student fee information is interfaced to the accounts receivable subsystem. Course enrollment reports are prepared for the instructors.


Required94 l.jpg

Required

  • Prepare a context diagram and at least two levels of logical DFDs for this operation.


  • Login