scispace - formally typeset
Search or ask a question
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
More filters
Proceedings ArticleDOI
18 May 2013
TL;DR: This paper's experience in recovering the ground-truth architectures of four open-source systems is presented, the primary insights gained in the process are discussed, the characteristics of the obtained ground- Truth architectures are analyzed, and the involvement of the systems' engineers is reflected in a limited but critical fashion.
Abstract: Undocumented evolution of a software system and its underlying architecture drives the need for the architecture's recovery from the system's implementation-level artifacts. While a number of recovery techniques have been proposed, they suffer from known inaccuracies. Furthermore, these techniques are difficult to evaluate due to a lack of “ground-truth” architectures that are known to be accurate. To address this problem, we argue for establishing a suite of ground-truth architectures, using a recovery framework proposed in our recent work. This framework considers domain-, application-, and context-specific information about a system, and addresses an inherent obstacle in establishing a ground-truth architecture - the limited availability of engineers who are closely familiar with the system in question. In this paper, we present our experience in recovering the ground-truth architectures of four open-source systems. We discuss the primary insights gained in the process, analyze the characteristics of the obtained ground-truth architectures, and reflect on the involvement of the systems' engineers in a limited but critical fashion. Our findings suggest the practical feasibility of obtaining ground-truth architectures for large systems and encourage future efforts directed at establishing a large scale repository of such architectures.

52 citations

ReportDOI
01 Aug 2001
TL;DR: The process of architecture reconstruction using the Dali architecture reconstruction workbench is described and guidelines for reconstructing the architectural representations of existing systems are outlined.
Abstract: : Architecture reconstruction is the process where the "as-built" architecture of an implemented system is obtained from the existing legacy system. This is done through a detailed analysis of the system using tool support. The tools extract information about the system and aid in building and aggregating successive levels of abstraction. If the reconstruction is successful, the end result is an architectural representation of the system that aids in reasoning about the system. In some cases, it may not be possible to generate a useful representation due to the system. Architecture reconstruction generates an architectural representation that can be used in several ways. One of the main uses is for documenting the existing architecture. If no documentation exists or it is out of date, the recovered architectural representation can be used as a basis for redocumenting the architecture. The recovered "as-built" architecture of the system can be used to check conformance against an "as-designed" architecture. The architectural representation can also be used as a starting point for reengineering the system to a new desired architecture. Finally, the representation can be used to help identify components for reuse, or to help establish a software product line. In this report, we describe the process of architecture reconstruction using the Dali architecture reconstruction workbench. We outline guidelines for reconstructing the architectural representations of existing systems. The process that is undertaken to reconstruct an architecture can be supported by other tools and in fact can be done manually.

51 citations

Proceedings ArticleDOI
22 Sep 2003
TL;DR: The approach underlying Menage is introduced, its detailed functionality is discussed, and its use with product line architecture for entertainment systems is demonstrated.
Abstract: The use of product lines is recognized as beneficial in promoting and structuring both component and architecture reuse throughout an organization. While the business practices of using product lines are well-understood and representations for specifying and capturing the underlying architecture of a product line are coming of age, support environments for managing the evolution of product line architecture are still lacking. In this paper, we present Menage, an environment specifically designed to alleviate this problem. Key features of Menage are its support for: (1) specifying variation points in product line architecture as optional and/or variant elements; (2) tracking the evolution of product line architecture and its constituent elements through explicit versioning techniques; and (3) selecting one or more product architectures out of overall product line architecture by applying user-specified criteria. In this paper, we introduce the approach underlying Menage, discuss its detailed functionality, and demonstrate its use with product line architecture for entertainment systems.

51 citations

Proceedings ArticleDOI
03 Oct 2016
TL;DR: By considering the umbrella of near-data processing as the urgent required breakthrough for future computing systems, this survey presents its derivations with a special emphasis on Processing-In-Memory (PIM), highlighting historical achievements in technology as well as architecture while depicting its advantages and obstacles.
Abstract: A major shift from compute-centric to data-centric computing systems can be perceived, as novel big data workloads like cognitive computing and machine learning strongly enforce embarrassingly parallel and highly efficient processor architectures. With Moore's law having surrendered, innovative architectural concepts as well as technologies are urgently required, to enable a path for tackling exascale and beyond -- even though current computing systems face the inevitable instruction-level parallelism, power, memory, and bandwidth walls. As part of any computing system, the general perception of memories depicts unreliability, power hungriness and slowness, resulting in a future prospective bottleneck. The latter being an outcome of a pin limitation derived by packaging constraints, an unexploited tremendous row bandwidth is determinable, which off-chip diminishes to a bare minimum. Building upon a shift towards data-centric computing systems, the near-memory processing concept seems to be most promising, since power efficiency and computing performance increase by co-locating tasks on bandwidth-rich in-memory processing units, whereas data motion mitigates by the avoidance of entire memory hierarchies. By considering the umbrella of near-data processing as the urgent required breakthrough for future computing systems, this survey presents its derivations with a special emphasis on Processing-In-Memory (PIM), highlighting historical achievements in technology as well as architecture while depicting its advantages and obstacles.

51 citations

Journal ArticleDOI
TL;DR: The twin peaks of requirements and architecture have been referred to as the twin peaks as mentioned in this paper, which describe the trade-offs that must be carefully considered and balanced between requirements and architectures.
Abstract: Quality concerns, often referred to as nonfunctional requirements, service-level agreements, quality attributes, performance constraints, or architecturally significant requirements, describe system-level attributes such as security, performance, reliability, and maintainability. In conjunction with functional requirements, these quality concerns drive and constrain a system's architectural design and often introduce significant trade-offs that must be carefully considered and balanced. The dependencies that exist between requirements and architecture have been referred to as the twin peaks of requirements and architecture. The guest editors of this special issue describe this unique situation.

51 citations


Network Information
Related Topics (5)
Software development
73.8K papers, 1.4M citations
89% related
Server
79.5K papers, 1.4M citations
85% related
Mobile computing
51.3K papers, 1M citations
83% related
Quality of service
77.1K papers, 996.6K citations
82% related
Wireless sensor network
142K papers, 2.4M citations
81% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
20236
202220
20216
20208
201914
201821