Abstract
Software organizations can significantly improve the quality of their output if they have a defined and documented software process, together with the appropriate techniques and tools to measure its effectiveness. Without a defined process it is impossible to measure success or focus on how development capability can be enhanced. To date, a number of software process improvement frameworks have been developed and implemented. However, most of these models have been targeted at large-scale producers. Furthermore, they have applied to companies who use traditional development techniques. Smaller companies and those operating in development areas where speed of delivery is paramount have not, as yet, had process improvement paradigms available for adoption.
This study examined the software process in a small company and emerged with the recommendation of the use of the Dynamic Systems Development Method (DSDM) and the Personal Software Process (PSP) for achieving software process improvement.
Similar content being viewed by others
References
W.S. Humphrey. Characterising the software process: a maturity framework. IEEE Software, March 1988, 73–79.
M.C. Paulk, B. Curtis, M.B. Chrissis and C. Weber. Capability Maturity Model, Version 1.1, IEEE Software, July 1993, 18–27.
DSDM Consortium, Dynamic Systems Development Method, Version 2.0. November 1995.
W.S. Humphrey. A Discipline for Software Engineering. (Addison Wesley, 1995).
J. Martin. Rapid Application Development. (Macmillan, 1991).
V.S. Gordon and J.M. Bieman. Rapid prototyping: lessons learned, IEEE Software, January 1995, 85–94.
J. Kerr and R. Hunter. Inside RAD — How to Build Fully Functional Computer Systems in 90 Days or Less. (McGraw-Hill, 1994).
Luqi and Royce, Winston Status Report: computer-aided prototyping. IEEE Software, November 1991, 77–81.
J.P. Reilly. Does RAD live up to the hype?, IEEE Software, September 1995, 24–26.
E. Carmel. Does RAD live up to the hype?, IEEE Software, September 1995, 25–26.
M.E. Fagan. Design and code inspections to reduce errors in program development, IBM Systems Journal, 15(3), (1976), 182–211.
M.E. Fagan. Advances in software inspections, IEEE Transactions on Software Engineering, SE-12 (1986), 744–751.
E.F. Weller. Lessons from three years of inspection data. IEEE Software, September 1993, 38–45.
A.M. Davis. Fifteen principles of software engineering. IEEE Software, November 1994, 94–101.
A.F. Ackerman, L.S. Buchwald and F.H. Lewski. Software inspections: an effective verification process, IEEE Software, May 1989, 31–36.
A. Joch and O. Sharp. How software doesn't work: nine ways to make your code more reliable. Byte, December 1995, 49–60.
B. Shostak. Adapting the personal software process to industry. Software Engineering Technical Council Newsletter, 14(2), (1996), 10–12.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Coleman, G., Verbruggen, R. A Quality Software Process for Rapid Application Development. Software Quality Journal 7, 107–122 (1998). https://doi.org/10.1023/A:1008856624790
Issue Date:
DOI: https://doi.org/10.1023/A:1008856624790