Rapid Development Method of Software Development

Posted by on June 16, 2013 in Programming | 0 comments

Rapid Development Method of Software Development

Rapid development strays from both methods discussed before. There is no team involved in most cases. Rapid development takes a single programmer and emphasizes the interaction between that programmer and the client. The main goal of rapid development is to get the product done as soon as possible. Therefore, the programmer has direct access to the client and has frequent meetings to get things done quickly.

The process happens in iterations just like agile methods. The programmer will discuss with the client only what he or she needs to know to get the next module completed. Therefore, when the module is completed, the programmer receives the next portion of information about what the product should do. There are no plan or technical specs with this method. The programmer creates the code for the modules so quickly after discussing what they should accomplish that there should be no time for any information or functionality to get lost. The process repeats until the project is done.

Advantages of Rapid Development

Rapid development, as its name implies, is fast. Clients like when their product is delivered in a timely manner. The client also has direct access to the programmer so he can relay ideas directly to the person who will be making the code without interpretations. The main attraction to this development method is its speed compared to the other methods.

Disadvantages of Rapid Development

Rapid development is not widely used in a corporate setting or with teams because it has a few drawbacks. It does produce code very fast, but you have to sacrifice something to achieve that. Quality is usually what is sacrificed. Coding standards are mainly nonexistent in this method and often code is not written in a way that can be reused later in the projects. The programmer does not know the whole scope of the project when they write the code either, which does not help with how to structure code. There is also no documentation using this method. There are no technical specifications, design documents, or internal code documentation found in this method.

This post sponsored by: CMA – providers of independent medical evaluations, FCE’s and more.

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

Leave a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>