H. Fergen, P. Reichelt, and K. P. Schmidt. Bringing objects into COBOL: MOORE - a tool for migration from COBOL85 to object-oriented COBOL. In Proceedings of the Conference on Technology of Object-Oriented Languages and Systems (TOOLS 14), pages 435--448. Prentice-Hall, 1994.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....research has been carried out to extract business objects groups of data and associated operations from existing systems. These business objects are extracted by inspecting sources, documentation, or by asking the original developers to provide appropriate design information; see, e.g. [6, 2] for techniques supporting this process. Once they are extracted, they form the basis for an object oriented re implementation of the kernel of the system, a re implementation which thanks to the object orientation is far more flexible and easier to adapt. There are three important steps in the ....

H. Fergen, P. Reichelt, and K. P. Schmidt. Bringing objects into COBOL: MOORE - a tool for migration from COBOL85 to object-oriented COBOL. In Proceedings of the Conference on Technology of Object-Oriented Languages and Systems (TOOLS 14), pages 435--448. Prentice-Hall, 1994.

....redesign of Mortgage, a real life legacy COBOL system. For many business appliations written in COBOL, the data stored and processed represent the core of the system. For that reason, the data records used in COBOL programs are the starting point for many object identification approaches (such as [4, 15, 8]) Object identification typically consists of several steps: 1) identify legacy records as candidate classes; 2) identify legacy procedures or programs as candidate methods; 3) determine the best class for each method via some form of cluster analysis [11] This approach gives good results in ....

....proceed to map similar records to single classes, and find sections that can be associated as methods to these records. Their approach exhibits a high level of automation, and, as a consequence, results in an object oriented program that stays close to the original COBOL sources. Fergen et al. [8] describe the MOORE tool, which analyses COBOL 85 code, and provides the engineer with a set of class proposals. All records are given a weight, which indicates the number of references made to that record. Proposals for methods consist of COBOL paragraphs which use or modify one of the record ....

FERGEN, H., REICHELT, P., AND SCHMIDT, K. P. Bringing objects into COBOL: MOORE - a tool for migration from COBOL85 to object-oriented COBOL. In Proceedings of the Conference on Technology of Object-Oriented Languages and Systems (TOOLS 14) (1994), Prentice-Hall, pp. 435--448.

....code. For many legacy applications written in COBOL, the data stored and processed represent the core of the system. For that reason, many approaches that support identification of objects in legacy code take the data 2 structures (variables and records) as starting point for candidate classes [5, 11, 19]. Unfortunately, legacy data structures tend to grow over time, and may contain many unrelated fields at the time of migration. Furthermore, in the case of COBOL, there is an additional disadvantage: since COBOL does not allow type definitions, there no way to recognize, or treat, groups of ....

....13 not been applied successfully to COBOL systems [5] Other class extraction techniques have been developed specifically with languages like COBOL in mind. They take specific characteristics into account, such as the structure of data definitions, or the close connection with databases [5, 11, 19]. The interested reader is referred to [7] for more related work on object identification. Concept analysis has been proposed as a technique for analyzing legacy systems. Snelting [27, 28] provides an overview of various applications. Applications in this context include reengineering of software ....

H. Fergen, P. Reichelt, and K. P. Schmidt. Bringing objects into COBOL: MOORE - a tool for migration from COBOL85 to object-oriented COBOL. In Proceedings of the Conference on Technology of ObjectOriented Languages and Systems (TOOLS 14), pages 435--448. Prentice-Hall, 1994.

....the code. For many legacy applications written in COBOL, the data stored and processed represent the core of the system. For that reason, many approaches that support identification of objects in legacy code take the data structures (variables and records) as starting point for candidate classes [5, 11, 19]. Unfortunately, legacy data structures tend to grow over time, and may contain many unrelated fields at the time of migration. Furthermore, in the case of COBOL, there is an additional disadvantage: since COBOL does not allow type definitions,there no way to recognize, or treat, groups of ....

....have not been applied successfully to COBOL systems [5] Other class extraction techniques have been developed specifically with languages like COBOL in mind. They take specific characteristics into account, such as 8 the structure of data definitions, or the close connection with databases [5, 11, 19]. The interested reader is referred to [7] for more related work on object identification. Concept analysis has been proposed as a technique for analyzing legacy systems. Snelting [27, 28] provides an overview of various applications. Applications in this context include reengineering of software ....

