Point-Counterpoint: Does RAD Live Up to the Hype?

Authors:
John P. Reilly;Erran Carmel
Affiliations:
-;-
Venue:
IEEE Software
Year:
1995

Citing 0
Cited 6

Risks of rapid application development

Communications of the ACM
A Quality Software Process for Rapid Application Development

Software Quality Control
Coupling Trends in Industrial Prototyping Roles: An Empirical Investigation

Software Quality Control
The critical success factors in the management of projects using innovative approaches

International Journal of Networking and Virtual Organisations
The concerns of prototypers and their mitigating practices: an industrial case-study

PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
What formal models cannot show us: people issues during the prototyping process

PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement

Quantified Score

Hi-index	0.02

Visualization

Abstract

The author makes the point that, to be successful with RAD (rapid application development), we can no longer look just at the software product in isolation. A RAD development process demands that we expand our view to encompass users and their work environments-and if we do it right, everyone benefits. But given all the risks, would you stake mission-critical projects on RAD? If it is not mission-critical, then why bother at all?