Topic
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.
Papers published on a yearly basis
Papers
More filters
TL;DR: A flexible and lightweight workflow framework based on the Object Modeling System (OMS) to deploy and execute data-centric workflows in a decentralized manner across multiple distinct Cloud resources, avoiding limitations of all data passing through a centralized engine.
18 citations
16 Jul 2012
TL;DR: An extension of the STREAM process, named STREAM-ADD (Strategy for Transition between Requirements and Architectural Models with Architectural Decisions Documentation) is defined, which aims to systematize the documentation of architectural decisions by the time they are made and to support the refinement of the architecture according to such decisions.
Abstract: Requirements Engineering and Architectural Design are activities of the software development process that are strongly related and intertwined. Thus, providing effective methods of integration between requirements and architecture is an important Software Engineering challenge. In this context, the STREAM process presents a model-driven approach to generate early software architecture models from requirements models. Despite being a systematic derivation approach, STREAM does not support the documentation of architectural decisions and their corresponding rationale. Recent studies in the software architecture community have stressed the need to treat architectural design decisions and their rationale as first class citizens in software architecture specification. In this paper we define an extension of this process, named STREAM-ADD (Strategy for Transition between Requirements and Architectural Models with Architectural Decisions Documentation). This extended process aims to systematize the documentation of architectural decisions by the time they are made and to support the refinement of the architecture according to such decisions. In order to illustrate our approach, it was applied for creating the architecture specification of a route-planning system.
18 citations
13 Nov 2009
TL;DR: This article compares the used service-oriented approach with other state-of-theart architectures to show that changeability and efficiency improve compared to alternative architectures.
Abstract: Service-oriented architecture (SOA) is based on a design principle for business software systems. The SOA movement has taken up momentum, especially because of widespread middleware vendor support, e.g. by IBM, HP, BEA, Microsoft, Sun, Software AG, TIBCO, Oracle, SAP and others. Still answers to questions of how the target architecture should look like and what the advantages over other architectures are remain open. We have implemented a scenario based on free software, which consists of a well-defined service-oriented target architecture. In this article, we compare the used service-oriented approach with other state-of-theart architectures to show that changeability and efficiency improve compared to alternative architectures.
18 citations
TL;DR: An "architecture" is presented where the key unit of analysis is human activity as proposed by the cultural–historical activity theory and yet addresses the issues of practical implementation from both the technical and organisational perspectives.
Abstract: This paper explores the design of computer-based systems that support the management of organisational knowledge. The information systems notions of databases and information architectures are extended to the search for a meaningful conceptual structure by which collective knowledge can be supported by existing information technologies. An "architecture" is presented where the key unit of analysis is human activity as proposed by the cultural–historical activity theory. This architecture has the richness of the activity theory philosophy and yet addresses the issues of practical implementation from both the technical and organisational perspectives. The paper articulates the architecture and also reports on a study where its effectiveness was evaluation by a target group. An implementation of the architecture is also introduced.
18 citations
02 May 2010
TL;DR: Data from interviews with software architects about how practitioners utilize architecture during system evolution shows basic architecture-centric practices are not followed systematically, and lack of quality attribute reasoning early on, and during the lifespan of the system is a key contributor to failing to use architecture knowledge effectively during evolution.
Abstract: It is widely accepted that awareness of architectural decisions enables better management and planning of system evolution, refactoring, and modernization efforts. In this paper we report data from interviews with software architects about how practitioners utilize architecture during system evolution. Our results show, despite the widely shared view that long-lived systems are better off with strong architectures; basic architecture-centric practices are not followed systematically. The key gap we observe is in correct and timely communication of architectural issues. This overall finding is not surprising. However, our data also contributes to how architecture knowledge management activities can be focused for most benefit throughout a system's lifespan. While the often-referenced problem is lack of time spent on documentation and design practices, our interviews show that lack of quality attribute reasoning early on, and during the lifespan of the system is a key contributor to failing to use architecture knowledge effectively during evolution.
18 citations