|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
ERP Requirements Engineering Practice: Lessons Learned
March/April 2004 (vol. 21 no. 2)
pp. 26-33
| ASCII Text | x | ||
| Maya Daneva, "ERP Requirements Engineering Practice: Lessons Learned," IEEE Software, vol. 21, no. 2, pp. 26-33, March/April, 2004. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2004.1270758, author = {Maya Daneva}, title = {ERP Requirements Engineering Practice: Lessons Learned}, journal ={IEEE Software}, volume = {21}, number = {2}, issn = {0740-7459}, year = {2004}, pages = {26-33}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2004.1270758}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - ERP Requirements Engineering Practice: Lessons Learned IS - 2 SN - 0740-7459 SP26 EP33 EPD - 26-33 A1 - Maya Daneva, PY - 2004 KW - Requirements Process KW - Process Models KW - Process Implementation and Change KW - Reuse Models VL - 21 JA - IEEE Software ER - | |||
Organizations implementing Enterprise Resource Planning (ERP) systems have been increasingly adopting generic, off-the-shelf requirements engineering (RE) process models. Yet, little information exists about the challenges of making a generic RE model a life process. This article discusses why bringing an off-the-shelf process in isn?t a sufficient foundation. The author shares experiences acquired over the past five years of eliciting, modeling, and validating requirements in ERP projects and highlights typical issues and their solutions. Among the keys to success are planning RE model use in the client?s context and installing processes to support key RE activities.
Index Terms:
Requirements Process, Process Models, Process Implementation and Change, Reuse Models
Citation:
Maya Daneva, "ERP Requirements Engineering Practice: Lessons Learned," IEEE Software, vol. 21, no. 2, pp. 26-33, March-April 2004, doi:10.1109/MS.2004.1270758
Usage of this product signifies your acceptance of the Terms of Use.