Björn Johansson
ABSTRACT
Identification and specification of business requirements are extremely important when development of Enterprise Resource Planning systems (ERPs) take place. It can be stated that this is still a problematic area not well researched and, as a result from that, it does not exist much guidance on how to deal with requirements. In this paper we discuss if existing problems of requirements management are the same or if they differ according to the type of development: closed source (proprietary) or open source ERP. The reason is that it is possible that these two approaches can promote each other in how to improve the first phase in ERP development. From the discussion about similarities and differences between the two approaches it is suggested further research in this area that could end up in some more practical guidelines on how to do the requirements definition so that the finally developed ERPs better support adopters' needs.
- Shehab, E. M., Sharp, M. W., Supramaniam, L., and Spedding, T. A., Enterprise resource planning: An integrative review. Business Process Management Journal, 10, 4 (2004), 359--386.Google Scholar
Cross Ref
- Esteves, J. and Pastor, J., Enterprise Resource Planning Systems Research: An Annotated Bibliography. Communications of AIS, 7, 8 (2001), 1--51.Google Scholar
- Botta-Genoulaz, V., Millet, P. A., and Grabot, B., A survey on the recent research literature on ERP systems. Computers in Industry, 56, 6 (2005), 510--522. Google ScholarDigital Library
- Soh, C., Kien, S. S., and Tay-Yap, J., Cultural fits and misfits: Is ERP a universal solution? Communications of the ACM, 43, 4 (2000), 47--51. Google ScholarDigital Library
- Askenäs, L. and Westelius, A. Five roles of an information system: a social constructionist approach to analyzing the use of ERP systems. in twenty first international conference on Information systems. 2000. Brisbane, Queensland, Australia: Association for Information Systems. Google ScholarDigital Library
- Sleeper, S. Z. AMR analysts discuss role-based ERP interfaces - the user-friendly enterprise. 2004 {cited 12-04-2007}; Available from: http://www.sapdesignguild.org/editions/edition8/print_amr.asp.Google Scholar
- Jackson, M., Software requirements & Specifications: a lexicon of practice, principles and prejudices. 1995, London: ACM Press. Google ScholarDigital Library
- Jackson, M., The meaning of requirements. Annals of Software Engineering, 3, 1 (1997), 5--21. Google ScholarDigital Library
- Power, N. M., A grounded theory of requirements documentation in the practice of software development, in School 2002, Dublin City University: Dublin. 223.Google Scholar
- IEEE, IEEE STD 830--1998: IEEE recommended practice for software requirements specifications. 1998, Los Alamitos, CA: IEEE Computer Society PressGoogle Scholar
- Robertson, S. and Robertson, J., Mastering the requirements process. 1999, Harlow, UK: Addison Wesley. Google ScholarDigital Library
- Zave, P. and Jackson, M., Four dark corners of requirements engineering. ACM Transactions on Software Engineering and Methodology, 6, 1 (1997), 1--30. Google ScholarDigital Library
- Wiegers, K. E., Software Requirements. Vol. 2nd ed. 2003, Redmond, Washington: Microsoft Press. Google ScholarDigital Library
- Odeh, M. and Kamm, R., Bridging the gap between business models and system models. Information and Software Technology, 45, 15 (2003), 1053--1060.Google ScholarCross Ref
- Daneva, M. and Wieringa, R., Cost estimation for cross-organizational ERP projects: research perspectives. Software Quality Journal, (2008). Google ScholarDigital Library
- Monnerat, R. M., de Carvalho, R. A., and de Campos, R., Enterprise systems modeling: the ERP5 development process, in Proceedings of the 2008 ACM symposium on Applied computing. 2008, ACM: Fortaleza, Ceara, Brazil. Google ScholarDigital Library
- Carvalho, R. A., Issues on evaluating Free/open source ERP sysyems, in Research and Practical Issues of Enterprise Informations Systems 2007, Springer Verlag New York Inc: New York. 667--676.Google Scholar
- Carvalho, R. A., Costa, H. G., and Xu, N., A Risk Based Method for Open Source Software Adoption Evaluation, in XIII CLAIO - Congreso Latino-Iberoamericano de Investigación Operativa. 2006: Montevideo, Uruguay.Google Scholar
- Johansson, B., Pain points challenges for future enterprise resource planning (ERP) systems, in 3gERP workshop. 2007: Copenhagen.Google Scholar
- Johansson, B., Developing a "better" ERP system: The risk of loosing competitive advantage, in Research and practical issues of enterprise information systems II, L. Xu, A. M. Tjoa, and S. Chaudbry, Editors. 2007, IFIP Springer.Google Scholar
- Boulanger, A., Open-source versus proprietary software: Is one more reliable and secure than the other? IBM Systems Journal, 44, 2 (2005), 239--248. Google ScholarDigital Library
- Evans, E. Domain-Driven Design Tackling Complexity in the Heart of Software. Addison-Wesley, 2003. Google ScholarDigital Library
Index Terms
- Management of requirements in ERP development: a comparison between proprietary and open source ERP
Recommendations
Odoo ERP with Business Intelligence Tool for a Small-Medium Enterprise: A Scenario Case Study
IC4E '20: Proceedings of the 2020 11th International Conference on E-Education, E-Business, E-Management, and E-LearningEnterprises can integrate business processes and information of across departments and can exhibit real-time information to decision maker by using an enterprise resource planning (ERP) system. The implementation of a commercial ERP system often has ...
An enterprise model and the organisation of ERP
Many BPR practitioners have indicated that the application of information technology is critical to the success of their BPR. ERP is currently one of the most popular information systems being employed to help organisations gain competitive advantage. ...
Software tools for requirements management in an ERP system context
SAC '10: Proceedings of the 2010 ACM Symposium on Applied ComputingIdentification and specification of business requirements are extremely important when development of Enterprise Resource Planning systems (ERPs) take place. Our aim is to present some prescriptive thoughts about requirements management useful when ...
Comments