An industry analysis of developer beliefs about object-oriented systems development

Abstract

Object-oriented systems development (OOSD) is a recent innovation in software development that is often cited as a viable solution to many of the ills plaguing this critical industry. However, some express doubt about the potentially over-hyped claims of OOSD. While there are many accounts of the successful application of OOSD, widespread acceptance has not been achieved, implying that OOSD may not be viewed as positively by industry as the literature would suggest.To address this dilemma, the present study examines a wide variety of specific beliefs about OOSD as provided by a survey of 150 systems developers. Using Ajzen's (1988) theory of planned behavior as a foundation, an exploratory factor analysis is performed to determine which specific beliefs about OOSD are indeed salient indicators of three fundamental concepts that should influence acceptance: the usefulness of OOSD, social pressure to use OOSD, and the ease of using OOSD. The results of the study reveal that while many specific beliefs about OOSD are indeed salient indicators of these more fundamental, potentially influential factors, many other beliefs are not. This study should prove helpful to practitioners who are considering the adoption or continued use of OOSD, and to researchers who are interested in the diffusion of innovations in general

References

1. Abrahamson, E. (1996). "Management Fashion," Academy of Management Review, Vol. 21, No. 1, pp. 254-285.
2. Agarwal, R., and Prasad, J. (1997). "The Role of Innovation Characteristics and Perceived Voluntariness in the Acceptance of Information Technologies," Decision Sciences, Vol. 28, No. 3, Summer, pp. 557-582.
3. Ajzen, I. (1988). Attitudes, Personality, and Behavior, Chicago, IL: The Dorsey Press.
4. Ajzen, I. (1991). "The Theory of Planned Behavior," Organizational Behavior and Human Decision Processes, Vol. 50, pp. 179-211.
5. Ajzen, I., and Fishbein, M. (1980). Understanding Attitudes and Predicting Social Behavior, Englewood Cliffs, NJ: Prentice-Hall.
6. Babbie, E. (1990). Survey Research Methods, Belmont, CA: Wadsworth.
7. Basili, V., Briand, L., and Melo, W. (1996). "How Reuse Influences Productivity in Object-Oriented Systems," Communications of the ACM, Vol. 39, No. 10, pp. 104-116.
8. Berg, W., Cline, M., and Girou, M. (1995). "Lessons Learned from the OS/400 OO Project," Communications of the ACM, Vol. 38, No. 10, pp. 54-64.
9. Blaha, M., and Premerlani, W. (1998). Object-Oriented Modeling and Design for Database Applications, Englewood Cliffs, NJ: Prentice-Hall.
10. Bock, D., and Ryan, T. (1993). "Accuracy in Modeling with Extended Entity Relationship and Object Oriented Data Models," Journal of Database Management, Vol. 4, No. 4, pp. 30-39.
11. Boehm-Davis, D., and Ross, L. (1992). "Program Design Methodologies and the Software Development Process," International Journal of Man-Machine Studies, Vol. 36, pp. 1-19.
12. Booch, G. (1994). Object-Oriented Analysis and Design with Applications, (2nd ed.), Redwood City, CA: Benjamin/Cummings.
13. Brown, D. (1997). Object-Oriented Analysis: Objects in Plain English, New York: John Wiley & Sons.
14. Burkle, U., Gryczan, G., and Zullighoven, H. (1995). "Object-Oriented System Development in a Banking Project: Methodology, Experience, and Conclusions," Human-Computer Interaction, Vol. 10, pp.293-336.
15. Chen, D.J., and Chen, D.T.K. (1994). "An Experimental Study of Using Reusable Software Design Frameworks to Achieve Software Reuse," Journal of Object-Oriented Programming, Vol. 7, No. 2, pp. 56-67.
16. Chin, W.W. (1998). "Issues and Opinion on Structural Equation Modeling," MIS Quarterly, Vol. 22, No. 1, pp. vii-xvi.
17. Coad, P., and Yourdon, E. (1991). Object-Oriented Analysis, (2nd ed.), Englewood Cliffs, NJ: Yourdon Press.
18. Cockburn, A. (1998). Surviving Object-Oriented Projects: A Manager's Guide, Reading, MA: Addison-Wesley.
19. Coleman, D., Arnold, P., Bodoff, S., Dollin, C., Gilchrist, H., Hayes, E, and Jeremaes, P. (1994). Object-Oriented Development: The Fusion Method, Englewood Cliffs, NJ: Prentice-Hall.
20. Davies, S.R, Gilmore, D.J., and Green, T.R.G. (1995). "Are Objects that Important? Effects of Expertise and Familiarity on Classification of Object-Oriented Code," Human-Computer Interaction, Vol. 10, pp. 227-248.
21. Davis, F., Bagozzi, R., and Warshaw, R (1989). "User Acceptance of Computer Technology: A Comparison of Two Theoretical Models," Management Science, Vol. 35, No. 8, pp. 982- 1003.
22. Doll, W.J., and Torkzadeh, G. (1988). "The Measurement of End-User Computing Satisfaction," MIS Quarterly, Vol. 12, No. 2, pp. 259-274.
23. Fayad, M., Tsai, W., Roberts, M., Hawn, L., and Schooley, J. (1994). "Adapting an Object-Oriented Development Method," IEEE Software, Vol. 11, No. 3, pp. 68-76.
24. Fichman, R.G., and Kemerer, C.F. (1992). "Object-Oriented and Conventional Analysis and Design Methodologies: Comparison and Critique," IEEE Computer, Vol. 25, No. 10, pp. 22-39.
25. Fichman, R.G., and Kemerer, C.F. (1993). "Adoption of Software Engineering Process Innovations: The Case of Object Orientation," Sloan Management Review, Vol. 34, No. 2, pp. 7-22.
26. Filman, R., Faught, W., and Solomon, J. (1992). "The Object-Oriented Development of a Transaction-Processing Application," Journal of Object-Oriented Programming, Vol. 5, No. 7, pp. 51-60.
27. Fishbein, M., and Ajzen, I. (1975). Belief, Attitude, Intention, and Behavior: An Introduction to Theory and Research, Reading, MA: Addison-Wesley.
28. Guimaraes, T., Igbaria, M., and Lu, M. (1992). "The Determinants of DSS Success: an Integrated Model," Decision Sciences, Vol. 23, pp. 409- 429.
29. Hardgrave, B. (1997). "Adopting Object-Oriented Technology: Evolution or Revolution?" The Journal of Systems and Software, Vol. 37, pp. 19-25.
30. Hardgrave, B., and Dalai, N. (1995). "Comparing Object-Oriented and Extended-Entity-Relationship Data Models," Journal of Database Management, Vol. 6, No. 3, pp. 15-21.
31. Harrison, D., Mykytyn, P., and Riemenschneider, C. (1997). "Executive Decisions about the Adoption of Information Technology in Small Business: Theory and Empirical Tests," Information Systems Research, Vol. 8, No. 2, pp. 171-195.
32. Harrison, R., Samaraweera, L., Dobie, M., and Lewis, P. (1996). "Comparing Programming Paradigms: An Evaluation of Functional and Object-Oriented Programs," Software Engineering Journal, Vol. 11, No. 4, pp. 247-254.
33. Herbsleb, J., Klein, H., Olson, G., Brunner, H., Olson, J., and Harding, J. (1995). "Object-Oriented Analysis and Design in Software Project Teams," Human-Computer Interaction, Vol. 10, pp. 249-292.
34. Hollenbeck, J., and Klein, H. (1987). "Goal Commitment and the Goal-Setting Process: Problems, Prospects, and Proposals for Future Research," Journal of Applied Psychology, Vol. 72, pp. 204-211.
35. Horn, J.L. (1965). "A Rationale and Test for the Number of Factors in Factor Analysis," Psychometrika, Vol. 30, pp. 179-186.
36. Igbaria, M., Guimaraes, T., and Davis, G.B. (1995). "Testing the Determinants of Microcomputer Usage via a Structural Equation Model," Journal of Management Information Systems, Vol. 11, No. 4, pp. 87-114.
37. Jacobson, I., Christerson, M., Jonsson, P., and Overgaard, G. (1995). Object-Oriented Software Engineering: A Use Case Driven Approach, 2nd ed. Reading, MA: Addison-Wesley.
38. Kanfer, R. (1990). "Motivation Theory and Industrial and Organizational Psychology," in M. Dunnette and L. Hough (Eds.), Handbook of Industrial and Organizational Psychology, (2nd ed.), Palo Alto, CA: Consulting Psychologists Press. Vol. 1, pp. 75-170.
39. Korson, T. and McGregor, J. (1990). "Understanding Object-Oriented: A Unifying Paradigm," Communications of the ACM, Vol. 33, No. 9, pp. 40-60.
40. Lewis, J., Henry, S., Kafura, D., and Schulman, R. (1992). "On the Relationship Between the Object-Oriented Paradigm and Software Reuse: An Empirical Investigation," Journal of Object-Oriented Programming, Vol. 5, No. 4, pp. 35-42.
41. Meyer, B. (1995). Object Success, London, England: Prentice-Hall.
42. Nunnally, J.C. and Bernstein, I.H. (1994). Psychometric Theory, New York: McGraw-Hill.
43. Pancake, C.M. (1995). "The Promise and the Cost of Object Technology: A Five-Year Forecast," Communications of the ACM, Vol. 38, No. 10, pp. 33-49.
44. Pedhazur, E.J., and Schmelkin, L.R (1991). Measurement, Design, and Analysis: An Integrated Approach, Hillsdale, N J: Lawrence Erlbaum Associates.
45. Pennington, N., Lee, A.Y., and Rehder, B. (1995). "Cognitive Activities and Levels of Abstraction in Procedural and Object-Oriented Design," Human-Computer Interaction, Vol. 10, pp. 171- 226.
46. Premkumar, G., and Potter, M. (1995). "Adoption of Computer Aided Software Engineering (CASE) Technology: An Innovation Adoption Perspective," The DATABASE for Advances in Information Systems, Vol. 26, No. 2 & 3, pp. 105-123.
47. Prescott, M.B., and Conger, S.A. (1995). "Information Technology Innovations: a Classification by IT Locus of Impact and Research Approach," The DATABASE for Advances in Information Systems, Vol. 26, No. 2&3, pp. 20-41.
48. Rogers, E.M. (1995). Diffusion of Innovations, 4th Ed. New York: The Free Press.
49. Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., and Lorensen, W. (1991). Object-Oriented Modeling and Design, Englewood Cliffs, NJ: Prentice Hall.
50. Sharma, S. (1996). Applied Multivariate Techniques, New York: Wiley & Sons.
51. Shlaer, S., and Mellor, S. (1992). Object Lifecycles: Modeling the World in States, Englewood Cliffs, NJ: Prentice-Hall.
52. Sheetz, S.D., Irwin, G., Tegarden, D.P., Nelson, H.J., and Monarchi, D.E. (1997). "Exploring the Difficulties of Learning Object-Oriented Techniques," Journal of Management Information Systems, Vol. 14, No. 2, pp. 103-131.
53. Smith, H.A., and McKeen, J.D. (1996). "Object-Oriented Technology: Getting Beyond the Hype," The DATABASE for Advances in Information Systems, Vol. 27, No. 2, pp. 20-29.
54. Taylor, D.A. (1992). Object-Oriented Information Systems: Planning and Implementation, New York: John Wiley & Sons.
55. Taylor, S., and Todd, P.A. (1995). "Understanding Information Technology Usage: A Test of Competing Models," Information Systems Research, Vol. 6, No. 2, pp. 144-176).
56. Vessey, I., and Conger, S. (1994). "Requirements Specification: Learning Object, Process, and Data Methodologies," Communications of the ACM, Vol. 37, No. 5, pp. 102-113.
57. Wang, S. (1996). "Toward Formalized Object-Oriented Management Information System Analysis," Journal of Management Information Systems, Vol. 12, No. 4, pp. 117-141.
58. Webster, B.F (1995). Pitfalls of Object-Oriented Development, New York: M&T Books.
59. Wirfs-Brock, R., and Johnson, R. (1990). "Surveying Current Research in Object-Oriented Design," Communications of the ACM, Vol. 33, No. 9, pp. 105-124.

Index Terms

• Information systems

  • Data management systems

    • Database management system engines

• Social and professional topics

  • Professional topics

    • Management of computing and information systems

      • Project and people management

        • Systems development

      • Software management

• Software and its engineering

  • Software creation and management

  • Software notations and tools

    • General programming languages

      • Language types

        • Object oriented languages