Tarkvara kokkuvõte inglise keeles
6. WATERFALL MODEL
The waterfall model is a sequential software development model (a process for the creation of software) in which
development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis,
design, implementation, testing (validation), integration, and maintenance.
Why a Pure Waterfall Process is Usually Not Practical
- Don’t know up front everything wanted and needed
o Usually hard to visualize every detail in advance
- We can only estimatethe costs of implementing requirements
o To gain confidence in an estimate, we need to design and actually implement parts, especially the riskiest ones
o We will probably need to modify requirements as a result
- We often need to execute intermediate builds
o Stakeholders need to gain confidence
o Designers and developers need confirmation they're building what’s needed and wanted
- Team members can't be idle while the requirements are being completed