Rapid – is something that happens quickly or we can just say fast?
Introduction: RAD is a software development process develops initially by James Martin in the 1980’s.
Traditionally the RAD approach involves compromises in usability features, and execution speed. It is described as a process through fast and efficiently which the development cycle of an application is expedited. RAD thus enables quality products to be developed faster, saving valuable resources.
What is RAD? A concept that products can be developed faster and of higher quality through:
Gathering requirements using workspace of focus group.
Prototyping and early reiterative user testing of design.
The re-use of software components.
A rigidly paced schedule that defers design improvements to the next product version.
Less formality in reviews and other team communication.
Some companies offer products that provide some or all of the tools for RAD software development. These products include requirements gathering tools, prototyping tools, computer aided software engineering tools, language development environments such as those for the java platform, groupware for communication development members and testing tools.
Brief History: In mid 1970’s RAD was first developed and successfully deployed by New York Telephone Co.’s System Development Center, And was under the direction of Mr. Dan Gielan following a series of remarkable successful implementations of this process, Gielan lectured extensively in various forms on the methodology, practice and benefits of this process. In year 1990, in his book RAD James Martin documented his interpretation of the methodology. More recently, the term and its acronym had come to be used in a broader, general sense that encompasses a variety of methods aim at speeding application development, such as the use of software frameworks of varied types, such as Web application frameworks. Starting with the