Saving legacy with objects

Dietrich, Walter C.; Nackman, Lee R.; Gracer, F.

doi:10.1145/74877.74886

Cited by 28 publications

(4 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…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

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

show abstract

“…see (9) who describes the technical problems that occurred when an object-oriented language was built on top of an existing system. In general, most of these aspects arises from the problem of communicating the state of one instance between the new and the old subsystem.…”

Section: 23 Map Each Analysis Object To the Implemen-iandion Of Thementioning

confidence: 99%

“…To get a complete understanding of the three systems we studied functions that spanned over all of the systems . After that, we created an analysis model and its motivations,see figure [9].…”

Section: Traffic Control Systemmentioning

confidence: 99%

Reengineering of old systems to an object-oriented architecture

Jacobson¹,

Lindström²

1991

Conference Proceedings on Object-Oriented Programming Systems, Languages, and Applications

View full text Add to dashboard Cite

Most of our present-day information systems have been in use for a long time. They have been developed using the system development methods, programming tools, data base handlers, etc. that were available when the development work started. Even if the systems are adapted to changed requirements from the surrounding world, the basic structure and the original technical and methodological ties have been retained. Our goal is to show how an object-oriented development method can be used to gradually modernize an old system, i.e re-engineer the system. We do this by showing how three typical cases of re-engineering are related to object-oriented development. The technique is based on experiences from real projects.The basis of our technology is system development using object-oriented technique. The technology implies that occurrences from the application domain are modelled as objects and associations between objects. The resulting system model will be used as a mapping between the occurrences of the application domain and programming elements in the existing system. Permissionto copy without fee all or part of this material is granted provided that the copies are not made or distributed for direct commercial advantage, the ACM copyright notice and the title of the publication and its date appear, and notice is given that copying is by permission of the Association for Computing Machinery.To copy otherwise, or to republish, requires a fee and/or specific permission.

show abstract

“…Scenarios and strategies for gradually reengineering into object-oriented are described in [l]. Techniques for encapsulation of legacy systems into object wrappers are discussed in [2]. Techniques, but not automation, for abstracting of functions from COBOL programs are described in [3].…”

Section: Introductionmentioning

confidence: 99%

Reengineering procedural into object-oriented systems

Newcomb

Kotik

Proceedings of 2nd Working Conference on Reverse Engineering

View full text Add to dashboard Cite

This paper describes a reengineering tool for automaticaltv transforming a system composed of procedural programs into a functionally comparable object-oriented system.The transformation into the object-oriented form locates redundant, duplicated and similar data and processes and abstracts them into classes and methods. The transformation process and the abstract object-oriented model are described in mflcient delail to illustrate the reengineering technique and approach.

show abstract

Saving legacy with objects

Cited by 28 publications

References 4 publications

Automated Translation of Java Source Code to Eiffel

Automated Translation of Java Source Code to Eiffel

Reengineering of old systems to an object-oriented architecture

Reengineering procedural into object-oriented systems

Contact Info

Product

Resources

About