IT 21103/ System Analysis & Design

Chapter 02 Project Initiation

Analyst Role Problem Solver

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

Information Relevancy Usefulness of system outputs Users need to be consulted

Information Accuracy Concerned with System Errors Develop an Error Threshold

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

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

Information Affordability Opportunity Costs Actual Costs Persistent Upgrades or High Maintenance

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

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

Solutions Page 37 Figure 2-2

Small Enterprise Problems Source Data Input Inefficiencies Breakdowns in Subsystem Integration

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

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

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

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

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

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

Fact-Finding Page 43

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

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

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

Feasibility Analysis Four Components: OperationalTechnicalScheduleEconomic

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

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

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

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

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

Feasibility Analysis Documentation: Page 47

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

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

Feasibility Analysis Project Contract: Problem Summary ScopeConstraintsObjectives

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)

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

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

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

Questions

Assignment # 02 Page 59 Appendix B