CSC/ECE 517 Spring 2014/ch1 1w1m bm: Difference between revisions
(Created page with "= Comparison of Waterfall, Prototype, and Agile Development = == Introduction == This article seeks to provide information about different development strategies, comparing thei...") |
No edit summary |
||
| Line 5: | Line 5: | ||
== Background == | == Background == | ||
Over the past few years, the trend in software development has been to use an agile approach. Before this, traditional approaches required precise and extensive planning, which left the process vulnerable to changing requirements and unforeseen problems. Agile development, on the other hand, attempts to adapt to changing conditions and requirements. Similarly, prototyping helps decide what specifications and features should be implemented in a product by providing a working model that users can interact with, thus | Over the past few years, the trend in software development has been to use an agile approach. Before this, traditional approaches required precise and extensive planning, which left the process vulnerable to changing requirements and unforeseen problems. Agile development, on the other hand, attempts to adapt to changing conditions and requirements. Similarly, prototyping helps decide what specifications and features should be implemented in a product by providing a working model that users can interact with, thus allowing them to provide more beneficial feedback. The following sections provide a quick overview of these software development processes. | ||
=== Traditional (Waterfall) Development === | === Traditional (Waterfall) Development === | ||
As stated before, waterfall relies on extensive planning, mapping out an entire process from start to finish. Progress flows steadily in one direction (as in a waterfall). The phases in this process include Conception, Initiation, Analysis, Design, Construction, Testing, and Maintenance <ref>[http://www.techrepublic.com/article/understanding-the-pros-and-cons-of-the-waterfall-model-of-software-development/# Understanding the pros and cons of the Waterfall Model of software development]</ref>. In the early days of software development, this methodology was adapted from construction and manufacturing industries because there was no formal model for software development. | |||
When following the waterfall model, during the Conception, Initiation, Analysis, and Design stages, the specifications for the project are permanent. This is essentially a blueprint that software developers will use to construct the product. These designs may be in the form of different components that will be later combined to produce functionality; however, a new phase may not be started until the first is completely done. | |||
== Examples == | == Examples == | ||
Revision as of 02:30, 19 February 2014
Comparison of Waterfall, Prototype, and Agile Development
Introduction
This article seeks to provide information about different development strategies, comparing their efficacy through empirical research.
Background
Over the past few years, the trend in software development has been to use an agile approach. Before this, traditional approaches required precise and extensive planning, which left the process vulnerable to changing requirements and unforeseen problems. Agile development, on the other hand, attempts to adapt to changing conditions and requirements. Similarly, prototyping helps decide what specifications and features should be implemented in a product by providing a working model that users can interact with, thus allowing them to provide more beneficial feedback. The following sections provide a quick overview of these software development processes.
Traditional (Waterfall) Development
As stated before, waterfall relies on extensive planning, mapping out an entire process from start to finish. Progress flows steadily in one direction (as in a waterfall). The phases in this process include Conception, Initiation, Analysis, Design, Construction, Testing, and Maintenance <ref>Understanding the pros and cons of the Waterfall Model of software development</ref>. In the early days of software development, this methodology was adapted from construction and manufacturing industries because there was no formal model for software development.
When following the waterfall model, during the Conception, Initiation, Analysis, and Design stages, the specifications for the project are permanent. This is essentially a blueprint that software developers will use to construct the product. These designs may be in the form of different components that will be later combined to produce functionality; however, a new phase may not be started until the first is completely done.
Examples
Narration
Terminology
References
<references />