Rapid application development: differenze tra le versioni

Versione delle 09:17, 28 mag 2007

Versione delle 00:40, 30 mag 2007

Riga 1:

{{T|lingua=inglese|argomento=informatica|data=maggio 2007}}

La '''Rapid application development''' ( o '''RAD'''), è una [[metodologia di sviluppo del software]] introdotta inizialmente da [[James Martin]] negli anni [[Anni 1980|Ottantaanni ottanta]]. Questa metodologia coinvolge [[Metodologie iterative|modelli di sviluppo iterativi]], la costruzione di [[Prototipo (informaticaprogrammazione)|prototipi]] e l'utilizzo di strumenti [[Computer-aided software engineering|CASE]]. Solitamente questo approccio allo sviluppo comporta compromessi ditra usabilità, feature, e/o velocità d'esecuzione.

<!--

== History ==

== HistoryStoria ==

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.<ref>''What is Application Development''</ref> 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 (author)|James Martin]] developed the Rapid Application Development approach during the [[1980s]] at [[IBM]] and finally formalised it by publishing a book in [[1991]].

<!--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.<ref>''What is Application Development''</ref> -->

Nacque in risposta all metodologie di programmazione sviluppate negli [[Anni 1970|anni settanta]], come ad esempio il [[modello a cascata]], che soffrivano principalmente del problema della lentezza di sviluppo. Spesso accadeva che i requisiti dell'applicazione cambiassero ancor prima che questa fosse stata completata, renendola di fatto inusabile. Starting with the ideas of Brian Gallagher, [[Barry Boehm]] and Scott Shultz, [[James Martin (author)|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 Enterprises|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 Computing Services|Droege]][http://www.droegecomputing.com/] 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 [[integrated development environment|IDE]] with the ability not only to siginificantly cut programming time, but additionally cut maintenance time on enterprise level projects.