What are the pros & cons of the Waterfall model?
Thread TagsAdobe Illustrator Adobe InDesign Adobe Photoshop Android Development Android Programming Android Studio Automation Testing C / C++ Programming Career Options College Lounge css digital marketing Digital Marketing / SEO Fireworks Graphic Design Graphic designing Graphics Design Graphics Designing HTML? Illustrator Internship Training logo Design logo designing Magento Photoshop PHP Programming QA react-native Scroll Website SEO Single Page Website Stock Managment System Testing Typography UI UI/UX Development UI Design UI Designing UI development User Interface UX Design Web Designing Website Design Wordpress wp
Log in with your username and password
Register for free!
Registration at Smart Mentors is completely free and takes only a few seconds. By registering you’ll gain:
- Full Posting Privileges.
- Access to Private Messaging.
- Optional Email Notification.
- Ability to Fully Participate.
- Author Replies
- January 29, 2019 at 6:10 pm #52864
– This model is preferred for smaller projects where requirements are well understood.
– It is less expensive as minimal resources are required.
– The output formed at the end of each phase is reviewed and approved and hence it has high visibility.
– The main strength of the Waterfall model is its simplicity and it is very simple to use.
– Minimal resources are needed.
– It is hard to implement any changes in the requirements.
– Not suitable when requirements are not clear.
– It is expensive to incorporate any changes once the project is into the testing phase.
– No working software is produced until the last stage of the life cycle.
– Not suitable for complex projects, long term projects.
You must be register. Registration is 100% free.to reply to this thread.Please or