The Experts below are selected from a list of 6417 Experts worldwide ranked by ideXlab platform
Nenad Medvidovic - One of the best experts on this subject based on the ideXlab platform.
-
On the role of Middleware in architecturebased software development
2013Co-Authors: Nenad MedvidovicAbstract:Software architectures promote development focused on modular functional building blocks (components), their interconnections (configurations), and their interactions (connectors). Since architecture-level components often contain complex functionality, it is reasonable to expect that their interactions will be complex as well. Middleware technologies such as CORBA, COM, and RMI, provide a set of predefined services for enabling component composition and interaction. However, the potential role of such services in the implementations of software architectures is not well understood. Furthermore, components adhering to one Middleware Standard cannot readily interact with those adhering to another. In order to understand the role and tradeoffs among Middleware technologies in implementing architectures and enable component interoperability across Middleware platforms, we have investigated a set of techniques and conducted preliminary case studies involving a particular architectural style, C2, and its implementation infrastructure. In particular, by encapsulating Middleware functionality within C2’s explicit software connectors, we have been able to couple C2’s existing benefits such as component interchangeability, substrate independence, and structural guidance with new capabilities of multi-lingual, multi-process, and distributed application development in a manner that is transparent to architects. Furthermore, we have demonstrated the utility of our connector-based approach in enabling components implemented on top of different Middleware platforms to interoperate. Though several details of our approach derive from the characteristics of the C2 style, we believe that a number of lessons learned are more generally applicable. We argue that these lessons can help form a broader research agenda for coupling the modeling power of software architectures with the implementation support provided by Middleware.
-
On the role of Middleware in architecture-based software development
2002Co-Authors: Nenad MedvidovicAbstract:Software architectures promote development focused on modular functional building blocks (components), their interconnections (configurations), and their interactions (connectors). Since architecture-level components often contain complex functionality, it is reasonable to expect that their interactions will be complex as well. Middleware technologies such as CORBA, COM, and RMI, provide a set of predefined services for enabling component composition and interaction. However, the potential role of such services in the implementations of software architectures is not well understood. Furthermore, components adhering to one Middleware Standard cannot readily interact with those adhering to another. In order to understand the role and tradeoffs among Middleware technologies in implementing architectures and enable component interoperability across Middleware platforms, we have investigated a set of techniques and conducted case studies involving a particular architectural style, C2, and its implementation infrastructure. In particular, by encapsulating Middleware functionality within C2’s explicit software connectors, we have been able to couple C2’s existing benefits such as component interchangeability, substrate independence, and structural guidance with new capabilities of multi-lingual, multi-process, and distributed application development in a manner that is transparent to architects. Furthermore, we have demonstrated the utility of our connector-based approach in enabling components implemented on top of different Middleware platforms to interoperate. Though several details of our approach derive from the characteristics of the C2 style, we believe that a number of lessons learned are more generally applicable. We argue that these lessons can help form a broader research agenda for coupling the modeling power of software architectures with the implementation support provided by Middleware. 1
Aniruddha Gokhale - One of the best experts on this subject based on the ideXlab platform.
-
evaluating transport protocols for real time event stream processing Middleware and applications
Lecture Notes in Computer Science, 2009Co-Authors: Joe Hoffert, Douglas C Schmidt, Aniruddha GokhaleAbstract:Real-time event stream processing (RT-ESP) applications must synchronize continuous data streams despite fluctuations in resource availability. Satisfying these needs of RT-ESP applications requires predictable QoS from the underlying publish/subscribe (pub/sub) Middleware. If a transport protocol is not capable of meeting the QoS requirements within a dynamic environment, the Middleware must be flexible enough to tune the existing transport protocol or switch to a transport protocol better suited to the changing operating conditions. Realizing such adaptive RT-ESP pub/sub Middleware requires a thorough understanding of how different transport protocols behave under different operating conditions. This paper makes three contributions to work on achieving that understanding. First, we define ReLate2, which is an evaluation metric that combines packet latency and reliability to evaluate transport protocol performance. Second, we use the ReLate2 metric to quantify the performance of various transport protocols integrated with the OMG's Data Distribution Service (DDS) QoS-enabled pub/sub Middleware Standard using our FLEXibleMiddleware AndTransports (FLEXMAT) prototype for experiments that capture performance data. Third, we use ReLate2 to pinpoint configurations involving sending rate, network loss, and number of receivers that show the pros and cons of the protocols.
Pupelis Justas - One of the best experts on this subject based on the ideXlab platform.
-
Communication in limited conditions using dds Middleware Standard
Institutional Repository of Vilnius University, 2017Co-Authors: Pupelis JustasAbstract:Nowadays technologies directly affect the life of modern people. Different devices and software systems help people to perceive and control the environment. There are plenty of ways to send data from one devices to another. The Data Distribution Service (DDS) is Middleware Standard which is specified by Real-Time Publish-Subscribe (RTPS) protocol, created by Object Management Group (OMG). RTPS protocol is one of the way to send data form one device to another which will be analyzed in this thesis. Author look over how one of DDS implementation – RTI Connext DDS – provide example, how it is possible using it, user can send video streaming media to one or more receivers. Author did an experiment using Fast-RTPS – open source RTPS protocol implementation. There were number of attemps to send data over network using different Linux Operating System parameters as well as various Fast-RTPS settings and chosen QoS. Computers with Fast-RTPS applications were set up far from router in order to create limited conditions. Based on results from the experiments, it was concluded that RTPS is not recommended for large video files or video streams sending, as the data transfer speed is too low or the high number of lost samples, depending on the settings and QoS used
Himanshu Aggarwal - One of the best experts on this subject based on the ideXlab platform.
-
hl 7 based Middleware Standard for healthcare information system fhir
2019Co-Authors: Meenakshi Sharma, Himanshu AggarwalAbstract:Fast health Interoperability Resources (FHIR), a advanced proposed emerging Standard of Health Level 7 (HL7) that inheritance various advantageous of HL7- v2 and v3 for providing health interoperability. HL7 messaging Standard has been widely implemented and adopted by healthcare domain internationally from last few decades. Among hospital HL7-V2 (version ‘v2’) is preferred choice as compared to Standard v3 to exchange healthcare information like electronic health records (EHR) among local hospitals. HL7-V3 was successor of the HL7-V2 that inherits various features and overcome various shortcomings of the V2. HL7-V3 Standard had been highly criticized by the healthcare industry due to various shortcomings like complex documentation, implementation and maintenance cost high along with stalled system. HL7 Standards has been introduced new approach FHIR Standard which yet under experimental stage. FHIR has various attractive features like user friendly features, various built in modules and widely compatible with existing web Standards. This research paper will provide substantiation evolution of the HL-7 Standards pattern messaging, prologue related to the HL7 FHIR and comparison among HL7 Standards.
Joe Hoffert - One of the best experts on this subject based on the ideXlab platform.
-
evaluating transport protocols for real time event stream processing Middleware and applications
Lecture Notes in Computer Science, 2009Co-Authors: Joe Hoffert, Douglas C Schmidt, Aniruddha GokhaleAbstract:Real-time event stream processing (RT-ESP) applications must synchronize continuous data streams despite fluctuations in resource availability. Satisfying these needs of RT-ESP applications requires predictable QoS from the underlying publish/subscribe (pub/sub) Middleware. If a transport protocol is not capable of meeting the QoS requirements within a dynamic environment, the Middleware must be flexible enough to tune the existing transport protocol or switch to a transport protocol better suited to the changing operating conditions. Realizing such adaptive RT-ESP pub/sub Middleware requires a thorough understanding of how different transport protocols behave under different operating conditions. This paper makes three contributions to work on achieving that understanding. First, we define ReLate2, which is an evaluation metric that combines packet latency and reliability to evaluate transport protocol performance. Second, we use the ReLate2 metric to quantify the performance of various transport protocols integrated with the OMG's Data Distribution Service (DDS) QoS-enabled pub/sub Middleware Standard using our FLEXibleMiddleware AndTransports (FLEXMAT) prototype for experiments that capture performance data. Third, we use ReLate2 to pinpoint configurations involving sending rate, network loss, and number of receivers that show the pros and cons of the protocols.