Error messages: the neglected area of the man/machine interface
Communications of the ACM
Knowledge-Based Program Analysis
IEEE Software
Study of novice programmers using Eclipse and Gild
eclipse '05 Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange
Understanding the value of program analysis tools
Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companion
Compiler error messages: what can help novices?
Proceedings of the 39th SIGCSE technical symposium on Computer science education
A report on a survey and study of static analysis users
DEFECTS '08 Proceedings of the 2008 workshop on Defects in large software systems
Why don't software developers use static analysis tools to find bugs?
Proceedings of the 2013 International Conference on Software Engineering
| Hi-index | 0.00 |
Program analysis tools are available to make developers' jobs easier by automating tasks that would otherwise be performed manually or not at all. To communicate with the developer, these tools use notifications which may be textual, visual, or a combination of both. Research has shown that these notifications need improvement in two areas: expressiveness and scalability. In the research described here, I begin an investigation into the expressiveness and scalability of existing program analysis tools and potential improvements in expressiveness and scalability in and across these tools for novice and expert developers. I begin with novices because I have conducted research with expert developers which found that both expressiveness and scalability play a part in an expert's ability to effectively use a subset of program analysis tools.