Algorithmic support for model transformation in object‐oriented software development

Abstract

SUMMARYCurrent methods for object-oriented software development provide notation for the specification of models, yet do not sufficiently relate the different model types to each other, nor do they provide support for transformations from one model type to another. This makes transformations a manual activity, which increases the risk of inconsistencies among models and may lead to a loss of information. We have developed and implemented an algorithm supporting one of the transitions from analysis to design, the transformation of scenario models into behavior models. This algorithm supports the Unified Modelling Language (UML), mapping the UML's collaboration diagrams into state transition diagrams. We believe that CASE tools implementing such algorithms will be highly beneficial in object-oriented software development. In this paper, we provide an overview of our algorithm and discuss all its major steps. The algorithm is detailed in semi-formal English and illustrated with a number of examples. Furthermore, the algorithm is assessed from different perspectives, such as scope and role in the overall development process, issues in the design of the algorithm, complexity, implementation and experimentation, and related work.

Automated Prototyping of User Interfaces Based on UML Scenarios

“…In this activity, we apply repeatedly on each CollD of the system the CTS (CollD To StateD) algorithm [42], in order to generate partial specifications automatically for all the objects participating in the input scenarios.…”

“…Koskimies et al [24], finally, present an algorithm for synthesizing state machines (StateDs) from a set of scenarios (the differences to our synthesis algorithm are detailed in [42]). They propose an approach for design called design by animation.…”

“…These diagrams are automatically transformed into the UML Statechart specifications of all objects involved, applying the algorithms we describe in [21,42]. The set of obtained specifications allows for the generation of a UI prototype, which is embedded in a UI builder environment for further refinement.…”

A toolkit for weaving aspect oriented UML designs

“…The main interest of this extensibility is the possibility of defining the weaving strategy by recomposition of primitive transformation operators. The transformation of software models is widely applied in tool automation for design patterns , software refactoring [23] [24], equivalence transformations [9], [1], [25], and formal reasoning [17]. UMLAUT's transformation incorporates ideas from these works, and extends them to automate the definition of weaving operations in the context of AOD.…”

Generating user interface prototypes from scenarios

“…Scenarios are acquired in the form of UML collaboration diagrams and enriched with UI information. These diagrams are automatically transformed, based on our previous work [13,19], into the UML Statechart specifications of all the objects involved. An algorithm is applied to generate a UI prototype from the set of obtained specifications.…”