Rapid application development

This is an old revision of this page, as edited by 136.186.1.186 (talk) at 01:08, 21 February 2008 (History). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Software-development-process Rapid application development (RAD), is a software development process developed initially by James Martin in 1991. The methodology involves iterative development, and the construction of prototypes. Traditionally the rapid application development approach involves compromises in usability, features, and/or execution speed. It is described as a process through which the development cycle of an application is expedited. Rapid Application Development thus enables quality products to be developed faster, saving valuable resources.

History

Application development refers to the developing of programming applications and differs from programming itself in that it has a higher level of responsibility, including for requirement capturing and testing.[1] Rapid Application Development was a response to non-agile processes developed in the 1970s, such as the Waterfall model. The problem with previous methodologies was that applications took so long to build that requirements had changed before the system was complete, often resulting in unusable systems. Starting with the ideas of Brian Gallagher, Barry Boehm and Scott Shultz, James Martin developed the Rapid Application Development approach during the 1980s at IBM and finally formalized it by publishing a book in 1991.


== Banana Man to the rescue

Why so glum Mary Jane?

Go Banana Man ==

References

  1. ^ What is Application Development
  • James Martin: Rapid Application Development, Macmillan Coll Div, ISBN 0-02-376775-8

See also