Reengineering legacy systems for distributed environments

Serrano, Miguel A.; Carver, Doris L.; de, Carlos Montes

doi:10.1016/s0164-1212(02)00020-1

Cited by 26 publications

(18 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…If a strong MemberGroup pattern is found and all previous preconditions are fulfilled, we can relocate the MemberGroup MG strong (m) to the target class T ∈ M tar using the relocation function moveStrongMG: Similar to the relocation algorithm for the common MemberGroup the function moveStrongMG resolves overlapping identifier names and moves the members and dependent constructor statements (lines [3][4][5][6][7][8]. After the relocation of the strong MemberGroup the formerly used variable of type T , passed to the method m as parameter, is unnecessary.…”

Section: Moving Strong Membergroupsmentioning

confidence: 99%

“…Apart from the need for software analysis tools for an extensive system understanding [2], there is also the need for transformation tools that support the programmer while restructuring the legacy code. An important restructuring task is the modularization (decoupling) of classes, which helps to reduce the systems' complexity [3] and to adapt legacy systems to distributed environments [4].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Reducing the Class Coupling of Legacy Code by a Metrics-Based Relocation of Class Members

Ferber

Hunold

Krellner

et al. 2012

Advances in Software Engineering Techniques

View full text Add to dashboard Cite

Abstract. With the rapid growth of the complexity of software systems, the problem of integrating and maintaining legacy software is more relevant than ever. To overcome this problem, many methods for refactoring legacy code have already been proposed such as renaming classes or extracting interfaces. To perform a real modularization, methods have to be moved between classes. However, moving a single method is often not possible due to code dependencies. In this article we present an approach to modularize legacy software by moving multiple related class members. It is shown how to identify groups of class members with similar concerns. We present two different code patterns that the related members and their dependent classes must match to allow a relocation of the related members. We also demonstrate how our pattern-based approach for automated modularization of legacy software can be applied to two open source projects.

show abstract

Section: Moving Strong Membergroupsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Reducing the Class Coupling of Legacy Code by a Metrics-Based Relocation of Class Members

Ferber

Hunold

Krellner

et al. 2012

Advances in Software Engineering Techniques

View full text Add to dashboard Cite

show abstract

“…Wrapping foreign code. A wrapper enables the reuse a foreign implementation through the API provided by a bridge library [5,4,19,13]. This approach does not change the foreign code, hence there is no risk of corrupting it or of introducing inconsistencies; on the other hand, it is usually restrictive in terms of the type of data that can be retrieved through the bridging API (for example, primitive types only).…”

Section: Related Workmentioning

confidence: 99%

Automated Translation of Java Source Code to Eiffel

Trudel

Manuel

Furia

et al. 2011

Objects, Models, Components, Patterns

View full text Add to dashboard Cite

Abstract. Reusability is an important software engineering concept actively advocated for the last forty years. While reusability has been addressed for systems implemented using the same programming language, it does not usually handle interoperability with different programming languages. This paper presents a solution for the reuse of Java code within Eiffel programs based on a source-to-source translation from Java to Eiffel. The paper focuses on the critical aspects of the translation and illustrates them by formal means. The translation is implemented in the freely available tool J2Eif; it provides Eiffel replacements for the components of the Java runtime environment, including Java Native Interface services and reflection mechanisms. Our experiments demonstrate the practical usability of the translation scheme and its implementation, and record the performance slow-down compared to custom-made Eiffel applications: automatic translations of java.util data structures, java.io services, and SWT applications can be re-used as Eiffel programs, with the same functionalities as their original Java implementations.

show abstract

“…Other researches, such as Serrano et al [12,13], encompassed data mining and evolutionary migration techniques into reengineering a legacy program. They also proposed a feasible reengineering methodology to migrate non-object-oriented systems into the CORBA platform [14].…”

Section: Related Workmentioning

confidence: 99%