Rapid application development: differenze tra le versioni

Versione delle 00:40, 30 mag 2007

Versione delle 01:58, 30 mag 2007

Riga 7:

<!--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 allalle 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. StartingSullla withbase thedelle ideasidee ofdi [[Brian Gallagher]], [[Barry Boehm]] and [[Scott Shultz]], [[James Martin (author)|James Martin]] developedsviluppò thel'approccio RapidRAD Applicationdurante Developmentgli approachanni duringottanta the [[1980s]] atpresso [[IBM]] anded finallyinfine formalisedlo itformalizzò bypubblicando publishingun alibro booksull'argomento innel [[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.