CSC/ECE 517 Spring 2014/ch1 1w1m bm

From Expertiza_Wiki
Revision as of 02:11, 19 February 2014 by Mdnevill (talk | contribs) (Created page with "= Comparison of Waterfall, Prototype, and Agile Development = == Introduction == This article seeks to provide information about different development strategies, comparing thei...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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 providing more beneficial feedback.

Traditional (Waterfall) Development

Examples

Narration

Terminology

References

<references />