"Explain what is meant by Rapid Applications Development (RAD) and discuss the reasons for the increased use of this method for information systems development in recent years".

        A library of common objects such as dialogue boxes and icons

        A code generator that automatically writes programmes to implement reports

        A programming language with an integrated development environment

Eva, writing in the Journal “Information and Management”, refers to RAD as a process that involves a development team incorporating end-user clients, a staged delivery by means of iterative prototyping through the use of high level workshops such as Joint Applications Development and Joint Requirements Planning and the use of strict of time management techniques to achieve project delivery as specified.  He states that in the opinion of those clients surveyed in a recent research project, many felt that RAD was closely associated with the JDI (Just Do It) approach – a slightly less disciplined attitude towards RAD.

RAD packages include a variety of tools, and developers enhance and extend the original version through the iterative process.  RAD projects are suited to a wide range of platforms and in particular client/server ones.. They are most appropriate in situations that deal primarily with data such as sales reporting and decision support.  RAD is not however the best option for applications that require calculations such as engineering or finance.

RAD is not a new approach to systems design and was developed in its original guise by the Du Pont Company where it was known as “rapid iterative production engineering” which in itself was an aspect of Information Engineering.  Du Pont recognised that in the fast moving marketplace in which it competed, it was neither desirable nor commercially sensible to engage in systems development that from the day the system was “live” it was obsolete.  Delays and cost over-runs in system implementation were common – in 1994 31.1% of all corporate software development projects are cancelled before they get completed and 52.7% are costing 189% of there original estimates.

RAD therefore came about as a response to:

The failure of traditional methods to bring a project to completion on time, on budget and with the quality specified

The need to combine the technical skills of the developers with the operational and commercial skills of the end users

The requirement to reduce development times and to ensure systems delivered client expectations and fully met client specifications

By the use of prototyping the client has access to a framework of the complete system and is therefore able to offer meaningful input and hence enable modifications to be made at an appropriate stage prior to the final system being built.  

But as Eva comments, “There is however an increasing recognition that the desire to get systems operational through use of RAD can over-ride the need for disciplined and accurate requirements specification, quality control and thorough testing.”

Alter also notes that in prototyping, the key users are often very busy individuals and can not give the time or commitment to the project and continual changes resulting from the iterative process compounds the calls upon their time

An example of RAD working to the advantage of an organisation is that of the French pharmaceutical company, Rhône-Poulenc SA, which operates in 160 countries.  The company discovered that the IT division in the USA was unable to develop new systems in the timescales required.  Twelve different business units operate in the USA and due to geographical and product diversity as well as market forces, the need to bring in new applications was critical.

A new autonomous cross-boundary RAD team was appointed and tasked with examining applications across operating companies and functional boundaries and to develop solutions accordingly.  Using Delphi, one of the first RAD projects was to develop a sales force automation application for use by field staff using lap top computers.  Sales data was extracted on a daily basis to a file according to criteria specified and inputted remotely by the sales agent.  It was then analysed, verified and then emailed automatically to agents.  Parts of the system such as automatic email can be used in other parts of the system.  The important element of this system is the involvement of the sales team in establishing the criteria.  

This major project was completed in 3 months using a development team of 3 staff and was concluded in November 1996.

---