Total quality of service provisioning in middleware and applications

Wang, Nanbor; Schmidt, Douglas C.; Gokhale, Aniruddha; Gill, Christopher; Natarajan, Balachandran; Rodrigues, Craig; Loyall, Joseph; Schantz, Richard

doi:10.1016/s0141-9331(02)00096-0

Cited by 47 publications

(25 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…To evaluate how component middleware technologies can help improve productivity by enabling developers to work at a higher abstraction level than objects and functions, we selected the Component Integrated ACE ORB (CIAO) [CIAO1,CIAO2] as the run-time platform for our ITS prototype. CIAO is QoS-enabled CCM middleware built atop the The ACE ORB (TAO) [TAO1,TAO2].…”

Section: Applying Component Middleware and Mda Tools To Itsmentioning

confidence: 99%

“…The PIM models are mapped into PSMs via translators. For example, the ITS uses the set of patterns and roles to describe the component collaboration infrastructure suggested by the OMG Component Collaboration Architecture [EDOC] that is specified in the PIM and could be mapped and refined to a specific type in the underlying platform, such as a QoS-enabled implementation of the CORBA Component Model (CCM) [CIAO1,CIAO2].…”

Section: Low-level Abstractions and Tools -Despite Improvements In Thmentioning

confidence: 99%

See 1 more Smart Citation

Concern-Based Composition and Reuse of Distributed Systems

Nechypurenko

Lü

Deng

et al. 2004

Software Reuse: Methods, Techniques, and Tools

Self Cite

View full text Add to dashboard Cite

Abstract. Successful reusable software for large-scale distributed systems often must operate in multiple contexts, e.g., due to (1) integration with other systems using different technologies and platforms, (2) constant fine tuning needed to satisfy changing customer needs, and (3) evolving market conditions resulting from new laws and regulations. This situation causes vexing challenges for developers of reusable software, who must manage the variation between these contexts without overcomplicating their solutions and exceeding project time and effort constraints. This paper provides three contributions to R&D efforts that address these challenges. First, it motivates the use of a concern-based approach to enhance the level of abstraction at which component-based distributed systems are developed and reused to (1) improve software quality and developer productivity, and (2) localize variability aspects to simplify substitution of reusable component implementations. Second, we present our experience dealing with different domain-and middleware-specific variability gained applying model-based component middleware software technologies to develop an Inventory Tracking System that manages the flow of goods in warehouses. Third, we present a concern-based research strategy aimed at effectively managing the variability caused by the presence of multiple middleware platforms and technologies. Our experience to date shows that using model-based software tools and component middleware as the core elements of software composition and reuse -in conjunction with concern-based commonality and variability analysis -helps reduce development complexity, improve system maintainability and reuse, and increase developer productivity.

show abstract

Section: Applying Component Middleware and Mda Tools To Itsmentioning

confidence: 99%

Section: Low-level Abstractions and Tools -Despite Improvements In Thmentioning

confidence: 99%

Concern-Based Composition and Reuse of Distributed Systems

Nechypurenko

Lü

Deng

et al. 2004

Software Reuse: Methods, Techniques, and Tools

Self Cite

View full text Add to dashboard Cite

show abstract

“…In the future, we will develop a distributed FCS service on an ORB middleware that provide end-to-end delay guarantees. We will also investigate and integrate other adaptation mechanisms such as task reallocation into the FCS service, and will integrate our work on FCS with our other research on multi-level scheduling aspects [7] and QoS-aware component middleware [26].…”

Section: Discussionmentioning

confidence: 99%

Feedback control real-time scheduling in orb middleware

Wang

Gill

The 9th IEEE Real-Time and Embedded Technology and Applications Symposium, 2003. Proceedings.

View full text Add to dashboard Cite

show abstract

“…In particular, they provide higher-level capabilities for developers and end-users of DRE systems to specify and enforce QoS requirements in complex DRE systems. Several implementations of CCM are now available, including the Component Integrated ACE ORB (CIAO) [21], Mico-CCM [7], Qedo [12], and StarCCM [17]. As CCM platforms mature and become suitable for DRE systems it is desirable to devise a standard set of metrics to compare and contrast different CCM implementations in terms of their: ¢ Suitability, e.g., how suitable is the CCM implementation for DRE applications in a particular domain, such as avionics, total ship computing, or telecom systems?…”

Section: Introductionmentioning

confidence: 99%

“…The vehicle used to test, obtain and analyze our results from CCMPerf is the Component Integrated ACE ORB (CIAO) [21], which is an opensource 2 implementation of CCM built upon the Real-time CORBA infrastructure of The ACE ORB (TAO) [14]. This paper shows how CCMPerf can be used to collect metrics and evaluate CCM implementations in the DRE domain.…”

mentioning

confidence: 99%