Waterfall Model
You Complete One Phase (Ex. Design) Before Moving on the
next phase (Ex. Development)
You rarely aim to re-visit a ‘Phase’ one’s its completed
1) (Analysis) requirement gathering when customer done
project
- System requirement
- Requirement for app development
- Business analysis and architect design decide /UML
- Entity relationship model
- ORM model (class diagram)
- Use case model
- Deployment model
This model can be send to developer
3) Developer start coding Phase/development
4) Testing
- Tester
1) Manual testing
2) Automation testing
3) JUnit Testing
After Testing-->
5) Deployment Phase & maintains Phase
Waterfall Model can’t use for long scale application
Because If you reach development phase then you can’t change
above phase.
This is limitation of waterfall model
Modification not possible in waterfall model
Waterfall model not recommendation
If you can use waterfall model is very costly and take more
time because every phase complete you can test all diagram are ready or not,
design and code are complete working or not because one time you will go to
next phase then you will not modified in waterfall model.
This approach is highly risky.
Most costly and more time consuming.
0 Comments