From Object-Oriented Applications to Component-Oriented Applications via Component-Oriented Architecture

Allier, Simon; Sadou, Salah; Sahraoui, Houari; Fleurquin, Régis

doi:10.1109/wicsa.2011.35

Cited by 28 publications

(29 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In one of our old work we presented an approach for component extraction that relies on a combination of static analysis (on source code) and dynamic analysis (calls between objects) [1]. This combination of the two approaches of analysis allowed to better cover aspects of extracted components.…”

Section: Resultsmentioning

confidence: 99%

Enactment of Components Extracted from an Object-Oriented Application

Seriai

Sadou

Sahraoui

2014

Software Architecture

Self Cite

View full text Add to dashboard Cite

Software architecture plays an important role for the application understanding before its maintenance. Unfortunately, for legacy systems code often there is no corresponding (or up to date) architecture. So, several work tackle this problem by extracting components from the legacy system and define their links. Although these components allow to get an architectural view of the legacy system, they still can't be easily implemented in a concrete framework. In fact, restructuring completely the legacy system facilitates the mapping between the architectural elements and their corresponding ones in the code. This paves the way to the future maintenance of the system.Our approach aims to reach this complete restructuring. Thus it goes beyond what exists in the state of the art by proposing a technique that makes components extracted from object-oriented applications implementable within a concrete component model. This is done by using class instances that compose the extracted components to infer possible instances the components. Thus, we propose for each extracted component its provided and required interfaces, and a way to construct its instances. We validated the feasibility of the proposed approach through the Spring framework and we illustrated it through a legacy Java application.

show abstract

Section: Resultsmentioning

confidence: 99%

Enactment of Components Extracted from an Object-Oriented Application

Seriai

Sadou

Sahraoui

2014

Software Architecture

Self Cite

View full text Add to dashboard Cite

show abstract

“…For example, the work in [19] is based on the definition of a correspondence model between code elements and architectural concepts. In [1] a component is considered as a group of classes collaborating to provide a system function. The authors in [7] recover BPMN models starting from service oriented systems that have been generated from web applications.…”

Section: Related Workmentioning

confidence: 99%

A bottom-up approach for reconstructing software architecture product lines

Kerdoudi

Ziadi²,

Tibermacine

et al. 2019

Proceedings of the 13th European Conference on Software Architecture - Volume 2

Self Cite

View full text Add to dashboard Cite

A large component and service-based software system exists in different forms, as different variants targeting different business needs and users. This kind of systems is provided as a set of "independent" products and not as a "single whole". The presence of a single model describing the architecture of the whole system may be of great interest for developers of future variants. Indeed, this enables them to see the invariant part of the whole, on top of which new functionality can be built, in addition to the different options they can use. We investigate in this work the use of software product line reverse engineering approaches, and in particular the framework named BUT4Reuse, for reconstructing an architecture model of a Software Architecture Product Line (SAPL), from a set of variants. We propose a generic process for reconstructing an architecture model of such a product line. We have instantiated this process for the OSGi Java framework and experimented it for building the architecture model of Eclipse IDE SPL.

show abstract

“…Allier et al [2] proposed a method to automate the process of migrating OO Java applications into CB OSGi ones. This method makes component interfaces operational by the use of two design patterns: Adapter and Façade.…”

Section: Related Workmentioning

confidence: 99%

“…Existing works that propose migration solutions [2,3] consider that the modularity and reuse unit, i.e. the component, is a group of classes, called a cluster.…”

Section: Introductionmentioning

confidence: 99%

Refactoring Object-Oriented Applications towards a better Decoupling and Instantiation Unanticipation

Zellagui¹,

Tibermacine²,

Bouziane³

et al. 2017

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Modularity in Object-Oriented (OO) applications has been a major concern since the early years of OO programming languages. Migrating existing OO applications to Component-Based (CB) ones can contribute to improve modularity, and therefore maintainability and reuse. In this paper, we propose a method for source code transformation (refactoring) in order to perform this migration. This method enhances decoupling by considering that some dependencies between classes should be set through abstract types (interfaces) like in CB applications. In addition, some anticipated instantiations of these classes "buried" in the source code are extracted and replaced by declarative statements (like connectors in CB applications) which are processed by a dependency injection mechanism. For doing so, a set of "Bad Smells", i.e., modularity-violating symptoms, has been defined. These are first detected in the source code. Then, some refactoring operations are applied for their elimination. An implementation of the method was successfully experimented on a set of open source Java projects. The results of this experimentation are reported in this paper.

show abstract

From Object-Oriented Applications to Component-Oriented Applications via Component-Oriented Architecture

Cited by 28 publications

References 17 publications

Enactment of Components Extracted from an Object-Oriented Application

Enactment of Components Extracted from an Object-Oriented Application

A bottom-up approach for reconstructing software architecture product lines

Refactoring Object-Oriented Applications towards a better Decoupling and Instantiation Unanticipation

Contact Info

Product

Resources

About