			Home About us Contact

Component Architecture (component + architecture)

Distribution by Scientific Domains

Information Science and Computing	85%

Selected Abstracts

The CCA core specification in a distributed memory SPMD framework

CONCURRENCY AND COMPUTATION: PRACTICE & EXPERIENCE, Issue 5 2002
Benjamin A. Allan
Abstract We present an overview of the Common Component Architecture (CCA) core specification and CCAFFEINE, a Sandia National Laboratories framework implementation compliant with the draft specification. CCAFFEINE stands for CCA Fast Framework Example In Need of Everything; that is, CCAFFEINE is fast, lightweight, and it aims to provide every framework service by using external, portable components instead of integrating all services into a single, heavy framework core. By fast, we mean that the CCAFFEINE glue does not get between components in a way that slows down their interactions. We present the CCAFFEINE solutions to several fundamental problems in the application of component software approaches to the construction of single program multiple data (SPMD) applications. We demonstrate the integration of components from three organizations, two within Sandia and one at Oak Ridge National Laboratory. We outline some requirements for key enabling facilities needed for a successful component approach to SPMD application building. Copyright © 2002 John Wiley & Sons, Ltd. [source]

Component architecture in a network management system

BELL LABS TECHNICAL JOURNAL, Issue 3 2003
Neil R. Bass
Component architectures are best known for the benefits of software reuse. However, they are also a basis for creating solutions that can be scaled in both size and feature content. These benefits were the motivation for choosing a component architecture for a large network management system. The architects selected Common Object Request Broker Architecture (CORBA)* and Java* as technologies to implement the architecture and specified a platform to support the components. This paper draws upon the experiences of this system to discuss the structure of such architecture, the implications of the tools and technologies, and the factors important to its success. © 2003 Lucent Technologies Inc. [source]

Design and implementation of a high-performance CCA event service,

CONCURRENCY AND COMPUTATION: PRACTICE & EXPERIENCE, Issue 9 2009
Ian Gorton
Abstract Event services based on publish,subscribe architectures are well-established components of distributed computing applications. Recently, an event service has been proposed as part of the common component architecture (CCA) for high-performance computing (HPC) applications. In this paper we describe our implementation, experimental evaluation, and initial experience with a high-performance CCA event service that exploits efficient communications mechanisms commonly used on HPC platforms. We describe the CCA event service model and briefly discuss the possible implementation strategies of the model. We then present the design and implementation of the event service using the aggregate remote memory copy interface as an underlying communication layer for this mechanism. Two alternative implementations are presented and evaluated on a Cray XD-1 platform. The performance results demonstrate that event delivery latencies are low and that the event service is able to achieve high-throughput levels. Finally, we describe the use of the event service in an application for high-speed processing of data from a mass spectrometer and conclude by discussing some possible extensions to the event service for other HPC applications. Published in 2009 by John Wiley & Sons, Ltd. [source]

21 CFR Part 11: electronic records.

QUALITY ASSURANCE JOURNAL, Issue 2 2002
An interactive voice response system.
Abstract A large full-service clinical research organization in the US needed to replace their legacy interactive voice response system which did not provide 21 CFR Part 11 compliant audit trails. They chose to custom-build the new software using C++ component architecture, eXtensible Markup Language (XML), Hypertext Markup Language (HTML), and Microsoft web telephony engine. The case study described in this article illustrates that when systems developers read, study, understand, and embrace 21 CFR Part 11 before designing and validating their product, the regulations are easily met. Copyright © 2002 John Wiley & Sons, Ltd. [source]

Component architecture in a network management system

Increased competitiveness through component technology for element management systems

BELL LABS TECHNICAL JOURNAL, Issue 3 2003
Alan J. McBride
Element management represents a necessary cost associated with all network devices. Isolated development of element management systems (EMSs) for diverse network device products results in replication of effort on common low-level aspects. This effort spent re-inventing the wheel affects cost-effectiveness and drains resources from features that reduce customer cost of ownership and operation. Reduced cost of EMS development and reduced operations expenditure for the customer can significantly contribute to competitiveness of the managed device itself. The Navis® element management framework (EMF) program addresses the cost-effectiveness of EMS development through a platform approach utilizing a components architecture and Bell Labs software tools together with high-productivity technologies such as J2EE*/EJB,* XML, Java,* and CORBA.* Use of a platform for aspects common across EMSs allows each development to focus on product-specific value-added features, while also facilitating common look-and-feel and integration of EMS products with current and next-generation operations support systems (OSSs) for seamless end-to-end network and service management. The benefits to service providers include faster time-to-market for new services and reduced training and integration costs. © 2003 Lucent Technologies Inc. [source]