http://sedici.unlp.edu.ar:80/handle/10915/134639 Fri, 13 Nov 2026 06:03:54 GMT 2026-11-13T06:03:54Z http://sedici.unlp.edu.ar:80/handle/10915/135149 Articulo Electronic Journal of SADIO; vol. 9 We present in this work an MDA approach for the definition of transformations for business process models. These transformations are based on the use of two platform independent workflow universal languages –UML 2.0 Activity Diagrams and BPMN– and a platform specific language, the XPDL language. The first two languages are used in the definition of a horizontal transformation, while BPMN and XPDL are used in the definition of a vertical transformation. Although there are several options for a model transformation language, we have adhered to one of the principles of MDA, namely the use of standards, therefore adopting the QVT language, which is the transformation language proposed by the OMG. We also show, in this work, a practical case of an application of the transformations proposed here. Fri, 04 Jun 2010 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/135149 2010-06-04T00:00:00Z We present in this work an MDA approach for the definition of transformations for business process models. These transformations are based on the use of two platform independent workflow universal languages –UML 2.0 Activity Diagrams and BPMN– and a platform specific language, the XPDL language. The first two languages are used in the definition of a horizontal transformation, while BPMN and XPDL are used in the definition of a vertical transformation. Although there are several options for a model transformation language, we have adhered to one of the principles of MDA, namely the use of standards, therefore adopting the QVT language, which is the transformation language proposed by the OMG. We also show, in this work, a practical case of an application of the transformations proposed here. http://sedici.unlp.edu.ar:80/handle/10915/135141 Articulo Electronic Journal of SADIO; vol. 9 The ever increasing number of publicly available Web Services makes standardcompliant service registries one of the essential tools to service-oriented application developers. Previous works have shown that the descriptiveness of published service descriptions is important from the point of view of the algorithms that support service discovery using this kind of registries as well as human developers, who have the final word on which discovered service is more appropriate. This paper presents a catalog of frequent bad practices in the creation of Web Service descriptions that attempt against their chances of being discovered, along with novel practical solutions to them.Additionally, the paper presents empirical evaluations that corroborated the benefits of the proposed solutions. These anti-patterns will help service publishers avoid common discoverability problems and improve existing service descriptions. Fri, 04 Jun 2010 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/135141 2010-06-04T00:00:00Z The ever increasing number of publicly available Web Services makes standardcompliant service registries one of the essential tools to service-oriented application developers. Previous works have shown that the descriptiveness of published service descriptions is important from the point of view of the algorithms that support service discovery using this kind of registries as well as human developers, who have the final word on which discovered service is more appropriate. This paper presents a catalog of frequent bad practices in the creation of Web Service descriptions that attempt against their chances of being discovered, along with novel practical solutions to them.Additionally, the paper presents empirical evaluations that corroborated the benefits of the proposed solutions. These anti-patterns will help service publishers avoid common discoverability problems and improve existing service descriptions. http://sedici.unlp.edu.ar:80/handle/10915/135137 Articulo Electronic Journal of SADIO; vol. 9 Numerous efforts have addressed the problem of defining the fundamental architectural building blocks and methods for modelling software architectures in dynamic mobile environments. However, there is a lack of tools for documentingthe evolution of the products generated during the design of software architectures for mobile systems. Based on a generic versioning administration scheme, a model to capture and manage the products of a software architecture design process is proposed placing the focus on mobility concerns. This model follows an operational approach, where design decisions are represented as architectural operations that are captured when they are applied during a design project. The capture of this information enables the tracing of such a design process and its resulting products. Fri, 04 Jun 2010 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/135137 2010-06-04T00:00:00Z Numerous efforts have addressed the problem of defining the fundamental architectural building blocks and methods for modelling software architectures in dynamic mobile environments. However, there is a lack of tools for documentingthe evolution of the products generated during the design of software architectures for mobile systems. Based on a generic versioning administration scheme, a model to capture and manage the products of a software architecture design process is proposed placing the focus on mobility concerns. This model follows an operational approach, where design decisions are represented as architectural operations that are captured when they are applied during a design project. The capture of this information enables the tracing of such a design process and its resulting products. http://sedici.unlp.edu.ar:80/handle/10915/135135 Contribucion a revista Electronic Journal of SADIO; vol. 9 Nota sobre el contenido del volumen 9, número especial del Electronic Journal of SADIO. Fri, 04 Jun 2010 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/135135 2010-06-04T00:00:00Z Nota sobre el contenido del volumen 9, número especial del Electronic Journal of SADIO. http://sedici.unlp.edu.ar:80/handle/10915/114615 Articulo Electronic Journal of SADIO; vol. 9 Model Driven Engineering proposes a software development process in which the key notions are models and model transformations. There are already several proposals for model transformation specification, implementation, and execution. In this paper we introduce the notion of domain specific transformation language (DSTL). A DSTL is a transformation language tailored for a specific domain; in contrast to well known transformation languages, such as QVT or ATL, the DSTL's syntax and semantics are directly related to a specific domain and/or kind of transformation. A DSTL makes transformations easer to write and understand, the code is intuitive and the users do not need to know a generic transformation language. Also we analyze a novel way to define its semantics. Our proposal consists in using transformation languages themselves to the implementation of such domain specific languages. We illustrate the proposal through an example in the database domain. Fri, 01 Jan 2010 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/114615 2010-01-01T00:00:00Z Model Driven Engineering proposes a software development process in which the key notions are models and model transformations. There are already several proposals for model transformation specification, implementation, and execution. In this paper we introduce the notion of domain specific transformation language (DSTL). A DSTL is a transformation language tailored for a specific domain; in contrast to well known transformation languages, such as QVT or ATL, the DSTL's syntax and semantics are directly related to a specific domain and/or kind of transformation. A DSTL makes transformations easer to write and understand, the code is intuitive and the users do not need to know a generic transformation language. Also we analyze a novel way to define its semantics. Our proposal consists in using transformation languages themselves to the implementation of such domain specific languages. We illustrate the proposal through an example in the database domain.