1. SYSTEMSDESIGNANALYSIS 1 Chapter 3 Feasibility Jerry Post Copyright © 1997

2. SYSTEMSDESIGN 2 Problem Signs

3. SYSTEMSDESIGN 3 Feasibility  Helps organization attain overall objectives.  Is possible to accomplish with present resources  Technical Feasibility Add on to present system. Technology available tomeet users’ needs.  Economic Feasibility Systems analysts’ time. Cost of systems study. cost of employees’ time for study. Estimated cost of hardware. Cost of packaged software/software development.  Operational Feasibility Whether the system will operate when installed. Whether the system will be used.

4. SYSTEMSDESIGN 4 Feasibility: Benefits and Costs  Benefits  Reduce Problems  Improve Operations Speeding up process Streamlining a process by eliminating steps. Combining processes. Reducing input errors. Reducing redundant output. Improving system integration. Improving worker satisfaction. Improving ease of customer, supplier, and vendor interaction.  Costs  Stages Design Analysis Development Implementation  Fixed versus variable Up-front Annual  Common sources Hardware Software People

5. SYSTEMSDESIGN 5 Selection Criteria  Backing from management.  Appropriate timing of project commitment.  Possibility of improving attainment of organizational goals.  Practical in terms of resources for analyst and organization.  Project is worthwhile compared to other ways organization could invest money.

6. SYSTEMSDESIGN 6 Activity Planning  Analysis  Data gathering  Data flow and decision analysis  Proposal presentation  Design  Data entry design  Input design  Output design  Data organization  Implementation  Implementation  Evaluation

7. SYSTEMSDESIGN 7 Scheduling: Gantt Charts  Data gathering  Conduct Interviews3  Administer questionnaires4  Read company reports4  Introduce prototype5  Observe reactions to prototype3  Data flow and decision analysis  Analyze data flow8  Proposal preparation  Benefit/cost analysis3  Prepare proposal2  Present proposal2 Estimated weeks Project time activity start end percent complete A B C D E 2 4 6 8 10 12 14 16

8. SYSTEMSDESIGN 8 Microsoft Project: Gantt Chart

9. SYSTEMSDESIGN 9 PERT Diagram  Program/Project Evaluation and Review Technique  Highlight parallel operations  Show precendence/ dependence  Critical path (limiting factor)  A + C = 4 + 5 = 9 Limiting/Critical path  B + D = 2 + 3 = 5 Slack Saving time will not speed up the project. 10 20 30 4050 A,4 C,5 B,2 D,3 E,6

10. SYSTEMSDESIGN 10 Microsoft Project: PERT  Automatically generated/Change view.  Tasks shown as boxes, not lines. Project

11. SYSTEMSDESIGN 11 PERT: Expediting  Find task segment with least cost of reduction.  Continue until no further time reduction is possible.  Management makes final choice based on costs and benefits. 103050607080 40 20 A,3 C,4 B,4 D,8 E,5 F,3 G,3H,2 I,2 Critical Path: 22 1 2 6 3 115