商業套裝企業資源規劃(ERP)系統已經被許多大企業採用來支援企業內部與外部的商業流程，中型企業也逐漸採用企業資源規劃系統。然而，相關研究卻指出大約3/4的企業資源規劃系統專案並不成功，其普遍發生的問題是企業資源規劃系統功\能與企業需求的適配性問題。
本研究在任務科技適配度與認知適配理論的基礎上提出企業資源規劃系統的適配性分析方法論，在系統導入前衡量企業資源規劃系統的功能與企業需求的適配性，亦即企業資源規劃系統所提供的系統功\能是否滿足企業需求。本研究已經開發一套內建該方法論的系統雛型，並在該系統上進行可用性評估實驗，藉以驗證該方法論的可行性。透過這套方法，企業可以比較容易而且系統化的找出企業資源規劃系統不適配的部分，以及不適配的程度來降低系統導入的風險。本研究的貢獻在於企業資源規劃系統導入前，對適配性分析提出一套實際可行的方案。

Commercial off-the-shelf enterprise resource planning (ERP) systems have been adopted by large companies to support their inter- and intra-business processes. Midsize market firms are now investing in ERP systems too. However, research has indicated that about three quarters of attempted ERP projects turned out to be unsuccessful. A common problem encountered in adopting ERP software has been the issue of fit or alignment.
This paper presents an ERP misfit analysis methodology, grounded on the task-technology fit theory and cognitive fit theory, for measuring misfits between ERP candidates and enterprise’s requirements in ex-ante implementation. A decision support system prototype embedded the approach has been developed. A usability evaluation is performed on the prototype to demonstrate the approach. With this approach, organizations can more easily and systematically determine where the misfits are and the degree of misfits, thereby reducing the risks in implementing ERP systems. Our research contributes to the practical solution of the problem of misfit analysis.

Chapter 1. Introduction 1
1.1. Research Background and Motivation 1
1.2. Research Objectives 2
1.3. Research Methodology 3
1.4. Organization of the Dissertation 4
Chapter 2. Literature Review 5
2.1. Financial perspective 5
2.2. Interpretive perspective 6
2.3. Functional Perspective 7
2.3.1. Goal-based Matching Approach 8
2.3.2. Functional, Data and Output Misfits 11
2.3.3. Accelerated SAP 12
Chapter 3. Theoretical Background 16
3.1. ERP misfit analysis from the cognitive fit perspective 18
Chapter 4. ERP Misfit Analysis Model 23
4.1. Task of ERP misfit analysis 24
4.2. Requirement modeling 27
4.2.1. Goal-based use case 28
4.2.2. Activity diagram 29
4.2.3. Drawing and data glossary 30
4.3. Misfit analysis methodology 32
4.3.1. Goal Misfit Analysis 33
4.3.2. Functional Misfit Analysis 34
4.3.3. Data/Output Misfit Analysis 38
4.4. ERPAnalyser: A prototype implementation 42
Chapter 5. Usability Evaluation 44
5.1. Measurements development 45
5.2. Experiment design 46
Chapter 6. Results and Discussion 50
6.1. Effectiveness 50
6.2. Efficiency 56
6.3. Satisfaction 57
Chapter 7. Conclusion 59
References 62
Appendix A. Functional Misfit Evaluation Function 68
Appendix B. Participant profile 68
Appendix C. Questionnaire 69
Appendix D. Data/output misfit analysis results 70

