Search

In order to create innovative business products, share knowledge between people and businesses, or increase the control and quality of services, more and more often enterprise business processes involve in collaborations by delegating or providing some pieces of work to other enterprises. Necessity to cooperate in the cross-enterprise setting leads to Collaborative Business Processes (CBPs). The difference between CBPs and Business Processes (BPs) is in the decentralized coordination, flexible backward recovery, participants notification about the state, efficient adaptability to changes, presence of multiple information systems, and individual authorization settings. In the paper we consider a specific case of CBPs where multiple collaborating partners use Enterprise Resource Planning (ERP) system of the same vendor. The vendor can see (e.g., monitor) the changes of data elements, but does not have explicit process awareness in the ERP system to support flow of activities in the cross-enterprise setting. The paper also discusses different settings of cross-enterprise CBP and shows simplified enterprise models behind the vendor possibilities to positively impact collaborative processes. The restrictions of the vendor are implicit information flows in BP, diversity of ERP integrations with third party Information Systems (IS), the lack of mechanisms for monitoring BP instances, backward recovery, user notification about the current state and tasks, and inability to make explicit changes in customers’ ISs.

Many legacy enterprise applications are large, monolithic and tightly coupled. Their maintenance is expensive and these systems are inflexible in fast changing environments. Modularization can improve the maintainability and increase the efficiency of legacy enterprise applications. This paper describes a source code driven decomposition of a large enterprise application using clustering methods and by taking into account business domain knowledge. The method is applied for decomposition of a large industrial ERP system.

Enterprise applications are used for managing operational data and are aimed at improving business efficiency. Many enterprise applications have been developed over the past three decades and are often referred to as legacy systems. Usually they are monolith, inflexible, poorly documented and hard to maintain. These issues can be addressed by improving their design using decomposition. The purpose of this paper is to introduce a method for decomposition of large scale enterprise applications and to present initial practical evaluation results. The paper systematically defines the general decomposition process including its tailoring options. The general process is adapted and applied for application in the industrial case study investigated as part of the university-industry collaboration research project.

Large enterprise applications are developed by teams of developers specializing in particular functional or technical areas. An overall application architecture is used to guide allocation of development tasks to the development teams. However, quality of the architecture degrades over the application life-cycle and manual refactoring is challenging due to the size and complexity of enterprise applications. This paper proposes to use automated clustering of large enterprise applications, where clusters are built around application business centers, as a means for refactoring the software design with an objective to improve allocation of software modules to development teams. The paper outlines a module allocation process in the framework of the overall enterprise application development process and reports an illustration of the allocation process. The illustration is based on the case of refactoring of a large third tier ERP system.

Enterprise applications are aimed at managing en- terprise operational data and improving business efficiency. Many enterprise applications have been developed over the past three decades, therefore, known as legacy systems. Usually, they are monolith, inflexible, poorly documented and hard to main- tain. The purpose of this paper is to describe best practices and limitations for enterprise application decomposition based on the results of the systematic literature review in order to introduce an approach for enterprise application decomposition. The paper focuses on decomposition of large-scale systems using clustering methods. The investigation is performed as part of the university- industry collaboration research project.

Many enterprise applications have been developed over the last three decades therefore known as legacy systems. Usually they are monolith, inflexible, poorly documented and hard to maintain, however they are important to enterprises. The evolution of these systems depends on their decomposability. The purpose of this paper is to summarize existing knowledge, requirements and limitations for object-oriented legacy system decomposition based on systematic literature review. The investigation is performed as a part of the university-industry collaboration research project.