Quality and RAD: A Contradiction in Terms?
Rapid Application Development (RAD) is commonly applied to delivery of point software solutions in isolation from enterprise-wide requirements. This is problematic in the context of large organisations seeking practical business-oriented software re-use, especially in a way which capitalises on legacy software. This article examines the role of architecture, and describes a component-based approach that facilitates re-use of services. The need for high quality and generality of components that are trusted by multiple consumers is increased by an order of magnitude and is set in vivid contrast to the need for fast solutions to pressing business needs.
KeywordsUser Service Business Service Legacy Software Collaboration Diagram Solution Project
Unable to display preview. Download preview PDF.
- 1.Martin, J., Rapid Application Development, Macmillan, New York, 1991Google Scholar
- 2.DSDM Consortium, DSDM Version 3, Tesseract Publishing., 1997.Google Scholar
- 3.Stapleton, J., DSDM - The Method in Practice, Addison Wesley Longman, 1997Google Scholar
- 5.Yourdon, E.N, The Yourdon Report, May, 1997Google Scholar
- 6.Mowbray, T.J., and Malveau, R.C., CORBA Design Patterns, Wiley, 1997Google Scholar
- 7.OMG, Unified Modelling Language Version 1.0, OMG, Framlington, Mass.,1997Google Scholar
- 8.Allen, P. and Frost, S., Component-Based Development for Enterprise Systems, Cambridge University Press- SIGS, 1998Google Scholar
- 9.Cox, B., Object-Oriented Programming: An Evolutionary Approach, Addison Wesley, 1986Google Scholar
- 12.Folkes, S., and Stubenvoll, S., Accelerated Systems Development, Prentice Hall, 1992Google Scholar
- 13.Allen, P. and Frost, S., Component Manager, Select Software Tools White Paper, 1996Google Scholar
- 14.Wilkinson, N.M, Using CRC Cards: An Informal Approach to Object Oriented Development, SIGS Books, 1995Google Scholar