ITU

Beyond the crystal ball assumption: Towards upgradable ERP systems

Research output: Conference Article in Proceeding or Book/Report chapterArticle in proceedingsResearch

Standard

Beyond the crystal ball assumption : Towards upgradable ERP systems. / Vaucouleur, Sebastien.

Pre-proceedings of the 2nd Workshop on 3rd Generation Enterprise Resource Planning Systems. 2008.

Research output: Conference Article in Proceeding or Book/Report chapterArticle in proceedingsResearch

Harvard

Vaucouleur, S 2008, Beyond the crystal ball assumption: Towards upgradable ERP systems. in Pre-proceedings of the 2nd Workshop on 3rd Generation Enterprise Resource Planning Systems. Second 3gERP Workshop, Copenhagen, Denmark, 17/11/2008.

APA

Vaucouleur, S. (2008). Beyond the crystal ball assumption: Towards upgradable ERP systems. In Pre-proceedings of the 2nd Workshop on 3rd Generation Enterprise Resource Planning Systems

Vancouver

Vaucouleur S. Beyond the crystal ball assumption: Towards upgradable ERP systems. In Pre-proceedings of the 2nd Workshop on 3rd Generation Enterprise Resource Planning Systems. 2008

Author

Vaucouleur, Sebastien. / Beyond the crystal ball assumption : Towards upgradable ERP systems. Pre-proceedings of the 2nd Workshop on 3rd Generation Enterprise Resource Planning Systems. 2008.

Bibtex

@inproceedings{13ff8a00f76311dd9b71000ea68e967b,
title = "Beyond the crystal ball assumption: Towards upgradable ERP systems",
abstract = "Most software engineering techniques that deal with software products customization are based on anticipation: The software designer has to foresee, somehow, the future needs for customization so that other programmers can adapt the software product with as little modifications as possible (programmers hide implementation details behind previously defined interfaces, or alternatively, they refine some pre-defined properties). While practical, this approach is unfortunately not completely satisfactory for Enterprise Resource Planning systems (ERPs). These software productshave to be customizable for numerous and various local contexts; they cover a very large domain, one that cannot be fully comprehended — hence accurate anticipation is difficult. To solve this problem, an extreme measure is to give the programmers the means to do modifications in place, directly in the source code. This approach trades control for flexibility. Unfortunately, it also makes the customized software product very sensitive to upgrades. We propose a more mitigated solution, that does not require accurate anticipation and yet offers some resilience to evolution of the base software product through the use of code quantification.We introduce the Eggther framework for customization of evolvable software products in general and ERP systems in particular. Our approach is based on the concept of code query by example. The technology being developed is based on an initial empirical study on practices around ERP systems. We motivate our design choices based on those empirical results, and we show how the proposed solution helps with respect to the upgrade problem.",
author = "Sebastien Vaucouleur",
year = "2008",
language = "English",
booktitle = "Pre-proceedings of the 2nd Workshop on 3rd Generation Enterprise Resource Planning Systems",
note = "null ; Conference date: 17-11-2008 Through 18-11-2008",

}

RIS

TY - GEN

T1 - Beyond the crystal ball assumption

AU - Vaucouleur, Sebastien

N1 - Conference code: 2

PY - 2008

Y1 - 2008

N2 - Most software engineering techniques that deal with software products customization are based on anticipation: The software designer has to foresee, somehow, the future needs for customization so that other programmers can adapt the software product with as little modifications as possible (programmers hide implementation details behind previously defined interfaces, or alternatively, they refine some pre-defined properties). While practical, this approach is unfortunately not completely satisfactory for Enterprise Resource Planning systems (ERPs). These software productshave to be customizable for numerous and various local contexts; they cover a very large domain, one that cannot be fully comprehended — hence accurate anticipation is difficult. To solve this problem, an extreme measure is to give the programmers the means to do modifications in place, directly in the source code. This approach trades control for flexibility. Unfortunately, it also makes the customized software product very sensitive to upgrades. We propose a more mitigated solution, that does not require accurate anticipation and yet offers some resilience to evolution of the base software product through the use of code quantification.We introduce the Eggther framework for customization of evolvable software products in general and ERP systems in particular. Our approach is based on the concept of code query by example. The technology being developed is based on an initial empirical study on practices around ERP systems. We motivate our design choices based on those empirical results, and we show how the proposed solution helps with respect to the upgrade problem.

AB - Most software engineering techniques that deal with software products customization are based on anticipation: The software designer has to foresee, somehow, the future needs for customization so that other programmers can adapt the software product with as little modifications as possible (programmers hide implementation details behind previously defined interfaces, or alternatively, they refine some pre-defined properties). While practical, this approach is unfortunately not completely satisfactory for Enterprise Resource Planning systems (ERPs). These software productshave to be customizable for numerous and various local contexts; they cover a very large domain, one that cannot be fully comprehended — hence accurate anticipation is difficult. To solve this problem, an extreme measure is to give the programmers the means to do modifications in place, directly in the source code. This approach trades control for flexibility. Unfortunately, it also makes the customized software product very sensitive to upgrades. We propose a more mitigated solution, that does not require accurate anticipation and yet offers some resilience to evolution of the base software product through the use of code quantification.We introduce the Eggther framework for customization of evolvable software products in general and ERP systems in particular. Our approach is based on the concept of code query by example. The technology being developed is based on an initial empirical study on practices around ERP systems. We motivate our design choices based on those empirical results, and we show how the proposed solution helps with respect to the upgrade problem.

M3 - Article in proceedings

BT - Pre-proceedings of the 2nd Workshop on 3rd Generation Enterprise Resource Planning Systems

Y2 - 17 November 2008 through 18 November 2008

ER -

ID: 956000