Abstract
This paper presents an approach to domain models validation with customers, end users and other stakeholders. From an early system model that represents the main domain (or business) entities in a UML class diagram, with classes, relationships, attributes and constraints, it is automatically generated an interactive form-based application prototype supporting the basic CRUD operations (create, retrieve, update and delete). The generated form-based user interface provides some features that are derived from the model's constraints and increase the prototype usability. This prototype allows the early validation of core system models, and can also be used as a basis for subsequent developments. The prototype generation process follows a model-driven development approach: the domain model, conforming to a defined domain meta-model, is first transformed to an application model, conforming to a defined application meta-model, based on a set of transformation rules; then a generator for a specific platform produces the executable files (currently, XUL and RDF files).

Abstract

Abstract
The use of wikis in software engineering dates back to 1995, when Ward Cunningham created the first ever wiki as a platform for discussing patterns and software development efforts. The simplicity and effectiveness of wikis as a medium for collaborative authoring has lead to their vast popularity across many domains. The Wikis for Software Engineering (Wikis4SE) workshop aims at bringing together researchers, practitioners, and enthusiasts interested in exploring the potential of wikis as an effective tool to support software engineering activities. It serves as a forum for presenting new ideas and tools, and reporting on experiences, best practices, and newly discovered problems. Based on lessons learned and obstacles identified, a research agenda will be defined with key opportunities and challenges. © 2008 ACM.

Abstract
A large part of the software development effort is typically spent on maintenance and evolution, namely on adding new and unanticipated features. As aspect-oriented programming (AOP) can be easily used to compose software in non-planned ways, many researchers are investigating AOP as a technique that can play an important role in this particular field. However, unexpected interactions between aspects are still a major problem that compromise AOP's applicability, especially in large projects where many developers, often including new team members, are involved in the process. This paper addresses the issues of aspect conflicts and interactions and proposes a technique to help compose aspects in a disciplined way using a test-driven development approach. A simple example for a banking system helps on illustrating the technique. © 2008 ACM.

Abstract
Learning and understanding a framework is usually a major obstacle to its effective reuse. Before being able to use a framework successfully, users often go through a steep learning curve by spending a lot of effort understanding its underlying architecture and design principles. This is mainly due to users having to understand not only single isolated classes, but also complex designs of several classes whose instances collaborate for many different purposes, and using many different mechanisms. In addition, frameworks are also full of delocalized plans, and use inheritance and delegation intensively, which makes their design more difficult to grasp. How to obtain the necessary information from the framework itself and its accompanying documentation is the main problem with framework understanding. Considering its importance, this paper presents an initial attempt to capture, in the pattern form, a set of proven solutions to recurrent problems of understanding frameworks. The fundamental objective of this work is to help non-experts on being more effective when trying to learn and understand object-oriented frameworks. © 2008 is held by the author(s).

Abstract