Term Paper on "Rapid Application Development RAD"

Term Paper 12 pages (3327 words) Sources: 6 Style: APA

[EXCERPT] . . . .

Rapid Application Development (RAD)

Rapid Application Development

Information Technology has become a more and more common presence within most domains of life. The business sector uses it for various purposes, such as increasing shareholder value, increasing the customer satisfaction, consolidating the market position or registering higher profits. A relevant strategy used to meet these desiderates is RAD, or the rapid application development, mostly used within web based applications destined to online commerce. The current paper will commence with a short presentation of the methodology, the concepts involved, the e-commerce application, to end with the overall advantages and limitations of RAD.

Introduction - RAD Definitions

The introduction of the rapid application development (RAD), some time in the early 1990s (James Martin, in 1991, is generally perceived as the scientist who introduces it), was an essential phase in the software development history, which increased the speed with which applications were developed, but also their capacity to better fit the customers' requirements. Additionally, with RAD, the development process could be changed and adapted along the way, which made for a very flexible development structure.

The RAD methodology is generally defined as "a software development process that allows usable systems to be built in as little as 60-90 days, often with some compromises." On the other hand, the RAD methodology is based on three essential elements:

Prototyping - this element relies on the creation of certain deliverable prototypes of the final product, which can then be gradually refined as feedback from customers and final users is obtained.

Iteration implies continuous improvement and development based on the refinement of the prototypes previously obtained.

Timeboxing is the applied managerial technology that coordinates the previous two elements and ensures that the final product is deliverable on time and to the standards required.

3. Rapid Application Development vs. Structured Systems Analysis and Design Method

Previous to the Rapid Application Development methodology, the software development industry had been dominated by non-agile processes that included the Structured Systems Analysis and Design Method and several Waterfall models. The SSADM was a static development framework based on logical data modelling or data flow modelling.

The SSADM also included several strictly determined development stages, such as the analysis of the current system previous to actual development (known as the feasibility stage), a descriptive outline with the business specifications, followed by a detailed business specification process, a logical system specification stage and the physical design of the final developed product.

The SSADM methodology was included in a larger software development methodological framework referred to as Waterfall models, mainly because one stage preceded the subsequent stage and each subsequent stage was dependent on the outcome of the previous stage. As such, no secondary stage could be completed until the previous primary stage was fully done as well. There was a strict dependency between all the development stages in the software product's cycle. The concept of sequential development is key in the waterfall models and all models based on this concept.

The main problem that waterfall models brought about was the fact that clients' feedback could generally not be incorporated in the final product until this was in the last stages of development. By that time, however, several situations could occur, such as (1) the client's specifications would have changed, especially if the product development took a longer period of time or (2) the client's input would have now implied consistent changes, which, in turn, increased financial and human resources costs.

With this, the agile software development methodology came about in an attempt to solve these problems. With a higher degree of open collaboration and higher flexibility and adaptability, the agile software development methodology encouraged communication, both within the development team and with the customer, which meant that the requirements could be better matched with the product and that the final product, with the changes along the way, reflected the customer's needs. The Rapid Application Development fitted exactly in this methodological framework.

4. Basic Concepts of RAD

Just like its name clearly implies, the rapid application development aims to increase the speed with which software programs are developed; "RAD projects have fast delivery of finished work as a primary goal." The author of Rapid Application Development with Mozilla identified five major concepts related to RAD: less time with the same effect, visual prototypes, vertical solutions, COTS software vs. home grown and finally, destructured testing.

Less time with the same effect

This particular RAD concept emphasises on that the most adequate solution to a problem is often the quickest solution. Foremost, the idea is enforced by the increased flexibility of the rapid application development, meaning that the projects can be improved in time, and the primary requirement is for a project to work. "This is an essential characteristic of RAD projects - there is no allegiance to any rigid rules. Whatever does the job fastest, wins. Even if the technique you chose isn't that beautiful, isn't that sophisticated and maybe isn't even flexible, the fact that it gets the job done is essential." As such, the effect will be the same regardless of the methodology chosen and the applications will work; in the case of RAD however, the work will be completed in less time, generating as such multiple positive effects, such as reduced costs with resource allocation or increased customer satisfaction.

Visual prototypes

