Database-centric architecture

About: Database-centric architecture is a research topic. Over the lifetime, 1799 publications have been published within this topic receiving 48836 citations.

Erroneous architecture is a relative concept.

Abstract: The problem this paper addresses is that an architecture formed of software components can contain composition errors (introduced, for instance, as a result of the choice of a framework’s parameters). The title “Erroneous architecture is a relative concept” is to emphasize that whether a composition error occurs in an architecture depends on the way the architecture is used in its environment. An important issue is finding a way to possibly statically verify that, for a given setup containing the architecture, no composition errors can occur in any run. The contribution of the paper is bringing an evidence that this can be done by employing behavior protocols and their consent operator.

IBM's jazz integration architecture: building a tools integration architecture and community inspired by the web

Abstract: In this paper, we describe our experience in the Jazz project, beginning from a "Classical" repository- and Java-centric design and evolving towards an architecture which borrows heavily from the architecture of the Web. Along the way, we formed an open community to collaborate on adapting this architecture to various tool domains. Finally, we discuss our experience delivering the first generation of tools built and integrated using these techniques.

Component replacement in a long-living architecture: the 3RDBA approach

Abstract: In order to respond to changing requirements and advances in technology, system and software architectures must evolve during their lifetimes. Usually, in this evolution, several key components of the architecture are replaced. Achieving successful architecture evolution at a reasonable cost and effort is difficult. It requires many architectural and technological decisions. This paper describes an approach, called 3RDBA that facilitates replacing a key component in a long-living architecture. It is based on systematically gathering all information needed to make well-founded decisions regarding evolution of the architecture. The approach consists of an exploration, consolidation and migration cycle. Each cycle contains four steps: requirements, design, build and analyze. 3RDBA enables construction and evaluation of several alternative architecture realizations together with a migration path from the existing architecture towards the selected, new architecture. We describe how we have successfully applied this approach to support the evolution of a medical imaging system architecture.

Pattern-based business-driven analysis and design of service architectures

Abstract: Service architectures are an increasingly adopted architectural approach for solving the Enterprise Application Integration (EAI) problem originated by business process automation requirements. In previous work, we developed a methodological framework for the designing of service architectures for EAI. The framework is structured in a layered architecture called LABAS, and is distinguished by using architectural abstractions in different layers. This paper describes the pattern-based techniques used in LABAS for service identification, for transformation from business models to service architectures and for architecture modifications.

Persistent Information State in a Data-Centric Architecture

Abstract: We present the ADAMACH data centric dialog system, that allows to perform on- and off-line mining of dialog context, speech recognition results and other system-generated representations, both within and across dialogs. The architecture implements a "fat pipeline" for speech and language processing. We detail how the approach integrates domain knowledge and evolving empirical data, based on a user study in the University Helpdesk domain.