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
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
In today's changing environments, organizational design must take into account; the fact that business processes are incomplete by nature and that they should be managed in such a way that they do not restrain human intervention. In this paper we propose the embedding of social software features, such as collaboration and wiki-like features, in the modeling and execution tools of business processes. These features will foster people empowerment in the bottom-up design and execution of business processes. We conclude this paper by identifying some research issues about the implementation of the tool and its methodological impact on Business Process Management.

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
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
Documentation is an important part of the captured knowledge of a software project, providing a flexible and effective way of recording informal contents. However, maintaining documentation's consistency requires a considerable effort. Existing solutions encompass different tools and approaches that support the process of creating, evolving and using documents and other artifacts derived from the software development process. Based on existing literature and expertise, we have identified the key problems and solutions for documentation consistency. In concrete, four distinct patterns and their relations were identified, which are here described - Information Proximity, Co-Evolution, Domain-Structured Information and Integrated Environment. Copyright 2009.