system analysis and sad
TRANSCRIPT
Phase 1 Systems PlanningPreliminary Investigation
SDLC PhasesPhase 1: Systems Planning
Systems Analysis and Design Fourth Edition
SDLC PhasesPhase 1: Systems Planning ObjectivesLearn how projects get started Learn how projects are evaluated initially
Systems Analysis and Design Fourth Edition
Chapter 2Preliminary Investigation
Systems Analysis and Design Fourth Edition
ObjectivesDescribe the strategic planning process, and why it is important to IT managers Explain the purpose of a mission statement Explain the SDLC as a framework for systems development and business modeling Explain the reasons for information systems projects and the factors that affect such projectsSystems 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 investigationSystems Analysis and Design Fourth Edition
IntroductionSystems planning tasksExamine the systems request Conduct a preliminary investigation Using SDLC and CASE tools to provide a framework
Systems Analysis and Design Fourth Edition
The Importance of Strategic PlanningOverview of the strategic planning processSWOT analysisStrengths Weaknesses Opportunities Threats
Systems Analysis and Design Fourth Edition
Click to see Figure 2-1 2-
Package
The Importance of Strategic PlanningFrom the strategic plan to business resultsExamples of mission statementsnFront Quebecor Printing Corp. Federal Express
Systems Analysis and Design Fourth Edition
Click to see Figure 2-2 2Package
The Importance of Strategic PlanningThe futureThriving e-commerce Rapid change
Systems Analysis and Design Fourth Edition
A Framework for Systems DevelopmentA business model exampleIT director favors SDLC using System Architect 2001 (S/A 2001)
Systems Analysis and Design Fourth Edition
Click to see Figure 2-3 2Package
A Framework for Systems DevelopmentA business model exampleIT director favors SDLC using System Architect 2001 (S/A 2001) Critical success factors Critical business issues Case for action S/A 2001 encyclopedias
Systems Analysis and Design Fourth Edition
Click to see Figure 2-4 2Package
A Framework for Systems DevelopmentThe role of the IT departmentClose link between operations and ITJAD and RAD
Some companies see IT as technology gatekeeper
Systems Analysis and Design Fourth Edition
Information Systems ProjectsStarting point is a systems request
Systems Analysis and Design Fourth Edition
Information Systems ProjectsReasons for systems projectsImproved service Better performance More information Stronger controls Reduced cost
Systems Analysis and Design Fourth Edition
Click to see Figure 2-5 2Package
Information Systems ProjectsReasons for systems projectsImproved service Better performance More information Stronger controls Reduced cost
Systems Analysis and Design Fourth Edition
Click to see Figure 2-6 2Package
Information Systems ProjectsFactors affecting systems projectsUser requests Top-management directives Existing systems Information technology department The economy Technology Government Software and hardware vendors Competitors Customers Click to see Figure 2-7 2SuppliersSystems Analysis and Design Fourth Edition
Package
Click to see Figure 2-8 2Package
Information Systems ProjectsSystems request formsStreamlines the process Ensures consistency Must be easy to understand and use Must include clear instructions
Systems Analysis and Design Fourth Edition
Click to see Figure 2-9 2Package
Evaluation of Systems RequestsEvaluation of projectsSystems review committeeEvaluate requests Set priorities Assess feasibility
Systems Analysis and Design Fourth Edition
Evaluation of Systems RequestsOverview of feasibilityFeasibility study uses three main yardsticks:Operational feasibility Technical feasibility Economic feasibility
Systems Analysis and Design Fourth Edition
Click to see Figure 2-10 2Package
Evaluation of Systems RequestsOperational feasibilityIs the system a practical and effective approach?
Operational feasibility depends on:Management and user support User involvement in planning Impact on performance, customers, and company image Reasonable schedulesSystems Analysis and Design Fourth Edition
Evaluation of Systems RequestsTechnical feasibilityDoes the organization have resources to develop/purchase and operate the system?
Technical feasibility depends on:Technical expertise within the organization Availability of necessary equipment Hardware and software reliability Adequate performance that will meet specifications Capacity for future needs/projected growth
Systems Analysis and Design Fourth Edition
Evaluation of Systems RequestsEconomic feasibilityDo the projected benefits outweigh the estimated costs of development, installation, and operation?
Economic feasibility depends on:Costs one time and continuing costs Benefits tangible and intangible benefits Timing of various costs and benefits Cost of not developing the system
Systems Analysis and Design Fourth Edition
Evaluation of Systems RequestsDetermining feasibilityFirst step is a determination of feasibility Goal is to identify nonfeasible projects as soon as possible Feasibility can change over timeNonfeasible projects can be resubmitted Initially feasible projects can be rejected later
Systems Analysis and Design Fourth Edition
Evaluation of Systems RequestsCriteria used to evaluate systems requestsReduce costs Increase revenue Produce more information or better results Serve customers and the organization better Reasonable time frame and lasting results Resources available Necessary or discretionary Tangible or intangible factors
Systems Analysis and Design Fourth Edition
Evaluation of Systems RequestsDiscretionary and non-discretionary projectsNecessity of project Possibly no need to review nondiscretionary projects in committee
Systems Analysis and Design Fourth Edition
Preliminary Investigation OverviewPurposeTo decide whether to continue the project
Objectives for a preliminary investigation1. Understand the problem 2. Define the project scope and constraints 3. Identify the benefits 4. Estimate the time and costs 5. Report to management
Interaction with managers and usersSystems Analysis and Design Fourth Edition
Click to see Figure 2-11 2Package
Steps in the Preliminary InvestigationStep 1: Understand the problemIdentify 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
Systems Analysis and Design Fourth Edition
Click to see Figure 2-12 2Package
Steps in the Preliminary InvestigationStep 2:Define the project scope and constraintsProject scopeDefine the range or extent of the project Set project boundaries
ConstraintsIdentify conditions, restrictions, or requirementsPresent vs. future Internal vs. external Mandatory vs. desirableSystems Analysis and Design Fourth Edition
Click to see Figure 2-13 2Package
Steps in the Preliminary InvestigationStep 3: Perform fact findingAnalyze organization charts Conduct interviews Observe operations Carry out a user survey
Systems Analysis and Design Fourth Edition
Click to see Figure 2-14 2Package
Steps in the Preliminary InvestigationStep 4: Determine feasibilityDetermine 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 needed Identify the sources of information Decide whether to use interviews, if so how many, and what time needed Decide whether to use surveys, if so who to complete it, and what time needed Estimate 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 investigation Key elementsEvaluation of systems request Estimate of costs and benefits Recommendations
Systems Analysis and Design Fourth Edition
Click to see Figure 2-15 2Package
Steps in the Preliminary InvestigationStep 6: Present results and recommendations to managementFinal task in the preliminary investigation Key elementsEvaluation of systems request Estimate of costs and benefits Recommendations
Oral and written presentations
Systems Analysis and Design Fourth Edition
Click to see Figure 2-16 2Package
SOFTWEAR, LIMITEDBackgroundSWL uses outside firm (BIS) for payroll processing Payroll deductions permitted for credit union and SWL stock purchase Recent reports of problems Errors in employee deductions Overtime necessary to correct Future Employee Savings Investment Plan (ESIP) is possibleSystems Analysis and Design Fourth Edition
SOFTWEAR, LIMITEDRequest for information technology servicesSystems request submitted by Michael JeremyDescribes problem generally Does not identify cause or propose solution
Systems Analysis and Design Fourth Edition
Click to see Figure 2-17 2Package
SOFTWEAR, LIMITEDRequest for information technology servicesSystems request submitted by Michael JeremyDescribes problem generally Does not identify cause or propose solution
IT department responseSWL does not have systems review committee Rick Williams assigned to preliminary investigationSystems Analysis and Design Fourth Edition
Click to see Figure 2-18 2Package
SOFTWEAR, LIMITEDRequest for information technology servicesSystems request submitted by Michael JeremyDescribes problem generally Does not identify cause or propose solution
IT department responseSWL does not have systems review committee Rick Williams assigned to preliminary investigation Michael Jeremy issues authorization memoSystems Analysis and Design Fourth Edition
Click to see Figure 2-19 2Package
SOFTWEAR, LIMITEDOrganization chartsCurrent organization charts not available Rick obtains job descriptions and draws charts
Systems Analysis and Design Fourth Edition
Click to see Figure 2-20 2Package
SOFTWEAR, LIMITEDInterviewsMichael Jeremy, vice president of finance Mike Feiner, director of human resources Amy Calico, director of payroll
Systems Analysis and Design Fourth Edition
SOFTWEAR, LIMITEDCurrent documentationResults and findingsSpecific procedures are being followed by the payroll department Written descriptions for these procedures are outdated Payroll department has never seen the stock plan deduction form
Systems Analysis and Design Fourth Edition
Click to see Figure 2-21 2Package
SOFTWEAR, LIMITEDPresentation to ManagementIT department tasksPrepared a preliminary investigation report Attached a cover memo Scheduled a presentation
Management decisionsAnalyze the payroll system as requested Scope to include whether current BIS can handle new ESIP optionsSystems Analysis and Design Fourth Edition
Click to see Figure 2-22 2Package
SOFTWEAR, LIMITEDPresentation to ManagementIT department tasksPrepared a preliminary investigation report Attached a cover memo Scheduled a presentation
Management decisionsAnalyze the payroll system as requested Scope to include whether current BIS can handle new ESIP optionsSystems Analysis and Design Fourth Edition
Click to see Figure 2-23 2Package
End Chapter 2