Runtime recovery and manipulation of software architecture of component-based systems

Abstract

Recently, more attention is paid to the researches and practices on how to use software architecture in software maintenance and evolution to reduce their complexity and cost. The key in such architecture-based maintenance and evolution is to recover software architecture from existing systems. Almost all studies on architecture recovery focus on analyzing the source code and other documents. Such recovered software architecture can hardly capture runtime states and behaviors of the system. At the same time, current work pays little attention on how to change the system directly via manipulating the recovered software architecture. This paper presents a novel approach to recovering software architecture from component based systems at runtime and changing the runtime systems via manipulating the recovered software architecture. Containing much more details than the designed software architecture, the recovered software architecture can accurately and thoroughly describe the actual states and behaviors of the runtime system. It can be described formally with the extension of traditional architecture description language, which enables the recovered software architecture to absorb the semantics embedded in the designed software architecture. The recovered software architecture can be represented as multiple views so as to help different users to control the complexity from different concerns. Based on the reflective ability of the component framework, the recovered software architecture is up-to-date at any time and changes made on it will immediately lead to the corresponding changes in the runtime system. The approach presented in this paper is demonstrated on PKUAS, a reflective J2EE (Java 2 Platform Enterprise Edition) application server, and the performance is also evaluated.

Model Driven Configuration of Fault Tolerance Solutions for Component-Based Software System

“…However, since the number of popular middleware in a period is relatively few, we argue that making a concrete middleware more powerful on exception handling is more important. This study is being carried out now, with the help of our Runtime Software Architecture [5][24].…”

An Architecture-Centric Approach for Information System Architecture Modeling, Enactement and Evolution

“…The evolution takes place at runtime, and concerns both the design and the code. (Huang et al, 2006) focus on dynamic software architecture extraction and evolution by catching the executing component-based system state and system behavior: an architectural representation is deduced and can be modified at runtime. The approach can be seen as a unifying one.…”

A development process for requirements based service choreography

“…Choreography synthesis concerns the realization of distributed coordination delegates that, supported by the CHOReOS middleware, cooperatively work to support the enactment and execution of the choreography. By relying on the CHOReOS service base management mechanisms, Model-to-Model Transformation techniques [10] are used to refine the Choreography Model together with the service Behavioral Models into a Peer-style Specification (see Figure 3).…”