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
Object oriented decomposition is the most successful decomposition strategy used nowadays. But a single decomposition strategy cannot capture all aspects of a concept. Roles have been successfully used to model the different views a concept may provide but, despite this, roles have not been used as building blocks. Roles are mostly used to extend objects at runtime. In this paper we propose roles as a way to compose classes that provides a modular way of capturing and reusing those aspects that fall outside a concept's main purpose, while being close to the OO approach. We present how roles can be made modular and reusable. We also show how we can use roles to compose classes using JavaStage, a java extension that support roles To validate our approach we developed generic and reusable roles for the Gang of Four patterns. We were able to develop reusable roles for 10 out of 23 patterns, which is a good outcome.

Abstract
Good documentation is crucial for the success of frameworks. In this research, a new documenting approach is proposed combining existing document styles in a kind of "minimalist" framework manual with a special emphasis on framework understandability and usability, rather than on describing framework design. Benefits and drawbacks are evaluated from frameworks of different domains and complexity. © 2000 ACM.

Abstract
Roles are not a new concept, but they have been used in two different ways: as modeling concepts in a static view and as instance extensions in a dynamic view. For these views only the dynamic offers supporting languages. The static view, although proving the utility of roles in modeling, does not offer a programming language that allows developers to use roles all the way from modeling to programming. We try to overcome this by presenting our role language JavaStage, based on the Java language. We do this by designing and implementing a simple framework and then compare the results with its OO equivalent. Our results show that static roles are in fact useful when used in code and that JavaStage features expand role reuse.

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
Using a wiki in software engineering settings dates back to its first usage in 1995. In fact, that was the motivation for Ward Cunningham to create the first wiki. Due to its simplicity, attractiveness and effectiveness for collaborative authoring and knowledge management, wikis are now massively disseminated and used in different domains. This workshop focuses on wikis for the specific domain of software engineering. It aims at bringing together researchers, practitioners, and enthusiasts interested on researching, exploring and learning how wikis can be improved, customized and used to better support software projects. Based on lessons learned and obstacles identified, a research agenda will be defined with key opportunities and challenges. © 2011 Authors.