Object Oriented Software Engineering   View all facts   Glossary   Help

subject > process model > waterfall model

waterfall model
subject			fact

waterfall model	has definition A process model in which the software engineer works in a series of stages
	forms the foundation of many software development methodologies in use today
	has principles software engineers should work in a series of stages before completing each stage, they should perform quality assurance so that the next stage can be built on a good foundation software engineers sometimes have to step back to earlier stages when they discover a problem in a subsequent stage
	has some limitations
	has weaknesses if followed too closely: It has an overly rigid viewpoint that you should attempt to complete the entire specification before moving on to the design, and the entire design before moving on to implementation It makes no allowances for prototyping It implies that you can get the requirements right by simply writing them down and reviewing them, something that only works for simple, well-understood types of software development It implies that once the product is finished, everything else is maintenance
	is better than the opportunistic approach
	is a subtopic of 11.2 - Software Process Models
	is named because diagrams of it tend to look like cascading waterfalls
	is a kind of process model
	recognizes the importance of requirements, design and quality assurance
process model	functions as an aid to thinking, not as a rigid prescription of the way to do things
	helps the project manager and his or her team to decide what work should be done and in what sequence to perform the work