Towards an MDA-oriented UML profile for distribution

Abstract

The era of distributed systems is upon us. Middlewarespecific concerns, and especially the distribution concern, which is the core of any middleware-mediated application, are addressed every day in all sorts of enterprise systems. However, object-oriented UML designs offer a very limited perspective on what exactly is distributed, how exactly the distribution is achieved, and where exactly distributed services are located. In order to answer these questions, the MDA-compliant Enterprise Fondue method proposes a hierarchy of UML profiles as a means for addressing the distribution concern at three different MDA-levels of abstraction. Model transformations are provided to incrementally refine existing design models according to the proposed profiles. For the last phase of the Enterprise Fondue process, code generation for specific middleware infrastructures is supported through the Parallax framework. The CORBA technology is used for illustrating the entire approach on a concrete example.

Explicit Architectural Policies to Satisfy NFRs Using COTS

“…From a component-based standpoint some projects [2][3][4] try to satisfy system NFRs through a model-driven process for selecting components to achieve systemic NFRs, and later configuring and deploying the selected components. Other projects from a more design-oriented approach [5][6][7][8] aim to generate implementations that satisfy multiples NFRs at once, starting out from design description at platform-independent (PIM) level; thus, NFRs must be modeled and solved at prior stages.…”

“…The platform-independent model P IM v for each concern v may also be implemented with a MDA approach for NFRs [5][6][7][8], or may be mapped to selected COTS. In the former case, each P IM v generates a P SM v as encoded in the P M v .…”

“…Some recent projects [2][3][4][5][6][7][8][9] have addressed explicit mechanisms to satisfy NFRs through MDA transformations. From a component-based standpoint some projects [2][3][4] try to satisfy system NFRs through a model-driven process for selecting components to achieve systemic NFRs, and later configuring and deploying the selected components.…”

“…Some proposals [2][3][4][5][6][7][8][9] extend MDA to deal explicitly with NFRs, especially from a perspective of components more than from detailed software design. Yet remains much work to be done: there is no traceability of decisions from NFRs to architecture to design and to final implementation, nor techniques to generate hybrid solutions that combine pre-existing components and ad-hoc development.…”

Developing Distributed Services Using an Aspect Oriented Model Driven Framework

“…5,13,38,40,41 The AOMDF is based on our aspect oriented modeling approach in which a design is expressed in terms of the following artifacts: 13,16 (i) A primary model that describes the business logic of the application.…”