McFarlane explains the visual prototypes characteristic with an analogy between software applications and the human influence. In this order of ideas, he states that it takes considerable amounts of time for a software engineer to become accustomed with the interface of the application. Only after the accommodation has occurred will the engineer be able to program. In the case of RAD methodologies, the user is able to configure the interface several times in order to be most comfortable with it. Ergo, the visual prototypes characteristic enhances the flexibility of the applications and methodologies used, increasing as such the satisfaction and creativity of the software engineers.

Then, this particular characteristic is not only beneficial for the developers, but also for the final client, who can request a particular user friendly interface, generally adapted to their unique characteristics and requirements. "The use of videos, story boards and prototypes demands that the final software has a smooth functionality and an easy-to-use interface." In other words, the visual feature of rapid application development not only eases the work of programmers, but also increases the satisfaction felt by end consumers.

Vertical solutions

The characteristic of vertical solutions is explained in the meaning that the RAD projects "used to build products that have a narrow purpose, whether it be a museum catalogue or a stock analysis package. Those products are so-called vertical solutions. There is usually no need to make the product so flexible it can be applied to other uses. That can be a later goal if the product works as it is." In other words, the RAD projects are developed with a specific task and to meet a certain established goal. In time, they can be further developed vertically to meet the same or highly similar goals, but they will not diverge significantly from the initial objective. For instance, a stock analysis program on a local market could be later enhanced to analyze the national stock market, but will never have to help with the database management of a museum.

COTS software vs. home grown

The most simplistic analysis of COTS and home grown application reveals several advantages and limitations of both types of projects. For instance, commercial off-the-shelf projects are easily procured and imply reduced financial resources; however, since they are developed by tertiary parties, they present reduced customization and the buyer has limited control over future developments. The home grown projects are financially and time costly, but have the benefit of a full adaptation to the needs of the organization and their customers, alongside with extensive control over the developments.

Destructured testing

The ability to conduct destructured testing is revealed by the software engineers' capability to break the project down into various smaller issues, analyze and test them in order to retrieve the desired results. This ability is mostly given by the flexibility of the RAD projects. Foremost, since the primary goal of the RAD projects is to work, the attention placed on testing is reduced. Therefore, a special complier has been developed, which will do most of the work, requesting as such little assistance from the software engineers.

5. RAD in Ecommerce particular feature of rapid application development is given by its usage within online commerce. In order for the process to function at the desired capacity and with increased capacity, four tools are required: the database programming language, the interface generator, the links to office applications and finally, the report generator. The database programming language "embeds knowledge of the database structure and includes fundamental database manipulation operations. SQL is the standard database programming language. The SQL commands may be input directly or generated automatically from forms filled in by an end-user. (the) interface… READ MORE

How to Reference "Rapid Application Development RAD" Term Paper in a Bibliography

Related Term Papers:

XML Latest Changes Are in Bolded Black Dissertation

XML

Latest changes are in bolded black text and underlined

Assessing AJAX Application Performance over Optimized XML Networks

Both TCP/IP and XML have emerged as market standards globally. AJAX-based applications… read more

Dissertation 10 pages (2900 words) Sources: 0 Topic: Computers / IT / Internet

---

Delphi History Thesis

Delphi History

With more than 1.7 million developers, Delphi is a widely used Rapid Application Development (RAD) environment. Delphi offers developers a variety of benefits. Applications built with Delphi are… read more

Thesis 3 pages (1047 words) Sources: 4 Style: MLA Topic: Computers / IT / Internet

---

XML Project Specification and Design Document Research Proposal

XML Project Specification and Design Document

Project Specification and Design Report

Specification

XML has emerged as the globally adopted standard for Internet-based integration of systems and processes and has made… read more

Research Proposal 10 pages (3292 words) Sources: 1+ Style: Harvard Topic: Computers / IT / Internet

---

Information Technology Aquarius Marketing Project Plan Term Paper

Information Technology

Aquarius Marketing Project Plan

The intent of this project plan is to comprehensively define the development process, testing, training, and introduction of an enterprise-class portal and series of… read more

Term Paper 12 pages (3970 words) Sources: 12 Style: Harvard Topic: Management / Organizations

---

Define What a Systems Analyst Term Paper

systems analyst is unique in that its role is a hybrid one.

Admittedly system analysts are highly skilled in IT technologies and their applications to core business problems, yet they… read more

Term Paper 8 pages (2585 words) Sources: 4 Style: APA Topic: Business / Corporations / E-commerce

---

View 100+ more related papers  >>