1. Aalst, W. M. P. V. D., and Berens, P. J. S. “Beyond workflow management: product-driven case handling,” In Proceedings of the 2001 International ACM SIGGROUP Conference on Supporting Group Work, Boulder, Colorado, USA, 2001, pp. 42-51.
2. Aggarwal, R. “Justifying investments in flexible manufacturing technology: adding strategic analysis to capital budgeting uncertainty,” Managerial Finance (17:2/3), 1991, pp. 77–88.
3. Aggarwal, R., and Sinha, A. P. “Object-oriented modeling with UML: A study of developers’ perceptions,” Communications of the ACM (46:9), 2003, pp. 248-256.
4. Aggarwal, R., Sinha, A. P., and Tanniru, M. “Cognitive Fit in Requirements Modeling: A Study of Object and Process Methodologies,” J. Management Information Systems (13:2), 1996, pp. 137-162.
5. Bacon, C. J. “The Use of Decision Criteria in Selecting Information Systems/Technology Investments,” MIS Quarterly (16:3), 1992, pp. 335-353.
6. Ballantine, J., and Stray, S. “Financial appraisal and the IS/IT investment decision making process,” Journal of Information Technology (13:3), 1998, pp. 3-14.
7. Bettman, I. R., and Kakkar, P. “Effects of Information Presentation Format on Consumer Information Acquisition Strategies,” Journal of Consumer Research (3:4), 1977, pp. 233-240.
8. Blake, S. P. Managing for Responsive Research and Development, San Francisco, CA: Freeman, 1978.
9. Bosch, J., and Juristo, N. “Designing Software Architectures for Usability,” In Proceedings of the 25th International Conference on Software Engineering, Portland, Oregon, May 2003.
10. Coobineth, J., Mannino, M. V., and Tseng, V. P. “A Form-based Approach for Database Analysis and Design,” Communications of the ACM (35:2), February 1992, pp. 108-120.
11. Daneva, M. “Lessons Learnt from Five Years of Experience in ERP Requirements Engineering,” In Proceedings of the 11th IEEE International Requirements Engineering Conference, Monterey, CA, 2003, pp. 45-54.
12. Davis, G. B. “Strategies for information requirements determination,” IBM Systems Journal, (21:1), 1982, pp. 4-30.
13. Dishaw, M. T., and Strong, D. M. “Extending the Technology Acceptance Model with Task–technology Fit Constructs,” Information & Management (36:1), July 1999, pp. 9-21.
14. Eschinger, C. Forecast: ERP Software, Worldwide 2005-2009 Update (Executive Summary), Gartner, 24 October 2005.
15. Farbey, B., Land, F., and Targett, D. “Evaluating investments in IT,” Journal of information Technology, (7:2), 1992, pp. 109-122.
16. Fleisch, E., Oesterle, H., and Powell, S. “Rapid Implementation of Enterprise Resource Planning Systems,” Journal of Organizational Computing and Electronic Commerce (14:2), June 2004, pp. 107-126.
17. Floyd, S. W. “A Micro Level Model of Information Technology Use by Managers,” in Studies in Technological Innovation and Human Resources, Volume 1: Managing Technological Development, U.E. Gattiker (ed.), Walter de Gruyter, Berlin & New York, 1988, pp. 123-142.
18. Gentner, D., and Stevens, A. L. Mental Models, Hillsdale, NJ: Lawrence Erlbaum, 1983.
19. Goodhue, D. L. “IS Attitudes: Toward Theoretical and Definition Clarity,” DataBase (19:3/4), Fall/Winter 1988, pp. 6-15.
20. Goodhue, D. L., and Thompson, R. L. “Task-Technology Fit and Individual Performance,” MIS Quarterly (19:2), 1995, pp. 213-236.
21. Hernandez, J. A., Bueno, E. R., Servera, S. A., and Elechiguerra, J. R. S. SAP R/3 Implementation Guide, McGraw-Hill, New York, 1999, Chapter 3.
22. Hillam, C. E., and Edwards, H. M. “A Case study approach to evaluation of Information Technology/Information systems (IT/IS) investment evaluation processes within SMEs,” Electronic Journal of Information Systems Evaluation (4:1), 2001.
23. Hippel, E. V. “Sticky information and the locus of problem solving: Implications for innovation,” Management Science (40:4), 1994, pp. 429–439.
24. Hochstrasser, B. “Justifying IT investments,” In Proceedings of the Advanced Information Systems Conference, The New Technologies in Today’s Business Environment, 1992, pp. 17–28.
25. Holbrook, C. H. “A Scenario-based Methodology for Conducting Requirements Elicitation,” ACM SIGSOFT Software Engineering Notes (15:1), January 1990, pp. 95-104.
26. Holsapple, C. W., and Sena, M. P. “ERP plans and decision-support benefits,” Decision Support Systems (38:4), 2005, pp. 575–590.
27. Holsapple, C. W., and Sena, M. P. “The decision-support characteristics of ERP systems,” International Journal of Human–Computer Interaction (16:1), 2003, pp. 101-123.
28. Holsapple, C. W., and Whinston, A. B. Decision Support Systems: A Knowledge-based Approach, West Publishing Co. St. Paul, MN, 1996.
29. Holsapple, C. W., Wang, Y. M., and Wu, J. H. “Empirically testing user characteristics and fitness factors in enterprise resource planning success,” International Journal of Human-Computer Interaction (19:3), 2005, pp. 323-342.
30. Irani, Z. “Information systems evaluation: navigating through the problem domain,” Information & Management (40:1), 2002, pp. 11–24.
31. Irani, Z., Sharif, A., and Love, P. E. D. “Transforming failure into success through organisational learning: an analysis of a manufacturing information system,” European Journal of Information Systems (10:1), 2001, pp. 55–66.
32. Keen, P. G. W., and Morton, M. S. S. Decision Support Systems: An Organizational Perspective, Addison-Wesley, Massachusetts, 1978.
33. Kobryn, C. “UML 2001: a standardization odyssey,” Communications of the ACM, (42:10), October 1999, pp. 29-37.
34. Kunda, D., and Brooks, L. “Identifying and classifying processes (traditional and soft factors) that support COTS component,” European Journal of Information Systems (9:4), 2000, pp. 226-234.
35. Larkin, J. H., and Simon, H. A. “Why a diagram is (sometimes) worth ten thousand words,” Cognitive Science (11), 1987, pp. 65-99.
36. Lee, J., and Xue, N. L. “Analyzing user requirements by use cases: a goal-driven approach,” IEEE Software (16:4), 1999, pp. 92-101.
37. Maiden, N. A. M., Ncube, C., and Moore, A. “Lessons Learned during Requirements Acquisition for COTS Systems,” Communications of the ACM (40:12), December 1997, pp. 21-25.
38. Mandal, P., and Gunasekaran, A. “Issues in implementing ERP: a case study,” European Journal of Operational Research (146:2), 2003, pp. 274-283.
39. Markus, M. L., Tanis, C., and Fenema, P. C. V. “Enterprise Resource Planning: Multisite ERP implementations,” Communications of the ACM (43:4), 2000, pp. 42-46.
40. Newell, A., and Simon, H. A. Human problem solving, Englewood, Cliffs, NJ: Prentice-Hall, 1972.
41. Nielsen, J. How to Conduct a Heuristic Evaluation, 1994, [online], http://useit.com/papers/heuristic/heuris tic_evaluation.html.
42. Nijland, M. “IT cost benefit management improvement from a critical perspective,” Electronic Journal of Information Systems Evaluation (6:1), 2001.
43. Nunamaker, J. F., Chen, M., and Prudin, T. D. M. “Systems Development in Information Systems Research,” Journal of Management Information Systems (7:3), Winter 1990-1991, pp.89-106.
44. Palvia, S. C., and Chervany, N. L. “An Experimental Investigation of Factors Influencing Predicted Success in DSS Implementation,” Information and Management (29:1), July 1995, pp. 43-53.
45. Potts, C., Takahashi, K., and Anton, A. I. “Inquiry-based requirements analysis,” IEEE Software (11:2), 1994, pp. 21-32.
46. Rao, S. S. “Enterprise Resource Planning: Business Needs and Technologies,” Industrial Management & Data Systems (100:2), 2000, pp. 81-88.
47. Rolland, C., and Prakash, N. “Bridging the gap between organizational needs and ERP functionality,” Requirements Engineering (5:3), 2000, pp. 180-193.
48. Rolland, C., Souveyet, C., and Achour, C. B. “Guiding goal modeling using scenarios,” IEEE Transactions on Software Engineering (24:12), 1998, pp. 1055-1071.
49. Sánchez, D. M., Cavero, J. M., and Marcos, E. “On models and ontologies,” 1st International Workshop on Philosophical Foundations of Information Systems Engineering (PHISE'05), Porto, Portugal, 13 June 2005, pp. 1-11.
50. Schambach, T. P., and Walstrom, K. A. “Systems development practices: Circa 2001,” Journal of Computer Information Systems (43:2), 2002-2003, pp. 87-92.
51. Serafeimidis, V., and Smithson, S. “Information systems evaluation in practice: a case study of organizational change,” Journal of Information Technology (15:2), 2000, pp. 93-106.
52. Simkin, D., and Hastie, R. “An Information-Processing Analysis of Graph Perception,” Journal of the American Statistical Association (52:398), 1987, pp. 454-465.
53. Simon, H. A. The sciences of the artificial (3rd ed.), the MIT press, Cambridge, Massachusetts, 1996, pp. 208-210.
54. Simon, H. A., and Hayes, J. R. “The understanding process: Problem isomorphs,” Cognitive Psychology (8:2), 1976, 165-190.
55. Sinha, A. P., and Vessey, I. “Cognitive fit: an empirical study of recursion and iteration,” IEEE Transactions on Software Engineering (18:5), May 1992, pp. 368-379.
56. Soh, C., Kien, S. S., and Tay-yap, J. “Enterprise resource planning: cultural fits and misfits: is ERP a universal solution?” Communications of the ACM (43:4), 2000, pp. 47-51.
57. Soh, C., Sia, S. K., Boh, W. F., and Tang, M. “Misalignments in ERP Implementation: A Dialectic Perspective,” International Journal of Human-Computer Interaction (16:1), 2003, pp. 81-101.
58. Sommerville, I. “Integrated Requirements Engineering: A Tutorial,” IEEE Software (22:1), Jan-Feb 2005, pp. 16-23.
59. Stefanou, C. J. “A framework for the ex-ante evaluation of ERP software,” European Journal of Information Systems (10:4), 2001, pp. 204–215.
60. Tam, K. Y. “Capital budgeting in information systems development,” Information & Management (23:6), 1992, pp. 345-357.
61. Vessey, I. “Cognitive Fit: A Theory-Based Analysis of the Graphs Versus Tables Literature,” Decision Science (22:2), 1991, pp. 219-240.
62. Vessey, I. and Weber, R. “Structured tools and conditional logic: an empirical investigation,” Communications of the ACM (29:1), 1986, pp. 48-57.
63. Weaver, S. C., Peters, D., Cason, R., and Daleiden, J. “Panel Discussions on Corporate Investment: Capital Budgeting,” Financial Management (18:1), 1989, pp. 10-17.
64. Weidenhaupt, K., Pohl, K., Jarke, M., and Haumer, P. “Scenarios in System Development: Current Practice,” IEEE Software (15:2), 1998, pp. 34-45.
65. Wexelblat, A. Report on Scenario Technology, MCC Technical Report STP-139-87, Microelectronics and Computer Technology, Corporation, Austin, Texas, 1987.
66. Wu, J. H., and Wang, Y. M. “Measuring KMS success: A respecification of the DeLone and McLean's model,” Information & Management (43:6), 2006, pp. 728-739.
67. Wu, J. H., Hsia, T. C., Tsai, S. J., and Hsieh, C. T. “A Methodology for Modeling the User Interfaces: An integrated UML and PAC Model,” Journal of Internet Technology (6:4), 2005, pp. 403-412.
68. Yadav, S. B., Bravoco, R. R., Chatfield, A. T., and Rajkumar, T. M. “Comparison of analysis techniques for information requirement determination,” Communications of the ACM (31:9), 1988, pp. 1090-1097.