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

Slides:



Advertisements
Similar presentations
1 9 Moving to Design Lecture Analysis Objectives to Design Objectives Figure 9-2.
Advertisements

Chapter 10: The Traditional Approach to Design
Systems Analysis and Design in a Changing World, Fifth Edition
Traditional Approach to Design
Chapter 10 The Traditional Approach to Design
Chapter 9: The Traditional Approach to Design Chapter 10 Systems Analysis and Design in a Changing World, 3 rd Edition.
Chapter 71 Information Technology For Management 6 th Edition Turban, Leidner, McLean, Wetherbe Lecture Slides by L. Beaubien, Providence College John.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 13 Application Architecture and Modeling.
Chapter 1 Assuming the Role of the Systems Analyst
Flow Anomaly Detection in Firewalled Networks Research Report Mike Chapple December 15, 2005.
Bina Nusantara 13 C H A P T E R APPLICATION ARCHITECTURE AND MODELING.
Information Systems Education: What’s missing? Paul H. Rosenthal Information Systems Department, California State University, Los Angeles.
13-1 Chapter 13 – Application Architecture and Modeling Objectives: Define an information system’s architecture in terms of the KNOWLEDGE, PROCESSES, and.
13-1 Chapter 13 - Objectives Define an information system’s architecture in terms of the KNOWLEDGE, PROCESSES, and COMMUNICATION building blocks. Differentiate.
Chapter 1 Assuming the Role of the Systems Analyst
 Dr. Syed Noman Hasany.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing and.
Process Models: Data Flow Diagrams
Information Technologies: Concepts and Management
INTRODUCTION Management information systems combine hardware, software and network products in an integrated solution that provides managers with data.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
NewTech Book Store Faculty: Mr. Hieu Le Trung Student: Tan Do Nhat Batch code: B Centre: NIIT Saigon Project Report.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
MIS 301 Information Systems in Organizations
Systems Analysis and Design: The Big Picture
System Analysis & Design
Review for Midterm Exam Accounting Information Systems Romney and Steinbart Linda Batch February 2012.
Management of Source Code Integrity Presented by O/o the Accountant General (A&E), Jammu and Kashmir.
UML - Development Process 1 Software Development Process Using UML (2)
Chapter 31 Information Technology For Management 6 th Edition Turban, Leidner, McLean, Wetherbe Lecture Slides by L. Beaubien, Providence College John.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Chapter 9 Moving to Design. The Structured Approach To Designing The Application Architecture Module-an identifiable component of a computer program that.
1. Topics to be discussed Introduction Objectives Testing Life Cycle Verification Vs Validation Testing Methodology Testing Levels 2.
Data Flow Diagrams A structured analysis technique that employs a set of visual representations of the data that moves through the organization, the paths.
Data Flow Diagram A method used to analyze a system in a structured way Used during: Analysis stage: to describe the current system Design stage: to describe.
Information Systems Analysis and Design
CHAPTER 8 Organizational Information Systems. CHAPTER OUTLINE  Transaction Processing Systems (TPS)  Functional Area Information Systems (FAIS)  Enterprise.
Chapter 10 Information Systems Analysis and Design
Submission doc.: IEEE wpp July 2004 Paul C. Canaan, Intel Corporation.Slide 1 Wireless Performance Prediction – Development Milestones.
Chapter 9 Moving to Design
13-1 Application Architecture Application architecture – a specification of the technologies to be used to implement information systems. The blueprint.
10 ITK261 The traditional approach to design Reading: Chapter 10 Oct 9, 11.
10 The traditional approach to design Hisham Alkhawar.
Systems Analysis What is it?. 2 A Systems Development Life Cycle The need for change is recognised or planned for Outline requirements may be issued,
An application architecture specifies the technologies to be used to implement one or more (and possibly all) information systems in terms of DATA, PROCESS,
SOA Landscape Recommendations By >. Who we are  Team Members  Company History  Current & Past Client Projects  Note: have fun here. Make up your history.
Decision Support and Date Warehouse Jingyi Lu. Outline Decision Support System OLAP vs. OLTP What is Date Warehouse? Dimensional Modeling Extract, Transform,
Computer Concepts 2014 Chapter 10 Information Systems Analysis and Design.
Structured design - 1 © Minder Chen, Produce Paycheck Retrieve Employee Record Global Data Store Offpage Calling Module Called Module System.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Systems Planning and Project Planning: Is Integration Needed? One of the weaknesses in our current SDLC methodologies is the isolation of system design.
Does IS Education Address Enterprise IT User Concerns? Bart Longenecker University of South Alabama Paul Rosenthal California State University, Los Angeles.
Data Flow Diagrams. A diagram which shows the movement of data in a system.
Physical Level Systems Design: A Methodology for Inclusion in Our Systems Analysis and Design Textbooks Paul H. Rosenthal L. Jane Park College of Business.
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
Chapter 1 Assuming the Role of the Systems Analyst.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 1: Introduction
Business System Development
Ch 7: using Data Flow Diagrams
Rumbaugh’s Objectmodeling Technique
LESSON 2 SYSTEM ANALYSIS & DESIGN PHASE
Profitability Management Logical Diagram
تحلیل سیستم‌ها مدل‌سازی پردازشی.
Application Architecture and Modeling
IS Theories & Practices
Figure 8. 1 Order-delivery cycle with and without EDI
G063 - Data flow diagrams.
Introduction to Databases Transparencies
EXAMPLE TEXT CORE DIAGRAMS EXAMPLE TEXT EXAMPLE TEXT EXAMPLE TEXT
Goal and Scope Rubric, 0.5 points
Presentation transcript:

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

The Need for Integrated Design Methodology Teaching

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

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

More Complete Online Scope

Oversimplification of Scope Shelly, Cashman & Rosenblatt (2006)

More Complete System Scope

Standard USE Case Charting Method

Replace Incorrect Symbols