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
TL;DR: This study suggests that architecture analysis can be improved if it explicitly challenge the initial requirements, and how and to what extent the process to elicit and assess the impact of such changes might be improved.

36 citations

01 Nov 1983
TL;DR: Some of the fundamental design issues in parallel architecture for Artificial Intelligence are laid out, limitations of previous parallel architectures are delineated, and a new approach is outlined that is pursuing.
Abstract: : Development of highly intelligent computers requires a conceptual foundation that will overcome the limitations of the von Neumann architecture. Architectures for such a foundation should meet the following design goals: Address the fundamental organizational issues of large-scale parallelism and sharing in a fully integrated way. This means attention to organizational principles, as well as hardware and software. Serve as an experimental apparatus for testing large-scale artificial intelligence systems. Explore the feasibility of an architecture based on abstractions, which serve as natural computational primitives for parallel processing. Such abstractions should be logically independent of their software and hardware host implementations. In this paper we lay out some of the fundamental design issues in parallel architecture for Artificial Intelligence, delineate limitations of previous parallel architectures, and outline a new approach that we are pursuing. (Author)

36 citations

Proceedings ArticleDOI
03 Jan 2001
TL;DR: The Viable System Architecture is presented as a high-level reference architecture motivated by an emerging class of applications the authors classify as "complex systems" and the concept of Viability is introduced as the overall quality desired of software for complex systems.
Abstract: This paper presents the Viable System Architecture as a high-level reference architecture. It is component system architecture motivated by an emerging class of applications we classify as "complex systems." The architecture is based on the Viable System Model: a cybernetic model of organizations. The concept of Viability is introduced as the overall quality desired of software for complex systems. We explain how viability is achieved by the interaction of a number of principles: autonomy and adaptation; recursion and hierarchy; and invariants and self-reference. The special structure of a component in this architecture is described in detail. The nature of an interface is also described. This unique component interface mechanism defines the component framework and provides for dynamic assembly of systems of sub-systems. We present an outline of a business-to-business e-commerce application to illustrate the qualities and principles expected from software systems developed based on the architecture. We are currently building a prototype of this system to verify and validate the architecture.

36 citations

Proceedings ArticleDOI
04 May 2015
TL;DR: The findings suggest that automotive software architects produce two different architectures (or views) of the same system, one of which is the working architecture, defining the actual blueprint for the implementation teams and being used in their daily work.
Abstract: To investigate the new requirements and challenges of architecting often safety critical software in the automotive domain, we have performed two case studies on Volvo Car Group and Volvo Group Truck Technology Our findings suggest that automotive software architects produce two different architectures (or views) of the same system The first one is a high-level descriptive architecture, mainly documenting system design decisions and describing principles and guidelines that should govern the overall system The second architecture is the working architecture, defining the actual blueprint for the implementation teams and being used in their daily work The working architecture is characterized by high complexity and considerably lower readability than the high-level architecture Unfortunately, the team responsible for the high-level architecture tends to get isolated from the rest of the development organization, with few communications except regarding the working architecture This creates tensions within the organizations, sub-optimal design of the communication matrix and limited usage of the high-level architecture in the development teams To adapt to the current pace of software development and rapidly growing software systems new ways of working are required, both on technical and on an organizational level

36 citations

Book ChapterDOI
22 Sep 2003
TL;DR: This paper shows how these two issues can be addressed in practice by employing a methodology relying on the combined use of AEmilia — an architectural description language based on stochastic process algebra and queueing networks — which allows for a quick prediction, improvement, and comparison of the performance of different software architectures for a given system.
Abstract: When tackling the construction of a software system, at the software architecture design level there are two main issues related to the system performance. First, the designer may need to choose among several alternative software architectures for the system, with the choice being driven especially by performance considerations. Second, for a specific software architecture of the system, the designer may want to understand whether its performance can be improved and, if so, it would be desirable for the designer to have some diagnostic information that guide the modification of the software architecture itself. In this paper we show how these two issues can be addressed in practice by employing a methodology relying on the combined use of AEmilia — an architectural description language based on stochastic process algebra — and queueing networks — structured performance models equipped with fast solution algorithms — which allows for a quick prediction, improvement, and comparison of the performance of different software architectures for a given system. The methodology is illustrated through a case study in which a sequential architecture, a pipeline architecture, and a concurrent architecture for a compiler system are compared on the basis of typical average performance indices.

36 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