VIEWS: 49 PAGES: 3 CATEGORY: Project Management POSTED ON: 10/30/2012
The waterfall methodology is a framework used by software companies and teams in designing and developing software products. It's a process that is made up of six steps that aims to cover everything from requirement analysis to maintenance.
Pros And Cons Waterfall Methodology Waterfall Methodology Page 1 The waterfall methodology is a framework used by software companies and teams in designing and developing software products. A sequential process, it follows six phases that cover defining clients' needs, designing the product, building the product, testing it, releasing it to the clients and checking to see if any bugs exist in it. This particular model has been many a topic of heated discussions in the sofware industry. One of the most particular points being debated about the model is the issue of its advantages vs disadvantages. If you don’t have any idea which side to go for, however, this broad overview of the advantages and disadvantages of the waterfall methodology below may help you. Advantages The waterfall methodology is a framework that closely follows all of its six phases. So, designers and developers need to ensure that the milestones expected for each phase would be achieved, right when they are defined to be. Discipline, therefore, should be a trait that the designers and developers have. Since the waterfall methodology, too, insists upon determining the issues and problems that the product may have way before it's released to the clients, Waterfall Methodology Page 2 clients can get a product that would be the best it could be. Also, clients would know when exactly they'd be able to get the product. This is ideal, as most clients would like to know when they can incorporate it into their business framework. The waterfall methodology, too, relies on setting the requirements and specifications ahead of time. This makes the whole team work harder, seeing as they have expectations to fill and goals to achieve; this also makes the whole process end more successfully. Disadvantages Since the waterfall methodology is very concerned with getting what clients need and delivering that to them, there are people who consider the framework to be impractical - especially as they have found that clients don't really know what they want the product to do, at the get-go. According to their experience, clients would only know what they want if they have seen issues and bugs that they certainly don't want. The framework is also not very flexible in terms of going back phases that can make the later phases a bit problematic. The model's insistence upon the division of labor, too, is not very practical and realistic, as far as some designers and developers are concerned. Waterfall Methodology Page 3
Pages to are hidden for
"The Top Advantages And Disadvantages Of The Waterfall Methodology"Please download to view full document