Home

— filed under: personal page

Hello I am Adrian

Hi, I am Adrian a PhD Candidate at the University of Victoria under the supervision of Daniela Damian. I landed here in Victoria (City of Gardens) a couple of months ago and I'm starting to like it here. So if you want to talk to me just drop by my office or write me an email.
If you want to know more about me, either continue reading this page and my project pages or take a peak at my CV. Another source to learn what I am doing is my wordpress blog.

Program Time-line

Jan 2008 - until I'm done

Primary Research Topic

Code/Collaboration/Coordination/Communication Evolution

Past research has looked very intensively on how a software system evolves. But during the development and maintenance of a software system not only the code evolves but the people and their interaction does to. And capturing and analyzing this co-evolution comprises my primary research topic.

Research Interests

Global Software Development

"Smart people can be found allover the world. Let's use their skills!"

Mining Software Repositories

"The past will help us to build a better future. Let's mine the treasure!"

Software Quality

"Failures are nasty, especially when the customer complains about them."

Team collaboration

"Nowadays a single person is hardly able to build a complex software system alone. We all need to collaborate!"

Recommendation Systems

"Don't only say what's wrong but also recommend how to do it better."

My Research Projects

Learn more about Communication in Global Software Development.

Team communication has been studies quite extensively over the past few year, but research so far lacks a clear notion of communication quality. The goal of the Communication Quality Project, or short CQP, is to study team communication with respect to different quality aspect. Those aspects reach from Software Quality to Communication Delay in globally distributed software development. This means we do not only look at the communication but bring it into a context which is measurable and valuable to practitioners.

Learn more about Recommending People and Topics in Software Engineering.

Effective coordination within a project is one key factor to successful software projects. While research shows that communication structures can predict the outcome of an integration build, we would like to take a step further making recommendations about who should collaborate together. By leveraging information about artifact dependencies and communication among team members, we can recommend which gaps between dependencies and communication should be resolved to ensure a successful project.

Learn more about A Framework of Coordination Driven by Requirements.

Global software development (GSD) has created challenges in coordination and collaboration within software teams. The increase in distance among project team members brings about problems in communication and knowledge management of requirement-related information. This project aims to examine communication and knowledge management processes in the coordination necessary in the development of software requirements.

Learn more about Bug Report Quality.

To find out, we conducted a survey among APACHE, ECLIPSE, and MOZILLA developers. The analysis of the 156 responses shows that steps to reproduce and stack traces are most sought after, while inaccurate steps to reproduce and incomplete information pose the largest hurdles. This insight is helpful to design new bug tracking tools that guide reporters at providing more helpful information. Our CUEZILLA prototype is a such tool and provides reporters with feedback on the quality of new bug reports and recommends to add missing elements.

Learn more about Eclipse Bug Data

We have mined the Eclipse bug and version databases to map failures to Eclipse components. The resulting data set lists the defect density of all Eclipse components. As we demonstrate in three simple experiments, the bug data set can be easily used to relate code, process, and developers to defects. The data-set is publicly available for download and use.

Learn more about Predicting Component Failures.

In an empirical study of 52 ECLIPSE plug-ins, we found that the software design as well as past failure history, can be used to build models which accurately predict failure-prone components in new programs. Our prediction only requires usage relationships between components, which are typically defined in the design phase; thus, designers can easily explore and assess design alternatives in terms of predicted quality. In the ECLIPSE study, 90% of the 5% most failure-prone components, as predicted by our model from design data, turned out to actually produce failures later; a random guess would have predicted only 33%.