RAD - fast programming technology

Basic principles of RAD

The toolkit should focus on minimizing development time. Creating a prototype to clarify customer requirements. Cyclical development: each new version of the product is based on the evaluation of the result of the previous version of the customer. Minimizing the development time of the version, due to the transfer of ready-made modules and adding functionality to the new version. The development team must work closely together, each participant must be prepared to perform several responsibilities. Project management should minimize the development cycle.

Story

The concept of RAD was a response to the awkward methods of developing programs of the 1970s and early 1980s, such as the “Waterfall model”. These methods provided for such a slow process of creating a program that often even the requirements for the program had time to change before the end of development. The founder of RAD is IBM employee James Martin, who in the 1980s formulated the basic principles of RAD, based on the ideas of Barry Boim and Scott Schulz. And in 1991, Martin published a famous book, in which he detailed the concept of RAD and the possibilities of its application. Currently, RAD is becoming a common scheme for creating software development tools.

RAD based development environments

Axure RP, C ++ Builder, Clarion, Code :: Blocks, Delphi, DevelStudio, Expression Studio, IBM Lotus Domino Designer, IntelliJ IDEA, IntraWeb, Lazarus, Macromedia Flash, Macromedia Authorware, Macromedia Director, Microsoft Visual Studio, MonoDevelop, NetBeans IDE, Omnis Studio, PowerBuilder, QDevelop (in conjunction with Qt-Designer), SharpDevelop, Visual DataFlex, WxDev-C ++, wxFormBuilder