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
Journal ArticleDOI
01 Jan 1975
TL;DR: This paper classifies the HLL computer architecture into four types (von Neumann architecture, syntax-oriented architecture, indirect execution architecture, and direct execution architecture) based on the criterion of proximity in lexicality, syntax and semantics between the high-level language and the machine language.
Abstract: High-level-language (HLL) computer architecture refers to those architecture which can accept one or more high-level languages (such as Fortran, Alogl, Snobol, etc.). This paper classifies the HLL computer architecture into four types (von Neumann architecture, syntax-oriented architecture, indirect execution architecture, and direct execution architecture) based on the criterion of proximity in lexicality, syntax and semantics between the high-level language and the machine language. It then introduce es concepts of these high-level-language architecture. A simple example is employed to illustrate the differences among these four types of architecture.

9 citations

Proceedings ArticleDOI
22 Mar 1996
TL;DR: The main idea is to use the membranes to denote basic software components of the architecture that can be further decomposed during a refinement process but that cannot be destroyed even if the behaviour of the overall system is preserved.
Abstract: Software architectures, chemical abstract machine, specification, refinement. In this paper we propose an approach to compare descriptions of software architectures based on the CHAM formalism. The need to compare descriptions of the same system at different level of abstraction often arises typically when the software practice uses a stepwise refinement approach. Differently from other approaches presented in the literature our framework allows for expressing correct refinement both of the static structure and of the dynamic behaviour of an architecture. Statically we rely on a suitable definition of partial morphism between the signatures of the two architectures. Dynamically we propose a notion of structure preserving simulation which allows the behaviors of the two CHAM descriptions to be (preorderly) related. In both definitions an important role is played by the membrane construct which allows for expressing non-functional constraints on the architecture to be refined. The main idea is to use the membranes to denote basic software components of the architecture that can be further decomposed during a refinement process but that cannot be destroyed even if the behaviour of the overall system is preserved. One point in favour of our approach is that we do not constrain too much the further development since we only require the membrane structure to be preserved.

9 citations

Journal ArticleDOI
TL;DR: Several typical open architecture controllers, such as NGC, OSACA, OMAC and OSEC, are compared based on the evaluation space and some valuable conclusions have been drawn.
Abstract: Existing open architecture controllers have different architectures and methods for realization, but none of them have been generally accepted or been widely applied in industry. Moreover, there is little literature that analyzes and compares these different open architecture controllers synthetically. So this paper establishes an evaluation space for open architecture controllers, a new method to analyze and compare the different open architecture controllers. The evaluation space enables the full evaluation of the open architectures and can easily find the controller’s advantages and disadvantages. The evaluation space for open architecture controllers is a multidimensional space, whose dimensions can be categorized as the requirement dimensions and the architecture dimensions. The requirement dimensions define different requirements of the open architecture controllers, and the architecture dimensions define the different realization methods of open architecture controllers. Establishing the relationships between the requirement dimensions and the architecture dimensions, the evaluation space can calculate the degree to which the different architectures meet the requirements of open architecture controllers, and then the integrated evaluation of different open architecture controllers can be obtained. Several typical open architecture controllers, such as NGC, OSACA, OMAC and OSEC, are compared based on the evaluation space; some valuable conclusions have been drawn.

9 citations

Proceedings ArticleDOI
20 Jan 2009
TL;DR: In this paper, the authors report the lessons learned in the development, analysis and evaluation of the proposed cyber architecture for process control for power grid, which has not been previously found together in a same class of computer-based systems.
Abstract: An architecture was recently proposed to protect the power grid, in the context of a European project. The design of the architecture, guided by an analysis of the evolution of critical information infrastructures, tried to be as generic as possible, with a view of possibly serving as a reference cyber architecture for process control infrastructures. The need for a new architecture is explained by the fact that cyber architectures for process control, despite being basically physical processes controlled by computers interconnected by networks, exhibit a potentially huge cost of failure in socio-economic terms, thus bringing extremely demanding requirements, which have not been previously found together in a same class of computer-based systems. In this paper we wish to report the lessons learned in the development, analysis and evaluation of the proposed cyber architecture for process control.

9 citations

Proceedings ArticleDOI
01 Dec 2014
TL;DR: ARAMIS-CICE is presented, an instantiation of ARAMIS, a general architecture for building tool-based approaches that support the architecture-centric evolution and evaluation of software systems with a strong focus on their behavior.
Abstract: Architecture descriptions greatly contribute to the understanding, evaluation and evolution of software but despite this, up-to-date software architecture views are rarely available. Typically only initial descriptions of the static view are created but during the development and evolution process the software drifts away from its description. Methods and corresponding tool support for reconstructing and evaluating the current architecture views have been developed and proposed, but they usually address the reconstruction of static and dynamic views separately. Especially the dynamic views are usually bloated with low-level information (e.g., Object interactions) making the understanding and evaluation of the behavior very intricate. To overcome this, we presented ARAMIS, a general architecture for building tool-based approaches that support the architecture-centric evolution and evaluation of software systems with a strong focus on their behavior. This work presents ARAMIS-CICE, an instantiation of ARAMIS. Its goal is to automatically test if the run-time interactions between architecture units match the architecture description. Furthermore, ARAMIS-CICE characterizes the intercepted behavior using two newly-defined architecture metrics. We present the fundamental concepts of ARAMIS-CICE: its meta-model, metrics and implementation. We then discuss the results of a two-folded evaluation. The evaluation shows very promising results.

9 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