Silver Pellets for Improving Software Quality

Information Resources Management Journal

Volumn 17, Issue 2, 2004, Pages 1-21

  Duggan, Evan W ^a  

^a UNIVERSITY OF ALABAMA   (United States)

Author keywords

Software development; Software engineering; Software quality

Indexed keywords

BENCHMARKING; COMPUTER HARDWARE; COMPUTER SYSTEMS; DATA PROCESSING; INFORMATION TECHNOLOGY; ORE PELLETS; PROBABILITY; PROBLEM SOLVING; SILVER; SOCIETIES AND INSTITUTIONS;

SOFTWARE CRISIS; SOFTWARE QUALITY;

SOFTWARE ENGINEERING;

EID: 1642307917     PISSN: 10401628     EISSN: None     Source Type: Journal    
DOI: 10.4018/irmj.2004040101     Document Type: Review

References (78)

1. Adamopoulos, D.X., Haramis, G., & Papandreou, C.A. (1998). Rapid prototyping of new telecommunications services: A procedural approach. Computer Communications, 21, 211-219.
2. Al-Mushayt, O., Doherty, N., & King, M. (2001). An investigation into the relative success of alternative approaches to the treatment of organizational issues in systems development projects. Organization Development Journal, 19(1), 31-48.
3. Andrews, D. C. (1991). JAD: A crucial dimension for rapid applications development. Journal of Systems Management, 42(3), 23-27,31.
4. Agrawal, K. & Whittaker, J. A. (1993). Experiences in applying statistical testing to a real-time, embedded software system. Proceedings of the Pacific Northwest Software Quality Conference.
5. Agarwal, R., De, P., Sinha, A. P., & Tanniru, M. (2000). On the usability of OO representations. Communications of the ACM, 43(10), 83-89.
6. Barki, H., & Hartwick, J. (1994). Measuring user participation, user involvement, and user attitude. MIS Quarterly, 18(1), 59-82.
7. Barrow, P. D. & Mayhew P. J. (2000). Investigating principles of stakeholder evaluation in a modern IS development approach. Journal of Systems and Software, 52(2-3), 95-103.
8. Baskerville, R. L. & Stage, J. (1996). Controlling prototype development through risk analysis. MIS Quarterly, 20(4), 481-504.
9. Beizer, B. (1997). Cleanroom process model: A critical examination. IEEE Software, 14(2), 14-16.
10. Beynon-Davies, P., Mackay, H., & Tudhope, D. (2000). Its lots of bits of paper and ticks and post-it notes and things: A case study of a rapid application development project. Information Systems Journal, 10(3), 195-216.
11. Beynon-Davies, P., Tudhope, D., & Mackay, H. (1999). Information systems prototyping in practice. Journal of Information Technology, 14(1), 107-120.
12. Boar, B. H. (1984). Application Prototyping. New York: John Wiley & Sons.
13. Bordoloi, B. & Lee, M. (1994). An object-oriented view: Productivity comparison with structured development. Information Systems Management, 11(1), 22-30.
14. Borovits, I., Ellis, S., & Yeheskel, O. (1990). Group processes and the development of information systems. Information & Management, 19, 65-72.
15. Bourne, K. C. (1994). Putting the rigor back in RAD. Database Programming & Design, 7(8), 25-30.
16. Broady, J. E., Walters, S. A., & Hartley, R. J. (1994). A review of information systems development methodologies (ISDMS). Library Management, 15(6), 5-19.
17. Brooks, F.P. Jr. (1987). No silver bullet: Essence and accidents of software engineering. IEEE Computer, 20(4), 10-19.
18. Brynjolfssen, E. (1993). The productivity paradox of information technology. Communications of the ACM, 36(12), 67-77.
19. Carmel, E., Whitaker, R. D., & George, J. F. (1993). PD and joint application design: A transatlantic comparison. Communications of the ACM, 36(6), 40-48.
20. Carmel, E., George, J.F., & Nunamaker, J.F. (1995). Examining the process of electronic-JAD, Journal of End User Computing, 7(1), 13-22.
21. Cox, B.J. (1995). No silver bullet revisited. American Programmer Journal, (November).
22. Dodd, J. L. & Carr, H. H. (1994). Systems development led by end-users. Journal of Systems Management, 45(8), 34-40.
23. Doherty, N. F. & King, M. (1998). The consideration of organizational issues during the systems development process: An empirical analysis. Behavior & Information Technology, 17(1), 41-51.
24. Dekleva, S.M. (1992). The influence of the information systems development approach on maintenance. MIS Quarterly, 16(3), 355-372.
25. Elboushi, M.I. (1997). Object-oriented software design utilizing quality function deployment. The Journal of Systems and Software, 38(2), 133-143.
26. Erikkson, I. & McFadden, F. (1993). Quality function deployment: A tool to improve software quality. Information & Software Technology, 35(9), 491-498.
27. Fichman, R. G. & Kemerer, C. F. (1992). Object-oriented and conventional analysis and design methodologies. IEEE Computer, 25(10), 22-39.
28. Fitzgerald, B. (1998). An empirical investigation into the adoption of systems development methodologies. Information and Management, 34(6), 317-328.
29. Fitzgerald, B. (2000). Systems development methodologies: The problem of tenses. Information Technology & People, 13(3), 174-182.
30. Flatten, P. O. (1992). Requirements for a life-cycle methodology for the 1990s.
31. W. W. Cotterman & J. A. Senn (Eds.), Challenges and Strategies for Research in Systems Development (pp.221-234). New York: John Wiley & Sons.
32. Friedlander P. (1992). Ensuring software project success with project buyers. Software Engineering Tools, Techniques, and Practices, 2(6), 26-29.
33. Fox, W. M. (1995). Sociotechnical system principles and guidelines: Past and present. The Journal of Applied Behavioral Science, 31(1), 91-105.
34. Gibbs, W. W. (1994). Software's chronic crisis. Scientific American, 271(3), 86-95.
35. Glass, R. L. (2001). Extreme programming: The good, the bad, and the bottom line. IEEE Software, 8(6), 111-112.
36. Grady, R. B. (1993). Practical results from measuring software quality. Communications of the ACM, 36(11), 62-68.
37. Hanna, M. (1995). Farewell to waterfalls? Software Magazine, 15(5), 38-46.
38. Hausler, P.A., Linger, R.C., & Trammell. C. J. (1994). Adopting cleanroom software engineering with a phased approach. IBM Systems Journal, 33(1), 89-109.
39. Harter, D. E., Slaughter, S. A., & Krishnan, M. S. (1998). The life cycle effects of software quality: A longitudinal analysis. International Conference on Information Systems, 346-351.
40. Head, G. E. (1994). Six-Sigma software using cleanroom software engineering techniques. Hewlett-Packard Journal, 45(3), 40-50.
41. Ho, E. S., Lai, Y. J., & Chang, S. I. (1999). An integrated group decision-making approach to quality function deployment. IIE Transactions, 31(6), 553-567.
42. Hocking, L. J. (1998). Developing a framework for examining systems development and its environmental context: The relationship between Gidden's structuration theory and Pettigrew's contextualist analysis. Proceedings of the 4th Association for Information Systems Americas Conference, 835-837.
43. Hough, D. (1993). Rapid delivery: An evolutionary approach for application development. IBM Systems Journal, 32(3), 397-419.
44. Jaakkola, I.E., & Drake, K.B. (1991). ASDM: The universal systems development methodology. Journal of Systems Management, 42(2), 6-11.
45. Jerva, M. (2001). Systems analysis and design methodologies: Practicalities and use in today's information systems development efforts. Topics in Health Information Management, 21(4), 13-20.
46. Johnson, R. A., Hardgrove, B. C., & Doke, E. R. (1999). An industry analysis of developer beliefs about object-oriented systems development. The DATA BASE for Advances in Information Systems, 30(1), 47-64.
47. Kettelhut, M. C. (1993). JAD methodology and group dynamics. Information Systems Management, 14(3), 46-53.
48. Khaliffa, M. & Verner, J. M. (2000). Drivers for software development method usage. IEEE Transactions on Engineering Management, 47(3), 360-369.
49. Kjaer, A. & Madsen, K. H. (1995). Participatory analysis of flexibility. Communications of the ACM, 38(5), 53-60.
50. Korac-Boisvert, N. & Kouzmin, A. K.N. (1995). It development: Methodology overload or crisis. Science Communication, 17, 81-88.
51. Lee, G. & Xia, W. (2002). Flexibility of information systems development projects: A conceptual framework. Proceedings of the Eighth Americas Conference on Information Systems (pp. 1390-1396).
52. Liou, Y. I. & Chen, M. (1993/4). Using group support systems in joint application development for requirements specifications. Journal of Management Information Systems, 8(10), 805-815.
53. Lyytinen, K. (1988). Expectation failure concept and systems analysts' view of information system failures: Results of an exploratory study. Information & Management, 14(1), 45-56.
54. Mankin, D. & Cohen S.G. (1997). Teams and technology: Tensions in participatory design. Organizational Dynamics, 26(1), 63-76.
55. Markus, M.L. & Keil, M. (1994). If we build it they will come: Designing information systems that users want to use. Sloan Management Review, 35(4), 11-25.
56. Martins, A. & Aspinwall, E.M. (2001). Quality function deployment: An empirical study in the UK. Total Quality Management, 12(5), 575-588.
57. Meso, P. & Madey, G.R. (2000). A complexity-based taxonomy of systems development methodologies. Association for Information Systems 2000 Americas Conference (pp. 238-244).
58. Mousinho, G. (1990). Project management: Runaway! Systems International, 6, 35-40.
59. Muller, M.J., Wildman, D.M., & White, E.A. (1993). Taxonomy of PD practices: A brief practitioner's guide. Communications of the ACM, 36(4), 26-27.
60. Newman, M. & Robey, D. (1992). A social process model of user-analyst relationships. MIS Quarterly, 16(2), 249-266.
61. Niederman, F., Brancheau, J. C., & Wetherbe, J.C. (1991). Information systems management issues for the 1990s. MIS Quarterly, 15(4), 474-500.
62. Paulk, M. (2001). Extreme programming from a CMM perspective. IEEE Software, 8(6), 19-26.
63. Ravichandran, T. & Rai, A. (1996). Impact of process management on systems development quality: An empirical study. Proceedings of the Americas Conference on Information Systems.
64. Robey, D., Welke, R., & Turk, D. (2001). Traditional, iterative, and component-based development: A social analysis of software development paradigms. Information Technology and Management, 2(1), 53-70.
65. Sabherwal, R. & Robey D. (1995). An empirical taxonomy of implementation processes based on sequences of events in information systems development. In G. P. Huber & A. H. Van de Ven (Eds.), Longitudinal Field Research Methods: Studying Processes of Organizational Change (pp. 228-266). London: Sage.
66. Schmidt, D.C. & Fayad, M.E. (1997) Lessons learned building reusable OO frameworks for distributed software, Communications of the ACM, 40(10), 85-87.
67. Shani, A.B. & Sena, J.A. (1994) Information technology and the integration of change: Sociotechnical system approach. The Journal of Applied Behavioral Science, 30(2), 247-270.
68. Spangler, A. (1996). Cleanroom software engineering: Plan your work and work your plan in small increments. IEEE Potentials, (October/November), 29-32.
69. Sparling, M. (2000). Lessons learned through six years of component-based development. Communications of the ACM, 43(10), 47-53.
70. Szyperski, C. (1998). Component Software, Beyond Object-Oriented Programming. New York: Addison-Wesley.
71. Trammell, C. J., Pleszkoch, M.G., Linger, R.C. & Hevner A. R. (1996). The incremental development process in cleanroom software engineering. Decision Support Systems, 17(1), 55-71.
72. Vessey, I. & Conger S.A. (1998). Strong vs. weak approaches to systems development. Communications of the ACM, 37(5), 102-112.
73. Vessey, I. & Glass R. (1994). Requirements specification: Learning object, process, and data methodologies. Communications of the ACM, 41(4), 99-102.
74. Vlasblom, G., Rijsenbrij, D., & Glastra, M. (1995). Flexibilization of the methodology of system development. Information and Software Technology, 37(11), 595-607.
75. Weinberg, R. S. (1991). Prototyping and the systems development life cycle. Information Systems Management, 8(2), 47-53.
76. Welke, R. J. (1994). The shifting software development paradigm. Database, 25(4), 9-16.
77. Wetherbe, J. C. (1991). Executive information requirements: Getting it right. MIS Quarterly, 15(1), 51-65.
78. Wood, J. & Silver, D. (1995). Joint Application Development. New York: John Wiley & Sons.