Document Type : Articles


Professor, Department of IT & Systems Institute of Rural Management Anand, India


Information Systems (IS) acquisition prescribes induction of information technologies (IT) in the organization. At times, IS is used for managing broader enterprise level issues like implementing e-business, e-commerce. Enterprise level issues are addressed through adequate involvement of people in the organization which are termed as “user capabilities”. Managing user capabilities is critical since their roles are very important in the entire Systems Development Life Cycle (SDLC). It is seen that failures in IT acquisition are not because of the technology, but failure in choosing it rightly, and poor user capabilities. If planned properly, user capabilities can contribute effectively to SDLC. SDLC works in stages with different sets of users and insensitivities to users contribute to the gap between satisfying organizational needs and end-user deliveries. This problem can be addressed by carefully integrating user capability issues in the SDLC process. In this paper a framework is suggested to capture user capabilities in an IT acquiring organization. User capabilities are identified in two categories: IT users who are IT experts and involved in design, development, and implementation of SDLC driven projects, and, second, non-IT users who, despite having inadequate or no exposure to IT, contribute to SDLC driven projects. The framework is implemented through Unified Modelling Language (UML) based approach. A case discusses the utility of this approach.DOR: 98.1000/1726-8125.2017.

  1. Abrahamson, P. & Jokela, T. (2001). “Implementing User-Centred Design in to a Software Development Organization: A Sub Cultural Analysis,” 24th Information Systems Research Seminar, Norway, August.
  2. Basili, Victor R., Caldiera, G. & Rombach, HD. (1994). “Goal Question Metrics Paradigm,” Encyclopedia of Software Engineering, Singapore: John Wiley.
  3. Basili, Victor R. & Boehm, B. (2001). “COTS-Based Systems Top 10 List,” Software Management, May.
  4. Boehm, B. & Wilfred J. (2001). “The Spiral Model as a Tool for Evolutionary Acquisition,” Journal of Defense Software Engineering, May.
  5. Bowen, P., Heales, J., & Monthira V. (2002). “Reliability Factors in Business Software: Volatility, Requirements and End-users,” Information Systems Journal, 12: (3), July.
  6. Broadbent, M., Weill, P. & O’Brien, T. (1996). “Firm Context and Patterns of IT Infrastructure Capability,” in Proceedings of the 17th International Conference on Information Systems, Cleveland.
  7. Karuppan, C. & Karuppan, M. (2008). “Resilience of Super Users’ Mental Models of Enterprise-wide Systems,” European Journal of Information Systems, 17.
  8. Gordon, B. & Margarethe, H. (2000). Management Information Systems: Conceptual Foundations, Structure and Development (2nd edition). Singapore: McGraw-Hill.
  9. Flynn, J. (1998). Information Systems Requirements: Determination and Analysis (2nd edition). Berkshire: McGraw-Hill.
  10. Frank, K. (1998). “A Contingency Based Approach to Requirements Elicitation and Systems Development,” Journal of systems and software, ISSN 0164-1212, vol. 40 (1).
  11. Grady, B. (1992). Practical Software Metrics for Project Management and Process Improvement, New Jersey: Prentice-Hall.
  12. Herron, D. (2002) IT Measurement: Practical Advice from Experts, International Function Point User Group Part-I, (1st edition). Boston: Addison Wesley Professional.
  13. Jalote, P. (2002) CMM in Practice: Process for Executing Software Projects at Infosys. New Delhi: Pearson Education.
  14. Kumar, K. & Hillegersberg, J. (2000) “ERP Experiences and Evolution,” Communications of the ACM, 43 (3).
  15. Lamb, R., & Kling, R. (2003) “Re-conceptualising Users as Social Actors in Information Systems Research,” MIS Quarterly, 27 (2), June.
  16. Lee, C. (2001) “Modelling the Business Value of Information Technology,” Information and Management, 39 (3) December 20.
  17. Leffingwell, D. (2007) Scaling Software Agility: Best Practices for Large Enterprises. Boston: Addison Wesley.
  18. Lientz, B., & Chen, M. (1981) “Assessing Impact of New Technology in Information Systems,” Long Range Planning, 14 (6), December.
  19. Luftman, J. (2003) “Assessing IT and Business Alignment,” Information Systems Management, 20 (4).
  20. Lycett, M., Macredie, R., Patel, Ch., & Paul, J. (2003) “Migrating Agile Methods to Standardised Development Practice,” Computer Magazine, New York, 36 (6), June.
  21. Mead, N., Robert, E., Linger R., Lipson H. & McHugh, J. (2000) “Life-Cycle Models for Survivable Systems,” Proceedings of the Third Information Survivability, Workshop (ISW-2000), Boston, October 24-26.
  22. Mellor, S. & Balcer, M. (2002) Executable UML: A Foundation for Model-Driven Architecture. Boston: Addison Wesley.
  23. Misra, H. K. (2009), User Capabilities Dimensions in Information System Development Life Cycle: A UML Based Modeling, Working Paper 216, IRMA.
  24. Misra, H. (2008) “Users’ Computer Human Interface Capabilities in Information Systems Development Life Cycle: An Organizational Perspective,” IEEE Engineering Management Conference (IEMC), Lisbon, June 28-30.
  25. Misra, H. & Mohanty, B. (2003) “The IT-Acquisition Models and User’s Perspective: A Review,” Working Paper Series 173, Institute of Rural Management, Anand, January.
  26. Narayanan, VK. (2001) Managing Technology and Innovation. New Delhi: Pearson Education.
  27. Nuseibeh, B. & Easterbrook, S. (2000) “Requirements Engineering: A Roadmap,” in Proceedings of the International Conference on Software Engineering (ICSE), Limerick, Ireland, June 4-11.
  28. Pervan, G. (1998) “How the Chief Executive Officers in Large Organizations View the Management of their Information Systems,” Journal of Information Technology, 13.
  29. Piekarski, W. & Plimmer, B. (2007) “A Conceptual Framework for Explaining the Value of End User Maturity Levels for IT Management,” in Proceedings of the Eighth Australasian User Interface Conference (AUIC), Ballarat, Australia. January-February.
  30. Zhang, P. & Te’eni, D. (2005) “Integrating Human-Computer Interaction Development into the Systems Development Life Cycle: A Methodology,” Communications of the Association for Information Systems, 15.
  31. Rumbaugh, J., Jacobson I. & Booch, G. (1999) “The Unified Modelling Language Reference Manual”. Singapore: Addison Wesley Longman.
  32. Shaw, M. & David, G. (1996) Software Architecture: Perspectives on an Emerging Discipline. Upper Saddle River, NJ: Prentice Hall.
  33. Vijay, K. Keil M., Mathiassenl, L. & Pedersen, K. (2008) “The Post Mortem Paradox: A Delphi Study of IT Specialist Perceptions,” European Journal of Information Systems, 17.
  34. Wang, E. & Tai, J. (2003) “Factors Affecting Information Systems PlanningEffectiveness: Organizational Contexts and Planning Systems Dimensions,” Information and Management, 40 (4).
  35. Ward, J., Griffiths, P., & Whitmore, P. (1990) Strategic Planning for Information Systems. England: John Wiley & Sons Ltd.
  36. Watson, T., Leyland, P. & Kavan, B. (1998) “Measuring Information Systems Service Quality: Lessons from Two Longitudinal Case Studies,” MIS Quarterly, March.
  37. Wohlin, C., Ohlsson, M. Regnell, B. & Wesslen, A. (2000) Experimentation in Software Engineering: An Introduction. London: Kluwer Academic Publishers.