Software Engineering: A Practitioner’s Approach, Software Engineering: A Practitioner’s Approach, 6/e6/eCCChapter 3Chapter 3Prescriptive Process ModelsPrescriptive Process Modelscopyright © 1996, 2001, 2005R.S. Pressman & Associates, Inc.These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20051For University Use OnlyMay be reproduced ONLY for student use at the university levelwhen used in conjunction with Software Engineering: A Practitioner's Approach.Any other reproduction or use is expressly prohibited.Prescriptive ModelsPrescriptive Models Prescriptive process models advocate an orderly approach to Prescriptive process models advocate an orderly approach to software engineeringsoftware engineeringggggThat leads to a few questions …That leads to a few questions … If prescriptive process models strive for structure and order, If prescriptive process models strive for structure and order, are they are they inappropriate for a software world that thrives on change?inappropriate for a software world that thrives on change? Yet, if we reject traditional process models (and the order they Yet, if we reject traditional process models (and the order they imply) and replace them with something less structured, imply) and replace them with something less structured, do we make do we make it impossible to achieve coordination and coherence in software it impossible to achieve coordination and coherence in software These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20052t possbetoac e ecood ato a dco ee ce sot aet possbetoac e ecood ato a dco ee ce sot aework?work?The Waterfall ModelThe Waterfall ModelCommunication Planning ModelingConstructionDeployment analysis designcode testproject initiat ion requirement gat heringestimating scheduling trackingdelivery support feedbackThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20053The Incremental ModelThe Incremental Modelincrement # nCommunicat ionincrement # 1increment # 2delivery of 2nd incrementdelivery of nt h incrementCommunicat ionPlanningModelingConst ruct ionDeployment delivery feedbackanaly sis desig ncode testCommunicat ionPlanningModelingConst ruct ionDeployment delivery feedbackanalysis designcode testThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20054PlanningMode lingConst ruct ionDeployment delivery feedbackanalysis designcode testdelivery of 1st incrementproject calendar timeThe RAD ModelThe RAD ModelCommunicationModelingbusiness m odeling data m odeling process m odelingConstructioncom ponent reuse autom atic code generation Team # 2Team # nPlanningModelingbusiness modeling dat a modeling process modelingDeploymentTeam # 1Modelingbusine ss m odel in g data modeling process modelingConst ructio ncomponent reuse automatic code generation t est ingtestingintegrat ion delivery feedbackThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20055Constructioncomponent reuse automatic code generation testing60 - 90 daysEvolutionary Models: PrototypingEvolutionary Models: PrototypingCommunicationQuick plancommunicationQuickplanModeling Quick designDeliveryDeploymentcommunicationModelingQuick designDeploymentdli &These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20056Construction of prototypeDelivery& FeedbackConstructionof prototypedelivery &feedbackEvolutionary Models: The SpiralEvolutionary Models: The Spiralplanning estimation scheduling risk analysiscommunicationmodelingstartanalysis designThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20057constructiondeployment delivery feedbackcode testEvolutionary Models: ConcurrentEvolutionary Models: ConcurrentUndernoneModeling act ivit yrepresents the stateofasoftwareengineeringUnder reviewUnderrevisionAwaitingchangesdevelopmentofasoftwareengineeringactivity or taskThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20058BaselinedDonerevisionStill Other Process ModelsStill Other Process Models Component based developmentComponent based development——the process to apply the process to apply when reuse is a development objectivewhen reuse is a development objective Formal methodsFormal methods——emphasizes the mathematical emphasizes the mathematical specification of requirementsspecification of requirements AOSDAOSD——provides a process and methodological provides a process and methodological approach for defining, specifying, designing, and approach for defining, specifying, designing, and constructing constructing aspectsaspectsUifidPUifidP““di hit tdi hit tThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20059Unified ProcessUnified Process——a “usea “use--case driven, architecturecase driven, architecture--centric, iterative and incremental” software process centric, iterative and incremental” software process closely aligned with the Unified Modeling Language closely aligned with the Unified Modeling Language (UML)(UML)The Unified Process (UP)The Unified Process (UP)InceptionElaborationinceptionelaborationinceptioninceptionThese courseware materials