Migrating from COBOL to Java

Sneed, Harry M.

doi:10.1109/icsm.2010.5609583

Cited by 43 publications

(20 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several past works have already described how to migrate from a particular technology to another one using dedicated components and mappings, e.g., from procedural COBOL to object-oriented COBOL [31], from COBOL to Java [32], from COBOL to Java EE [33] or from Mainframe to Java EE [34]. These tools use specific and/or proprietary parsers, grammars, metamodels, etc.…”

Section: Specific Reverse Engineering Solutionsmentioning

confidence: 99%

A Model Driven Reverse Engineering Framework for Extracting Business Rules Out of a Java Application

Cosentino

Cabot

Albert

et al. 2012

Rules on the Web: Research and Applications

View full text Add to dashboard Cite

Context: Most companies, independently of their size and activity type, are facing the problem of managing, maintaining and/or replacing (part of) their existing software systems. These legacy systems are often large applications playing a critical role in the company's information system and with a non-negligible impact on its daily operations. Improving their comprehension (e.g., architecture, features, enforced rules, handled data) is a key point when dealing with their evolution/modernization.Objective: The process of obtaining useful higher-level representations of (legacy) systems is called reverse engineering (RE), and remains a complex goal to achieve. Socalled Model Driven Reverse Engineering (MDRE) has been proposed to enhance more traditional RE processes. However, generic and extensible MDRE solutions potentially addressing several kinds of scenarios relying on different legacy technologies are still missing or incomplete. This paper proposes to make a step in this direction.Method: MDRE is the application of Model Driven Engineering (MDE) principles and techniques to RE in order to generate relevant model-based views on legacy systems, thus facilitating their understanding and manipulation. In this context, MDRE is practically used in order to 1) discover initial models from the legacy artifacts composing a given system and 2) understand (process) these models to generate relevant views (i.e., derived models) on this system. Results: Capitalizing on the different MDRE practices and our previous experience (e.g., in real modernization projects), this paper introduces and details the MoDisco open source MDRE framework. It also presents the underlying MDRE global methodology and architecture accompanying this proposed tooling.Conclusion: MoDisco is intended to make easier the design and building of modelbased solutions dedicated to legacy systems RE. As an empirical evidence of its relevance and usability, we report on its successful application in real industrial projects and on the concrete experience we gained from that.

show abstract

Section: Specific Reverse Engineering Solutionsmentioning

confidence: 99%

A Model Driven Reverse Engineering Framework for Extracting Business Rules Out of a Java Application

Cosentino

Cabot

Albert

et al. 2012

Rules on the Web: Research and Applications

View full text Add to dashboard Cite

show abstract

“…[23] reports that some manual corrections of the automatically generated Java code were necessary during the translation of the code base, although these manual interventions were later implemented as an extension of the translator; anyway, [23] targets the translation of domain-specific applications and in fact does not support the full input language; the authors of [23] expect that tackling new applications will require extending the tool.…”

Section: Object-oriented Reengineeringmentioning

confidence: 99%

“…no Newcomb [20] Cobol-OOSM yes yes no 168KL yes ? no Mossienko [17] Cobol-Java yes no no 25KL yes no no Sneed [23] Cobol-Java yes yes no 200KL yes ? no Sneed [24] PL/I-Java yes yes no 10KL yes ?…”

Section: Object-oriented Reengineeringmentioning

confidence: 99%

“…no Sneed [24] PL/I-Java yes yes no 10KL yes ? no AutoOO C-Eiffel YES yes yes 750KL yes yes yes [20] and [23] are the only authors that report evaluations on code bases of significant size. [20]'s reengineering, however, produces OOSM (hierarchical object-oriented state LIMITATIONS Gall [9] requires assistance of human expert Jacobson [10] only defines a process; 3 case studies from industry Livadas [13] prototype implementation; no support for pointers Kontogiannis [11] sound reengineering for only about 36% of the source code Frakes [8] translation may change the behavior; requires expert judgement Fanta [6] requires expert judgement Newcomb [20] only a model is generated, no program code Mossienko [17] only partial automation; the translation may change the behavior Sneed [23] domain-specific translation Sneed [24] domain-specific translation Table 5.…”

Section: Object-oriented Reengineeringmentioning

confidence: 99%

See 1 more Smart Citation

Really Automatic Scalable Object-Oriented Reengineering

Trudel

Furia

Nordio

et al. 2013

ECOOP 2013 – Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. Even when implemented in a purely procedural programming language, properly designed programs possess elements of good design that are expressible through object-oriented constructs and concepts. For example, placing structured types and the procedures operating on them together in the same module achieves a weak form of encapsulation that reduces inter-module coupling. This paper presents a novel technique, and a supporting tool AutoOO, that extracts such implicit design elements from C applications and uses them to build reengineered object-oriented programs. The technique is completely automatic: users only provide a source C program, and the tool produces an object-oriented application written in Eiffel with the same input/output behavior as the source. An extensive evaluation on 10 open-source programs (including the editor vim and the math library libgsl) demonstrates that our technique works on applications of significant size and builds reengineered programs exhibiting elements of good object-oriented design, such as low coupling and high cohesion of classes, and proper encapsulation. The reengineered programs also leverage advanced features such as inheritance, contracts, and exceptions to achieve a better usability and a clearer design. The tool AutoOO is freely available for download.

show abstract

“…The complexity of programming language translation depends on the syntactic and semantic gap between the source and target languages. Significant research works have been done for developing PLTSs for generating Java code from various source programming languages [1,11,12,13,14]. An approach to compile Standard ML program to Java bytecode has been presented in [11].…”

Section: Programming Language Translation System (Plts)mentioning

confidence: 99%

Automatic Construction of Java Programs from Functional Program Specifications

Humayun

2015

ijacsa

View full text Add to dashboard Cite

Abstract-This paper presents a novel approach to construct Java programs automatically from the input functional program specifications on natural numbers from the constructive proofs of the input specifications using an inductive theorem prover called Poiti′n. The construction of a Java program from the input functional program specification involves two phases. The theorem prover is used to construct a higher order functional (HOF) program from the input specification expressed as an existential theorem. A set of mapping rules for a Programming Language Translation System (PLTS) is defined for translating functional expressions to their semantic equivalent Java code. The generated functional program is translated into intermediate Java code in the form of a Java function using the PLTS module. The generated Java function requires a small refinement to obtain a syntactically correct Java function. This Java function is encapsulated within a user defined Java class as a member operation, which is invoked within a Java application class consisting of a main function by creating objects resulting in an executable Java program. The constructed functional program and the generated Java program both are correct with respect to the input specification as they produce the same output.

show abstract

Migrating from COBOL to Java

Cited by 43 publications

References 17 publications

A Model Driven Reverse Engineering Framework for Extracting Business Rules Out of a Java Application

A Model Driven Reverse Engineering Framework for Extracting Business Rules Out of a Java Application

Really Automatic Scalable Object-Oriented Reengineering

Automatic Construction of Java Programs from Functional Program Specifications

Contact Info

Product

Resources

About