Exploring software systems

Moonen, Leon

doi:10.1109/icsm.2003.1235430

Cited by 27 publications

(11 citation statements)

References 107 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…system has been proposed several times in more articles with some additions -we might therefore refer to either (van Deursen and Moonen, 1998), (van Deursen and Moonen, 2001), (van Deursen and Moonen, 2000), (Kuipers and Moonen, 2000) or (Moonen, 2003). 3 Syntax of types in (van Deursen and Moonen, 1998) oddly carries along the variable identifiers and picture format strings as is, leaving unclear how the type environment and type comparisons formally related to them.…”

Section: Comparisons and Motivationmentioning

confidence: 99%

“…As already mentioned, the legacy software analysis system thoroughly presented in (Moonen, 2003) • We translate COBOL into a simpler intermediate language as (van Deursen and Moonen, 1998) does, though without leaving out important language constructs whose behavior is relevant to typing real-world programs, such as goto, perform and perform-thru jump statements, call-by-reference procedure calls and if statements.…”

Section: Comparisons and Motivationmentioning

confidence: 99%

“…From the system first described in (van Deursen and Moonen, 1998) to its later refinement in (Moonen, 2003), giving informative types to COBOL variables seems to be a good way for automatically generating a basic tier of documentation of legacy software (van Deursen and Moonen, 2006) and is also a reliable starting point for further Program Understanding approaches (Kuipers and Moonen, 2000). These systems are quite sophisticate and rely on a number of complex side models and tools aimed to extract properties and information from COBOL programs at a high level of abstraction, thus inevitably omitting several details at a lower language and type level -e.g.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Type-Flow Analysis for Legacy Cobol Code

Spanò

Bugliesi

Cortesi

2011

Proceedings of the 6th International Conference on Software and Database Technologies

View full text Add to dashboard Cite

Abstract:Many business applications today still rely on COBOL programs written decades ago that are difficult to maintain and upgrade due to technological limitations and lack of experts in the language. Several companies have been trying to migrate their software base to modern platforms, but code translation is problematic because most business processes implemented are often no longer documented or even known. Applying existing Program Understanding techniques to COBOL could be a way for aiding IT specialists in charge of a porting -but useful raw information must be extracted from the source code in order to get these techniques yield to meaningful results. We believe that the types of variables used in programs are an important part of such raw information and we present an approach based on static analysis of types rather than data. Our system is capable of reconstructing the type-flow of a COBOL program throughout branches, jumps and loops in finite time and to track type information on reused variables occurring in the code. It also detects a number of error-prone situations, type mismatches or misuses and notifies that by means of messages annotated in the code along with types inferred for each variable occurrence.

show abstract

Section: Comparisons and Motivationmentioning

confidence: 99%

Section: Comparisons and Motivationmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Type-Flow Analysis for Legacy Cobol Code

Spanò

Bugliesi

Cortesi

2011

Proceedings of the 6th International Conference on Software and Database Technologies

View full text Add to dashboard Cite

show abstract

“…As fifty to ninety percent of the time, depending upon the system under consideration is spent on program understanding [6]. And reverse engineering is used as a significant aid to program comprehension and from there, recovery of higher level abstractions [4,7].…”

Section: Benefits To Software Engineering Studentsmentioning

confidence: 99%

Why teach reverse engineering?

Ali¹

2005

SIGSOFT Softw. Eng. Notes

View full text Add to dashboard Cite

Software reverse engineering is a fascinating discipline of software engineering. But it has failed to attract attention from students. Largely due to the facts that many universities around the world do not offer relevant courses, developing new software has always been considered superior then to maintain existing systems. But owing to the arrival of the internet, and client-server technology. Many organizations wish to adapt their existing systems. Thus the trend has somewhat shifted towards software evolution and maintenance. And now, more than ever before we need software engineers who can work effectively with legacy systems. In this paper I wish to highlight importance of incorporating Reverse engineering concepts and techniques into software engineering curriculum. I will start with a brief overview of reverse engineering concepts, and then discuss advantages of teaching reverse engineering.

show abstract

“…Our experiences show that some of the data needed for a reconstruction project can be easily gathered manually by: examining the directory structure, observing the behavior, or by exploring the source code for beacons that signal aspects of interest [24]. In our cases, this included for example the package structure and build relations for Duke's Bank and the verification of client-server separation in the Assessment case.…”

Section: Data Gatheringmentioning

confidence: 99%

Symphony: view-driven software architecture reconstruction

Deursen¹,

Hofmeister

Koschke

et al.

Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004)

Self Cite

View full text Add to dashboard Cite

C e n t r u m v o o r W i s k u n d e e n I n f o r m a t i c aSymphony: View-Driven Software Architecture Reconstruction ABSTRACT Authentic descriptions of a software architecture are required as a reliable foundation for any but trivial changes to a system. Far too often, architecture descriptions of existing systems are out of sync with the implementation. If they are, they must be reconstructed. There are many existing techniques for reconstructing individual architecture views, but no information about how to select views for reconstruction, or about process aspects of architecture reconstruction in general. In this paper we describe view-driven process for reconstructing software architecture that fills this gap. To describe Symphony, we present and compare different case studies, thus serving a secondary goal of sharing real-life reconstruction experience. The Symphony process incorporates the state of the practice, where reconstruction is problemdriven and uses a rich set of architecture views. Symphony provides a common framework for reporting reconstruction experiences and for comparing reconstruction approaches. Finally, it is a vehicle for exposing and demarcating research problems in software architecture reconstruction. ACM Computing Classification

show abstract

Exploring software systems

Cited by 27 publications

References 107 publications

Type-Flow Analysis for Legacy Cobol Code

Type-Flow Analysis for Legacy Cobol Code

Why teach reverse engineering?

Symphony: view-driven software architecture reconstruction

Contact Info

Product

Resources

About