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.

Abstract
Software development is a knowledge-intensive activity and frequently implies a progressive crystallization of knowledge, towards programming language statements. Although wikis have proved very effective, for both collaborative authoring and knowledge management, it would be useful for knowledge acquisition to better support team awareness and the recognition of knowledge structures, their relations, and their incremental evolution. This paper presents Weaki, a wiki prototype especially designed to support incremental formalization of structured contents that uses weakly-typed pages and type evolution. Weaki was applied in academic settings, by students of Software Engineering Labs. Copyright 2009 ACM.

Abstract
The Adaptive Object-Model (AOM) architectural pattern has been significantly documented in literature, but there is not yet enough documentation explaining how to design and build a full AOMbased system. A AOM framework would need to address an additional number of issues that go well beyond individual software patterns. In this paper, we propose a design for a AOM framework that addresses several issues of building AOM-based systems, namely: integrity, runtime co-evolution, persistency, user-interface generation, communication and concurrency. We borrow concepts from distributed version-control systems. We show how applications based on a concrete realization of this framework, called Oghma, helps to avoid a traditional two-level domain classification, reduces accidental complexity, and directly exposes confined model evolution to the end-user.