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
Navigating and querying code without getting lost
Proceedings of the 2nd international conference on Aspect-oriented software development
Representing concerns in source code
Representing concerns in source code
Mylar: a degree-of-interest model for IDEs
Proceedings of the 4th international conference on Aspect-oriented software development
Using structural context to recommend source code examples
Proceedings of the 27th international conference on Software engineering
Concern modeling in the concern manipulation environment
MACS '05 Proceedings of the 2005 workshop on Modeling and analysis of concerns in software
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
FrUiT: IDE support for framework understanding
eclipse '06 Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange
Guidance through active concerns
eclipse '06 Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange
Automatically locating framework extension examples
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Hi-index | 0.00 |
Program documentation is often incomplete and out of date due to its tediousness and perceived low value. This requires evolution tasks to be preceded by time-consuming exploration. In this paper, we explore a concern-oriented approach to documentation that focuses on the code artifacts and their relationships to make the process of creating and using program documentation more efficient. As opposed to traditional documents or tutorials, guides created using this approach are interactive, almost wordless and automatically maintain implementation examples. We also present the rationale and the architecture of Mismar, a toolset tightly integrated in the Eclipse environment and implementing this approach. Moreover, since program documentation involves different artifact types, Mismar was build from the ground up to be extensible, and to support artifacts written in multiple languages or modeling approaches.