week 14 - 5130_Ch18-19_SystemDev

week 14 - 5130_Ch18-19_SystemDev - -1-Systems...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: -1-Systems DevelopmentSystems DevelopmentDr. Myles SternACC 5130 and 7145(513LEC10)-2-Some Overall ConsiderationsSome Overall Considerations&Emphasize the "business needs."&Analysis vs. Design vs. Development&Structured systems development&Distinguish between "design" and"implementation"-3-Emphasize the "BusinessNeeds."Emphasize the "BusinessNeeds."$Involve the users!%The "Steering Committee" approach%"An informed user is our best customer!"%Involve users at each phase of the SDLC.$Cost-benefit analysis%Tangible and intangible benefits and costs%Don't let the technology obscure your vision!-4-Analysis vs. Design vs.DevelopmentAnalysis vs. Design vs.Development$Again, the user perspective$Very generally, "analysis" involves specifying theusers' needs.$Design is building a system to meet those needs.$In practice, activities flow from analysis intodesign, often without a clear demarcationbetween these phases.-5-Structured SystemsDevelopmentStructured SystemsDevelopmentCombining top-down and bottom-up approachesCombining top-down and bottom-up approaches$Top-down view of the overall business situation$Bottom-up analysis of users' needs%Involve as many users as possible.$Top-down, hierarchical design%Structure charts: an organization chart for the system%Modular approach-6-Distinguish between "design"and "implementation."Distinguish between "design"and "implementation."Design for the future but implement for today!Design for the future but implement for today!$System design should be conceptual and largelyindependent of specific hardware and software.%Avoid biasing the design.%Examples of past mistakes$Reduce conceptual design to an implementationthat will work.%Examples of past mistakes$The importance of information systems planning:a long-term roadmap-7-Systems Development Life Cycle (SDLC)Systems Development Life Cycle (SDLC)Elements of the cycle1. Initiation: Define the need.2. Feasibility study3. Systems analysis4. Systems design5. Programming6. Conversion and implementation7. Operation (production)8. Post-implementation review-8-$Two versions of theSDLCInitiationFeasibility StudyOperationSystems AnalysisConversion andImplementationProgrammingSystems DesignPost-ImplementationReviewSystemsAnalysisConceptual DesignPhysical DesignImplementationand ConversionOperation andMaintenanceSTERNROMNEY & STEINBART-9-1. Initiation1. Initiation1....
View Full Document

Page1 / 37

week 14 - 5130_Ch18-19_SystemDev - -1-Systems...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online