Tip #1: Don't Invite Pure Academics
The paper presents a tool (and process) called Prodet, to assists developer in navigating the code, in MSFT Visual studio. They validate their assumptions about the benefit of Prodet through an experiment.
The tool is nicely presented, the experiment rigorously documented and executed; the results are convincingly presented and supported by the statistical data. The results and conclusion are contrasted with existing literature.
A good paper indeed, well executed and documented. I just find it not very exciting, sorry.
Fortunately, there's a simple fix for this issue: invite those from industry. As you'll see from a quick glance at our PC, this is what we've tried to do. We have people like:
- Paul Anderson, the VP of Engineering at Grammatech, a company that was founded based on software engineering research,
- Marc Lambert, former CEO of Kalistick, a company that regularly interfaced with researchers and was was recently acquired by Coverity,
- Jacek Czerwonka, a member of the groundbreaking Tools for Software Engineers group at Microsoft, that is working at the boundary of research and practice,
- John Penix, who's innovating Google's testing tools.
Tip #2: Invite Some Industry-Leaning Academics
However, when inviting academics I'd still recommend inviting a certain type of academic, one with an industrial leaning or background. For instance, we have invited people like:
- David Hovemeyer, one of the original authors of FindBugs, a tool which has over 200K downloads,
- Magiel Bruntink, who spent four years in industry as a consultant prior to returning to academia,
- Joost Visser, who, in addition to being a professor, is also head of research at the Software Improvement Group, a consultancy.
Spread the Word: ICSME Industry Track
Submit to the ICSME Industry Track. Abstracts due Jun 19th.