Smalltalk scaffolding: a case study of minimalist instruction
CHI '90 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
What programmers really want: results of a needs assessment for SDK documentation
Proceedings of the 20th annual international conference on Computer documentation
The relevance of software documentation, tools and technologies: a survey
Proceedings of the 2002 ACM symposium on Document engineering
A Reuse Case Perspective on Documenting Frameworks
APSEC '98 Proceedings of the Fifth Asia Pacific Software Engineering Conference
Pedagogical framework documentation: how to document object-oriented frameworks. an empirical study
Pedagogical framework documentation: how to document object-oriented frameworks. an empirical study
Identifying and addressing problems in object-oriented framework reuse
Empirical Software Engineering
Clustering for Generating Framework Top-Level Views
WCRE '07 Proceedings of the 14th Working Conference on Reverse Engineering
An empirical study of software developers' management of dependencies and changes
Proceedings of the 30th international conference on Software engineering
Automatically locating framework extension examples
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Human-Computer Interaction
CASCON '08 Proceedings of the 2008 conference of the center for advanced studies on collaborative research: meeting of minds
Improving API documentation usability with knowledge pushing
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
MAPO: Mining and Recommending API Usage Patterns
Genoa Proceedings of the 23rd European Conference on ECOOP 2009 --- Object-Oriented Programming
What Makes APIs Hard to Learn? Answers from Developers
IEEE Software
SpotWeb: Detecting Framework Hotspots and Coldspots via Mining Open Source Code on the Web
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Moving into a new software project landscape
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
The impact of social media on software engineering practices and tools
Proceedings of the FSE/SDP workshop on Future of software engineering research
Measuring API documentation on the web
Proceedings of the 2nd International Workshop on Web 2.0 for 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
Effective communication of software development knowledge through community portals
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Recovering traceability links between an API and its learning resources
Proceedings of the 34th International Conference on Software Engineering
Temporal analysis of API usage concepts
Proceedings of the 34th International Conference on Software Engineering
An Information Foraging Theory Perspective on Tools for Debugging, Refactoring, and Reuse Tasks
ACM Transactions on Software Engineering and Methodology (TOSEM)
Proceedings of the 2013 conference on Computer supported cooperative work
Creating a shared understanding of testing culture on a social coding site
Proceedings of the 2013 International Conference on Software Engineering
Detecting API documentation errors
Proceedings of the 2013 ACM SIGPLAN international conference on Object oriented programming systems languages & applications
Making the right decision: supporting architects with design decision data
ECSA'13 Proceedings of the 7th European conference on Software Architecture
Hi-index | 0.00 |
Developer documentation helps developers learn frameworks and libraries. To better understand how documentation in open source projects is created and maintained, we performed a qualitative study in which we interviewed core contributors who wrote developer documentation and developers who read documentation. In addition, we studied the evolution of 19 documents by analyzing more than 1500 document revisions. We identified the decisions that contributors make, the factors influencing these decisions and the consequences for the project. Among many findings, we observed how working on the documentation could improve the code quality and how constant interaction with the projects' community positively impacted the documentation.