Rapid Application Development model, Software process model, Pros & Cons, omparison, Example, Conclusion

1. Rapid Application
Development
(RAD)
Model

2. Software process model
–Set of activities required to develop a software system
–Software process model provide roadmap for software
engineering work
Phases
–Specification
–Design and implementation
–Integration and testing
–Operation and maintenance

3. Rapid application developm
– The Rapid Application Development Model was first proposed by
IBM in 1980’s in James Martin’s book by the same name.
– Its starts by defining a loose set of requirements, so developers
get an idea of what the product needs to achieve.
– Developers then create a prototype that satisfies all or some of
the requirements.
– This prototype is presented to the client and feedback collected.
At this point, clients may change their mind or discover that
something that seemed right on paper makes no sense in practice.

4. Cont.
–This kind of revision is an accepted part of
the RAD approach and developers return to
step two to revise the product.
–If client feedback is entirely positive then
developers can move to the ultimate step of
finalizing the product and it can be handed to
the client with confidence that it meets their
requirements

5. Cont.
–Rapid application development falls under the
category of agile development techniques
–RAD is more focused on prototypes. In RAD, the
primary focus is to get something usable in front of
the client as quickly as possible to get feedback.
–In the RAD model, you may show the client
something still in the development phase, whereas
Agile will usually wait until a specific feature is
designed and built before showing it.

6. RAD Model

7. Pros & Cons of RAD
– Reduced development time.
– Increases reusability of components
– Quick initial reviews occur
– Encourages customer feedback
– Integration from very beginning solves a lot of integration issues.
Disadvantages
– Depends on strong team and individual performances for identifying business
– requirements.
– Only system that can be modularized can be built using RAD
– Requires highly skilled developers/designers.
– High dependency on modeling skills

8. Example
– KiSSFLOW uses the rapid application development model.
– For example, if you’re looking into developing an app on KiSSFLOW
for some use case, say to manage your finance department, you’ll
have a basic idea of what your finance department needs. Using
rapid prototyping, you can make several models and get feedback
from the finance team on what they’re looking for.
– Once you have a prototype that has all the features that they’re
looking for, you can develop the final app, and launch it.

9. RAD vs. Agile

10. Comparison

11. Conclusion
–The Rapid Application Development (RAD)
model is a software development model,
where developers produce a prototype of
the software as quickly as possible to get
feedback from the client and add new
functionalities.