PowerPoint PresentationChapter Three Information System DevelopmentChapter MapProcess of System DevelopmentThe CMM Process Management ModelWhat is the Point of Processes?Capability Maturity ModelSlide 9Slide 10Slide 11Impact of System Development “Process” on QualityLife Cycle versus MethodologyA System Life CycleRepresentative System Development MethodologiesPrinciples of System DevelopmentSlide 17Establish Phases and ActivitiesManage the Process and ProjectsJustify Information Systems as Capital InvestmentsDon’t Be Afraid to Cancel or Revise ScopeWhere Do Systems Development Projects Come From?Slide 23Slide 24The PIECES Problem-Solving FrameworkThe Classic Project PhasesBuilding Blocks View of System DevelopmentScope DefinitionLogical DesignDecision AnalysisSlide 31Physical Design & IntegrationConstruction and TestingInstallation and DeliverySystem Operation & MaintenanceCross Life-Cycle ActivitiesSystem Development Documentation, Repository, and PresentationsA Taxonomy for System Development Methodologies & StrategiesModel-Driven Development StrategySlide 40Model DrivenRapid Application Development StrategySlide 43RAD w/prototypingExtreme ProgrammimgCommercial Application Package Implementation StrategySlide 47COTSHybrid StrategiesA System Maintenance PerspectiveAutomated Tools and TechnologyComputer-Assisted Software Engineering (CASE)CASE Tool ArchitectureApplication Development EnvironmentsProcess and Project ManagersSlide 561Irwin/McGraw-Hill3C H A P T E RINFORMATION SYSTEMS DEVELOPMENT2Irwin/McGraw-HillChapter Three Information System DevelopmentChapter Three Information System DevelopmentDescribe the Capability Maturity Model (CMM) for quality management.Differentiate between the system life cycle and a system development methodology.Describe 10 basic principles of system development.Define problems, opportunities, and directives—the triggers for systems development projects.Describe the PIECES framework for categorizing problemsDescribe the essential phases of system development. For each phase, describe its purpose, inputs, and outputs.Describe cross life cycle activities that overlap multiple system development phases.Describe typical alternative “routes” through the basic phases of system development. Describe how routes may be combined or customized for different projects.Describe various automated tools for system development.3Irwin/McGraw-HillChapter MapChapter Map4Irwin/McGraw-HillProcess of System DevelopmentProcess of System Development•System development process – •a set of activities, methods, best practices, deliverables, and automated tools •that stakeholders use to develop and continuously improve information systems and software–Many variations–Using a consistent process for system development:–Create efficiencies that allow management to shift resources between projects–Produces consistent documentation that reduces lifetime costs to maintain the systems–Promotes quality5Irwin/McGraw-HillThe CMM Process Management ModelThe CMM Process Management ModelCapability Maturity Model (CMM) – a standardized framework for assessing the maturity level of an organization’s information system development and management processes and products. SEI 1991Defense Industry early adopters It consists of five levels of maturityAs the system development process matures and becomes more standardized TimelinessProductivityCost controlCorrectness improve6Irwin/McGraw-HillWhat is the Point of Processes?What is the Point of Processes?Basically, so we don’t reinvent the wheel!Learn from mistakesNever make the same mistake twice.Incorporate best practicesSomething works better than anotherRoutinisation of standard tasksDo it right once and then reuse itPredictability7Irwin/McGraw-HillThe CMM Levels 12345Process MaturityProcess CapabilityProcess PerformanceLowHighRiskHighLow8Irwin/McGraw-HillCapability Maturity ModelCapability Maturity ModelDefines the state of maturity of an organizations Systems MethodologyLevel 1 – Initial - chaosNo defined methodologySuccess based on skills and experience of project teamProcess is unpredictable and not repeatableDocumentation is sporadic and inconsistentLevel 2 – Repeatable – effort to repeat past successes Focus is on project managementSoftware Quality assuranceA methodology is followed but varies project to projectSuccess dependent on skills and experience9Irwin/McGraw-HillCapability Maturity ModelCapability Maturity ModelLevel 3 - DefinedStandard methodology in placeAll projects use the methodologyTraining programPeer reviewsConsistent quality – Software Engineering Process Group (SEPG)High quality documentation and deliverablesProcess is stable, predictable, and repeatable10Irwin/McGraw-HillCapability Maturity ModelCapability Maturity ModelLevel 4 - ManagedMeasurable goals for quality and productivityData collected and analyzed for improvements in project managementProactive vs Reactive approach to Systems Development problemsLevel 5 - OptimizedContinuous monitoring of the process (CPI)Technology change managementBest PracticesDefect preventionShared information across the organization11Irwin/McGraw-Hill 12Irwin/McGraw-HillImpact of System Development “Process” on QualityImpact of System Development “Process” on QualityCMM Project Statistics for a Project Resulting in 200,000 Lines of CodeOrganization’s CMM LevelProject Duration (months)Project Person-MonthsNumber of Defects ShippedMedian Cost ($ millions)Lowest Cost ($ millions)Highest Cost ($ millions)1 30 600 61 5.5 1.8 100+2 18.5 143 12 1.3 .96 1.73 15 80 7 .728 .518 .93313Irwin/McGraw-HillLife Cycle versus MethodologyLife Cycle versus MethodologySystem life cycle – the factoring of the lifetime of an information system into two stages, (1) systems