Requirements Elicitation in ERP Implementation Process

Abstract

Management software has gained an increasing preponderance over the years. Following that increased demand, as ERPs evolve and diversify, the characteristics and the correspondent needs of companies adopting them expanded significantly. To fulfill these needs, consulting companies in charge of implementing the ERP applications, resource to complex implementation processes. The value that consultants add to this implementation process comes from their experience and knowledge not only of the area of intervention and the specific characteristics of the software, but also from their experience in previous implementations in other projects. It is in this context, that transfer of knowledge between projects and consultants gains an increased importance. Due to its ability to model all possible products of a software product line in a given context, Feature Model concept has been used in the ERP domain with the objective of reducing time and costs in ERP projects by mapping requirements to correspondent past configurations and customizations. Using feature model and user stories methods, this work analyzes the development and implementation of a suggested ERP configuration methodology in a consulting company, aiming to improve the transfer of knowledge within projects and consultants. Following design research methods, the methodology developed was tested through an ERP implementation project. Findings of this work include an easier traceability between requirements and features, reutilization of configurations between projects and improved uniformization regarding requirements elicitation process.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 9 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.