sdlc_ptB - Software Development Life Cycles, part B 26 Jan...

Info iconThis preview shows pages 1–6. 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
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Software Development Life Cycles, part B 26 Jan 2011 SCD08 Software Engineering 1 University of Toronto at Scarborough © Kersti Wain-Bantin, Dave Wortman 2002, Michael Szamosi 2007, Alan Rosselet 2011 CSCD08 methodologies 39 Uncertainty and Risk Removal • A useful way to look at the software development process is to think of it as removing uncertainty and risk • At the beginning of a project, there may be high uncertainty about what the project is doing and how it is going to do it. • As a project proceeds through requirements, specification, design and implementation, uncertainty is gradually removed as the solution becomes more and more specific. • At the beginning of a project there may be high risk that the project will not succeed in producing a software system to solve the given problem. • As the project proceeds, risk is gradually removed as parts of the solution become evident and implemented. Software Development Life Cycles, part B 26 Jan 2011 SCD08 Software Engineering 2 University of Toronto at Scarborough © Kersti Wain-Bantin, Dave Wortman 2002, Michael Szamosi 2007, Alan Rosselet 2011 CSCD08 methodologies 40 Spiral model • Combines waterfall life cycle and prototyping with risk analysis preceding each phase and evaluation following each phase • Uses prototyping for high-risk specifications • Risk analysis tries to identify problems early in the process • Each cycle removes some uncertainty about the final design of the system • Most appropriate for large projects since it incurs high management overhead Software Development Life Cycles, part B 26 Jan 2011 SCD08 Software Engineering 3 University of Toronto at Scarborough © Kersti Wain-Bantin, Dave Wortman 2002, Michael Szamosi 2007, Alan Rosselet 2011 CSCD08 methodologies 41 Spiral model Risk analysis Risk analysis Risk analysis Risk analysis Proto- type 1 Prototype 2 Prototype 3 Opera- tional protoype Concept of Operation Simulations, models, benchmarks S/W requirements Requirement validation Design V&V Product design Detailed design Code Unit test Integration test Acceptance test Service Develop, verify next-level product Evaluate alternatives identify, resolve risks Determine objectives alternatives and constraints Plan next phase Integration and test plan Development plan Requirements plan Life-cycle plan REVIEW Software Development Life Cycles, part B 26 Jan 2011 SCD08 Software Engineering 4 University of Toronto at Scarborough © Kersti Wain-Bantin, Dave Wortman 2002, Michael Szamosi 2007, Alan Rosselet 2011 CSCD08 methodologies 43 YES NO build system increment specify system increment validate increment deliver system system complete? design system architecture define system deliverables validate system integrate increment Sommerville fig 8.4 Incremental Development process Software Development Life Cycles, part B 26 Jan 2011 SCD08 Software Engineering 5 University of Toronto at Scarborough © Kersti Wain-Bantin, Dave Wortman 2002, Michael Szamosi 2007, Alan Rosselet 2011...
View Full Document

This note was uploaded on 02/05/2011 for the course CS 8 taught by Professor Alanrosselet during the Winter '11 term at University of Toronto.

Page1 / 33

sdlc_ptB - Software Development Life Cycles, part B 26 Jan...

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

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