Brief history of RAD (Rapid Application Development)

In my previous post, outline of RAD (Rapid Application Development) was discussed. In this post I elaborate little bit about the history of RAD and Problems of RAD. I’ll discuss the solutions and Pros and Cons of RAD on my next post.

History of RAD

Rapid Application development refers to the growing of programming applications and differs from programming itself in that it has a higher level of dependability, including for necessity capturing and testing. Rapid Application Development was a response to non-agile processes developed in the 1970s, for example the Waterfall model. The difficulty with earlier methodologies was that application takes so time-consuming to construct that necessities had changed before the scheme was full, often resultant in impractical systems. Initial with the thoughts of Brian Gallagher, Scott Shultz & Barry Boehm, James Martin developed the Rapid Application Development shift toward during the 1980s at IBM and finally formalized it by publishing a book in 1991.

Rapid Application Development (RAD) has been in survival for nearly 20 years, but is as suitable these days as it was when it was primarily conceptualized.