Ch03 process models
Download as PPT, PDF0 likes68 views
The document discusses various prescriptive process models for software engineering including the waterfall model, incremental model, RAD model, evolutionary prototyping model, spiral model, concurrent model, and unified process model. It provides diagrams illustrating the phases and workflows of each model.
Ch03 process models
- 1. 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, 2005 1 Software Engineering: A Practitioner’s Approach, 6/eSoftware Engineering: A Practitioner’s Approach, 6/e Chapter 3Chapter 3 Prescriptive Process ModelsPrescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited.
- 2. 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, 2005 2 Prescriptive ModelsPrescriptive Models Prescriptive process models advocate an orderly approach toPrescriptive process models advocate an orderly approach to software engineeringsoftware engineering That 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, areare they inappropriate for a software world that thrives on change?they inappropriate for a software world that thrives on change? Yet, if we reject traditional process models (and the order theyYet, 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 wedo we make it impossible to achieve coordination and coherence inmake it impossible to achieve coordination and coherence in software work?software work?
- 3. 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, 2005 3 The Waterfall ModelThe Waterfall Model Communicat ion Planning Modeling Const ruct ion Deployment analysis design code t est project init iat ion requirement gat hering estimating scheduling tracking delivery support f eedback
- 4. 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, 2005 4 The Incremental ModelThe Incremental Model C o m m u n i c a t i o n P l a n n i n g M o d e l i n g C o n s t r u c t i o n D e p l o y m e n t d e l i v e r y f e e d b a c k analy s is des ign c ode t es t increment # 1 increment # 2 delivery of 1st increment delivery of 2nd increment delivery of nt h increment increment # n project calendar time C o m m u n i c a t i o n P l a n n i n g M o d e l i n g C o n s t r u c t i o n D e p l o y m e n t d e l i v e r y f e e d b a c k analy sis des ign c ode t es t C o m m u n i c a t i o n P l a n n i n g M o d e l i n g C o n s t r u c t i o n D e p l o y m e n t d e l i v e r y f e e d b a c k analy s is des ign c ode t es t
- 5. 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, 2005 5 The RAD ModelThe RAD Model Communicat ion Planning Modeling business modeling dat a modeling process modeling Const ruct ion component reuse aut omat ic code generat ion t est ing Deployment 60 - 90 days Team # 1 Modeling business m odeling dat a m odeling process m odeling Const ruct ion com ponent reuse aut om at ic code generat ion t est ing M o d e lin g business m odeling data m odeling process m odeling Co n st ru ct io n com ponent reuse autom atic code generation testing Team # 2 Team # n int egrat ion delivery feedback
- 6. 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, 2005 6 Evolutionary Models: PrototypingEvolutionary Models: Prototyping Communicat ion Quick plan Const ruct ion of prot ot ype Mode ling Quick de sign Delivery & Feedback Deployment communication Quick plan Modeling Quick design Construction of prototype Deployment delivery & feedback
- 7. 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, 2005 7 Evolutionary Models: The SpiralEvolutionary Models: The Spiral communication planning modeling construction deployment delivery feedback start analysis design code test estimation scheduling risk analysis
- 8. 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, 2005 8 Evolutionary Models: ConcurrentEvolutionary Models: Concurrent Under review Baselined Done Under revision Await ing changes Under development none Modeling act ivit y represents the state of a software engineering activity or task
- 9. 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, 2005 9 Still 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, andapproach for defining, specifying, designing, and constructingconstructing aspectsaspects Unified ProcessUnified Process—a “use-case driven, architecture-centric,—a “use-case driven, architecture-centric, iterative and incremental” software process closelyiterative and incremental” software process closely aligned with the Unified Modeling Language (UML)aligned with the Unified Modeling Language (UML)
- 10. 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, 2005 10 inceptioninception The Unified Process (UP)The Unified Process (UP) soft ware increment Release Incept ion Elaborat ion const ruct ion t ransit ion product ion inception elaboration
- 11. 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, 2005 11 UP PhasesUP Phases Inception Elaboration Construction Transition Production UP Phases Workflows Requirements Analysis Design Implementation Test Iterations #1 #2 #n-1 #n Support
- 12. 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, 2005 12 UP Work ProductsUP Work ProductsInception phase Elaboration phase Construction phase Transition phase Vision document Init ial use-case model Init ial project glossary Init ial business case Init ial risk assessment . Project plan, phases and it erat ions. Business model, if necessary. One or more prot ot ypes I nc e pt i o n Use-case model Supplement ary requirement s including non-funct ional Analysis model Soft ware archit ect ure Descript ion. Execut able archit ect ural prot ot ype. Preliminary design model Revised risk list Project plan including it erat ion plan adapt ed workflows milest ones t echnical work product s Preliminary user manual Design model Soft ware component s Int egrat ed soft ware increment Test plan and procedure Test cases Support document at ion user manuals inst allat ion manuals descript ion of current increment Delivered soft ware increment Bet a t est report s General user feedback