Campus Event Calendar
Event Entry
What and Who
Object Usage Models
Andrzej Wasylkowski
Ringvorlesung
AG 1, AG 2, AG 3, AG 4, AG 5, SWS
Public Audience
English
Note: We use this to send email in the morning.
Date, Time and Location
Thursday, 30 November 2006
13:00
60 Minutes
E1 3 - Hörsaal Gebäude
016
Saarbrücken
Abstract
Many (if not all) programs have bugs.Typically before the program is released, it is tested as thoroughly as possible, but this resembles looking for a needle in a haystack. We usually have no clue, where the bugs could be, and so testing is done in a very random manner. This in turn causes people to overlook bugs, which are then discovered by the users and this is something we want to avoid. We need a tool that could point us to program fragments that are likely to be buggy.
We have developed an approach to extract from a program information about the way classes are being used. To represent this information we use so-called "object usage models". Each object usage model represents the part of the program control flow that is relevant to the object (that is, instance of some class) being modeled. Based on those models we are able to find in a program such usages of objects that differ from standard usages exhibited by the program in question.
Our tool has been implemented and preliminarily tested on the newest version of AspectJ, a specialized Java compiler. We discovered the models to be helpful in trying to understand the # program. We have found one previously unknown bug in AspectJ and several places, where the code violated informal conventions established by the programmers.
We have developed an approach to extract from a program information about the way classes are being used. To represent this information we use so-called "object usage models". Each object usage model represents the part of the program control flow that is relevant to the object (that is, instance of some class) being modeled. Based on those models we are able to find in a program such usages of objects that differ from standard usages exhibited by the program in question.
Our tool has been implemented and preliminarily tested on the newest version of AspectJ, a specialized Java compiler. We discovered the models to be helpful in trying to understand the # program. We have found one previously unknown bug in AspectJ and several places, where the code violated informal conventions established by the programmers.
Contact
--email hidden
passcode not visible
logged in users only
Veronika Weinand, 11/28/2006 09:39
Veronika Weinand, 11/21/2006 10:39
Silke Wagner, 11/06/2006 16:17
Veronika Weinand, 11/06/2006 14:39
Veronika Weinand, 11/03/2006 12:21
Veronika Weinand, 10/25/2006 15:08
Veronika Weinand, 10/24/2006 12:47
Veronika Weinand, 10/23/2006 15:06
Veronika Weinand, 10/19/2006 14:54
Veronika Weinand, 10/16/2006 17:07
Veronika Weinand, 11/21/2006 10:39
Silke Wagner, 11/06/2006 16:17
Veronika Weinand, 11/06/2006 14:39
Veronika Weinand, 11/03/2006 12:21
Veronika Weinand, 10/25/2006 15:08
Veronika Weinand, 10/24/2006 12:47
Veronika Weinand, 10/23/2006 15:06
Veronika Weinand, 10/19/2006 14:54
Veronika Weinand, 10/16/2006 17:07