Quality of service issues related to transforming platform independent models to platform specific models

Burt, Carol C.; Bryant, Barrett R.; Raje, R.R.; Olson, Andrew M.; Auguston, Mikhail

doi:10.1109/edoc.2002.1137710

Cited by 7 publications

(9 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [16], Burt et al explore how QoS requirements can impact decisions related to the transformation from platform-independent models in UML to platform-specific models in IDL. It complements our work but does not address how QoS requirements can be integrated in a UML specification and how they should be resolved or refined in model transformations.…”

Section: Discussion and Related Workmentioning

confidence: 99%

An Aspect-oriented Approach to Manage QoS Dependability Dimensions in Model Driven Development

Köllmann

Kutvonen²,

Linington

et al. 2007

Proceedings of the 3rd International Workshop on Model-Driven Enterprise Information Systems

View full text Add to dashboard Cite

Abstract. Model-driven development approaches commonly use an abstraction of platform specific features for improving reusability and verifiability of the core functionality models. However, the core functionality may still be tangled with features that address important dependability concerns across a design model -for example features such as security, trust and performance. These features can commonly be called Quality of Service (QoS) features. This paper presents an approach for managing several dependability dimensions. We use aspect oriented and model driven development techniques to separate and construct QoS independent models, and graph-based transformation techniques to derive the corresponding QoS specific models.

show abstract

Section: Discussion and Related Workmentioning

confidence: 99%

An Aspect-oriented Approach to Manage QoS Dependability Dimensions in Model Driven Development

Köllmann

Kutvonen²,

Linington

et al. 2007

Proceedings of the 3rd International Workshop on Model-Driven Enterprise Information Systems

View full text Add to dashboard Cite

show abstract

“…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.…”

Section: Mda Nfrs and Component-based Developmentmentioning

confidence: 99%

“…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 .…”

Section: Treatment Of Policies-specific Pimsmentioning

confidence: 99%

“…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.…”

Section: Mda Nfrs and Component-based Developmentmentioning

confidence: 99%

“…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.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Explicit Architectural Policies to Satisfy NFRs Using COTS

López

Astudillo

2006

Satellite Events at the MoDELS 2005 Conference

View full text Add to dashboard Cite

Abstract. Software architecture decisions hinge more on non-functional requirements (NFRs) than on functional ones, since the architecture stipulates which software to build. Model-Driven Architecture (MDA) aims to automate the derivation/generation of software from high level architectural specifications, but most current MDA implementations start from software design (i.e. how to build a software piece) rather than software architecture. This article presents an approach to extend MDA through the concepts of architectural policies and mechanisms. The key ideas are representation of NFRs through architectural concerns using architectural policies, systematic reification of policies into mechanisms, and multi-dimensional description of components as implementators of mechanisms. A detailed illustrative example is provided. Azimut framework realizes these ideas, supports larger-scale work through catalogs of policies and components, and allows traceability and reuse of architecture by enabling enabling these architecture-level descriptions and reasoning.

show abstract