Abstract
Aspect Oriented Programming (AOP) is a powerful programming technique with the objective of improving modularity by encapsulating crosscutting concerns. The nature of AOP makes it prone to unexpected and harmful interactions between the different components of a system. The claim behind this PhD is that unit tests can be used to detect these interactions. In this paper we explain how these can be accomplished. A brief state of the art, work plan and a support tool (drUID) are also presented.

Abstract
Knowledge plays a key role in software development, and the effectiveness of how it is captured into artifacts, and acquired by other team members, is of crucial importance to a project's success. The life-cycle of knowledge in software development is derived from the adopted artifacts, practices and tools. These axes are here reviewed from a knowledge capture and acquisition perspective, and several open research issues are identified. The present work is being carried out in the context of the author's doctoral research. The research objectives are derived from the presented open issues, and a research strategy is outlined. Some preliminary results are also presented.

Abstract
Software development is a social activity. Teams of developers join together to coordinate their efforts to produce software systems. This effort encompasses the development of a shared understanding surrounding multiple artifacts throughout the process. Frameworks are a powerful technique for large-scale reuse, but its complexity makes them hard to understand and learn how to use. Developers resort to their colleagues for help and insight, at the expense of time and intrusion, as documentation is often outdated and incomplete. This paper presents an approach to harness this collective knowledge of the team through a collaborative environment. Teams can share, rank and recommend their learning knowledge without too much intrusion and follow best practices of framework understanding.

Abstract
In recent years, wikis have gained a prominent position among web-based collaboration platforms. However, special practices and adaptations are necessary; when applying wikis to software documentation and other development activities. The Wikis for Software Engineering (Wikis4SE) workshop aims to bring together researchers and practitioners interested in the use of wiki technology in this domain. It serves as a forum for presenting new ideas and tools, and reporting on experiences, best practices, and newly discovered problems. The Wikis4SE'2009 workshop builds on the success of prior events at WikiSym'2008 and WikiSym'2007.

Abstract
This paper reports on the implementation of a cooperative personal agenda integrated into a collaborative team environment. Concerning developers, traditional project management tools are mainly focused on tasks exclusively related to the project, failing to provide users with the capability of managing tasks not necessarily associated with the work at hand. Scheduling tasks from divergent domains towards a more efficient user planning becomes unfeasible. To overcome this inaptness, we have extended the Redmine platform with an agenda-like behaviour bearing in mind each user's individual constraints.

Abstract
Although some agile projects can succeed without producing any documentation at all, others may require a little more. Best practices of agile documentation suggest producing just enough documentation, at just the right time, and for just the right audience. It is not by coincidence that wikis and agility share goals of simplicity, flexibility, and open collaboration, thus being natural documentation tools to agile projects. When well integrated with other tools, wikis provide open collaboration, quick feedback, easy navigability, integrated contents, and a low barrier for developers to document. In this hands-on tutorial, participants will learn how to adapt and use a wiki to better support software projects. Copyright © 2009 ACM.