Wikipedia

Rapid application development

Versione del 27 mag 2007 alle 20:39 di Dinwath (discussione | contributi) (correzione categoria + interlink)
(diff) ← Versione meno recente | Versione attuale (diff) | Versione più recente → (diff)
Questa voce o sezione sull'argomento informatica è stata parzialmente tradotta dalla lingua inglese.
Puoi contribuire terminando la traduzione o usando altre fonti. Non usare programmi di traduzione automatica. Usa {{Tradotto da}} quando hai terminato. Se nella pagina di modifica trovi del testo nascosto, controlla che sia aggiornato servendoti dei collegamenti «in altre lingue» in fondo alla colonna di sinistra. Segui i suggerimenti del progetto di riferimento.
Data "Maggio 2007" non riconosciuta. Sintassi: {{T|lingua|argomento|mese anno}}

Rapid application development (RAD), is a software development process developed initially by James Martin in the 1980s. The methodology involves iterative development, the construction of prototypes, and the use of Computer-aided software engineering (CASE) tools. Traditionally the rapid application development approach involves compromises in usability, features, and/or execution speed.

History

Application development refers to the developing of programming applications and differs from programming itself in that it has a higher level of responsibility, including for requirement capturing and testing.[1] Rapid Application Development was a response to non-agile processes developed in the 1970s, such as the Waterfall model. The problem with previous methodologies was that applications took so long to build that requirements had changed before the system was complete, often resulting in unusable systems. Starting with the ideas of Brian Gallagher, Barry Boehm and Scott Shultz, James Martin developed the Rapid Application Development approach during the 1980s at IBM and finally formalised it by publishing a book in 1991.

One such company which concentrated on the development of RAD programming, Magic Software, developed a unique paradigm which enabled both programmers and non-progammers to quickly write sophisticated programs by defining business rules in tables rather than reusing or developing new code. In the mid 90's a programming event was established, the Droege[1] Competition, in which programmers from all over the world raced to complete an application using the language and platform of their choice. Magic Software's paradigm not only won the competition each of the five years the event was held, but dominated all the top positions by an overwhelming margin. Magic Software's paradigm went on to become an established IDE with the ability not only to siginificantly cut programming time, but additionally cut maintenance time on enterprise level projects.

Pros and Cons of RAD

Pros

  1. Increased speed of development through methods including rapid prototyping, virtualization of system related routines, the use of CASE tools, and other techniques.
  2. Decreased end-user functionality (arising from narrower design focus), hence reduced complexity
  3. Larger emphasis on simplicity and usability of GUI design

Cons

  1. Reduced Scalability, and reduced features when a RAD developed application starts as a prototype and evolves into a finished application
  2. Reduced features occur due to time boxing when features are pushed to later versions in order to finish a release in a short amount of time [senza fonte]

References

See also

  1. ^ What is Application Development
Estratto da "https://it.wikipedia.org/w/index.php?title=Rapid_application_development&oldid=8968185"