Please enable JavaScript.
Coggle requires JavaScript to display documents.
Waterfall Models - Coggle Diagram
Waterfall Models
Common Phases
3- Implementation
4- Testing
2- Design
5- Deployment
1- Requirements Analysis
6- Maintenance
V-Waterfall Model
Additional
Phases
Verification
Validation
Design
System Design
Architectural design
Requirements analysis
Module design
Testing
Integration Testing
System Testing
Unit testing
User Acceptance Testing (UAT)
Principles of the model
Scalability
Cross Referencing
Data/Process Integrity
Tangible Documentation
Why prefered ?
Management
Proactive Defect Tracking
Large to Small
When to use ?
Technical mastery and availability of technical ressources
Small to Medium-sized projects
Clear & fixed Requirements
Manage unstable needs
Advantages
Simple to use
Accurate progress tracking
Early verification & validation
Clear and structured process
Disciplined Model
Emphasized on testing
Improved Traceability
Better communication
Disadvantages
Unsupportive of phase iteration
Does not easily handle concurrent events
Ambiguous requirements
Inflexibility
Complex and Object Oriented Projects
Time-consuming
High risk and uncertainty
Over-reliance on Documentation
Waterfall Model
Advantages
Properly Defined
Clear Milestones
Properly Documented
Simple to understand
Individual Processing
Working
Disadvantages
No Overlapping of Phases
Limited Flexibility
Not a good model for long and Object Oriented projects
No Feedback Path
Cannot accomodate changing requirements.
Late Defect Detection
Lengthy Development Cycle
Use
Technology is well understood
Large-scale Software Development Projects
Minimal risk & low cost
Projects with Clear & Stable Requirements
Features
Quality Control
Rigorous Planning
Document-Driven
Sequential Approach
Iterative Waterfall Model
Advantages
Risk Reduction
Quality Assurance
Well-organized
Improved Customer Satisfaction
Cost-Effective
Predictable Outcomes
Simple
Faster Time to Market
Feedback Path
Easy to Manage
Disadvantages
Overlapping of phases not supported
Risk handling not supported
Incremental delivery not supported
Limited customer interactions
Difficult to incorporate change requests