Session 02 CH 2 Introduction To Transaction Processing
Session 02 CH 2 Introduction To Transaction Processing
Chapter 2
Introduction to
Transaction
Processing
Dr Mark Gregory
Email:
[email protected]
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 2
An Overview of Transaction Processing
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 3
TRANSACTION CYCLES
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 4
Relationship Between Transaction Cycles
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 5
Accounting Records
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 6
MANUAL SYSTEMS
• Documents
• Source documents are documents that capture and formalize transaction data
needed for processing by their respective transaction cycles.
• Product documents are documents that result from transaction processing.
• Turnaround documents are product documents of one system that become source
documents for another system.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 7
THE AUDIT TRAIL
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 8
DIGITAL ACCOUNTING RECORDS
• Accounting systems may store data in four types of digital computer files:
• A master file contains account data.
• A transaction file is a temporary file that holds transaction records that will be used
to change or update data in a master file.
• A reference file is a file that stores the data used as standards for processing
transactions.
• An archive file is a file that contains records of past transactions that are retained for
future reference.
• The Digital Audit Trail
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 9
File Structures
• Digital file structures and storage techniques vary widely among transaction
processing systems.
• Some structures are effective at processing all records in large master files.
• Some file structures are better for directly locating and processing a single
record in a large file.
• So-called legacy systems are usually large mainframe systems implemented
in the late 1960s through the 1980s. The bespoke software is the stored
knowledge of the organization and is therefore difficult to replace (and to
maintain).
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 10
THE FLAT-FILE MODEL
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 11
THE FLAT-FILE MODEL (continued)
• Currency of Information
• Currency of information is a problem associated with the flat-file model because of
its failure to update all the user files affected by a change in status; this may result in
decisions based on outdated or incorrect information.
• Task-Data Dependency
• Task-data dependency is a user’s inability to obtain additional information as his or
her needs change.
• Flat Files Limit Data Integration
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 12
THE DATABASE APPROACH AND MODEL
• The database approach splits an organization’s data into separate tables,
with one table for each different entity (kind of data) – e.g. customer, order,
purchase…
• The database model is a symbolic model of the structure of, and the
associations between, an organization’s data entities.
• The database management system (DBMS) is a software system that
controls access to the data resource.
• The most striking difference between the database model and the flat-file
model is the pooling of data into a common database that all organizational
users share.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 13
Documentation Techniques
• Visual images convey vital system information more effectively and
efficiently than words.
• Accountants use system documentation routinely, as both systems
designers and auditors.
• Five basic documentation techniques commonly used by accountants are:
data flow diagrams, entity relationship diagrams, system flowcharts,
program flowcharts, and record layout diagrams.
• I also use NotionStructuring, my own modelling language.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 14
DATA FLOW DIAGRAMS AND ENTITY
RELATIONSHIP DIAGRAMS
• Data Flow Diagrams
• The data flow diagram (DFD) is the use of a set of symbols in a diagram to
represent the processes, data sources, data flows, and process sequences of
a current or proposed system.
• Entity Relationship Diagrams
• An entity relationship (ER) diagram is a documentation technique used to
represent the relationship among data entities in a system.
• Cardinality is the numeric mapping between entities such as one-to-one
(1:1), one-to-many (1:M), and many-to-many (M:M).
• A data model is the blueprint for what ultimately will become the physical
database.
• Relationship between ER Diagrams and DFDs
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 15
Data Flow Diagram Symbol Set
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 16
Data Flow Diagram of Purchases System
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 17
Entity Relationships Diagram Symbols
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 18
Data Model
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 19
SYSTEM FLOWCHARTS
• A system flowchart is used to show the relationship between the key
elements—input sources, programs, and output products—of computer
systems.
• Flowcharting Manual Activities
• Lay out the physical areas of activity.
• Transcribe the written facts into visual format.
• Flowcharting Computer Processes
• Transcribe the written facts into visual format.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 20
Symbol Set for Representing Manual Procedures
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 21
Symbol Set for Representing Computer
Processes
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 22
PROGRAM FLOWCHARTS
• A program flowchart is a diagram providing a detailed description of the
sequential and logical operations of the program.
• Every program represented in a system flowchart should have a supporting
program flowchart that describes its logic.
• The connector lines between the symbols establish the logical order of
execution.
• Program flowcharts are obsolescent.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 23
Program Flowchart Symbols
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 24
Program Flowchart for Edit Programs
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 25
System Flowchart
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 26
RECORD LAYOUT DIAGRAMS
• Record layout diagrams are used to reveal the internal structure of the
records that constitute a file or database table. The layout diagram usually
shows the name, data type, and length of each attribute (or field) in the
record.
• Detailed data structure information is needed for such tasks as identifying
certain types of system failures, analyzing error reports, and designing tests
of computer logic for debugging and auditing purposes.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 27
Record Layout Diagram for Customer File
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 28
Transaction Processing Models
• Alternative transaction processing models fall broadly into two types: (1)
batch processing and (2) real-time processing.
• Batch processing involves gathering transactions into groups or batches and
then processing the entire batch as a single event.
• Real-time processing systems process individual transactions continuously
as they occur.
• Many systems incorporate both real-time and batch processing features.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 29
UPDATING MASTER FILES FROM
TRANSACTIONS
• Updating a master file record involves changing the value of one or more of
its variable fields to reflect the effects of a transaction.
• Master file backup procedures
• If the current master file becomes corrupted or is destroyed, corporate IT
professionals can retrieve the most current backed-up file from the
archives.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 30
BATCH PROCESSING USING REAL-TIME
DATA COLLECTION
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 31
REAL-TIME PROCESSING
• Real-time systems process the entire transaction as each one occurs.
• Real-time processing is well suited to systems that process lower
transaction volumes and those that do not share common records.
• Terminals at distributed sites throughout the organization are used for
receiving, processing, and sending information on the status of current
transactions.
• Increasingly, real-time processing is made available outside a business.
Customers register themselves and place orders directly - this is online
business.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 32
Data Coding Schemes
• Data coding involves creating simple numeric or alphabetic codes to
represent complex economic phenomena that facilitate efficient data
processing.
• Many examples, such as car registration numbers, social security numbers
(National Insurance in the UK), IBAN numbers…
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 33
A SYSTEM WITHOUT CODES
• Business organizations process large volumes of transactions that are
similar in their basic attributes.
• Uncoded entry takes a great deal of recording space, is time-consuming to
record, and is obviously prone to many types of errors.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 34
A SYSTEM WITH CODES
• Advantages of data coding in AIS are:
• Concisely representing large amounts of complex information that would
otherwise be unmanageable.
• Providing a means of accountability over the completeness of the
transactions processed.
• Identifying unique transactions and accounts within a file.
• Supporting the audit function by providing an effective audit trail.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 35
NUMERIC AND ALPHABETIC CODING
SCHEMES
• Sequential Codes
• Sequential codes are codes that represent items in some sequential order
(ascending or descending).
• ADVANTAGES
• DISADVANTAGES
• Block Codes
• A numeric block code is a coding scheme that assigns ranges of values to specific
attributes such as account classifications.
• A chart of accounts is a listing of an organization’s accounts showing the account
number and name.
• ADVANTAGES
• DISADVANTAGES
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 36
Chart of Accounts
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 37
NUMERIC AND ALPHABETIC CODING
SCHEMES (continued)
• Group Codes
• Group codes are used to represent complex items or events involving two or more
pieces of related data.
• ADVANTAGES
• DISADVANTAGES
• Alphabetic Codes
• Alphabetic codes are alphabetic characters assigned sequentially.
• ADVANTAGES: Alphanumeric codes are codes that allow the use of pure alphabetic
characters embedded within numeric codes.
• DISADVANTAGES
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 38
NUMERIC AND ALPHABETIC CODING
SCHEMES (continued)
• Mnemonic Codes
• Mnemonic codes are alphabetic characters in the form of acronyms and other
combinations that convey meaning.
• ADVANTAGES
• DISADVANTAGES
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 39
Appendix - Data Structures
• Data structures are techniques for physically arranging records in a file.
• Organization refers to the way records are physically arranged on the
secondary storage device (e.g., a disk).
• Access method is a technique used to locate records and navigate through
the database. The most important are sequential (serial) and indexed.
• Flat-file approach is an organizational environment in which users own
their data exclusively within their own application. The data is difficult or
impossible to share with others.
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 40
Typical File Processing Operations
James A. Hall, Accounting Information Systems, 10th Edition. © 2019 Cengage. All Rights Reserved.
May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part. 41