Transcript Transaction Processing Systems: The Need for Systems Design Methodology Teaching Paul Rosenthal California State University, Los Angeles.

Transaction Processing Systems:
The Need for Systems Design
Methodology Teaching
Paul Rosenthal
California State University, Los Angeles
Outline
• Importance of TPS Applications
• Scope of TPS Applications
• Recommended Physical Design Charting
Approach
• Typical Physical Design Methodologies
• Oversimplification of Design Examples
Transaction Processing Systems
• Transaction Processing Systems
applications (TPS) are the core of
information systems (IS) impact on the
public.
• In the typical business organization,
because of the number of clerical workers
normally involved, they constitute the
majority of IS project funding
requirements.
A Typical Text’s View
Turban, McLean & Wetherbe (2004). IT for Management.
The True Scope of Transaction Processing Systems
Op's Data
Interactiv e
Data
Customers et.
Online TPS
Processing
(24/7)
Clerks
Log Data
Superv isors
Mgmt Data
Cumulativ e
Data
Analy sis
Data
Night-time Batch
Processing
Interf acing
Sy stems
Daily
Reports
Back
up
Data
Periodic Batch
Processing
(Monthly )
Monthly
Reports
MIS\DSS
Data
Warehouse
Financial
Sy stems
Managers
MIS/DSS Retriev al
Sy stem
Staf f /Researchers
Critical
Success
Factors
ESS Analy sis
Sy stem
External
Data
ESS Data
ESS Graphic
Presentation
Sy stems
Executiv es
Planners
Figure 1: Structure of Trans action Proce s s ing Sys te m s
The Need for Integrated Design
Methodology Teaching
System
Design
Process
Project
Design
Process
Relationship
Customer
Purchasing System
Use Case
Enroll or update
Rent videos
m em ber
<<Include>>
Analysis
Return videos
<<Include>>
<<Include>>
Charge credit
card
Find overdue
videos
<<Include>>
System
Boundary
Actor
Clerk
Credit Card Company
USE Case Diagram from V/S/P Chapter 8
Logical
Design
Analysis
Module 1
Entry
to
Table
Order
Slip
Membership
Card
Receptionist
Scan
Card
Process
Ne
w Tab
Re
cor
d
Tab
Processing
System
Physical Design
Module 3
Exiting
in Inse
to
Ta
d
Scan
Order
Slip
Receptionist
Re
Tab
Order
Entry
Process
Member
Design WBS
r Ite
ms
cor
Order
Process
Server
Ba
s
Item
Order
Slip
od
at Table
Module 2
Ordering
Fo
rt
b Ord
Re er
co s
rd
Member
Kitchen
Order
Bar
Order
to
Monthly
Billing
System
Priced Tab
Billing
Process
Sign
Signature
Process
Receipt
Receipt
File
Design Plan
Op's Data
Interactive
Data
Online TPS
Processing
(24/7)
Customers et.
Clerks
Log Data
Supervisors
Mgmt Data
Cumulative
Data
Analysis
Data
Night-time Batch
Processing
Interfacing
Systems
Daily
Reports
Periodic Batch
Processing
(Monthly)
MIS\DSS
Data
Warehouse
Back
up
Data
Monthly
Reports
Financial
Systems
Project Planning and Staffing Design
Managers
MIS/DSS Retrieval
System
Staff/Researchers
ESS Analysis
System
ESS Data
External
Data
ESS Graphic
Presentation
Systems
Executives
Planners
Figure 1: Structure of Transaction Processing Systems
CostBenefit
Analysis
Implementation
Process
The Need for Physical Design
Methodology Teaching
For TPS, a physical design is created from a
DFD based logical design, by separating
processes and data stores by:
•
•
•
•
time (daily vs. monthly, day vs. night ...),
place (client or server),
centralized vs. distributed...,
online vs. batch,
• manual vs. automated, etc.
A Term Project Architecture
Country Club Architecture
Tennis
Office
Managers
Office
A/P
Restaurant
Golf
Office
Reception/
Membership
Kitchen
Bar
Store
WAN
Executive
Offices
Queries
Accounting
LAN
Online
and
Batch
Operations
Data
MIS
Data
AS/400 (i5)
AdHoc &
Scheduled
MIS Reports
Statements etc..
Headquarters Architecture
Accounting
Reports
Payments etc..
Receptionist
Scan
Card
Process
d
Tab
Processing
System
Receptionist
s
d
Re
Kitchen
Order
Priced Tab
Billing
Process
to
Monthly
Billing
System
Sign
Signature
Process
Ite
m
cor
Scan
Order
Slip
Ba
r
s
Order
Entry
Process
Member
co r
Order
Process
Waitress
Module 3
Exiting
Re
Item
Order
Slip
wT
ab
od
Fo
at Table
Module 2
Ordering
Ne
Tab
Member
to
Table
Order
Slip
in Inse
to r
Ta t O
b rd
R er
ec s
or
d
Membershi
p
Card
Module 1
Entry
Receipt
Receipt
File
Physical Level Process Design (Restaurant)
Bar
Order
Typical Physical Design Methodologies
Whitten (2004) - Their physical data flow
diagram based method for an online
system demonstrates:
• person/machine boundaries
• network architecture
• technology assignment
• process distribution
• data distribution
Typical Physical Design Methodologies
Pressman (2004) – diagrams a process view of the
transition to design
Oversimplification of Design
Examples
Partial Function Design
Enter Valid Card
C Invalid Card or “Time Out”
C Enter Valid Bank Card
Insert Password
C Valid Password
C Invalid Password or “Time Out”
Main Menu
C Select “Deposit”
C Select “Withdraw”
C Select “Inquiry”
C Select “Transfer”
Deposit Funds
Transfer Funds
Withdraw Funds
C Complete Activity
Bank Teller state transition diagram
(Langer , page 72)
Inq uiry
More Complete Online Scope
Welcome Screen
Startup
Insert Bank Card
Validate Card
Proposed Symbolism
Eject
if Invalid
A State
An Automated Transition
Keyin Password
(A system originated action )
Validate Password
A Physical Transition
(A Customer originated action )
Valid Account
Complete Activity
Main Menu
Select “Deposit”
Select “Done”
Select “Withdraw”
Select “Inquiry”
Select “Transfer”
Deposit Funds
Transfer Funds
Withdraw Funds
Recommended Bank Teller state transition diagram
Inq uiry
Oversimplification of Scope
Illustration of com bined Online and Batch from S&C Chap 8
Shelly, Cashman & Rosenblatt (2006)
More Complete System Scope
End of
Day
POS
Terminal
POS
Program
(Online)
Inventory
Database
Cumulative
Daily Sales
Transaction
File
Daily Sales
Program
(Batch)
Accounting
Database
Phys ical Ele m e nts Adde d/Corre cte d
Daily Sales
Report
Standard USE Case Charting Method
Relationship
Customer
Purchasing System
Use Case
Enroll or update
Rent videos
member
<<Include>>
Return videos
<<Include>>
<<Include>>
Charge credit
card
<<Include>>
Find overdue
videos
System
Boundary
Actor
Credit Card Company
Clerk
USE Case Diagram from V/S/P Chapter 8
Replace Incorrect Symbols
Relationship
Inve ntory
Sys te m
Customer
Use Case
Enroll or update
Rent videos
member
<<Include>>
Return videos
<<Include>>
<<Include>>
Charge credit
card
Cre dit Card
Com pany Sys te m
<<Include>>
Find overdue
videos
System
Boundary
Actor
Clerk