A case study of exploiting enterprise resource planning requirements

Enterprise Information Systems

Volumn 5, Issue 2, 2011, Pages 183-206

  Niu, Nan ^a   Jin, Mingzhou ^a   Cheng, Jing Ru C ^b  

^a MISSISSIPPI STATE UNIVERSITY   (United States)

^b US ARMY ENGINEER RESEARCH AND DEVELOPMENT CENTER   (United States)

Author keywords

Application implementation method; Enterprise resource planning; Exploratory case study; Oracle; Requirements engineering

Indexed keywords

BUSINESS APPLICATIONS; DATA VISIBILITY; ECONOMIC DEVELOPMENT; EMPIRICAL EVALUATIONS; ENTERPRISE RESOURCES; EXPLORATORY CASE STUDY; IMPLEMENTATION METHODS; INTEGRATED SOLUTIONS; ORACLE; PILOT PROJECTS; PROJECT MANAGEMENT EXPERIENCE; SERVICE COMPANIES; TEAM COLLABORATION;

MANUFACTURE; PROJECT MANAGEMENT; REQUIREMENTS ENGINEERING; RESEARCH; RESOURCE ALLOCATION;

ENTERPRISE RESOURCE PLANNING;

EID: 79960030961     PISSN: 17517575     EISSN: 17517583     Source Type: Journal    
DOI: 10.1080/17517575.2010.519052     Document Type: Article

References (54)

