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
Object-oriented frameworks are a powerfitl reuse technique but they are also very complex and difficult to design. Framework's design aims at separating the invariant aspects across several applications in a domain - frozen spots - from the aspects that vary among applications and thus must be kept flexible and customizable - hot spots. The flexibility and extensibility provided at hot spots is usually achieved by following common design patterns, which are often hard and tiresome to identify without proper documentation. This paper proposes a reverse engineering approach to identify the design patterns used in a framework, using a high-level hot spot representation. The goals of this work include: researching a design approach that produces usable intermediate reuse information; defining a representation for design patterns based on meta-patterns; and developing a supporting tool to automate the reverse engineering process.

Abstract
The PhDOOS workshop differs from other workshops because the range of participants is much smaller (only PhD students) but has a wide scope of topics. Even with the limitation to PhD students in Object Oriented Systems, the presentations covered topics such as Generic Ownership, Generic Algorithms, Model Driven Architecture, Prediction of Size, QoS assessment, Frameworks, Teaching of Frameworks and Object Calculus. Several topics of shared interest were identified and targeted in separate discussion groups on a general theme on the future of object oriented programming. As the participants had various research interests covering very different parts of the OO spectrum, we can confidently state that these topics reflect actual concerns and needs of the OO community, and emerge from its concrete needs. This document is to be complemented by a workshop proceedings online document which will contain the full versions of the presented papers.

Abstract
Although roles have been around for a long time they have not yet reached mainstream programming languages. The variety of existing role models may be a limiting factor. We believe that for roles to be widely accepted they must enhance code reuse. An outcome would be a library of roles. We present and discuss what we feel are the characteristics that a role model must have to enable reusable and playerindependent roles. In this paper we present our role model and JavaStage, a role language that extends Java, with examples of reusable roles. Finally, we present our steps towards the building of a role library, by presenting the roles developed from the analysis of the GoF Design Patterns. The results obtained, we developed roles for 10 of the 23 GoF patterns, are promising. © Copyright 2011 Carnegie Mellon University.