it 21103/41103-01 system analysis & design. chapter 02 project initiation

Post on 04-Jan-2016

221 Views

Category:

Documents

3 Downloads

Preview:

Click to see full reader

TRANSCRIPT

IT 21103/41103-01IT 21103/41103-01

System Analysis & DesignSystem Analysis & Design

Chapter 02Chapter 02

Project InitiationProject Initiation

Analyst RoleAnalyst Role

Problem SolverProblem Solver

First StepsFirst Steps

““What is the Problem?”What is the Problem?”

Define the Real ProblemDefine the Real Problem

Information RelevancyInformation Relevancy

Usefulness of system outputsUsefulness of system outputs

Users need to be consultedUsers need to be consulted

Information AccuracyInformation AccuracyConcerned with System ErrorsConcerned with System Errors

Develop an Error ThresholdDevelop an Error Threshold

Information TimelinessInformation TimelinessProblems with information Problems with information

availabilityavailability

I/O BottlenecksI/O Bottlenecks

Time causes erosion of the system Time causes erosion of the system processing speedprocessing speed

Information UsabilityInformation UsabilityInformation PackagingInformation Packaging

Tailor information to fit the user’s Tailor information to fit the user’s needsneeds

Information AffordabilityInformation AffordabilityOpportunity CostsOpportunity Costs

Actual CostsActual Costs

Persistent Upgrades or High Persistent Upgrades or High MaintenanceMaintenance

Information AdaptabilityInformation Adaptability

Flexibility in Hardware and Software Flexibility in Hardware and Software expandability and compatibilityexpandability and compatibility

Users will abandon unused portions Users will abandon unused portions of the systemof the system

Information AccessibilityInformation AccessibilityUsers interaction with the systemUsers interaction with the system

Internet & IntranetsInternet & Intranets

Depends on the type of userDepends on the type of user

SolutionsSolutions

Page 37Page 37

Figure 2-2Figure 2-2

Small Enterprise ProblemsSmall Enterprise Problems

Source Data Input InefficienciesSource Data Input Inefficiencies

Breakdowns in Subsystem Breakdowns in Subsystem IntegrationIntegration

Small Enterprise ProblemsSmall Enterprise ProblemsSource Data Input InefficienciesSource Data Input Inefficiencies

How the data is entered into the How the data is entered into the systemsystem

A major problemA major problem

Small Enterprise ProblemsSmall Enterprise ProblemsBreakdowns in Subsystem Breakdowns in Subsystem

IntegrationIntegration

Many subsystems functioning Many subsystems functioning together logicallytogether logically

Fact-FindingFact-Finding

The Analyst must do Research The Analyst must do Research about the information system they about the information system they

are to examineare to examine

Fact-FindingFact-FindingIndustry ResearchIndustry Research

Journals, Magazines, Libraries, Journals, Magazines, Libraries, State/Federal Agencies, State/Federal Agencies,

Professional Organizations, etcProfessional Organizations, etc

Fact-FindingFact-Finding

Online ResearchOnline Research

Search Engines (Google), etcSearch Engines (Google), etc

Fact-FindingFact-FindingPersonal ContactsPersonal Contacts

Personal InterviewsPersonal Interviews

QuestionnairesQuestionnaires

On-Site ObservationsOn-Site Observations

Fact-FindingFact-Finding

Page 43Page 43

Fact-FindingFact-Finding

Request for ServicesRequest for Services

Very Important to get in writing what Very Important to get in writing what the user wants!the user wants!

Page 44Page 44

Fact-FindingFact-Finding

Documentation ReviewDocumentation Review

Collect samples of source and Collect samples of source and output documents of the current output documents of the current

systemsystem

Feasibility AnalysisFeasibility AnalysisA ballpark estimate of what the A ballpark estimate of what the

project will cost and how long it will project will cost and how long it will take to completetake to complete

An Estimate OnlyAn Estimate Only

Feasibility AnalysisFeasibility AnalysisFour Components:Four Components:

OperationalOperational

TechnicalTechnical

ScheduleSchedule

EconomicEconomic

Feasibility AnalysisFeasibility AnalysisOperational:Operational:

Is there a workable design for the Is there a workable design for the intended systemintended system

Feasibility AnalysisFeasibility AnalysisTechnical:Technical:

Is there technology available to Is there technology available to make the system workmake the system work

Feasibility AnalysisFeasibility Analysis

Schedule:Schedule:

Can the project be completed within Can the project be completed within the agreed timeframethe agreed timeframe

Feasibility AnalysisFeasibility Analysis

Economic:Economic:

Can the project be completed within Can the project be completed within the budget constraintsthe budget constraints

Feasibility AnalysisFeasibility Analysis

Build-Or-BuyBuild-Or-Buy

This is a strategy to determine if This is a strategy to determine if building a system or buying a pre-building a system or buying a pre-

built system is most feasiblebuilt system is most feasible

Feasibility AnalysisFeasibility Analysis

Documentation:Documentation:

Page 47Page 47

Feasibility AnalysisFeasibility Analysis

Feasibility Report:Feasibility Report:

A project deliverableA project deliverable

A common point of reference for A common point of reference for negotiationsnegotiations

Feasibility AnalysisFeasibility Analysis

Project Contract:Project Contract:

Clear agreement about the work to Clear agreement about the work to be done for the projectbe done for the project

(Modifications may occur)(Modifications may occur)

Feasibility AnalysisFeasibility Analysis

Project Contract:Project Contract:

Problem SummaryProblem Summary

ScopeScope

ConstraintsConstraints

ObjectivesObjectives

Feasibility AnalysisFeasibility Analysis

Problem Summary:Problem Summary:

Concise statement including the Concise statement including the user’s original request and the user’s original request and the

preliminary findings of the analystpreliminary findings of the analyst

(The Analyst and (The Analyst and

Users must agree)Users must agree)

Feasibility AnalysisFeasibility Analysis

Scope:Scope:

Agreement on the boundaries of the Agreement on the boundaries of the work to be donework to be done

Agree on changes that may occur Agree on changes that may occur during the projectduring the project

Feasibility AnalysisFeasibility Analysis

Project Constraints:Project Constraints:

CostsCosts

DeliveryDelivery

Access to the current system and Access to the current system and usersusers

Unusual circumstancesUnusual circumstances

Feasibility AnalysisFeasibility Analysis

Project Objectives:Project Objectives:

Agreement on the consequences of Agreement on the consequences of the new systemthe new system

What is the measurement of What is the measurement of successsuccess

(Develop a Baseline measurement)(Develop a Baseline measurement)

QuestionsQuestions

Assignment # 02Assignment # 02

Page 59Page 59

Appendix BAppendix B

top related