Waterfall Software Life Cycle Model Features and Risks Software Engineering Tutorial

Explains the appropriate way to use the Waterfall model. It's not meant for every situation and comes with certain risks.

Category:

Education

Tags:

• software
• engineering
• development
• life
• cycle
• sdlc
• waterfall
• model
• tutorial
• agile
• scrum
• project
• risk
• change
• management
• rup
• uml
• object-oriented
• analysis
• design
• ooad
• iterative
• learn
• teach
• education
• six
• sigma
• java
• visual
• studio
• .net
• c#
• basic
• Waterfall Model
• Software Tutorial

[sirkhalid]

I thought the Waterfall approach was used for large projects, it is within our blue chip organisation, in the last 4 years we have switched to Agile/SCRUM to deliver both large and small projects.

[bidwx]

@sirkhalid In how many of those projects did the team never have to change the approved output from a previous phase? Was design never revisited during development or the requirements completed and never revised after passing the requirements complete milestone? If so, waterfall may not have been the least costly option. I am strongly in favor of iterative life cycles for large, complex projects, for the main purpose of reducing risk in areas such as schedule and quality.

[ThorBarstad]

This was the best video I found in explaining the waterfall model. Thanks for taking the time to make it! :)

[Akiii001]

good analysis, thanks !

keep posting more videos..

[sirkhalid]

@bidwx I actually agree with you, I've studied report after report of how costly requirements change further down the project life cyle. I am much more in favour of iterative life cycles for large projects, I am currently on a 2 year Agile project and the cost and delivery benefits are immense, I guess when a corporation chooses a methodology it sticks with it, and in my organisations case adds it's own flavour, a bit like bailing out a sinking ship! Great presentation by the way :)