1. IT 21103/41103-01 System Analysis & Design

2. Chapter 02 Project Initiation

3. Analyst Role Problem Solver

4. First Steps “What is the Problem?” Define the Real Problem

5. Information Relevancy Usefulness of system outputs Users need to be consulted

6. Information Accuracy Concerned with System Errors Develop an Error Threshold

7. Information Timeliness Problems with information availability I/O Bottlenecks Time causes erosion of the system processing speed

8. Information Usability Information Packaging Tailor information to fit the user’s needs

9. Information Affordability Opportunity Costs Actual Costs Persistent Upgrades or High Maintenance

10. Information Adaptability Flexibility in Hardware and Software expandability and compatibility Users will abandon unused portions of the system

11. Information Accessibility Users interaction with the system Internet & Intranets Depends on the type of user

12. Solutions Page 37 Figure 2-2

13. Small Enterprise Problems Source Data Input Inefficiencies Breakdowns in Subsystem Integration

14. Small Enterprise Problems Source Data Input Inefficiencies How the data is entered into the system A major problem

15. Small Enterprise Problems Breakdowns in Subsystem Integration Many subsystems functioning together logically

16. Fact-Finding The Analyst must do Research about the information system they are to examine

17. Fact-Finding Industry Research Journals, Magazines, Libraries, State/Federal Agencies, Professional Organizations, etc

18. Fact-Finding Online Research Search Engines (Google), etc

19. Fact-Finding Personal Contacts Personal Interviews Questionnaires On-Site Observations

20. Fact-Finding Page 43

21. Fact-Finding Request for Services Very Important to get in writing what the user wants! Page 44

22. Fact-Finding Documentation Review Collect samples of source and output documents of the current system

23. Feasibility Analysis A ballpark estimate of what the project will cost and how long it will take to complete An Estimate Only

24. Feasibility Analysis Four Components: OperationalTechnicalScheduleEconomic

25. Feasibility Analysis Operational: Is there a workable design for the intended system

26. Feasibility Analysis Technical: Is there technology available to make the system work

27. Feasibility Analysis Schedule: Can the project be completed within the agreed timeframe

28. Feasibility Analysis Economic: Can the project be completed within the budget constraints

29. Feasibility Analysis Build-Or-Buy This is a strategy to determine if building a system or buying a pre- built system is most feasible

30. Feasibility Analysis Documentation: Page 47

31. Feasibility Analysis Feasibility Report: A project deliverable A common point of reference for negotiations

32. Feasibility Analysis Project Contract: Clear agreement about the work to be done for the project (Modifications may occur)

33. Feasibility Analysis Project Contract: Problem Summary ScopeConstraintsObjectives

34. Feasibility Analysis Problem Summary: Concise statement including the user’s original request and the preliminary findings of the analyst (The Analyst and Users must agree)

35. Feasibility Analysis Scope: Agreement on the boundaries of the work to be done Agree on changes that may occur during the project

36. Feasibility Analysis Project Constraints: CostsDelivery Access to the current system and users Unusual circumstances

37. Feasibility Analysis Project Objectives: Agreement on the consequences of the new system What is the measurement of success (Develop a Baseline measurement)

38. Questions

39. Assignment # 02 Page 59 Appendix B