Waterfall vs. Agile Methodology
(→Example of Use) |
(→Waterfall Model) |
||
| Line 18: | Line 18: | ||
The following example demonstrates the different approaches of each methodology. The project goal is the development of a customer adress book. | The following example demonstrates the different approaches of each methodology. The project goal is the development of a customer adress book. | ||
==Waterfall Model== | ==Waterfall Model== | ||
| + | '''Product Requirements''' | ||
| + | '''Analysis''' | ||
| + | '''Design''' | ||
| + | '''Implementation''' | ||
| + | '''Testing''' | ||
| + | '''Release''' | ||
==Agile Model== | ==Agile Model== | ||
Revision as of 20:24, 17 September 2017
Most software development projects apply either the Waterfall or Agile methodology. A development methodology is the procidure used by an engineering team in order to create a desired product. The Waterfall methodology represents the traditional approach, where the development process is conducted in a linear series of events. On its way toward the conclusion the progress flows continously through the phases of a project (analysis, design, development, testing) like a waterfall. The entire project is planned in advance. Agile is a more recently developed software development methodology, where the linear approach is replaced by an incremental, iterative one. Instead of planning the whole project in advance, Agile enables the adaption of requirements during the whole project. This artice provides an introduction of each methodology, a comparison and examples of use, in order to facilitate the decision whether Agile or Waterfall is more suitable for the next project.
Contents |
Waterfall Methodology
Pros
Cons
Agile Methodology
Pros
Cons
Comparison of the Waterfall and the Agile Methodology
Example of Use
The following example demonstrates the different approaches of each methodology. The project goal is the development of a customer adress book.
Waterfall Model
Product Requirements Analysis Design Implementation Testing Release
