Explore topic-wise InterviewSolutions in .

• The model makes use of EFFICIENT tools, to DEVELOP the prototype quickly, which calls for hiring skilled professional.
• Team leader MUST WORK closely with developers and customers/users to close the project in TIME.
• Absence of reusable components can lead to failure of the project.

• As customer is involved at all stages of development, it leads to a product achieving customer satisfaction.
• Usage of powerful development tools RESULTS into reduced software development cycle time.
• FEED back from the customer/user is AVAILABLE at the initial stages.
• MAKES use of reusable components, to decrease the cycle time.
• Results into reduced costs as less developers are required.

• When stakeholders think they will SAVE a LOT of money using RAD.
• When stakeholders are not willing to compromise on Quality and will not allow secondary requirements to be ‘timeboxed’ out of the development iteration.
• When project management will not ACCEPT INFORMAL project deliverables.
• When the product must support or interface with other critical systems (reliability and performance are not critical). 

• When development time is critical, or when a product is needed now before THINGS CHANGE.
• When stakeholders are not SURE exactly what they WANT other than some basic requirements.
• When Quality is negotiable.

The STEPS MAY INCLUDE:

• Requirement GATHERING
• Creating Design
• BUILDING Prototype
• Refine Requirement and repeat the steps.

The steps may include:

Rapid Application DEVELOPMENT (RAD) is an incremental software development process model that emphasises a very SHORT development cycle [typically 60-90 days].

The RAD model, is a very high-speed adaptation of the WATERFALL model, where the result of each cycle a FULLY FUNCTIONAL system.

Rapid Application Development (RAD) is an incremental software development process model that emphasises a very short development cycle [typically 60-90 days].

The RAD model, is a very high-speed adaptation of the waterfall model, where the result of each cycle a fully functional system.

The information FLOW among business functions is modeled in a way that ANSWERS the following QUESTIONS:

What information DRIVES the business process?
What information is generated?
Who generates it?
Where does the information go?
Who processes it?

The information flow among business functions is modeled in a way that answers the following questions:

What information drives the business process?
What information is generated?
Who generates it?
Where does the information go?
Who processes it?

The information flow DEFINED as part of the BUSINESS modeling PHASE is refined into a set of data objects that are needed to support the business. The characteristics (CALLED ATTRIBUTES) of each object are identified and the relationships between these objects are defined.

The information flow defined as part of the business modeling phase is refined into a set of data objects that are needed to support the business. The characteristics (called attributes) of each object are identified and the relationships between these objects are defined.

The data objects defined in the data-modeling phase are transformed to achieve the information FLOW NECESSARY to implement a business function. Processing descriptions are created for adding, modifying, DELETING, or RETRIEVING a data object.

The data objects defined in the data-modeling phase are transformed to achieve the information flow necessary to implement a business function. Processing descriptions are created for adding, modifying, deleting, or retrieving a data object.

RAD assumes the use of the RAD fourth generation techniques and tools like VB, VC++, Delphi etc rather than CREATING SOFTWARE using conventional third generation programming languages. The RAD works to REUSE existing program components (when possible) or create reusable components (when necessary). In all cases, automated tools are used to FACILITATE CONSTRUCTION of the software.

RAD assumes the use of the RAD fourth generation techniques and tools like VB, VC++, Delphi etc rather than creating software using conventional third generation programming languages. The RAD works to reuse existing program components (when possible) or create reusable components (when necessary). In all cases, automated tools are used to facilitate construction of the software.

Since the RAD PROCESS emphasizes reuse, many of the PROGRAM COMPONENTS have already been tested. This MINIMIZES the testing and DEVELOPMENT time.

Since the RAD process emphasizes reuse, many of the program components have already been tested. This minimizes the testing and development time.

• For Large (but scalable) projects, RAD requires sufficient resources to create the right NUMBER of RAD teams.
• RAD projects will fail if there is no commitment by the developers or the CLIENTS to ‘rapid-fire' ACTIVITIES necessary to get a system complete in a much ABBREVIATED time frame.
• If a system cannot be properly modularized, building COMPONENTS for RAD will be problematic
• RAD is not appropriate when technical risks are high, e.g. this occurs when a new application makes heavy use of new technology.