Abstract

ERP Implementations follow the traditional model (derived from waterfall model). The traditional model is inflicted with many issues. These issues usually rotate around requirement gathering and defects found in later stage. Most of the literature available is a researcher’s experience as an observer or the beliefs. The main objective is to understand the pain of industry practitioners working in ERP Implementations and comparing the same with literature available. The aim of the study is to validate the literature and highlight the issues still not captured. In this paper a study has been presented to understand the actual issues straight from the Industry practitioners’ experiences. The literature and findings of the studies were compared to validate the problems in traditional model using empirical research. The interviews and analysis suggest the need of a new framework that includes feedback mechanism, continuous integration with delivery and looking the total value chain instead of small phases.

Keyword

ERP implementation issues, ERP implementation model, Waterfall model issues, Industry view.

Cite this article

Refference

[1][1]Royce WW. Managing the development of large software systems. In proceedings of IEEE WESCON 1970 (pp. 1-9).

[2][2]Thomas M. It projects sink or swim. British computer society review. 2001.

[3][3]Singh D, Thakur A, Chaudhary A. A comparative study between waterfall and incremental software development life cycle model. International Journal of Emerging Trends in Science and Technology. 2015; 2(4):2204-8.

[4][4]Raccoon LB. Fifty years of progress in software engineering. ACM SIGSOFT Software Engineering Notes. 1997; 22(1):88-104.

[5][5]Sommerville I. Software Engineering. Pearson Education Ltd; 2011.

[6][6]Cohen D, Larson G, Ware B. Improving software investments through requirements validation. In annual NASA Goddard software engineering workshop 2001 (pp. 106-14).

[7][7]McBreen P. Software craftsmanship: the new imperative. Addison-Wesley Professional; 2002.

[8][8]Pfleeger SL, Atlee JM. Software engineering: theory and practice. Pearson Education India; 1998.

[9][9]Jones C. Patterns of software system failure and success. ITP New Media; 1996.

[10][10]Tipaldi M, Götz C, Ferraguto M, Troiano L, Bruenjes B. The robust software feedback model: an effective waterfall model tailoring for space SW. In DASIA-data systems in aerospace conference 2013.

[11][11]Madgunda S, Suman U, Praneeth GS, Kasera R. Steps in requirement stage of waterfall model. International Journal of Computer & Mathematical Sciences. 2015:86-7.

[12][12]Yin RK. Case study research: design and methods. Sage Publication; 2013.

[13][13]Johnson J. Keynote speech: build only the features you need. In proceedings of the international conference on extreme programming and agile processes in software engineering 2002 (pp. 73-82).

[14][14]Chandra V. Comparison between various software development methodologies. International Journal of Computer Applications. 2015; 131(9):7-10.

[15][15]Anderson DJ. Agile management for software engineering: Applying the theory of constraints for business results. Prentice Hall Professional; 2003.

[16][16]Boehm B. Get ready for agile methods, with care. Computer. 2002; 35(1):64-9.