1. Andersson, A. and Linderoth, H.C.J., 2008. Learn not to learn-a way of keeping budgets and deadlines in ERP projects? Enterprise Information Systems, 2 (1), 77-95.
2. Basili, V.R. and Boehm, B., 2001. COTS-based systems top 10 list. IEEE Software, 34 (5), 91-95.
3. Choi, J., Ashokkumar, S., and Sircar, S., 2007. An approach to estimating work effort for enterprise systems software projects. Enterprise Information Systems, 1 (1), 68-87.
4. Ciborra, C., 2000. From control to drift: the dynamics of corporate information infrastructures. Oxford: Oxford University Press.
5. Daneva, M., 2002. Using maturity assessments to understand the ERP requirements engineering process. In: Proceedings of International Requirements Engineering Conference (RE'02). Washington, DC: IEEE Computer Society, 255-262.
6. Daneva, M., 2004. ERP requirements engineering practice: lessons learned. IEEE Software, 21 (2), 26-33.
7. Daneva, M. and Wieringa, R.J., A requirements engineering framework for crossorganizational ERP systems. 2006. Requirements Engineering, 11 (3), 194-204.
8. Davenport, T.H., 1998. Putting the enterprise into the enterprise system. Harvard Business Review, 76 (4), 121-131.
9. Davenport, T.H., 2000. Mission critical: realizing the promise of enterprise systems. Boston, MA: HBS Press.
10. Easterbrook, S., et al., 2007. Selecting empirical methods for software engineering research. In: Shull, F., Singer, J., and Sjøberg, D.I.K., eds. Guide to advanced empirical software engineering. London: Springer, 285-311.
11. Feblowitz, M., et al., 1996. ACME/PRIME: requirements acquisition for process-driven systems. In: Proceedings of International Workshop on Software Specification and Design (IWSSD'96), Washington, DC: IEEE Computer Society, 36-45.
12. Finkelstein, A., Spanoudakis, G., and Ryan, M., 1996. Software package requirements and procurement. In: Proceedings of International Workshop on Software Specification and Design (IWSSD'96). Washington, DC: IEEE Computer Society, 141-145.
13. Frakes, W.B. and Kang, K., 2005. Software reuse research: status and future. IEEE Transactions on Software Engineering, 31 (7), 529-536.
14. Graml, T., Bracht, R., and Spies, M., 2008. Patterns of business rules to enable agile business processes. Enterprise Information Systems, 2 (4), 385-402.
15. Holland, C. and Light, B., 1999. Success factors model for ERP implementation. IEEE Software, 16 (3), 30-36.
16. Izza, S., 2009. Integration of industrial information systems: from syntactic to semantic integration approaches. Enterprise Information Systems, 3 (1), 1-57.
17. Johansson, B. and Newman, M., 2010. Competitive advantage in the ERP system's value-chain and its influence on future development. Enterprise Information Systems, 4 (1), 79-93.
18. Klaus, H., Rosemann, M., and Gable, G.G., 2000. What is ERP? Information Systems Frontiers, 2 (2), 141-162.
19. Kumar, K. and van Hillegersberg, J., 2000. ERP experiences and evolution. Communications of the ACM, 43 (4), 22-26.
20. Lapouchnian, A., Yu, Y., and Mylopoulos, J., 2007. Requirements-driven design and configuration management of business processes. In: Proceedings of International Conference on Business Process Management (BPM'07). Berlin, Heidelberg: Springer-Verlag, 246-261.
21. Lauesen, S. and Mathiassen, M., 1999. Use cases in a COTS tender. In: Proceedings of International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'09). Berlin, Heidelberg: Springer-Verlag, 115-130.
22. Lethbridge, T.C., Sim, S.E., and Singer, J., 2005. Studying software engineers: data collection techniques for software field studies. Empirical Software Engineering, 10 (3), 311-341.
23. Li, L., et al., 2008. Assessing the effects of manufacturing infrastructure preparation prior to enterprise information systems implementation. International Journal of Production Research, 46 (6), 1645-1665.
24. Liang, H., et al., 2004. Why Western vendors don't dominate China's ERP market. Communications of the ACM, 47 (7), 69-72.
25. Maiden, N. and Ncube, C., 1998. Acquiring COTS software selection requirements. IEEE Software, 15 (2), 46-56.
26. Markus, M.L., Tanis, C., and van Fenema, P.C., 2000. Multisite ERP implementations. Communications of the ACM, 43 (4), 42-46.
27. Martinsons, M.G., 2004. ERP in China: one package, two profiles. Communications of the ACM, 47 (7), 65-68.
28. Moon, Y.B., 2007. Enterprise resource planning (ERP): a review of the literature. International Journal of Management and Enterprise Development, 4 (3), 235-264.
29. Ncube, C. and Maiden, N., 1999. Guiding parallel requirements acquisition and COTS software selection. In: Proceedings of International Symposium on Requirements Engineering (RE'99). Washington, DC: IEEE Computer Society, 133-140.
30. Niu, N. and Easterbrook, S., 2008. Exploiting COTS-based RE methods: an experience report. In: Proceedings of International Conference on Software Reuse (ICSR'08). Berlin, Heidelberg: Springer-Verlag, 212-216.
31. Nuseibeh, B. and Easterbrook, S., 2000. Requirements engineering: a roadmap. In: Proceedings of the Conference on the Future of Software Engineering, New York, NY: ACM, 35-46.
32. Oracle, AIM, 1999. Oracle application implementation method (release 3.0.0). CA, USA: Oracle Corporation.
33. Parr, A.N. and Shanks, G., 2000. A taxonomy of ERP implementation approaches. In: Proceedings of Hawaii International Conference on System Sciences (HICSS'00). Washington, DC: IEEE Computer Society, 7018.
34. Peterson, W.J., Gelman, L., and Cooke, D.P., 2001. ERP trends. The Conference Board Report, R-1292-01-RR. New York, NY: The Conference Board.
35. Potts, C., 1995. Invented requirements and imagined customers: requirements engineering for off-the-shelf software. In: Proceedings of International Symposium on Requirements Engineering (RE'95). Washington, DC: IEEE Computer Society, 128-130.
36. Rajagopal, P., 2002. An innovation-diffusion view of implementation of enterprise resource planning systems and development of a research model. Information and Management, 40 (2), 87-114.
37. Richards, L., 2005. Handling qualitative data: a practical guide. London: Sage Publications.
38. Rolland, C. and Prakash, N., 2001. Matching ERP system functionality to customer requirements. In: Proceedings of International Symposium on Requirements Engineering (RE'01). Washington, DC: IEEE Computer Society, 66-75.
39. Scheer, A.-W. and Habermann, F., 2000. Making ERP a success. Communications of the ACM, 47 (4), 57-61.
40. Scott, J.E. and Kaindl, L., 2000. Enhancing functionality in an enterprise software package. Information and Management, 37 (3), 111-122.
41. Soh, C., Kien, S.S., and Tay-Yap, J., 2000. Cultural fits and misfits: is ERP a universal solution? Communications of the ACM, 43 (4), 47-51.
42. Soh, C., et al., 2003. Misalignments in ERP implementation: a dialectic perspective. International Journal of Human-Computer Interaction, 16 (1), 81-100.
43. Srivardhana, T. and Pawlowski, S.D., 2007. ERP systems as an enabler of sustained business process innovation: a knowledge-based view. Journal of Strategic Information Systems, 16 (1), 51-69.
44. Sumner, M.R., 2009. How alignment strategies influence ERP project success. Enterprise Information Systems, 3 (4), 425-448.
45. Teltumbde, A., 2000. A framework for evaluating ERP projects. International Journal of Production Research, 38 (17), 4507-4520.
46. Tukey, J., 1977. Exploratory data analysis. Reading, MA: Addison-Wesley.
47. van Everdingen, Y., van Hillegersberg, J., and Waarts, E., 2000. ERP adoption by European midsize companies. Communications of the ACM, 43 (4), 27-31.
48. Vipola, I.H., 2008. A method for improving ERP implementation success by the principles and process of user-centred design. Enterprise Information Systems, 2 (1), 47-76.
49. Wang, J.W., Gao, F., and Ip, W.H., 2010. Measurement of resilience and its application to enterprise information systems. Enterprise Information Systems, 4 (2), 215-223.
50. Wu, S.L., Xu, L., and He, W., 2009. Industry-oriented enterprise resource planning. Enterprise Information Systems, 3 (4), 409-424.
51. Xu, L., 2007. Enterprise information systems. Enterprise Information Systems, 1 (1), 1-2.
52. Xu, X., 2008. Effects of two national environment factors on e-commerce functionality adoption: a cross-country case study of a global bank. Enterprise Information Systems, 2 (3), 325-339.
53. Yin, R.K., 2003. Case study research: design and methods. 3rd ed. CA, USA: Sage Publications.
54. Zhang, W.J. and Lin, Y., 2010. On the principle of design of resilient systems-application to enterprise information systems. Enterprise Information Systems, 4 (2), 99-110.