Rapid Application Development Process

FIRSTLY,

The rapid application development (RAD) component enables you to configure a server project so that you can repeatedly deploy a server configuration (containing your message flows and message sets) to the runtime with a single toolbar button click. The RAD component uses the broker archive generation component, which creates the compiled message flow (.cmf) and compiled message set (dictionary) files, and stores them in a broker archive (bar). It then publishes (deploys) these resources to the target execution groups. Unlike with normal deployment, the bar file created using RAD is not retained for future use.

The RAD component is a quick way for people who are developing message flow applications to repeatedly test their message flows, ESQL transformation programs, and mapping transformation programs, in a safe environment, before they are used on a production system.

The following figure shows how RAD relates to the normal deployment cycle:

There are two ways to run RAD:

1. Run on Server
2. Debug on Server

• When you select Run on Server, a check is made to see if a default server is defined for the project. If it is, the project is published (deployed) to the default server. If not, the Server Selection wizard is opened before continuing and, when complete, a Publish action is performed for the server instance and its configuration.
• Debug on Server is similar to Run on Server, except that, after the action successfully completes, the Flow Debug perspective is opened for you to begin debugging your flow.
• SECONDLY,
• RAD allows the technology team to define the scope of the project, identify the iterations and begin working immediately in lieu of the older methodologies where the entire systems is designed on paper and then developed. As each iteration is finalized, based on priority, the complete system begins to take shape.   Tasks that normally could not be completed until the end of the project can most likely be completed during any stage of the product.  
• RAD begins with the End Goal in mind.  "Organize and perform activities according to their priority" (Stephen Covey). All iterations are working toward the same goal.  The graph below demonstrates a RAD cycle:

• THIRD,  It is a methodology for compressing the feasibility analysis, planning, design, build, and test phases into a series of short, iterative development cycles. Refer to book by James Martin: Rapid Application Development, Macmillan for details.

Rapid Application Development

ADVANTAGES OF USING RAD

• Conventional software development methods take, on an average almost 20% more time than the RAD procedure. Using RAD can enable quicker visualization of the end-design and hence allow rapid software testing and rectifying steps. The customer is able to have a faster look at the design to add valuable inputs, in order to make the design more user-friendly.
• The current competitive scenario demands frequently upgraded softwares in order to effectively satisfy customers' requirements. RAD enables a faster and updated version to reach the end user, by systematically eliminating redundant steps or using the prototype methods.
• Cost overruns and meeting the time constraints are another advantage, though not a big consideration in high-end uses.
• RAD makes the development process to be a more credible one by facilitating a scope for the customer to actively provide inputs in the development process. This may also prove a feasible study from the point of view of a developer.
• It protects the current project from the variations in the market.

For the conclusion, Rapid Application Development is an efficient methodology which can assist faster software development, and at the same time ensure maximum quality of the project.








Source Retrieved From,
http://www.brinex.com/solutions-bas-process-rad.html
http://www.buzzle.com/articles/advantages-of-rapid-application-development.html