A method for the design and development of distributed applications using UML

Abstract

With this contribution we present a design and development method for distributed applications, which are running on top of advanced object middleware platforms. We introduce the basic concept of distinction between the set of concepts and their relations, the definition of a notation supporting such concepts and rules for automatic code generation that help to provide a smooth transition from the design step to the implementation stage. Although the set of concepts is based on RM-ODP, we refine a number of ODP definitions in order to reflect practical design tasks. The supporting notation we present here rests upon costumization of the Unified Modeling Language (UML). Automatic code generation issues are presented briefly, taking a extended CORBA 2.3 object middleware as target distributed infrastructure

TURTLE-P: a UML profile for the formal validation of critical and distributed systems

“…Protocol modeling with UML has been studied at the very beginning of the UML standardization process at the OMG. Since, several studied have been published, first, with academic examples [12,13] and then, with protocols subjacent to systems such as cooperative systems [7], electronic commerce systems [24], multi-agents systems [15,17], and ODP-based systems [3,11].…”

Un environnement de conception de systèmes distribués basé sur UML

“…La modélisation des protocoles avec UML a été étudiée à diverses reprises depuis les prémices de la normalisation du langage UML à l'OMG. Depuis, plusieurs études ont été publiées, tout d'abord, sur des exemples académiques [7] [8], puis, sur des systèmes coopératifs [9], des systèmes de commerce électronique [10], des systèmes multi-agents [11] [12] [14] et enfin sur les approches ODP [13]. La réutilisation de composants de communication devient un enjeu important [15] [16].…”

Addressing computational viewpoint design

“…To improve upon this, we have adopted a more flexible approach to using UML, providing stereotypes to enable design using specifically the concepts defined in the RM-ODP. This approach has also been used in [34] although they do not use the RM-ODP terminology and in [21] and [23] which stereotype UML elements to define a language for creating ODP Enterprise specifications.…”