system analysis and design
44
Phase 1 Systems Planning Preliminary Investigation
Transcript of system analysis and design
Phase 1Systems Planning
Preliminary Investigation
Systems Analysis and Design Fourth Edition
SDLC Phases
Phase 1: Systems Planning
Systems Analysis and Design Fourth Edition
SDLC Phases
Phase 1: Systems Planning ObjectivesLearn how projects get startedLearn how projects are evaluated initially
Systems Analysis and Design Fourth Edition
Chapter 2
Preliminary Investigation
Systems Analysis and Design Fourth Edition
ObjectivesDescribe the strategic planning process,
and why it is important to IT managersExplain the purpose of a mission
statementExplain the SDLC as a framework for
systems development and business modeling
Explain the reasons for information systems projects and the factors that affect such projects
Systems Analysis and Design Fourth Edition
ObjectivesDescribe the initial review of systems
requests and the role of the systems review committee
Describe the internal and external factors that affect information systems projects
Define operational feasibility, technical feasibility, and economic feasibility
Describe the steps and end product of a preliminary investigation
Systems Analysis and Design Fourth Edition
Systems planning tasksExamine the systems requestConduct a preliminary investigationUsing SDLC and CASE tools to provide a
framework
Introduction
Systems Analysis and Design Fourth Edition
The Importance of Strategic PlanningOverview of the strategic planning
processSWOT analysis
StrengthsWeaknessesOpportunitiesThreats
Click to see Figure 2-1Click to see Figure 2-1 Package
Systems Analysis and Design Fourth Edition
The Importance of Strategic PlanningFrom the strategic plan to business
resultsExamples of mission statements
nFrontQuebecor Printing Corp.Federal Express
Click to see Figure 2-2Click to see Figure 2-2Package
Systems Analysis and Design Fourth Edition
The Importance of Strategic PlanningThe future
Thriving e-commerceRapid change
Systems Analysis and Design Fourth Edition
A Framework for Systems DevelopmentA business model example
IT director favors SDLC using System Architect 2001 (S/A 2001)
Click to see Figure 2-3Click to see Figure 2-3Package
Systems Analysis and Design Fourth Edition
A Framework for Systems DevelopmentA business model example
IT director favors SDLC using System Architect 2001 (S/A 2001)
Critical success factorsCritical business issuesCase for actionS/A 2001 encyclopedias
Click to see Figure 2-4Click to see Figure 2-4Package
Systems Analysis and Design Fourth Edition
A Framework for Systems DevelopmentThe role of the IT department
Close link between operations and ITJAD and RAD
Some companies see IT as technology gatekeeper
Systems Analysis and Design Fourth Edition
Information Systems Projects
Starting point is a systems request
Systems Analysis and Design Fourth Edition
Information Systems Projects
Reasons for systems projectsImproved serviceBetter performanceMore informationStronger controlsReduced cost
Click to see Figure 2-5Click to see Figure 2-5Package
Systems Analysis and Design Fourth Edition
Information Systems Projects
Reasons for systems projectsImproved serviceBetter performanceMore informationStronger controlsReduced cost
Click to see Figure 2-6Click to see Figure 2-6Package
Systems Analysis and Design Fourth Edition
Information Systems ProjectsFactors affecting systems projects
User requestsTop-management directivesExisting systemsInformation technology departmentThe economyTechnologyGovernmentSoftware and hardware vendorsCompetitorsCustomersSuppliers
Click to see Figure 2-8Click to see Figure 2-8Package
Click to see Figure 2-7Click to see Figure 2-7Package
Systems Analysis and Design Fourth Edition
Information Systems Projects
Systems request formsStreamlines the processEnsures consistencyMust be easy to understand and useMust include clear instructions
Click to see Figure 2-9Click to see Figure 2-9Package
Systems Analysis and Design Fourth Edition
Evaluation of Systems Requests
Evaluation of projectsSystems review committee
Evaluate requestsSet prioritiesAssess feasibility
Systems Analysis and Design Fourth Edition
Evaluation of Systems Requests
Overview of feasibilityFeasibility study uses three main
yardsticks:Operational feasibilityTechnical feasibilityEconomic feasibility
Click to see Figure 2-10Click to see Figure 2-10Package
Systems Analysis and Design Fourth Edition
Evaluation of Systems Requests
Operational feasibilityIs the system a practical and effective
approach?Operational feasibility depends on:
Management and user supportUser involvement in planningImpact on performance, customers, and
company imageReasonable schedules
Systems Analysis and Design Fourth Edition
Evaluation of Systems RequestsTechnical feasibility
Does the organization have resources to develop/purchase and operate the system?
Technical feasibility depends on:Technical expertise within the organizationAvailability of necessary equipmentHardware and software reliability Adequate performance that will meet
specificationsCapacity for future needs/projected growth
Systems Analysis and Design Fourth Edition
Evaluation of Systems Requests
Economic feasibilityDo the projected benefits outweigh the estimated
costs of development, installation, and operation?
Economic feasibility depends on:Costs — one time and continuing costsBenefits — tangible and intangible benefitsTiming of various costs and benefitsCost of not developing the system
Systems Analysis and Design Fourth Edition
Evaluation of Systems Requests
Determining feasibilityFirst step is a determination of feasibilityGoal is to identify nonfeasible projects as
soon as possibleFeasibility can change over time
Nonfeasible projects can be resubmittedInitially feasible projects can be rejected later
Systems Analysis and Design Fourth Edition
Evaluation of Systems Requests
Criteria used to evaluate systems requestsReduce costsIncrease revenueProduce more information or better resultsServe customers and the organization betterReasonable time frame and lasting resultsResources availableNecessary or discretionaryTangible or intangible factors
Systems Analysis and Design Fourth Edition
Evaluation of Systems Requests
Discretionary and non-discretionary projectsNecessity of projectPossibly no need to review non-
discretionary projects in committee
Systems Analysis and Design Fourth Edition
Preliminary Investigation OverviewPurpose
To decide whether to continue the projectObjectives for a preliminary investigation
1. Understand the problem2. Define the project scope and constraints3. Identify the benefits4. Estimate the time and costs5. Report to management
Interaction with managers and users
Click to see Figure 2-11Click to see Figure 2-11Package
Systems Analysis and Design Fourth Edition
Steps in the Preliminary InvestigationStep 1: Understand the problem
Identify the true nature of the problem and the reason for the systems request
Stated problem may not be the real problem
Clear statement defines the investigation scope
Click to see Figure 2-12Click to see Figure 2-12Package
Systems Analysis and Design Fourth Edition
Step 2:Define the project scope and constraintsProject scope
Define the range or extent of the projectSet project boundaries
ConstraintsIdentify conditions, restrictions, or requirements
Present vs. future Internal vs. external Mandatory vs. desirable
Click to see Figure 2-13Click to see Figure 2-13Package
Steps in the Preliminary Investigation
Systems Analysis and Design Fourth Edition
Steps in the Preliminary InvestigationStep 3: Perform fact finding
Analyze organization chartsConduct interviewsObserve operationsCarry out a user survey
Click to see Figure 2-14Click to see Figure 2-14Package
Systems Analysis and Design Fourth Edition
Steps in the Preliminary InvestigationStep 4: Determine feasibility
Determine operational, technical, and economic feasibility
Systems Analysis and Design Fourth Edition
Steps in the Preliminary InvestigationStep 5: Estimate time and cost to continue
developmentDetermine what information is neededIdentify the sources of informationDecide whether to use interviews, if so how
many, and what time neededDecide whether to use surveys, if so who to
complete it, and what time neededEstimate the cost of gathering, analyzing, and
reporting the information to management
Systems Analysis and Design Fourth Edition
Steps in the Preliminary InvestigationStep 6: Present results and
recommendations to managementFinal task in the preliminary investigationKey elements
Evaluation of systems requestEstimate of costs and benefitsRecommendations
Click to see Figure 2-15Click to see Figure 2-15Package
Systems Analysis and Design Fourth Edition
Steps in the Preliminary InvestigationStep 6: Present results and
recommendations to managementFinal task in the preliminary investigationKey elements
Evaluation of systems requestEstimate of costs and benefitsRecommendations
Oral and written presentations
Click to see Figure 2-16Click to see Figure 2-16Package
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITED
BackgroundSWL uses outside firm (BIS) for payroll
processing Payroll deductions permitted for credit
union and SWL stock purchase Recent reports of problems Errors in employee deductionsOvertime necessary to correctFuture Employee Savings Investment
Plan (ESIP) is possible
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITED
Request for information technology servicesSystems request submitted by
Michael JeremyDescribes problem generallyDoes not identify cause or propose
solution
Click to see Figure 2-17Click to see Figure 2-17Package
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITEDRequest for information technology
servicesSystems request submitted by Michael
JeremyDescribes problem generallyDoes not identify cause or propose solution
IT department responseSWL does not have systems review
committeeRick Williams assigned to preliminary
investigation
Click to see Figure 2-18Click to see Figure 2-18Package
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITEDRequest for information technology
servicesSystems request submitted by Michael
JeremyDescribes problem generallyDoes not identify cause or propose solution
IT department responseSWL does not have systems review
committeeRick Williams assigned to preliminary
investigationMichael Jeremy issues authorization memo
Click to see Figure 2-19Click to see Figure 2-19Package
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITEDOrganization charts
Current organization charts not availableRick obtains job descriptions and draws
charts
Click to see Figure 2-20Click to see Figure 2-20Package
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITEDInterviews
Michael Jeremy, vice president of finance
Mike Feiner, director of human resources
Amy Calico, director of payroll
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITEDCurrent documentation
Results and findingsSpecific procedures are being followed
by the payroll department Written descriptions for these
procedures are outdatedPayroll department has never seen the
stock plan deduction form
Click to see Figure 2-21Click to see Figure 2-21Package
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITED
Presentation to ManagementIT department tasks
Prepared a preliminary investigation report
Attached a cover memoScheduled a presentation
Management decisionsAnalyze the payroll system as
requestedScope to include whether current BIS
can handle new ESIP options
Click to see Figure 2-22Click to see Figure 2-22Package
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITED
Presentation to ManagementIT department tasks
Prepared a preliminary investigation report
Attached a cover memoScheduled a presentation
Management decisionsAnalyze the payroll system as
requestedScope to include whether current BIS
can handle new ESIP options
Click to see Figure 2-23Click to see Figure 2-23Package
EndChapter 2