H. Fergen, P. Reichelt, and K. P. Schmidt. Bringing objects into COBOL: MOORE - a tool for migration from COBOL85 to object-oriented COBOL. In Proceedings of the Conference on Technology of Object-Oriented Languages and Systems (TOOLS 14), pages 435--448. Prentice-Hall, 1994.

....in order to make them accessible via a more flexible architecture. In this section, we will look at object identification, that is, viewing existing systems in an object oriented manner. Several techniques for distilling object structures from legacy systems exist, covered, for example, in [20, 26, 11]. Most of these are based on system remodularization using some form of cluster analysis, of which a survey is provided by Lakhotia [16] In this section, we will work with another technique called concept analysis, which recently has been proposed as a tool for analyzing the modular structure of ....

H. Fergen, P. Reichelt, and K. P. Schmidt. Bringing objects into COBOL: MOORE - a tool for migration from COBOL85 to object-oriented COBOL. In Proceedings of the Conference on Technology of Object-Oriented Languages and Systems (TOOLS 14), pages 435--448. Prentice-Hall, 1994.

....several other, highly practical, reasons for renovation 7 [49] In short, finding objects 8 in legacy systems is a key research area in software renovation. The literature reports several systematic approaches to object identification, some of which can be partially automated, such as [42, 36, 18, 40, 26, 54]. These typically involve three steps: 1) identify legacy records as candidate classes; 2) identify legacy procedures or programs as candidate methods; 3) determine the best class for each method via some form of cluster analysis [34] There are several problems, however, with the application ....

....and maintenance monitoring. 2.4 Concept Analysis For many business applications written in COBOL, the data stored and processed represent the core of the system. For that reason, the data records used in COBOL programs are the starting point for many object identification approaches (such as [18, 40, 26]) These records are then in turn combined with procedures or programs, thus arriving at candidate classes. A common way of finding the desired combinations is to use cluster analysis [34] Recently, the use of mathematical concept analysis has been proposed as an alternative to the use of cluster ....

H. Fergen, P. Reichelt, and K. P. Schmidt. Bringing objects into COBOL: MOORE - a tool for migration from COBOL85 to object-oriented COBOL. In Proc. Conf. on Technology of Object-Oriented Languages and Systems (TOOLS 14), pages 435--448. Prentice-Hall, 1994.

....research has been carried out to extract business objects groups of data and associated operations from existing systems. These business objects are extracted by inspecting sources, documentation, or by asking the original developers to provide appropriate design information; see, e.g. [6, 2] for techniques supporting this process. Once they are extracted, they form the basis for an object oriented re implementation of the kernel of the system, a re implementation which thanks to the object orientation is far more flexible and easier to adapt. There are three important steps in the ....

H. Fergen, P. Reichelt, and K. P. Schmidt. Bringing objects into COBOL: MOORE - a tool for migration from COBOL85 to object-oriented COBOL. In Proceedings of the Conference on Technology of Object-Oriented Languages and Systems (TOOLS 14), pages 435--448. Prentice-Hall, 1994.

....redesign of Mortgage, a real life legacy Cobol system. For many business appliations written in Cobol, the data stored and processed represent the core of the system. For that reason, the data records used in Cobol programs are the starting point for many object identification approaches (such as [4, 15, 8]) Object identification typically consists of several steps: 1) identify legacy records as candidate classes; 2) identify legacy procedures or programs as candidate methods; 3) determine the best class for each method via some form of cluster analysis [11] This approach gives good results in ....

....proceed to map similar records to single classes, and find sections that can be associated as methods to these records. Their approach exhibits a high level of automation, and, as a consequence, results in an object oriented program that stays close to the original Cobol sources. Fergen et al. [8] describe the MOORE tool, which analyses Cobol 85 code, and provides the engineer with a set of class proposals. All records are given a weight, which indicates the number of references made to that record. No attempt is made at splitting up large records into smaller structures. Proposals for ....

FERGEN, H., REICHELT, P., AND SCHMIDT, K. P. Bringing objects into COBOL: MOORE - a tool for migration from COBOL85 to object-oriented COBOL. In Proceedings of the Conference on Technology of Object-Oriented Languages and Systems (TOOLS 14) (1994), Prentice-Hall, pp. 435--448.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC