August 12, 2009
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.
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.
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.
Pros and Cons of RAD:
1. Increased speed of development through methods including rapid prototyping,
virtualization of system related routines, and other techniques.
2. Decreased end-user functionality (arising from narrower design focus), hence
3. Larger emphasis on simplicity and usability of GUI design.
1. Reduced Scalability, and reduced features when a RAD developed application starts
as a prototype and evolves into a finished application.
2. Reduced features occur due to time boxing when features are pushed to later
versions in order to finish a release in a short amount of time.
3. The data needed should already exist.