1 / 17

Transaction Processing Systems: The Need for Physical Design Methodology Teaching

Transaction Processing Systems: The Need for Physical 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

darice
Télécharger la présentation

Transaction Processing Systems: The Need for Physical Design Methodology Teaching

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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

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

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

  10. Oversimplification of Design Examples

  11. Partial Function Design

  12. More Complete Online Scope

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

  14. More Complete System Scope

  15. Standard USE Case Charting Method

  16. Replace Incorrect Symbols

More Related