N degrees of separation: multi-dimensional separation of concerns
Proceedings of the 21st international conference on Software engineering
What programmers really want: results of a needs assessment for SDK documentation
Proceedings of the 20th annual international conference on Computer documentation
Mylar: a degree-of-interest model for IDEs
Proceedings of the 4th international conference on Aspect-oriented software development
DocWizards: a system for authoring follow-me documentation wizards
Proceedings of the 18th annual ACM symposium on User interface software and technology
ConcernMapper: simple view-based separation of scattered concerns
eclipse '05 Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange
Presentations by Programmers for Programmers
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Mismar: A New Approach to Developer Documentation
ICSE COMPANION '07 Companion to the proceedings of the 29th International Conference on Software Engineering
Aiding evolution with concern-oriented guides
Proceedings of the 3rd workshop on Linking aspect technology and evolution
SmartTutor: Creating IDE-based interactive tutorials via editable replay
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Hi-index | 0.00 |
Producing usable documentation has always been a tedious task, and even communicating important knowledge about a system among collaborators is difficult. This paper describes an approach to creating documentation in the form of guides, which encapsulate passive information about important tasks along with active steps to be followed. The approach is concern-based, and introduces active steps into traditionally passive concerns. A developer can begin by creating a concern that identifies elements of importance in the context of a task, which, we believe, is easier and more natural than trying to formulate a process up front. S/he can then easily create a guide to the task based on this concern, and export it. Other developers can follow the guide, and, as they do so, their results are recorded as examples for future reference. As an early step towards validation, we created a guide for the complex task of creating an Eclipse editor.