Computer Science

Computer Science

|
CRITICAL THINKING |
|
LITERATURE REVIEWArgument against the statement that agile software development techniques are more effective than structured methods. |

2011
Authored by: Sean Kehoe
     


Introduction

Structured methodologies require defining and documenting a stable set of requirements at the beginning of a project (Awad 2005).   The agile software development method involves the customer at every level of software development, thus reducing the impact of change in the requirement at a later stage (Biju 2008).   Software has been around now for over half a century and software development methodologies are constantly evolving due to changing technologies and new demands from users. Today's dynamic business environment has given rise to emergent organizations that continuously adapt their structures, strategies, and policies to suit their new surroundings.   There are several different methodologies but we can define the majority of companies as having either one or the other of two software development methodologies, Agile or Structured.   Structured, which is the more traditional of the two is a lot more detailed, relying on extensive documentation and comprehensive planning and design.   Agile methods involve short repetitive design cycles and rely more on interaction and adaptability between the developer and the design.   While the first agile techniques were first implemented in 1975, the term agile development only really came to prominence in 2001 (Awad 2005).   The purpose of this review is to examine the role of structured development techniques and their equal; if not superior standing opposed to agile development techniques, in software development.   We begin by delving into structured development and outlining some of its key methods, giving particular mention to the waterfall model.   We then focus on agile development and its limitations before we compare the two methods.   Finally we arrive at our conclusion.

Structured...