The Experts below are selected from a list of 7854 Experts worldwide ranked by ideXlab platform

Seongbin Park - One of the best experts on this subject based on the ideXlab platform.

  • ICALT - A system that helps learning Web services
    Fifth IEEE International Conference on Advanced Learning Technologies (ICALT'05), 2005
    Co-Authors: Jinhyun Ahn, Seongbin Park
    Abstract:

    A Web service is a software system interoperating with each other in a Platform Independence manner. COM (component object model) enables components to interoperate with each other. Based on the similarities between a Web service and COM, we provide a system that helps users who get started learning the concept of Web services by experiencing and seeing the process involved in using Web services.

Luis Ferreira Pires - One of the best experts on this subject based on the ideXlab platform.

  • Model-driven design, refinement and transformation of abstract interactions
    International Journal of Cooperative Information Systems, 2006
    Co-Authors: João Paulo A. Almeida, Luis Ferreira Pires, Remco M. Dijkman, Dick Quartel, Marten Van Sinderen
    Abstract:

    In a model-driven design process the interaction between application parts can be described at various levels of Platform-Independence. At the lowest level of Platform-Independence, interaction is realized by interaction mechanisms provided by specific middleware Platforms. At higher levels of Platform-Independence, interaction must be described in such a way that it can be further refined and realized onto a number of different middleware Platforms, each with its particular interaction mechanisms and implementation constraints. In this paper, we investigate concepts that support interaction design at various levels of middleware-Platform-Independence. In addition, we propose design operations for interaction refinement. The application of these operations to source designs results in target designs that take into account implementation constraints imposed by Platforms, while preserving characteristics prescribed in source designs. Target designs are related to source designs by conformance. We discuss how transformation and conformance can be related, such that transformations indeed preserve the characteristics prescribed by a source design.

  • Platform-independent modelling in MDA : Supporting abstract Platforms
    Lecture Notes in Computer Science, 2005
    Co-Authors: João Paulo A. Almeida, Remco Dijkman, Marten Van Sinderen, Luis Ferreira Pires
    Abstract:

    An MDA-based design approach should be able to accommodate designs at different levels of Platform-Independence. We have previously proposed a design approach [2], which allows these levels to be identified. An important feature of this approach is the notion of abstract Platform. An abstract Platform is determined by considering the Platform characteristics that are relevant for applications at a certain level of Platform-Independence as well as the various design goals. In this paper, we discuss how our design approach can be supported using the MDA standards UML 2.0 and MOF 2.0. Since our methodological framework is based on the notion of abstract Platform, we pay particular attention to the representation of abstract Platforms and the language requirements to specify abstract Platforms.

  • EDOC - On the notion of abstract Platform in MDA development
    2004
    Co-Authors: João Paulo A. Almeida, Marten Van Sinderen, Remco M. Dijkman, Luis Ferreira Pires
    Abstract:

    Although Platform-Independence is a central property in MDA models, the study of Platform-Independence has been largely overlooked in MDA. As a consequence, there is a lack of guidelines to select abstraction criteria and modelling concepts for Platform-independent design. In addition, there is little methodological support to distinguish between Platform-independent and Platform-specific concerns, which could be detrimental to the beneficial exploitation of the PIM-PSM separation-of-concerns adopted by MDA. This work is an attempt towards clarifying the notion of Platform-independent modelling in MDA development. We argue that each level of Platform-Independence must be accompanied by the identification of an abstract Platform. An abstract Platform is determined by the Platform characteristics that are relevant for applications at a certain level of Platform-Independence, and must be established by balancing various design goals. We present some methodological principles for abstract Platform design, which forms a basis for defining requirements for design languages intended to support Platform-independent design. Since our methodological framework is based on the notion of abstract Platform, we pay particular attention to the definition of abstract Platforms and the language requirements to specify abstract Platforms. We discuss how the concept of abstract Platform relates to UML.

  • EDOC - Abstract interactions and interaction refinement in model-driven design
    Ninth IEEE International EDOC Enterprise Computing Conference (EDOC'05), 1
    Co-Authors: João Paulo A. Almeida, Luis Ferreira Pires, Remco M. Dijkman, Dick Quartel, Marten Van Sinderen
    Abstract:

    In a model-driven design process the interaction between application parts can be described at various levels of Platform-Independence. At the lowest level of Platform-Independence, interaction is realized by interaction mechanisms provided by specific middleware Platforms. At higher levels of Platform-Independence, interaction must be described in such a way that it can be further refined and realized onto a number of different middleware Platforms, each with its particular interaction mechanisms and implementation constraints. In this paper, we investigate concepts that support interaction design at various levels of middleware-Platform-Independence. Also, we propose design operations for interaction refinement. The application of these operations to source designs results in target designs that take into account implementation constraints imposed by Platforms, while preserving characteristics prescribed in source designs.

T Richardson - One of the best experts on this subject based on the ideXlab platform.

  • enhancing the Platform Independence of the real time specification for java
    Java Technologies for Real-time and Embedded Systems, 2009
    Co-Authors: Andy Wellings, Yang Chang, T Richardson
    Abstract:

    The Real-Time Specification for Java (RTSJ) extends Java's support for Platform-Independence into the realms of real-time systems. It supports an environment that facilitates on-line feasibility analysis. However, an RTSJ program is normally run on an execution Platform that might be shared with other (possibly non Java) applications. This paper explores how the notion of service contracts can be used to enhance the Platform-Independence of RTSJ applications. It also considers the role of real-time application components within an RTSJ environment.

  • JTRES - Enhancing the Platform Independence of the real-time specification for Java
    Proceedings of the 7th International Workshop on Java Technologies for Real-Time and Embedded Systems - JTRES '09, 2009
    Co-Authors: Andy Wellings, Yang Chang, T Richardson
    Abstract:

    The Real-Time Specification for Java (RTSJ) extends Java's support for Platform-Independence into the realms of real-time systems. It supports an environment that facilitates on-line feasibility analysis. However, an RTSJ program is normally run on an execution Platform that might be shared with other (possibly non Java) applications. This paper explores how the notion of service contracts can be used to enhance the Platform-Independence of RTSJ applications. It also considers the role of real-time application components within an RTSJ environment.

João Paulo A. Almeida - One of the best experts on this subject based on the ideXlab platform.

  • Model-driven design, refinement and transformation of abstract interactions
    International Journal of Cooperative Information Systems, 2006
    Co-Authors: João Paulo A. Almeida, Luis Ferreira Pires, Remco M. Dijkman, Dick Quartel, Marten Van Sinderen
    Abstract:

    In a model-driven design process the interaction between application parts can be described at various levels of Platform-Independence. At the lowest level of Platform-Independence, interaction is realized by interaction mechanisms provided by specific middleware Platforms. At higher levels of Platform-Independence, interaction must be described in such a way that it can be further refined and realized onto a number of different middleware Platforms, each with its particular interaction mechanisms and implementation constraints. In this paper, we investigate concepts that support interaction design at various levels of middleware-Platform-Independence. In addition, we propose design operations for interaction refinement. The application of these operations to source designs results in target designs that take into account implementation constraints imposed by Platforms, while preserving characteristics prescribed in source designs. Target designs are related to source designs by conformance. We discuss how transformation and conformance can be related, such that transformations indeed preserve the characteristics prescribed by a source design.

  • DAIS - Model-driven development of context-aware services
    Distributed Applications and Interoperable Systems, 2006
    Co-Authors: João Paulo A. Almeida, Maria-eugenia Iacob, Henk M. Jonkers, Dick Quartel
    Abstract:

    In this paper, we define a model-driven design trajectory for context-aware services consisting of three levels of models with different degrees of abstraction and Platform Independence. The models at the highest level of Platform Independence describe the behaviour of a context-aware service and its environment from an integrated perspective. The models at the intermediate level describe abstract components, which realize the context-aware service in terms of a service-oriented abstract Platform. At the lowest level, the realization of a context-aware service is described in terms of specific target technologies, such as Web Services, BPEL and Parlay technologies. Our approach allows service designers to concentrate their efforts on the services they intend to create and offer, by facilitating the handling of context information and auto-mating design steps through model transformation. In addition, our approach enables the reuse of Platform-independent models for different target Platforms.

  • Platform-independent modelling in MDA : Supporting abstract Platforms
    Lecture Notes in Computer Science, 2005
    Co-Authors: João Paulo A. Almeida, Remco Dijkman, Marten Van Sinderen, Luis Ferreira Pires
    Abstract:

    An MDA-based design approach should be able to accommodate designs at different levels of Platform-Independence. We have previously proposed a design approach [2], which allows these levels to be identified. An important feature of this approach is the notion of abstract Platform. An abstract Platform is determined by considering the Platform characteristics that are relevant for applications at a certain level of Platform-Independence as well as the various design goals. In this paper, we discuss how our design approach can be supported using the MDA standards UML 2.0 and MOF 2.0. Since our methodological framework is based on the notion of abstract Platform, we pay particular attention to the representation of abstract Platforms and the language requirements to specify abstract Platforms.

  • EDOC - On the notion of abstract Platform in MDA development
    2004
    Co-Authors: João Paulo A. Almeida, Marten Van Sinderen, Remco M. Dijkman, Luis Ferreira Pires
    Abstract:

    Although Platform-Independence is a central property in MDA models, the study of Platform-Independence has been largely overlooked in MDA. As a consequence, there is a lack of guidelines to select abstraction criteria and modelling concepts for Platform-independent design. In addition, there is little methodological support to distinguish between Platform-independent and Platform-specific concerns, which could be detrimental to the beneficial exploitation of the PIM-PSM separation-of-concerns adopted by MDA. This work is an attempt towards clarifying the notion of Platform-independent modelling in MDA development. We argue that each level of Platform-Independence must be accompanied by the identification of an abstract Platform. An abstract Platform is determined by the Platform characteristics that are relevant for applications at a certain level of Platform-Independence, and must be established by balancing various design goals. We present some methodological principles for abstract Platform design, which forms a basis for defining requirements for design languages intended to support Platform-independent design. Since our methodological framework is based on the notion of abstract Platform, we pay particular attention to the definition of abstract Platforms and the language requirements to specify abstract Platforms. We discuss how the concept of abstract Platform relates to UML.

  • The role of the RM-ODP computational viewpoint concepts in the MDA approach
    2004
    Co-Authors: João Paulo A. Almeida, Marten Van Sinderen, L. Ferreira Pires
    Abstract:

    An MDA design approach should be able to accommodate designs at different levels of Platform-Independence. We have proposed a design approach previously (in [2]), which allows these levels to be identified. An important feature of this approach is the notion of abstract Platform. An abstract Platform is determined by the Platform characteristics that are relevant for applications at a certain level of Platform-Independence, and must be established by considering various design goals. In this paper, we define a framework that makes it possible to use RM-ODP concepts in our MDA design approach. This framework allows a recursive application of the computational viewpoint at different levels of Platform-Independence. This is obtained by equating the RM-ODP notion of infrastructure to our notion of abstract Platform.

Hugo De Man - One of the best experts on this subject based on the ideXlab platform.

  • FPL - Adding Hardware Support to the HotSpot Virtual Machine for Domain Specific Applications
    Lecture Notes in Computer Science, 2002
    Co-Authors: Radovan Hipik, Serge Vernalde, Diederik Verkest, Marc Engels, Rudy Lauwereins, Hugo De Man
    Abstract:

    Like real general-purpose processors, Java Virtual Machines (JVMs) need hardware acceleration for computationally intensive applications. JVMs however require that Platform Independence can be maintained while resorting to hardware acceleration. To this end, we invented a scheme to seamlessly add hardware support to Sun's HotSpot JVM. By means of run-time profiling, we select the most heavily used Java methods for execution in Field Programmable Gate Arrays (FPGA) hardware. Methods running in hardware are designed at compiletime, but the bitstreams are generated at run-time to guarantee Platform Independence. If no method improves the performance by running in hardware, all Java methods still can run in software with trivial run-time overheads. We have implemented this hardware supported JVM. The results show that hardware acceleration for JVMs can be achieved while maintaining Platform Independence for domain specific applications.