Management of requirements in ERP development: a comparison between proprietary and open source ERP

Authors:
Björn Johansson;Rogério Atem de Carvalho
Affiliations:
Copenhagen Business School, Frederiksberg;Federal Center for Technological, Brazil
Venue:
Proceedings of the 2009 ACM symposium on Applied Computing
Year:
2009

Citing 12
Cited 0

Software requirements & specifications: a lexicon of practice, principles and prejudices

Software requirements & specifications: a lexicon of practice, principles and prejudices
Four dark corners of requirements engineering

ACM Transactions on Software Engineering and Methodology (TOSEM)
Mastering the requirements process

Mastering the requirements process
Enterprise resource planning: cultural fits and misfits: is ERP a universal solution?

Communications of the ACM
Five roles of an information system: a social constructionist approach to analyzing the use of ERP systems

ICIS '00 Proceedings of the twenty first international conference on Information systems
The meaning of requirements

Annals of Software Engineering
Domain-Driven Design: Tacking Complexity In the Heart of Software

Domain-Driven Design: Tacking Complexity In the Heart of Software
Software Requirements

Software Requirements
Open-source versus proprietary software: is one more reliable and secure than the other?

IBM Systems Journal
Survey paper: A survey on the recent research literature on ERP systems

Computers in Industry - Special issue: Current trends in ERP implementations and utilisation
Enterprise systems modeling: the ERP5 development process

Proceedings of the 2008 ACM symposium on Applied computing
Cost estimation for cross-organizational ERP projects: research perspectives

Software Quality Control

Quantified Score

Hi-index	0.00

Visualization

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.