No abstract

No abstract

The Model Driven Architecture (MDA) is a software design approach initiated by OMG. MDA is intended to support model driven engineering of software systems. Under MDA, the central artifacts are models which are transformed to include platform-specific detail, and eventually to source code. Therefore, model transformations play a key role in making MDA succeed. However, much less attention has been given to the need to ensure that model transformations generate the intended results. This paper explores validation and verification of model transformations using testing techniques. The paper describes the steps for generating test input models from a given set of transformation rules and the corresponding source metamodel(s). The process of testing model transformations has been implemented in a prototype tool that is built using the Eclipse Modeling Framework (EMF). 19th Australian Conference on Software Engineering 1530-0803/08 $25.00

Design patterns are typically defined imprecisely using natural language descriptions with graphical annotations. It is also common to describe patterns using a concrete design example with implementation details. Several approaches have been proposed to describe design patterns abstractly based on role concepts. However, the notion of role differs in each approach. The behavioral aspects of patterns are not addressed in the role-based approaches. This paper presents a rigorous approach to describe design patterns based on role concepts. Adopting metamodeling and formalism, our work defines an innovative framework where generic pattern concepts based on roles are precisely defined as a formal role metamodel using Object-Z. Individual patterns are specified using these generic role concepts in terms of pattern role models. Temporal behaviors of patterns are also specified using Object-Z and integrated in the pattern role models. Patterns described this way are abstract, separating pattern realization information from the pattern description. They are also precise providing a rigorous foundation for reasoning about pattern properties. This paper also formalizes the properties that must be captured in a class model when a design pattern is deployed. These properties are defined generically in terms of role bindings from a pattern role model to a class model. They provide a precise basis for checking the validity of pattern utilisation in designs. Our work is supported by tools. We have developed an initial role metamodel using an existing modeling framework, Eclipse Modeling Framework (EMF) and have transformed the metamodel to Object-Z using model transformation techniques. Complex constraints are added to the transformed Object-Z model. More importantly, we implement the role metamodel. Using this implementation, pattern authors can develop an initial pattern role model in the same modeling framework and convert the initial model to Object-Z using our transformation rules. The transformed Object-Z model is then enhanced with behavioral features of the pattern. This tool support significantly improves the practicability of applying formalism to design patterns.

No abstract