There are two ways to run RAD:
- Run on Server
- 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
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 |