ERP Customization as Software Engineering: Knowledge Sharing and Cooperation

Dittrich, Yvonne; Vaucouleur, Sebastien; Giff, Stephen

doi:10.1109/ms.2009.173

Cited by 64 publications

(45 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Furthermore, 96 % of the data centers spent less than 50 % of the dialog executions on custom transactions. This practical study supports the theoretical assumption that ERP implementation projects aim at using as much of the existing functionality as possible without having to customize [50]. Hence, the average usage profile of an EA strongly fosters the feasibility of a domain-specific but standardized capacity management approach that can be offered as a service in order to leverage economies of scale.…”

Section: Standardization Degree Of Enterprise Applicationssupporting

confidence: 72%

“…We distinguish between standard and custom transaction types. If customers require functionality beyond available components, the source code of the product must be adapted [50], resulting in custom transaction types that are known solely to the organization and are not used by any other party. Therefore, cross-organizational performance models cannot be built for these components and their capacity needs to be planned traditionally using individual analytical models or gathered data.…”

Section: Process Overviewmentioning

confidence: 99%

See 1 more Smart Citation

Capacity Management as a Service for Enterprise Standard Software

Müller

Bosse

Turowski

2018

J. Complex Syst. Inform. Model. Q.

View full text Add to dashboard Cite

Abstract. Capacity management approaches optimize component utilization from a strong technical perspective. In fact, the quality of involved services is considered implicitly by linking it to resource capacity values. This practice hinders to evaluate design alternatives with respect to given service levels that are expressed in user-centric metrics such as the mean response time for a business transaction. We argue that utilized historical workload traces often contain a variety of performance-related information that allows for the integration of performance prediction techniques through machine learning. Since enterprise applications excessively make use of standard software that is shipped by large software vendors to a wide range of customers, standardized prediction models can be trained and provisioned as part of a capacity management service which we propose in this article. Therefore, we integrate knowledge discovery activities into well-known capacity planning steps, which we adapt to the special characteristics of enterprise applications. Using a realworld example, we demonstrate how prediction models that were trained on a large scale of monitoring data enable cost-efficient measurement-based prediction techniques to be used in early design and redesign phases of planned or running applications. Finally, based on the trained model, we demonstrate how to simulate and analyze future workload scenarios. Using a Pareto approach, we were able to identify cost-effective design alternatives for an enterprise application whose capacity is being managed.

show abstract

Section: Standardization Degree Of Enterprise Applicationssupporting

confidence: 72%

Section: Process Overviewmentioning

confidence: 99%

Capacity Management as a Service for Enterprise Standard Software

Müller

Bosse

Turowski

2018

J. Complex Syst. Inform. Model. Q.

View full text Add to dashboard Cite

show abstract

“…Despite of this general interest to the "people factor", there is little evidence available about specifics of collaboration, such as its change over time and its different modes in large software development efforts including enterprise software development. The collaborative practice of enterprise development can be easily disturbed [16], but still collaborative patterns and their changes have been rarely studied [17]. In this study, we refer to collaboration as a practice where at least two parties work together to achieve a common goal or co-create value in the form of enhancing the software-based enterprise system [18].…”

Section: Research Areamentioning

confidence: 99%

Collaboration change in enterprise software development

Smolander

Rossi

Pekkola

2016

Proceedings of the 9th International Workshop on Cooperative and Human Aspects of Software Engineering

View full text Add to dashboard Cite

Enterprise software development is a complex effort that may last years. Enterprise software is often developed by a systems integrator that makes modifications to a pre-made package or builds tailored software for the specific purpose. The development may include many developer organizations, the user organization, and their different departments and sub-units. Their collaboration evolves through project incidents, phases and even crises. The practices of project management, communication, contracts, and ultimately personal relationships change intentionally or unintentionally. These changes may cause uncertainties and discontinuities for the development. This study observes changes during enterprise software development and their influence on collaboration practices in different situations. During twenty years of development both internal and external crises and changes in the business environment triggered changes in collaboration. The collaboration practices are classified with four modes of collaboration (contract, cooperation, personified, and process) that illustrate emphasis in collaboration in different circumstances. CCS ConceptsSoftware and its engineering  Software creation and management  Collaboration in software development Information systems  Information systems application  Enterprise information systems

show abstract

“…Different vendors may use different explanation for each term [9]. In the literature it has been found that customizations is usually described as the process of implementing a new feature to the application that doesn"t even exist which requires changes in the source code with deep understanding of the exciting program functionality and the domain the program should support [9], [32], [33]. This ability is limited to the application vendor most of the times hence the changes are made in the second phase of the application lifecycle (implementation phase) [32].…”

Section: Configuration and Customizationmentioning

confidence: 99%

Configuration as a Service in Multi-Tenant Enterprise Resource Planning System

Al-Shardan¹,

Ziani²

2015

LNSE

View full text Add to dashboard Cite

Abstract-Enterprise resource planning (ERP) systems are the organizations tickets to the global market. Thus, organizations can manage and coordinate all functions, processes, resources and data from different departments by a single software. However, many organizations consider the cost of traditional ERP is expensive and look for alternative affordable solutions within their budget. One of these alternative solutions is providing ERP over a software as a service (SaaS) model. A key feature of any SaaS system is the multi-tenancy architecture where multiple customers (tenants) share the system software. However, the SaaS developers accommodate each tenant's unique requirements by allowing tenant-level customization or configuration. While customization requires source code changes and in most cases a programming experience, the configuration process allows user to change many features within a pre-defined scope in an easy and controlled manner. Although literature provides many techniques to accomplish the configuration process in different SaaS systems, the nature and complexity of SaaS ERP are merely described in previous researches. Thus, this research is built on strong knowledge regarding the configuration in SaaS to define specifically the configuration borders in SaaS ERP and to design a configuration service with the consideration of the different configuration aspects.Index Terms-Configuration, software as a service, multi-tenancy, ERP.

show abstract

ERP Customization as Software Engineering: Knowledge Sharing and Cooperation

Cited by 64 publications

References 6 publications

Capacity Management as a Service for Enterprise Standard Software

Capacity Management as a Service for Enterprise Standard Software

Collaboration change in enterprise software development

Configuration as a Service in Multi-Tenant Enterprise Resource Planning System

Contact Info

Product

Resources

About