Rapid application development
Philosophy:
- Applications must be produced quickly
- to be economical
- to reduce the number of changes between analysis and final delivery
- to be relevant when delivered, not solving last year's problem
- because users want their new system now, or because the organisation
must conform to new legislation
- to clear the application backlog
- User requirements must be understood
- users must be involved in the development process
- understanding is ensured by the use of concrete examples, hence the
emphasis on
- prototyping
- Software developers must be allowed to do their job with the minimum
of bureaucratic interference
Rapid application development
Advantages: Quick results, not abstract, users have assurance
that correct solution will be produced
Bibliography
Martin, J (1991) "Rapid Application Development",
Macmillan
See also various books on the methodology: "Dynamic Systems Development Methodology".
CAI (2005) "Focus on Tom Gilb: Expert Evolutionary Development Practitioner and Author." IT Metrics and Productivity Journal, December 2005.
http://www.compaid.com/caiInternet/ezine/tomgilbinterview1.pdf
Other topics