Designing documentation to compensate for delocalized plans
Communications of the ACM
Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
API documentation from source code comments: a case study of Javadoc
SIGDOC '99 Proceedings of the 17th annual international conference on Computer documentation
Proceedings of the 27th international conference on Software engineering
Preliminary design of JML: a behavioral interface specification language for java
ACM SIGSOFT Software Engineering Notes
Shared waypoints and social tagging to support collaboration in software development
CSCW '06 Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
/*icomment: bugs or bad comments?*/
Proceedings of twenty-first ACM SIGOPS symposium on Operating systems principles
Notation and representation in collaborative object-oriented design: an observational study
Proceedings of the 22nd annual ACM SIGPLAN conference on Object-oriented programming systems and applications
Modular typestate checking of aliased objects
Proceedings of the 22nd annual ACM SIGPLAN conference on Object-oriented programming systems and applications
Proceedings of the 30th international conference on Software engineering
Empirical evidence of the benefits of workspace awareness in software configuration management
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
CASCON '09 Proceedings of the 2009 Conference of the Center for Advanced Studies on Collaborative Research
A search engine for finding highly relevant applications
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Exemplar: EXEcutable exaMPLes ARchive
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Architecting in software ecosystems: interface translucence as an enabler for scalable collaboration
Proceedings of the Fourth European Conference on Software Architecture: Companion Volume
Proceedings of the eighteenth ACM SIGSOFT international symposium on Foundations of software engineering
An empirical study on evolution of API documentation
FASE'11/ETAPS'11 Proceedings of the 14th international conference on Fundamental approaches to software engineering: part of the joint European conferences on theory and practice of software
Inferring specifications for resources from natural language API documentation
Automated Software Engineering
Analyzing temporal API usage patterns
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Controversy Corner: Preserving knowledge in software projects
Journal of Systems and Software
Recovering traceability links between an API and its learning resources
Proceedings of the 34th International Conference on Software Engineering
Detecting similar software applications
Proceedings of the 34th International Conference on Software Engineering
Synthesizing API usage examples
Proceedings of the 34th International Conference on Software Engineering
Temporal analysis of API usage concepts
Proceedings of the 34th International Conference on Software Engineering
Inferring method specifications from natural language API descriptions
Proceedings of the 34th International Conference on Software Engineering
What should developers be aware of? An empirical study on the directives of API documentation
Empirical Software Engineering
Understanding multilayered applications for building extensions
Proceedings of the 1st workshop on Comprehension of complex systems
dCloud: a document link provision cloud for software extension tasks
Proceedings of the International C* Conference on Computer Science and Software Engineering
Detecting API documentation errors
Proceedings of the 2013 ACM SIGPLAN international conference on Object oriented programming systems languages & applications
WHYPER: towards automating risk assessment of mobile applications
SEC'13 Proceedings of the 22nd USENIX conference on Security
Hi-index | 0.00 |
The documentation of API functions typically conveys detailed specifications for the benefit of interested readers. In some cases, however, it also contains usage directives, such as rules or caveats, of which authors of invoking code must be made aware to prevent errors and inefficiencies. There is a risk that these directives may be “lost” within the verbose text, or that the text would not be read because there are so many invoked functions. To address these concerns for Java, an Eclipse plug-in named eMoose decorates method invocations whose targets have associated directives. Our goal is to lead readers to investigate further, which we aid by highlighting the tagged directives in the JavaDoc hover. We present a lab study that demonstrates the directive awareness problem in traditional documentation use and the potential benefits of our approach.