Systems architecture

About: Systems architecture is a research topic. Over the lifetime, 17612 publications have been published within this topic receiving 283719 citations. The topic is also known as: system architecture.

Processing flows of information: From data stream to complex event processing

Abstract: A large number of distributed applications requires continuous and timely processing of information as it flows from the periphery to the center of the system. Examples include intrusion detection systems which analyze network traffic in real-time to identify possible attacks; environmental monitoring applications which process raw data coming from sensor networks to identify critical situations; or applications performing online analysis of stock prices to identify trends and forecast future values.Traditional DBMSs, which need to store and index data before processing it, can hardly fulfill the requirements of timeliness coming from such domains. Accordingly, during the last decade, different research communities developed a number of tools, which we collectively call Information flow processing (IFP) systems, to support these scenarios. They differ in their system architecture, data model, rule model, and rule language. In this article, we survey these systems to help researchers, who often come from different backgrounds, in understanding how the various approaches they adopt may complement each other.In particular, we propose a general, unifying model to capture the different aspects of an IFP system and use it to provide a complete and precise classification of the systems and mechanisms proposed so far.

Specification and analysis of system architecture using Rapide

Abstract: Rapide is an event-based, concurrent, object-oriented language specifically designed for prototyping system architectures. Two principle design goals are: (1) to provide constructs for defining executable prototypes of architectures and (2) to adopt an execution model in which the concurrency, synchronization, dataflow, and timing properties of a prototype are explicitly represented. This paper describes the partially ordered event set (poset) execution model and outlines with examples some of the event-based features for defining communication architectures and relationships between architectures. Various features of Rapide are illustrated by excerpts from a prototype of the X/Open distributed transaction processing reference architecture. >

Rainbow: architecture-based self-adaptation with reusable infrastructure

Abstract: While attractive in principle, architecture-based self-adaptation raises a number of research and engineering challenges. First, the ability to handle a wide variety of systems must be addressed. Second, the need to reduce costs in adding external control to a system must be addressed. Our rainbow framework attempts to address both problems. By adopting an architecture-based approach, it provides reusable infrastructure together with mechanisms for specializing that infrastructure to the needs of specific systems. The specialization mechanisms let the developer of self-adaptation capabilities choose what aspects of the system to model and monitor, what conditions should trigger adaptation, and how to adapt the system.

CORBA: integrating diverse applications within distributed heterogeneous environments

Abstract: Large computer networks such as corporate intranets and the Internet are inherently heterogeneous due to such factors as increasingly rapid technological change, engineering trade-offs, accumulation of legacy systems over time, and varying system costs. Unfortunately, such heterogeneity makes the development and maintenance of applications that make the best use of such networks difficult. The Common Object Request Broker Architecture specification created by the Object Management Group provides a stable model for distributed object-oriented systems that helps developers cope with heterogeneity and inevitable change. Applications written to the CORBA standard are abstracted away from underlying networking protocols and transports, instead relying on object request brokers to provide a fast and flexible communication and object activation substrated. The abstractions provided by CORBA ORBs are currently serving as the basis for applications in a wide variety of problem domains, including telecommunications, finance, medicine, and manufacturing, running on platforms ranging from mainframes down to test and measurement equipment. This article first provides an overview of the Object Management Architecture, then describes in detail the CORBA component of that architecture, and concludes with a description of the OMG organization along with some of its current and future work.