1. Physical Level Systems Design: A Methodology for Inclusion in Our Systems Analysis and Design Textbooks Paul H. Rosenthal L. Jane Park College of Business and Economics California State University, Los Angeles

2. Physical System Design: Completes the Planning/Justification Life-Cycle

3. The Physical Design Methodology A physical design is created from a DFD based logical design, by separating processes, data stores, and interfaces by time (daily vs. monthly, day vs. night...), place (client or server, centralized vs. distributed...), online vs. batch, manual vs. automated, etc.

4. Levels of Physical Design Charting Enterprise Application Level Business Process Level Program Level Using VISIO Symbols

5. Enterprise Application Level TPS Example

6. A Simplification from Turban

7. Business Process Level

8. Program Level

9. The Simplification from Langer

10. The Key Tool in Planning/Justification: Estimation It is possible to estimate Software Projects accurately. Such estimation is useful. Why? Once all stakeholders agree on estimation procedures, negotiations can involve inputs (features and resources) NOT outputs (time and dollars). Function Point measures are the most popular for Information Systems estimation. Illustration Follows

11. Function Points Methodology

12. Analyzing the Information Domain

13. We need to raise the Justification content level in our courses so that our graduates will be able to specify, estimate, design, and implement high quality and successful systems, and continue to reduce our industry's high project failure rate. Note: “Successful systems” are defined as those measured and confirmed useful by their end users in their operational environment SUMMARY STATEMENT