Abstract
Model-driven engineering approaches aim at avoiding productivity, model quality and model maintenance problems that arise when models are used for documentation only, by generating executable applications from models. However, in many cases, the level of detail of the models needed to generate complete applications is too much or only effective for specific domains. For those cases where it is not practical to build complete models and generate complete applications from them, we propose a lightweight approach, applicable at different levels (unit, integration and system testing), that combines partial application generation from structural models with test generation from partial behavioral models. To demonstrate the approach, we developed a plug-in that adds to the code generation capabilities of an existing UML modeling tool, the capability of generating executable tests from sequence diagrams acting also as parameterized test scenarios, including some novel features as compared to existing model-based testing tools.

Abstract
CMMI practices can be poorly implemented leading to weak performance gain. SCAMPI verifies model compliance but not performance. Hence, a framework to evaluate the quality of implementation of each practice, based on compliance and performance results, will prevent poor implementation, locate and fix problems, and ultimately achieve better results. In this paper we propose such a framework, based on a combination of leading and lagging indicators measuring compliance, efficiency and efficacy. © 2012 Springer-Verlag.

Abstract
Several approaches exist to automatically derive test cases that check the conformance of the implementation of abstract data types (ADTs) with respect to their specification. However, they lack support for the testing of implementations of ADTs defined by generic classes. In this paper, we present a novel technique to automatically derive, from specifications, unit test cases for Java generic classes that, in addition to the usual testing data, encompass implementations for the type parameters. The proposed technique relies on the use of Alloy Analyzer to find model instances for each test goal. JUnit test cases and Java implementations of the parameters are extracted from these model instances. © 2012 Springer-Verlag.

Abstract

Abstract
This paper presents an approach to analyse the application of tactics in architectural patterns. We define and illustrate the approach using ARCHERY, a language for specifying, analysing and verifying architectural patterns. The approach consists of characterising the design principles of an architectural pattern as constraints, expressed in the language, and then, establishing a refinement relation based on their satisfaction. The application of tactics preserving refinement ensures that the original design principles, expressed themselves as constraints, still hold in the resulting architectural pattern. The paper focuses on fault-tolerance tactics, and identifies a set of requirements for a semantic framework characterising them. The application of tactics represented as model transformations is then discussed and illustrated using two case studies.

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.