Object Oriented Software Engineering   View all facts   Glossary   Help

subject > process model > waterfall model

waterfall model comparison table

Subject	name because	form	recognize	have weaknesses	have some limitations	has definition	be	is a synonym of	is a kind of	have principles
process model						A general approach for organizing a project into activities; an aid to thinking, not a rigid prescription of the way to do things		software process model	subject
waterfall model	diagrams of it tend to look like cascading waterfalls	the foundation of many software development methodologies in use today	the importance of requirements, design and quality assurance	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		A process model in which the software engineer works in a series of stages	better than the opportunistic approach		process model	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

Next process model: concurrent engineering model    Up: process model    Previous process model: spiral model