We describe how to express homomorphic translations with an object-oriented design. This includes a uniform approach to the addition of external functionality to data structures. We present the tradeoffs of distributing intrinsic and extrinsic properties to data structures and external functions respectively. A mini-architecture (design pattern) for the emulation of multidispatching functions i...

A design pattern description is much more complex than a semi-formal solution, often restricted to a class diagram. Applying a pattern mainly depends on the solution specification but a lot of useful information can be found into other items. Neglecting variants of the main solution the pattern engineer might explain can be detrimental to the pattern itself because, most of the time, they affec...

Design patterns are of tremendous value to developers when faced with recurring problems [1]. Given their various applications and uses, model transformations would benefit tremendously from design patterns as well. Although several studies have proposed design patterns for model transformation[2,3,4,5,6], there is still no accepted common language to express them. In this paper, we propose a u...

In training and gaming systems, distributed multimedia are often used, in which the basic content elements must be conveyed or presented in a synchronized order at synchronized moments over multiple devices and in many cases over a network. These content elements are often presented or represented as “Synchronizable Objects” with which their control and management fall into a design pattern. Th...

Design patterns provide a medium-grained abstraction and can be used as an effective tool for understanding object-oriented systems. This paper presents a simple tool for the extraction of design information from C++ code using design patterns. The design of the tool’s model is based on logicprogramming approach. This approach extracts design information by using relationships detection algorit...

In reengineering legacy code it is frequently useful to introduce a design pattern in order to add clarity to the system and thus facilitate further program evolution. We show that this type of transformation can be automated in a pragmatic manner and propose a methodology for the development of design pattern transformations. We address the issues of the definition of a starting point for the ...

[GHJV94] proposed a number of design patterns that offer good solutions for recurring design situations. Along with the good solutions they also discuss naiv solutions to these design situations and argue why such naiv solutions should be replaced by a sound design pattern. Our position is that this exactly describes the task of OO reengineering: find patterns within a legacy OO program that sh...

Developing code free of defects is a major concern for the object-oriented software community. In this paper, we classify design defects as those within classes ( intra-class), those among classes ( interclasses), and those of semantic nature (behavioral). Then, we introduce guidelines to automate the detection and correction of inter-class design defects: We assume that design patterns embody ...

Design patterns describe good solutions to common and recurring problems. The applications of design patterns may vary in different layouts, which pose challenges for recovering and changing these design pattern instances since essential characteristics of each design pattern are described implicitly. In this paper, we categorize different characteristics of each design pattern as its traits in...

In reengineering legacy code it is frequently useful to introduce a design pattern in order to add clarity to the system and thus facilitate further program evolution. We show that this type of transformation can be automated in a pragmatic manner and present a methodology for the development of design pattern transformations. We address the issues of the definition of a starting point for the ...