Transformation of Centralized Software Components into Distributed Ones by Code Refactoring

Abstract

Abstract. Adapting software components to be used in a particular application is a crucial issue in software component based technology. In fact, software components can be used in contexts with characteristics different from those envisaged when designing the component. Centralized or distributed deployment infrastructure can be one of these assumptions. Thus, a component can be designed as a monolithic unit to be deployed on a centralized infrastructure, nevertheless the used infrastructure needs the component to be distributed. In this paper, we propose an approach allowing to transform a centralized software component into a distributed one. Our technique is based on refactoring and fragmentation of component source code.

Dynamic Adaptation of Software Component Structures

“…These possibilities are very useful for load balancing and to increase performance. Indeed, the utility of the structural adaptation for the flexible deployment in the distributed environments was illustrated in [11]. Nevertheless, this flexible deployment was realizable in a static way in spite of disadvantages mentioned above.…”

“…Thus 1 Issues related to the integration of distribution mechanisms into the composite configuration is out of this paper's scope. See [11].…”

“…This means that component behavior will be preserved. In our previous works [1] [11], we proposed to carry out the structural adaptation in a static way. In this case, to adapt a component, this last must be stopped and if it is required, the entire application must be stopped too.…”

“…The second phase of the adaptation process is activated at run-time and aims at reconfiguring the canonical component internal subcomponent structure and links. We base ourselves for the realization of the first phase on the results of our previous work allowing the update of a software component structure in a static way [1] [11]. We discuss the proposed approach in the rest of this paper as follows.…”

Experiences from Monitoring Effects of Architectural Changes

“…It is a way to restore quality after frequent changes [6], improve extensibility, modularity, reusability, complexity, maintainability and efficiency [6] or transform centralized software components into distributed [7]. Software restructuring is a form of "perfective maintenance" with the goal to modify the structure of the source code and facilitate correctly previously undetected errors [8].…”