Restructuring programs by tucking statements into functions

Lakhotia, Arun; Deprez, Jean-Christophe

doi:10.1016/s0950-5849(98)00091-3

Cited by 69 publications

(46 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…That means it is predominantly method extraction. Since Program Slicing has been used for method extraction [3,4,6,19,21,22] and we can say that it can be used for aspect extraction as well.…”

Section: Questions and Discussionmentioning

confidence: 99%

Application of Program Slicing for Aspect Mining and Extraction � A Discussion

Katti¹,

Bingi²,

Chavan³

2012

IJCA

View full text Add to dashboard Cite

Aspect Orientation removed the code scattering and tangling drawback of Object Orientation by encapsulating the cross cutting concerns into their own modules called Aspects. It is gaining popularity these days as lot of languages, frameworks, programming and modeling tools already support aspects and developers have started to embrace these. But there exists lot of legacy object oriented code that needs to be moved to aspects as this makes cross cutting concerns easy to change (localized changes would be enough), test, extend, more comprehensible, etc. Converting it manually is tedious and there exist different techniques that semi automate the process making the maintenance engineer"s job easier. Another approach to the automation process using program slicing is also possible. In this paper, we discuss aspect mining and extraction from program slicing point of view.

show abstract

Section: Questions and Discussionmentioning

confidence: 99%

Application of Program Slicing for Aspect Mining and Extraction � A Discussion

Katti¹,

Bingi²,

Chavan³

2012

IJCA

View full text Add to dashboard Cite

show abstract

“…Many slicing algorithms have been proposed in the literature and used in their original or slightly modified form for method extraction [2,3,4,5,7]. All these algorithms first convert the program into some alternative representation and then apply some correctness preserving transformations on it to produce slice and its complement.…”

Section: Introductionmentioning

confidence: 99%

Program Slicing for Refactoring: Static Slicer using Dynamic Analyser

Katti¹,

Terdal²

2010

IJCA

View full text Add to dashboard Cite

Refactoring is the process of changing the code of the software such that its internal design is improved without altering its observable behavior. Method Extraction is the process of separating out a subset of method's statements into another method and replacing their occurrence in the original method with a call to this new method. Method extraction is a classical problem to improve the modularity of the system and is used in extracting methods from long procedural programs. It can also be used in extracting aspects from object oriented code. Thus it makes the software easier to understand, maintain and reusable. In the earlier days of method extraction, programmer selected a random set of statements for extraction which was made more sensible by specifying the variables of interest and separating the statements concerning them into a method. Thus, program slicing became part of method extraction. Many slicing algorithms exist in the literature; they first convert the program into some alternative representation and then apply some correctness preserving transformations on it to produce slice and its complement. This process was identified to be expensive and an algorithm was proposed to act directly on the source code. It statically analyzes the source code to produce the slice but fails to handle dynamic constructs like aliasing and polymorphism effectively. To overcome this limitation we propose a new slicing algorithm that dynamically analyzes source code to produce static slices. It exploits the behavior preservation requirement of refactoring and uses the data collected during testing, which we perform prior to refactoring, for slicing. This algorithm suits better to the refactoring domain.

show abstract

“…Some of the techniques in the first category focus on compressing assembly code by detecting duplicated fragments and extracting them into procedures [24,6,7], while others concern procedure extraction in source code [9,16,10]. The problem solved in the second category (eliminating gotos) is different from ours; however, our technique of using the variable exitKind to handle exiting jumps bears resemblance to their techniques.…”

Section: Contributions Over Previous Workmentioning

confidence: 99%

“…The first step is context-dependent; it can be performed either by the programmer, or by program analysis tools, such as [17,4,11]. The third step is essential, but the main issue (determining what the parameters to the new procedure should be and how they should be used), is straightforward (e.g., discussed in [9,16]). The chief contributions of this paper are:…”

Section: Introductionmentioning

confidence: 99%