Toward a Maturity Model for Knowledge Management Systems Integration

  • David G. Schwartz
  • Doron Tauber
Part of the Annals of Information Systems book series (AOIS, volume 4)


We present a maturity model that reveals the levels an organization traverses in the move from independent and distinct to integrated analysis and development of information systems and knowledge management systems. The Knowledge Management Systems Integration Maturity Model emerged from a 5-year action research project in the Israeli Navy documenting the development of 15 systems as the organization went through the different stages of maturity. Comparison is made with other maturity models related to knowledge management and software development. Implications for monitoring and evolving the systems development group of a large organization are discussed.


Knowledge Management Maturity Stage Maturity Model Management Information System Organizational Procedure 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. Alavi, M., and D.E. Leidner. 2001. Knowledge management and knowledge management systems: Conceptual foundations and research issues. MIS Quarterly 25(1): 107–136.CrossRefGoogle Scholar
  2. Aneerav, S., B. Andries, M.E. Mariki, and A.V. John. 2007. An evolutionary software project management maturity model for Mauritius. Interdisciplinary Journal of Information, Knowledge, and Management 2: 100–118.Google Scholar
  3. Avison, D.E., F. Lau, M. Myers, and P.A. Nielsen. 1999. Action research. Communications of the ACM 42(1): 94–97.CrossRefGoogle Scholar
  4. Avison, D.E., R. Baskerville, and M. Myers. 2001. Controlling action research projects. Information technology & people 14(1): 28–45.CrossRefGoogle Scholar
  5. Baskerville, R.L., and A.T. Wood-Harper. 1996. A critical perspective on action research as a method for information systems research. Journal of Information Technology 11: 235–246.CrossRefGoogle Scholar
  6. Bate, R., D. Kuhn, C. Wells, J. Armitage, G. Clark, K. Cusick, Garcia, et al. 1995. A systems engineering capability maturity model, SECMM-95-01 CMU/SEI-95-MM-003. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.Google Scholar
  7. Bell Canada. 1994. Trillium model – For telecom product development and support process capability. Model Issue 3.0, Bell Canada.Google Scholar
  8. Benbasat, I., D.K. Goldstein, and M. Mead. 1987. The case research strategy in studies of information systems. MIS Quarterly 11(3): 369–386.CrossRefGoogle Scholar
  9. Berztiss, A.T. 2002. Capability maturity for knowledge management, 162–166., Proceedings of the 13th international workshop on database and expert systems applications Washington, DC: IEEE Computer Society.Google Scholar
  10. Berztiss, A.T. 2006. Capability maturity. In Encyclopedia of knowledge management, ed. D.G. Schwartz, 24–29. Hershey, PA: Idea Group Publishing.Google Scholar
  11. Booch, G. 1994. Object-oriented analysis and design with applications, 2nd ed. Reading, MA: Addison Wesley.Google Scholar
  12. Ciborra, C. 2002. The labyrinth of information: Challenging the wisdom of systems. Oxford: Oxford University Press.Google Scholar
  13. CMMI for Development, Version 1.2. Technical report CMU/SEI-2006-TR-008, Carnegie Mellon Software Engineering Institute, August 2006.Google Scholar
  14. Cooper, J., and M. Fisher. 2002. Software acquisition capability maturity model, technical report CMU/SEI-2002-TR-010. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.Google Scholar
  15. Cooper, J., M. Fisher, and S.W. Sherer. 1999. Software acquisition capability maturity model, technical report CMU/SEI-99-TR-002. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.Google Scholar
  16. Crawford, J.K. 2006. The project management maturity model. Information Systems Management 23(4): 50–58.CrossRefGoogle Scholar
  17. Curtis, B., W.E. Hefley, and S.A. Miller. 2001. People capability maturity model. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.Google Scholar
  18. Davenport, T.H., and J. Glaser. 2002. Just-in-time delivery comes to knowledge management. Harvard Business Review 7(80): 107–111.Google Scholar
  19. Demarco, T. 1978. Structured analysis and systems specification. Englewood Cliffs, NJ: Prentice-Hall.Google Scholar
  20. Dick, B. 1993. You want to do an action research thesis?. Australia: Southern Cross University. Retrieved 5 April 2008, from Scholar
  21. Ferguson, J., J. Cooper, M. Falat, M. Fisher, A. Guido, J. Marciniak, J. Matejceck, and R. Webster. 1996. Software acquisition capability maturity model, technical report CMU/SEI-96-TR-020. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.Google Scholar
  22. Ferrucci, D., and A. Lally. 2004. Building an example application with the unstructured information management architecture. IBM Systems Journal 43(3): 455–475. Retrieved 10 April 2008, from Scholar
  23. Freeze, R., and U. Kulkarni. 2005. Knowledge management capability assessment: Validating a knowledge assets measurement instrument. Proceedings of the 38th annual Hawaii international conference on system sciences, p. 251a.Google Scholar
  24. Gane, C., and T. Sarson. 1979. Structured systems analysis – Tools and techniques. Englewood Cliffs, NJ: Prentice-Hall.Google Scholar
  25. Gottschalk, P., and H. Solli-Saether. 2006. Maturity model for IT outsourcing relationships. Industrial Management & Data Systems 106(2): 200–212.CrossRefGoogle Scholar
  26. Gray, P.M.D., A. Preece, N.J. Fiddian, W.A. Gray, T. Bench-Capon, M. Shave, et al. 1997. KRAFT: Knowledge fusion from distributed databases and knowledge bases, 682–691., Proceedings of 8th international workshop on database and expert systems applications New York: IEEE.Google Scholar
  27. Hahn, J., and M.R. Subramani. 2000. A framework of knowledge management systems: issues and challenges for theory and practice. In Proceedings of the 21st International Conference on Information Systems (ICIS 2000), ed. W.J. Orlikowski, S. Ang, P. Weill, H.C. Krcmar, and J.I. DeGrosss, 302–312. Atlanta, GA: Association for Information Systems.Google Scholar
  28. Harigopal, U., and A. Satyadas. 2001. Cognizant enterprise maturity model (CEMM). IEEE Transactions on Systems, Man, and Cybernetics – Part C: Applications and Reviews 31(4): 449–459.CrossRefGoogle Scholar
  29. Herndon, M.A., R. Moore, and M. Phillips. 2003. Interpreting capability maturity model integration for service organizations, technical note CMU/SEI-2003-TN-005. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.Google Scholar
  30. ISO. 2002. Information technology – Systems security engineering-capability maturity model (SSE-CMM®), ISO/IEC 21827, 2002.Google Scholar
  31. ISSEA. 2003. Systems security engineering capability maturity model SSE-CMM, June 2003.Google Scholar
  32. Jackman, M., and C. Pavelin. 1989. Conceptual graphs. In Approaches to knowledge representation, ed. G.A. Ringland, and D.A. Duce. New York: Wiley.Google Scholar
  33. Jacobson, I., G. Booch, and J. Rumbaugh. 1999. The unified software development process, 2nd ed. Reading, MA: Addison Wesley.Google Scholar
  34. Kendall, K.E., and J.E. Kendall. 2001. Systems analysis and design, 5th ed. Englewood Cliffs, NJ: Prentice-Hall.Google Scholar
  35. King, W.R., and T.S.H. Teo. 1997. Integration between business planning and information systems planning: Validating a stage hypothesis. Decision Sciences 20(2): 279–308.CrossRefGoogle Scholar
  36. Kock, N. 2003. Action research: Lessons learned from a multi-iteration study of computer-mediated communication in groups. IEEE Transactions on Professional Communication 46(2): 105–128.CrossRefGoogle Scholar
  37. Kulkarni, U., and R. Freeze. 2006. Measuring knowledge management capabilities. In Encyclopedia of knowledge management, ed. D.G. Schwartz, 605–613. Hershey, PA: Idea Group Publishing.Google Scholar
  38. Lavoie, D., and S.A. Culbert. 1978. Stages in organization and development. Human Relations 31(5): 417–438.CrossRefGoogle Scholar
  39. Liebowitz, J., and T. Beckman. 2008. Moving toward a knowledge management maturity model (K3M) for developing knowledge management strategy and implementation plans. In Knowledge management: An evolutionary view, ed. I. Becerra-Fernandez, and D. Leidner, 163–179. Armonk, NY: M.E. Sharpe.Google Scholar
  40. Lindvall, M., L. Rus, and S.S. Sinha. 2003. Software systems support for knowledge management. Journal of Knowledge Management 5(5): 137–150.CrossRefGoogle Scholar
  41. Malhotra, Y. 2002. Why knowledge management systems fail? Enablers and constraints of knowledge management in human enterprises. In Handbook of knowledge management, ed. C.W. Holsapple, 577–599. Heidelberg: Springer.Google Scholar
  42. Muller, M.J., M.E. Raven, S. Kogan, D.R. Millen, and K. Carey. 2003. Introducing chat into business organizations: Toward an instant messaging maturity model, 50–57., Proceedings of the 2003 international ACM SIGGROUP conference on supporting group work Sanibel Island, FL: ACM.Google Scholar
  43. Mumford, E. 2001. Advise for an action researcher. Information Technology & People 14(1): 12–27.CrossRefGoogle Scholar
  44. Niazi, M., D. Wilson, and D. Zowghi. 2005. A maturity model for the implementation of software process improvement: An empirical study. Journal of Systems and Software 74(2): 155–172.CrossRefGoogle Scholar
  45. Niessink, F., V. Clerc, T. Tijdinkm, and H. van Vliet. 2002. The IT service capability maturity model, CMM Release L2+3–0.3. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.Google Scholar
  46. Norman, R.J. 1996. Object oriented systems analysis and design. Upper Saddle River, NJ: Prentice-Hall.Google Scholar
  47. Paulk, M.C., Chrissis M.B., Weber, C.V., 1993. Capability maturity model for software, Version 1.1, Software Engineering Institute, CMU/SEI-93-TR-24.Google Scholar
  48. Paulk, M.C., C.V. Weber, B. Curtis, and M.B. Chrissis. 1995. The capability maturity model: Guidelines for improving the software process. Boston, MA: Addison Wesley.Google Scholar
  49. Plass, J.L., and L.W. Salisbury. 2002. A living-systems design model for Web-based knowledge management systems. Educational Technology Research and Development 1(50): 35–58.CrossRefGoogle Scholar
  50. Pressman, R.S. 2000. Software engineering: A practitioner’s approach, 5th ed. Boston, MA: McGraw-Hill.Google Scholar
  51. Susman, G.I., and R.D. Evered. 1978. An assessment of the scientific merits of action research. Administrative Science Quarterly 23(4): 582–603.CrossRefGoogle Scholar
  52. Tauber, D., and D.G. Schwartz. 2006. Integrating knowledge management with the systems analysis process. In Encyclopedia of knowledge management, ed. D.G. Schwartz, 259–266. Hershey, PA: Idea Group Publishing.Google Scholar
  53. Vail, E.F. 1999. Knowledge mapping: Getting started with knowledge management. Information Systems Management 16(1): 16–23.Google Scholar
  54. Whitten, J.L., L.D. Bentley, and K.C. Dittman. 2001. System analysis and design methods. Boston, MA: McGraw-Hill.Google Scholar
  55. Yin, R. 1994. Case study research: Design and methods, 2nd ed. Beverly Hills, CA: Sage.Google Scholar
  56. Yourdon, E. 1989. Modern structured analysis. Englewood Cliffs, NJ: Prentice-Hall.Google Scholar

Copyright information

© Springer Science+Business Media, LLC 2009

Authors and Affiliations

  1. 1.Graduate School of Business Administration, Bar-Ilan UniversityRamat GanIsrael

Personalised recommendations