Advertisement

Abstract

Open Source receives high attention among organizations today, and there is also a growing interest on Open Source Enterprise Resource Planning (OS ERP) systems. Open source development is often considered having a high level of involvement from stakeholders in adopting organizations. However, it depends on for the first what is meant by stakeholders, but also what is meant by involvement. In the area of ERP development stakeholder involvement is defined as to what extent users of the system are involved in the development of the standardized software package. The way this is done differs between different vendors but it can be summarized as dealing with management of requirements. In this paper we explore how requirements management is done in development of OS ERP. To do this, we use a theoretical base on requirements management in the ERP field from which we investigate stakeholder involvement in four organizations and the development of it’s respectively OS ERP system. The basic question asked was: how are end-users of OS ERPs involved in the development of OS ERP. From the investigation we present a general picture of the requirements management process in the OS ERP area. The main conclusion is that end-users are not involved to the extent first expected and when comparing with proprietary ERP development a tendency towards a similar approach to requirements management in OS ERP development was discovered.

Keywords

Requirements Engineering Enterprise Resource Planning ERP Open Source Standard systems user involvement 

References

  1. Daneva, M.: Understanding Success and Failure Profiles of ERP Requirements Engineering: an Empirical Study. In: 33rd EUROMICRO Conference on Software Engineering and Advanced Applications (EUROMICRO 2007) (2007)Google Scholar
  2. Davis, A.M.: Just enough requirements management: where software development meets marketing. Dorset House Publishing, New York (2005)Google Scholar
  3. Eriksson, U.: Requirements engineering for IT-systems (in Swedish: Kravhantering för IT-system), 2nd edn. Studentlitteratur, Lund (2008)Google Scholar
  4. Fitzgerald, B.: The Transformation of Open Source Software. MIS Quarterly 30(3) (2006)Google Scholar
  5. Hickey, A.M., Davis, A.M.: Elicitation technique selection: how do experts do it? In: 11th IEEE International Requirements Engineering Conference (2003)Google Scholar
  6. Jiang, L., Eberlein, A., Far, B.H.: Combining Requirements Engineering Techniques - Theory and Case Study. In: 12th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems, ECBS 2005 (2005) Google Scholar
  7. Karlsson, J.: Software requirements prioritizing. In: The Second International Conference on Requirements Engineering (1996)Google Scholar
  8. Kotonya, G., Sommerville, I.: Requirements engineering: Processes and techniques. John Wiley & Sons, Chichester (1998)Google Scholar
  9. Lemos, R.: Open Source ERP grows up. CIO.com (2008), http://www.cio.com/
  10. Loucopoulos, P., Karakostas, V.: System requirements engineering. McGraw-Hill, Berkshire (1995)Google Scholar
  11. Rapp, J.: Increased Interest for Open Source (in Swedish: Ökat intresse för Open Source.) Logica (2009), http://www.logica.se
  12. Robertson, S., Robertson, J.: Mastering the requirements process, 2nd edn. Addison-Wesley, Upper Saddle River (2006)Google Scholar
  13. Sailor, J.D.: System Engineering: An introduction. In: Thayer, I.R.H., Dorfman, M. (eds.) System and Software Requirements Engineering, pp. 35–47. IEEE Computer Society Press, Washington (1990)Google Scholar
  14. Sommerville, I.: Software Engineering, 8th edn. Pearson Education Limited, Harlow (2007)zbMATHGoogle Scholar
  15. Sommerville, I., Sawyer, P.: Requirements engineering: a good practice guide. John Wiley & Sons Ltd., Chichester (1997)zbMATHGoogle Scholar
  16. The Standish Group. CHAOS Report (1995), http://www.projectsmart.co.uk/docs/chaos-report.pdf
  17. Verville, J. J., Palanisamy, R., Bernadas, C., Halingten, A.: ERP Acquisition Planning: A Critical Dimension for Making the Right Choice. Long Range Planning 40(1) (2007)Google Scholar
  18. Wiegers, K.E.: Software Requirements. Microsoft Press, Redmond (1999)Google Scholar
  19. Young, R.R.: Effective Requirements Practices. Addison-Wesley, Boston (2001)Google Scholar
  20. Zhao, L., Elbaum, S.: Quality assurance under the open source development model. The Journal of Systems and Software 66(1) (2003) Google Scholar
  21. Zowghi, D., Coulin, C.: Requirements Elicitation: A survey of techniques, approaches and tools. In: Aurum, I.A., Wohlin, C. (eds.) Engineering and Managing Software Requirements, pp. 19–46. Springer, Berlin (2005)CrossRefGoogle Scholar

Copyright information

© IFIP International Federation for Information Processing 2011

Authors and Affiliations

  • Björn Johansson
    • 1
  1. 1.Department of Informatics, School of Economics and ManagementLund UniversitySweden

Personalised recommendations