Transaction Processing Systems: The Need for Physical Design Methodology Teaching

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

2. Outline • Importance of TPS Applications • Scope of TPS Applications • Recommended Physical Design Charting Approach • Typical Physical Design Methodologies • Oversimplification of Design Examples

3. 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.

4. A Typical Text’s View Turban, McLean & Wetherbe (2004). IT for Management.

5. The True Scope of Transaction Processing Systems

6. 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.

7. A Term Project Architecture

9. 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

10. Typical Physical Design Methodologies Pressman (2004) – diagrams a process view of the transition to design

11. Oversimplification of Design Examples

12. Partial Function Design

13. More Complete Online Scope

14. Oversimplification of Scope Shelly, Cashman & Rosenblatt (2006)

15. More Complete System Scope

16. Standard USE Case Charting Method

17. Replace Incorrect Symbols