A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2010; you can also visit the original URL.
The file type is application/pdf
.
Filters
Identifying procedural structure in Cobol programs
1999
Software engineering notes
In this paper, we show how a Cobol program can be efficiently transformed into a semantically-equivalent procedurally well-structured representation, in which conventional procedures (i.e., with the usual ...
The principal control-flow abstraction mechanism in the Cobol language is the PERFORM statement. ...
Our Approach Given a Cobol program, numerous procedurally well-structured representations are possible, via a variety of analyses. ...
doi:10.1145/381788.316163
fatcat:k6or2mrzybandbadctjnuuamqy
Identifying procedural structure in Cobol programs
1999
Proceedings of the 1999 ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering - PASTE '99
In this paper, we show how a Cobol program can be efficiently transformed into a semantically-equivalent procedurally well-structured representation, in which conventional procedures (i.e., with the usual ...
The principal control-flow abstraction mechanism in the Cobol language is the PERFORM statement. ...
Our Approach Given a Cobol program, numerous procedurally well-structured representations are possible, via a variety of analyses. ...
doi:10.1145/316158.316163
dblp:conf/paste/FieldR99
fatcat:xnshkz5prvfehkatpitkbuvntq
Design of a Reverse Engineering Model (A Case Study of Cobol to Java Migration)
2013
International Journal of Computer Applications
The Java is pure object-oriented, where as the COBOL is procedure oriented programming language. The legacy systems designed earlier needs the huge amount of maintenance. ...
Most of the legacy systems designed using COBOL, as it is a programming language. On the other hand, today Java widely used programming language for designing systems. ...
The procedure begins with identifying candidate classes by analyzing global data structures and function formal limits in a single source code file. ...
doi:10.5120/13734-1532
fatcat:fflg6qteu5c3fhnys5v5vt46ea
The COBOL jigsaw puzzle: Fitting object-oriented and legacy applications together
1997
IBM Systems Journal
This paper examines the use of object wrappers and introduces two other types of wrappers, the procedural wrapper and the combination wrapper, for practical use with COBOL legacy applications. ...
However, object wrappers do not always solve the interoperability problem for COBOL legacy applications. ...
To write the subclasses, or child programs: 1. Identify all the different data structures that exist in the legacy program. Each data structure defines a subclass. ...
doi:10.1147/sj.361.0049
fatcat:ry2yf5trg5g63hnabgev3nnzfq
Extracting Business Rule from existing COBOL programs for Redevelopment
2019
International Journal Of Engineering And Computer Science
into a unified documentation describing the data, decision and procedural flow of each program slice. ...
The paper describes an industrial business study carried out to regain the business knowledge embedded in a legacy COBOL application. ...
Much effort has been invested in the re-engineering of COBOL code to transform programs written in COBOL-74 to COBOL-85 [Sneed and Jandrasics. 1987 ]. ...
doi:10.18535/ijecs/v8i05.4317
fatcat:nl7tz343zjfzxgxz7cuc52ncti
Page 27 of Journal of Systems Management Vol. 29, Issue 2
[page]
1978
Journal of Systems Management
— 6C7
Figure 2
STRUCTURED COBOL PROGRAM
PROCEDURE DIVISION. ...
These techniques are normally applied in analyzing problem program (ocx series) Abends. The techniques and illustrations are based
FEBRUARY e 1978
UNSTRUCTURED COBOL PROGRAM PROCEDURE DIVISION. ...
Using Aspect Orientation in Understanding Legacy COBOL Code
2007
Computer Software and Applications Conference (COMPSAC) Proceedings of the IEEE International
Furthermore, the approach for aspect location and operations in COBOL code is presented. Program slicing technique is adopted to locate aspect code from large COBOL systems. ...
This paper reports our experience to date on the application of aspect-oriented program understanding in COBOL code, and more future work will be carry out shortly. ...
of those procedures in program P. ...
doi:10.1109/compsac.2007.232
dblp:conf/compsac/PuZKXY07
fatcat:24nneqfuz5acdi46aof56lc7gi
Page 65 of Journal of Research and Practice in Information Technology Vol. 17, Issue 2
[page]
1985
Journal of Research and Practice in Information Technology
But there is no difficulty in writing well-structured Cobol programs. The programmer simply avoids the THRU option of PERFORM. ...
In my opinion, its benefits are illusory. A potential gain is that the last-in-first-out discipline forces programs to be well- structured. ...
Extracting business rules from COBOL: A model-based framework
2013
2013 20th Working Conference on Reverse Engineering (WCRE)
In this sense, the goal of this paper is to facilitate the comprehension of legacy systems (in particular COBOL-based ones) by providing a model driven reverse engineering framework able to extract and ...
This logic implements the business rules in place in the organization, which must be continuously adapted in response to market changes. ...
COBOL BASIC CONCEPTS COBOL is a procedural language that structures programs in 4 divisions: identification, environment, data and procedure divisions. ...
doi:10.1109/wcre.2013.6671316
dblp:conf/wcre/CosentinoCABP13
fatcat:2mny4mj5pvdlrml2ll346qdtmq
A macro facility for cobol
[chapter]
1978
Lecture Notes in Computer Science
The British Computer Society's COBOL Specialist Group has designed a Macro Facility for COBOL for the purpose of permitting users to obtain a more up-to-date portable version of COBOL. ...
Acknowledgements The macro facility described in this paper was designed by a working group consisting The opinions expressed in this paper are not necessarily shared by those named above. ...
Firstly, it is kept up-to-date: the current version of CODASYL COBOL [I] contains extensive facilities for Database Handling, Telecommunications and Structured Programming. ...
doi:10.1007/3-540-08934-9_91
fatcat:v6iqzvzx3za3xc5ysmyfuqlncm
Graph-based tools for re-engineering
2002
Journal of Software Maintenance and Evolution Research and Practice
REforDI is fed with the source code of an application written in COBOL 85 (or COBOL 77). The source code is parsed and analyzed, resulting in a graph representation aiding program understanding. ...
While modern programming languages such as Java and C++ are becoming more and more widespread, a considerable amount of code being operational today is still written in FORTRAN and COBOL. ...
in Education, which was carried out in cooperation with two German companies: Aachener und Münchener Informatik-Service AG (AMI) and Gebühreneinzugszentrale (GEZ). ...
doi:10.1002/smr.254
fatcat:mo4d2eghazftracb2ir7fw4bci
Re-engineering legacy Cobol programs
1998
Communications of the ACM
Finally, we can trace every procedure call from the original Cobol program to the OO program. ...
The inability to pass parameters to called procedures in Cobol limits their generality and makes the entire program the unit of modularity. ...
doi:10.1145/276404.276410
fatcat:vpxiksqrunhntmiueeabaaxdm4
Mini-COBOL
1969
Computer journal
This resulted in a simple and straightforward structure in the Procedure Division, entirely compatible except for the verb WRITE. ...
It has also been biased, where possible, towards the inclusion of features demonstrating the basic principles of COBOL and of clear and well structured programs. ...
This Mini-COBOL specification, however, does not aim at providing an efficient object program, but rather at providing a tool for teaching a basic understanding of the main principles of COBOL. ...
doi:10.1093/comjnl/12.3.208
fatcat:kdewscog6zcqtltrsq7xzo2fie
Page 84 of Journal of Research and Practice in Information Technology Vol. 16, Issue 3
[page]
1984
Journal of Research and Practice in Information Technology
Unlike earlier stan- dards and many implementations, both COBOL 74 and COBOL 83 require a CALL statement to use a literal or identifier to define the name of the called program. ...
The term “export” in this con- text means a positive action which makes otherwise invisible identifiers visible to another program. Exportation is thus selective. ...
A Toolchain for Metrics-based Comparison of COBOL and Migrated Java Systems
2012
Softwaretechnik-Trends
Migrating COBOL legacy systems to Java results in functional equivalent systems expressed in the new language, while the programming paradigm remains that of the old systems. ...
This paper presents an integrated toolchain enabling metricsbased comparisons of original and translated systems to substantiate or refute this hypothesis, characterize the change in code quality, and ...
Tools can map a COBOL program to a functional equivalent Java program, but usually cannot introduce an object-oriented design into a program conceived procedural (cf. Terekhov and Verhoef [7] ). ...
doi:10.1007/bf03323484
fatcat:haazhsfl3vde5fgzrubiq4jrm4
« Previous
Showing results 1 — 15 out of 2,386 results