Problems in RAD (Rapid Application Development)
Innovative ideas are necessary for any application development. When we planned for any application, we need to think its problem (i.e. what kind of problem can be occurred) also & when problem occurred then there must a solution for that problem.
The same rules applied for RAD (Rapid Application Development) too. Let see what kind of problem can be occurred:
Problems
In 1970’s when processes developed, for instance the Waterfall development methodology, repeatedly resulted in the development of applications that did not meet up client needs as applications take so long to make that requirements had changed before the system was complete. As a result, for bigger projects, these methodologies often resulted in complete, except unfeasible, system.
The reason of the crisis was recognized in the strict devotion to completion of one lifecycle stage before touching on to the next lifecycle stage. Particularly, building an application based on necessities that have been frozen at a point in time means that the longer development take, the more possible that industry needs will transform and overthrow the necessities that the system being developed is based upon.
In my next post I’ll discuss little bit of solutions of these problems.
2 comments:
Rapid application development (RAD) is a term originally used to describe a software development process introduced by James Martin in 1991. Martin's methodology involves iterative development and the construction of prototypes. More recently, the term and its acronym have come to be used in a broader, generic sense that encompasses a variety of techniques aimed at speeding application development, such as the use of web application frameworks and other types of software frameworks. RAD approaches may entail compromises in functionality and performance in exchange for enabling faster development and facilitating application maintenance.
Post a Comment