Tracing distributed systems executions using AspectJ

Briand, Lionel C.; Labiche, Yvan; Leduc, Johanne

doi:10.1109/icsm.2005.96

Cited by 12 publications

(26 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…OVATION; TPTP* preliminary; user feedback general understanding [15] SCENE* preliminary software reuse [6], [16] ISVIS* case study architecture reconstruction, feature location [17], [18] SCED; SHIMBA case study debugging; various comprehension tasks [19] FORM case study detailed understanding; distributed systems [20] JAVAVIS preliminary; user feedback educational purposes; detailed understanding [21], [4], [22], [23] SEAT small case studies; user feedback general understanding [24], [25], [26], [27] SCENARIOGRAPHER multiple case studies detailed understanding; distributed systems; feature analysis; large-scale software [28], [29], [30] small case study quality control; conformance checking [10] multiple case studies general understanding [31] case study trace comparison; feature analysis [32] case study feature analysis [33] case study architecture reconstruction; conformance checking; behavioral profiles [34] TRACEGRAPH industrial case study feature analysis [35], [36] SDR; JRET* multiple case studies detailed understanding through test cases [37] FIELD; JIVE; JOVE multiple case studies performance monitoring; phase detection [38] --API understanding [39], [7] EXTRAVIS* multiple case studies fan-in/-out analysis; feature analysis; phase detection [40] OASIS user study various comprehension tasks [41] small case studies general understanding; wireless sensor networks March 8, 2010 DRAFT Cornelissen, Zaidman, van Deursen -A Controlled Experiment for Program Comprehension…”

Section: A Execution Trace Analysismentioning

confidence: 99%

A Controlled Experiment for Program Comprehension through Trace Visualization

Cornelissen

Zaidman

Deursen

2011

IIEEE Trans. Software Eng.

114

View full text Add to dashboard Cite

Software maintenance activities require a sufficient level of understanding of the software at hand that unfortunately is not always readily available. Execution trace visualization is a common approach in gaining this understanding, and among our own efforts in this context is EXTRAVIS, a tool for the visualization of large traces. While many such tools have been evaluated through case studies, there have been no quantitative evaluations to the present day. This paper reports on the first controlled experiment to quantitatively measure the added value of trace visualization for program comprehension.We designed eight typical tasks aimed at gaining an understanding of a representative subject system, and measured how a control group (using the Eclipse IDE) and an experimental group (using both Eclipse and EXTRAVIS) performed in terms of correctness and time spent. The results are statistically significant in both regards, showing a 22% decrease in time needed for the given tasks, and a 43% increase in correctness of the results for the group using trace visualization. Index TermsProgram comprehension, dynamic analysis, controlled experiment.B. Cornelissen is with the Software Improvement Group, A.J.

show abstract

Section: A Execution Trace Analysismentioning

confidence: 99%

A Controlled Experiment for Program Comprehension through Trace Visualization

Cornelissen

Zaidman

Deursen

2011

IIEEE Trans. Software Eng.

114

View full text Add to dashboard Cite

show abstract

“…Cheon and Avila (2010) use AspectJ to generate test cases for automating Java program testing by combining random testing and Object Constraint Language (OCL). Briand et al (2005)investigate use of AOP to gather information for program execution by abstracting design details related to thread and distributed communications. Using AOP, the program being tested need not modify, providing an advantage during regression testing.…”

Section: Aspect-based Testing Techniquementioning

confidence: 99%

“…Briand et al (2005) use AOP as instrumentation strategy to get necessary information at runtime. They have presented aspects to intercept method and constructor execution, remote method calls and executions and method control flow.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Observability using aspect-oriented programming for OO software testing

Meetei

Goel

Wasan

2011

Int J Syst Assur Eng Manag

View full text Add to dashboard Cite

Software testing is a process of executing software with the goal of finding errors. It is an important phase in the software development process. It still remains an art due to limitations in understanding of the principles of software. In this paper, we present a new approach to testing object-oriented software using aspect-oriented programming. We propose an aspect-based testing technique that facilitates observing internal details of execution at unit, integration and system levels, during testing of objectoriented software. Our technique adapts logging aspect, to suit the testing needs of object-oriented software. The logging aspect is introduced externally to the software under test, for observing the system's internal and external behavior. The internal execution details are stored in a log file for use during post-analysis. Test coverage reports are generated from the information gathered from the log file. It includes coverage at method, class, inheritance and dynamic binding levels.

show abstract

“…However, given a system implementation, it is also possible to reverse engineer sequence diagrams. These diagrams can be reverse engineered either statically [24] through an analysis of the program source or dynamically from program execution traces [19,4] or more recently by utilising aspect-oriented programming [3].…”

Section: Dynamic Sequence Diagramsmentioning

confidence: 99%

Ensuring behavioural equivalence in test-driven porting

Hennessy

Power

2006

Proceedings of the 2006 Conference of the Center for Advanced Studies on Collaborative Research - CASCON '06

View full text Add to dashboard Cite

In this paper we present a test-driven approach to porting code from one object-oriented language to another. We derive an order for the porting of the code, along with a testing strategy to verify the behaviour of the ported system at intra and inter-class level. We utilise the recently defined methodology for porting C++ applications, eXtreme porting, as a framework for porting. This defines a systematic routine based upon porting and unit-testing classes in turn. We augment this approach by using Object Relation Diagrams to define an order for porting that minimises class stubbing. Since our strategy is class-oriented and test-driven, we can ensure the structural equivalence of the ported system, along with the limited behavioural equivalence of each class. In order to extend this to integration-level equivalence, we exploit aspect-oriented programming to generate UML sequence diagrams, and we present a technique to compare such automatically-generated diagrams for equivalence. We demonstrate and evaluate our approach using a case study that involves porting an application from C++ to Java.

show abstract

Tracing distributed systems executions using AspectJ

Cited by 12 publications

References 8 publications

A Controlled Experiment for Program Comprehension through Trace Visualization

A Controlled Experiment for Program Comprehension through Trace Visualization

Observability using aspect-oriented programming for OO software testing

Ensuring behavioural equivalence in test-driven porting

Contact Info

Product

Resources

About