Requirements engineering method and maturity model for ERP projects

International Journal of Enterprise Information Systems

Volumn 4, Issue 4, 2008, Pages 1-14

  Parthasarathy, S ^a   Ramachandran, Muthu ^b  

^a THIAGARAJAR COLLEGE OF ENGINEERING   (India)

^b LEEDS METROPOLITAN UNIVERSITY   (United Kingdom)

Author keywords

Customization; ERP functionality; ERP maturity model (EMM); Information systems; Requirements engineering method; Validation; Verification

Indexed keywords

INFORMATION SYSTEMS; REQUIREMENTS ENGINEERING; VERIFICATION;

CUSTOMIZATION; ENTERPRISE RESOURCE PLANNING (ERP); ERP PROJECTS; KEY INDICATOR; KEY PROCESS; MATURITY MODEL; PROCESS DATABASE; VALIDATION;

ENTERPRISE RESOURCE PLANNING;

EID: 55949120171     PISSN: 15481115     EISSN: 15481123     Source Type: Journal    
DOI: 10.4018/jeis.2008100101     Document Type: Article

References (40)

1. Agrawal, M. & Chad, K. (2007). Software effort, quality and cycle time: A study of CMM Level 5 projects. IEEE Transaction on Software Engineering, 33(3), 145-156.
2. Agarwal, R. & Tanniru, M.R. (1990). Knowledge acquisition using structured interviewing: An empirical investigation. Journal of Management Information Systems, 7, 123-140.
3. Beatty, R.C. & Williams, C.D. (2006). ERP II: Best practices for successfully implementing an ERP upgrade. Communications of the ACM, 49(3).
4. Bingi, P., Sharma, M.K., & Godla, J.K. (1999). Critical success factors affecting an ERP implementation. Information Systems Management.
5. Brehm, L., Heinzi, A., & Markus, M. L. (2001). Tailoring ERP systems: A spectrum of choices and their implications. Proceedings of 34th Annual Hawaii International Conference on System Sciences.
6. Brehm, L. & Markus, M. L. (2000). The divided software life cycle of ERP packages. Paper presented at the 1st Global Information Technology Management World Conference, Memphis, TN.
7. Brown, C. & Vessey, I. (1999). ERP implementation approaches: toward a contingency framework. Proceedings of the International Conference on Information Systems, 411-416.
8. Carmel, E. & Sawyer, S. (1998). Packaged software development teams: What makes them different? Information Technology People, 11(1), 7-19.
9. Daneva, M. (2004). ERP requirements engineering practice: Lessons learned. IEEE Software, 26-33.
10. Daneva, M. & Wieringa, R.J. (2006). A requirements engineering framework for cross-organizational ERP systems. Requirements Engineering, 11, 194-204.
11. Davenport, T. H. (1998). Putting the enterprise into the enterprise system. Harvard Business Review, July-August, 121-131.
12. Deloitte & Touche (2002). Achieving, meauring and communicating IT value, An IDG Research Services Group report.
13. Fui-Hoom Nah, F. & Lee-Shang Lau, J. (2001). Critical factors for successful implementation of enterprise systems. Business Process Management Journal, 7(3), 285-296.
14. Glass, R. L. (1998). Enterprise resource planning-Breakthrough and/or term problems. Database for Advances Information System, 29(2), 14-16.
15. Grady, R. & Caswell, D. (1999). Software metrics: Establishing a company-wide program. Prentice Hall.
16. Hiquet, B. & Kelly, A. F. (1998). SAP R/3 implementation guide: A manager's guide to understanding SAP. India: Macmillan Technical.
17. Holland, C. P. & Light, B. (1999). A critical success factor model for ERP implementation. IEEE Software, May/June, 30-36.
18. Holland, C. P. & Light, B. (2001). A stage for maturity model for enterprise resource planning systems use. The DATA BASE for Advances in Information Systems - Spring 2001, 32(2).
19. Hong, K. & Kim, Y. (2002). The critical success factors for ERP implementation: An organizational fit perspective. Information Management, 40(1).
20. Humphrey, W. (1989). Managing the software process. Addison-Wesley.
21. Jalote, P. (1999). CMM in practice, Processes for executing project at Infosys. Addison-Wesley.
22. Jalote, P. (2002). Software project management in practice. Addison-Wesley.
23. Lynch, R. K., (1985). Nine pitfalls in implementing packaged applications software. Journal of Information System Management, 2(2) 88-92.
24. Maiden, N. (2006). Improve your requirements: Quantify them. IEEE Software, 2006, 68-69.
25. Marakas, G. & Elam, J. (1998). Semantic structuring in analyst acquisition and representation of facts in requirements analysis. Information Systems Research, 9, 37-63.
26. Markus, L., Axtine, S., Petrie, D., & Tanis, C. (2000). Learning from adopters' experience with ERP problems encountered and success achieved. Journal of Information Technology, 245-265.
27. Markus, M.L. & Tanis, C. (2000). The enterprise systems experience: From adoption to success. In R.W. Zmud (Ed.), Framing the domains of IT research: Glimpsing the future through the past, 173-207. Cincinnati, OH: Pinnaflex Educational Resources Inc.
28. Oslen, K.A. & Saetre, P. (2007). IT for niche companies: Is an ERP system the solution? Information Systems Journal, 17, 37-58.
29. Parr, A. & Shanks, G. (2000). A model of ERP project implementation. Journal of Information Technology, 289-303.
30. Pitts, M.G. & Browne, G.J. (2007). Improving requirements elicitation: An empirical investigation of procedural prompts. 17, 89-110.
31. Procaccino, J., Verner, J., Overmyer, S., & Darter, M. (2002). Case study: Factors for early prediction of software development success. Information and Software Technology, 44, 53-62.
32. Ross, J. (1998). The ERP revolution: Surviving versus thriving. MIT Sloan Working Paper, Center for Information Systems Research.
33. Sawyer, S. (2000). Packaged software: Implications of the differences from custom approaches to software development. European Journal of Information System, 9, 47-58.
34. Soh, C., Kein, S.S., & Tay, J. (2000). Cultural fits and misfits: Is ERP a universal solution? Communications of ACM, 43(4).
35. Strong, D.M. & Volkoff, O. (2004). A roadmap for enterprise system implementation. IEEE Computer Society.
36. Stensrud, E. & Myrtveit, I. (2003). Identifying high performance ERPprojects. IEEE Transactions on Software Engineering, 29(5).
37. Togur, D. M. & Bloomberg, E. Morgan Stanley (2003). CIO survey series: Release 4.5, Morgan Stanley Research Report, 2003.
38. Van Everdingen, Y., Hilsberg, J., & Waarts, E. (2002). ERP adoption by European midsize companies. Communications of ACM, 43(2).
39. Weinberg, G. (1971). The Psychology of computer programing. New York: van Nostrand Reinhold Co.
40. Willcocks, L.P. (2000). The role of the CIO and IT function in ERR. Communication of ACM.