This first FAQ is about Rapid application development(RAD). Rapid application development is widely used in the development world nowadays. But what is it? How does the model work? When should I use it? When shouldn’t I use it? We are here to answer those questions and make you understand Rapid Application Development even better.
click here to read this article in Dutch
Rapid application development is a form of software development that focuses on making a working prototype and gathering feedback from users instead of strict planning and the recording of requirements.
Rapid application development is described as a form of agile software development in which you deliver the preferred piece of software in small iterations.
So as you might already understand, you need to be willing to give up some quality because you are going for speed over quality. The amount of quality you give up, however, can be limited if you do it right and with the right people.
The model has six steps you’ll need to go through:
Figuring out the requirements: Start to figure out what your project needs to succeed;
Build a prototype: Start building right away, it has rapid in the name for a reason;
Get feedback from you users: Make sure it matches the user expectations. RAD is an ongoing collaboration between developers and users;
Repeat steps 2 and 3: Repeat until you are sure that the program works and met user expectations;
Test ….. A lot: Developers and users need to test different scenarios in order to make sure it actually works properly under different circumstances.
Present your system: The final step is to present your final product.
This way of developing software has a few advantages:
The first and most obvious advantage is that it saves time. Using this method means that the development of an application will take significantly less time than it normally would.
The second advantage is that a lot of components can be reused.
The third advantage is that the method encourages customers to give their feedback.
The fourth and final advantage is that by integrating the program from the beginning, you will avoid a lot of integration problems.
No method has only advantages, just like this one there are disadvantages to using a certain method.
The disadvantages of using rapid application development are: High costs, the need for skilled developers (which contributes to the high costs) and only programs that can be modularized can be built by using RAD.
One thing is time, time is not only an advantage but also a requirement if you want to use rapid application development. If your project is going to take more than 2 or 3 months to build, we don’t recommend you to use rapid application development.
A second thing is that you’ll need to have the right resources. Rapid application development requires a highly skilled development team. Highly skilled developers come at a price, so make sure you have enough resources (money) to get a good team together.
The last thing is the amount of time you ask of your test users. Because of the small iterations you won’t have to ask user for loads of time, but you will still have to make sure if they have any time at all to test your iterations.
One of the most used and popular programming languages around is Python. Python is especially efficient when you are building & integrating multiple systems.
Another great framework we also like to use for RAD is the Ruby on Rails framework. This framework is based around the “don’t repeat yourself” philosophy. The biggest advantage of Ruby on Rails is the speed that it provides and since time is — one of — the biggest factors in RAD, Ruby on Rails is a good option.
If you have any additional questions after this about Rapid application developement or any other subject, don’t hesitate to call. We will answer all your questions!