CSE 436—Software Development Models Ron K. Cytron 10 October 2005

CSE 436 Software Engineering Workshop Today Review of software development models Discussion of architecture for today and for SRRD Break Groups present block diagram of architecture, turn in requirements –These requirements will be graded. If you’re not ready, get them under my door before 5 PM today. –For architecture What are the pieces? How do you anticipate assigning them to people? What are the resulting interactions What is a reasonable schedule for integration and deliverables? Break More software development models Plan

CSE 436 Software Engineering Workshop Waterfall Model What is it? Describe the 5 steps (next slide)

CSE 436 Software Engineering Workshop Waterfall Model Communication Planning Modeling Construction Deployment

CSE 436 Software Engineering Workshop Waterfall Model Discussion –Advantages –Disadvantages

CSE 436 Software Engineering Workshop RAD–Rapid Application Deployment Explain the diagram below For what kinds of projects is it useful? Communication Planning DesignConstruction DesignConstruction DesignConstruction Deployment

CSE 436 Software Engineering Workshop RAD drawbacks Discussion –Advantages –Disadvantages

CSE 436 Software Engineering Workshop Prototyping Model Communication Quick plan Quick design Construction of prototype Deployment, delivery, feedback Explain the diagram below

CSE 436 Software Engineering Workshop Prototyping Model Discussion –Advantages –Disadvantages

CSE 436 Software Engineering Workshop Architecture What are the pieces? –Block diagram –Interconnection of parts What’s a likely development schedule for the parts? –Partial order –Integration schedule Which parts will be assigned to the same person? –How did you decide who would do what? What are the resulting interactions? –How will they be facilitated? –How will they be managed?

CSE 436 Software Engineering Workshop Architecture SRDD –Go over parts –Write up for Friday meetings

CSE 436 Software Engineering Workshop Spiral Model credit What’s missing from this slide?

CSE 436 Software Engineering Workshop Spiral Model Like Prototype model –Acknowledges need for iteration But –Heavier use of the 5 steps –Concrete products spun out in each cycle Specification Prototype Beta Final

CSE 436 Software Engineering Workshop Unified Process (UP) Model Spiral Defined work products Phases –Inception Communication and Planning –Elaboration Planning and Modeling (design) –Construction As before –Transition Construction and deployment –Production Is the increment of software produced

CSE 436 Software Engineering Workshop UP Inception –Vision document –Project plan –Business model Elaboration –Use cases –Preliminary design –Risk identification –Project planning

CSE 436 Software Engineering Workshop UP Construction –Architecture –Test plan –Documentation Transition –Delivered software –Beta test reports –User feedback

CSE 436 Software Engineering Workshop Summary so far Models limited or focus on static work products Don’t adapt well to changing circumstances or requirements that evolve Next week: Agile Development Models