Waterfall development process methodology

The waterfall model of development process was first introduced by Winston Royce in 1970 and has been widely used in IT industry ever since. It is considered the classic approach to software development. The waterfall model is also called linear-sequential life cycle, since it involves sequential series of stages that start from the concept and system requirements analysis, through design, implementation, testing, and finishing with product release and maintenance. After the completion of each stage and approval from the client, service provider smoothly moves to the next stage.

Waterfall approach differs from the agile development model, because it demands fully described product documentation before any code is even written. Thus waterfall methodology suits short-term and small projects that have requirements to features, design, and functionality fully specified and understood by clients and service provider.

Waterfall model has clear goals for each stage of development. Schedule must provide deadlines and workload for each stage. The resulting departmentalization and managerial control are ensured by the strictness of the model – each stage has specific deliverables and review process.

Total cost, timeline, and size of the project may be accurately estimated when the product specifics are unambiguously defined. Clients know what to expect. This model enforces discipline and structure. Every stage has predicted start and end point, so it is easy to measure progress by clearly defined milestones. Stages are processed and completed one at a time. Design errors are captured before any software is written saving time during the implementation stage. Meticulous documentation allows to understand product more, even if development team will be dispersed in future.

Disadvantage of this model is that it depends on the level of clearness of client’s requirements. There is no place for any changes, reflection, or revision during the development cycle. If a requirement error or change is found, or a change needs to be made, the project can’t just go back to the previous (approved) stage and has to start from the beginning with all new code.

Though waterfall model is often criticized, it still can be successfully applied to certain types of projects and with proper implementation and management can be very time and cost effective. Quintagroup uses this approach for small scope projects, like Plone themes development, Web design, Plone add-ons, simple Python solutions, etc., though in most use cases we prefer agile methodology.

Testimonials

It is a pleasure working with the Plone developers at Quintagroup. They are very knowledgeable, efficient, and customer-focused. I have found Plone to be a powerful and user-friendly Content Management System.

August 13, 2013
Robert Loftur-Thun

Wonderful Plone developers. Fast, efficient and very knowledgeable.

August 12, 2013
Jason Atwood

Thanks a lot... I've always appreciated the level of services provided by your company, I'm a big fan and shall continue to advertise your services among my fellow Zope developers!

Nov 30, 2011
Dominique Trembloy

I have used a Plone site environment hosted by Quintagroup to develop a workflow application for my business. Since January 2010 ... I have been a customer of Quintagroup and I am very happy about the good and reliable service, including update of the website to version 4.1 of Plone.

Apr 20, 2011
Maarten de Vries
www.insolweb.info

...I was a very satisfied customer for 7 years. They made sure that my website was always up, even during a couple episodes of being "slashdotted", and fixed the very few problems that I had in record time. This is a very professionally run outfit...

Feb 14, 2011
Mario Butter

http://silent-tower.org

I just want to thank each of you for your work... My business has increased and my anxiety level has been lowered since using Plone...It's been such a pleasure working with a professional and intelligent group like your.

Tom Parish
http://tomparish.com

Follow