Life Cycle Waterfall Method Introduced by Winston Royce in 1970 Illustrated as a flawed model Oldest and most well tested methodology Still used by 70 of software development organizations ID: 441227
Download Presentation The PPT/PDF document "Software Development" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Software Development Life Cycle
Waterfall MethodSlide2
Introduced by Winston Royce in
1970
Illustrated as a flawed modelOldest and most well tested methodologyStill used by 70% of software development organizations (VersionOne survey, 2007)
BackgroundSlide3
The classic approach to
the
Systems Development Life CycleLinear and sequentialSeveral phases of development
Each
phase is assigned to a separate team 100% complete and absolutely correctSeen as flowing steadily downward
What is it?Slide4
Goes downwards and not
backwards
StagesSlide5
Pros and Cons
Pros
Clear initial requirements S
trict order of phases
Faults are detected earlyEmphasis on documentationWell-known and easy to use
Cons
Does
not allow for
revision
Time wasted waiting
Late testing period
Not
suitable for smaller
projects
Users are not
involved until testing stageSlide6
Use
only
when:Clear and fixed requirements Experienced organization or inexperienced leaderThe project is simple or largeThe project requires better control
Who still uses:
Toyota - embedded software (moving toward Agile)
Who Uses and When?Slide7
The V-ModelAorta Lifecycle Model
Sashimi Model
Royce ModelCombat Waterfall’s assumption that the requirements will not change
Modified MethodologySlide8
Development and testing stages start simultaneouslyAllow
for Developing Acceptance Criteria early
The V-ModelSlide9
Waterfall
Benefits small projects
Strict with Predictability“Big Design Up Front”To fix problem, must redesign entire systemOne BIG model release at the end
Agile
Benefits projects with constant changing requirements
Flexible with Adaptability
Fit puzzles together at the “right” time
A working model
Waterfall vs. Agile Method
Agile
is
a lower overhead method that emphasizes values
& principles
rather than processes.Slide10
Be aware of your chosen technologies capabilitiesEmphasis on requirements and design
No room for changing of requirements
Enforces disciplineScheduleKnow what your customers needs are!ConclusionSlide11
“Agile Introduction for Dummies, part 1.”
http://agileintro.wordpress.com/2008/01/04/waterfall-vs-agile-methodology/
Melonfire, Contributor. Understanding the pros and cons of the Waterfall Model of software development. http://www.techrepublic.com/article/understanding-the-pros-and-cons-of-the-waterfall-model-of-software-development/6118423Mochal, Tom. How to pick the right method for
your
project. http://www.techrepublic.com/article/waterfall-vs-rad-how-to-pick-the-right-method-for-your-project/1044102“
All About the Waterfall
Model”
http
://www.waterfall-model.com/
“
Waterfall SDLC Methodology”
http://
skysigal.xact-solutions.com/Resources/SoftwareDevLifeCycle/WaterfallMethodSDLC/tabid/600/Default.aspx
Elssamadisy
,
Amr
. Toyota Using Waterfall?
http://
www.infoq.com/news/2010/04/toyota-waterfall
References