Application Development Model (RAD)
application development approach relies on adaptability and the need to modify
requirements in response to knowledge acquired as the project progresses.
Prototypes and rapid cycles of repetitive development are often used to
accelerate development and to benefit from early feedback from business users.
After each repeat, developers can fine-tune and validate features with
stakeholders. Generally, RAD’s approaches to software development have been placed
less emphasis on planning and greater focus on the process.
RAD is typically
divided into four basic phases that complement the process.
Planning: The first step where all developers, designers, engineers
and technology personnel meet together to discuss project requirements and
specifications. The prototype needs are thus identified and agreed upon.
Design: Once the design needs are collected, the prototypes and
feedback from the user experiences where they help in the design of the model
and the overall architecture of the application.
Development: With design and model real work starts with development.
At this stage, basic encryption, architecture and integration with back-end
services occur. With the rapid application development model, there can be
improvements that are made according to the need of the project.
Release: The final transition is where the rapid application
launches. The development team moves components from the test environment to
production. The application is deployed where the user can now use it to
increase business efficiency.
Advantages of Rapid
Application Development Model
It is adaptable and flexible for changes.
It is easier to transfer delivered as scripts, high level abstractions
Use intermediate symbols.
There is a decrease in manual encryption. Because of the code generators and
• Each stage in RAD provides
high priority functions to the customer.
basically is about tradition engineering approach that is applied to such
software engineering. . It is also called the Linear
Chain Life Cycle Model. The project contains a set of specific stages. At each
stage, there is a set of activities that must occur in a particular order, and
a set of results called (“deliveries”) that must be produced and
signed as completed by the project manager for each stage before the next stage
At the end of each
certain stage, revision and revision of any
earlier stage once completed didn’t receive any encouragement from the strict
• Simple model, easy to understand and use.
• Each stage has an
easy manage outputs and a review process.
• In this process,
the stages are processed and completed each time. For that they never interfere
with each other.
• it’s well worked
for small projects where each require is easy to understand.
the application is in the testing phase, it is difficult to come back and
change something that was not well
thought out at the concept stage.
any work programs are such produced until late all through the life cycle.
Highly risk amount
object-oriented projects are not good processed at this approach.
suitable for projects with moderate to high risk requirements for change.