N-ary Relations of Association in Class Diagrams: Design Patterns

Abstract

Abstract-Most of the technology of object-oriented development relies on the use of UML diagrams, in particular, class diagrams. CASE tools, used for automation of objectoriented development, often do not support n-ary associations in the class diagrams, and their implementation in the form of program code in contrast to binary rather time-consuming. The article will show how in some cases it is possible to move from the n-ary association between classes to binary and how can reduce the number of objects. The rules to transform models, that contain n-ary association, will be presented in the form of design patterns. Proposed three new design patterns can be used in the process of developing software systems. These patterns describe transformations of n-ary (often ternary) associations occur between classes in binary and the introduction of additional classes and binary association with the aim of optimizing the model.

Model and Criteria for the Automated Refactoring of the UML Class Diagrams

“…The second approach is connected with the developing frameworks of automated model refactoring [15][16][17][18], where the main role is given to the software designer. And the framework applies transformations, using some transformation rules in interaction with the designer.…”