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
05 Jan 2004
TL;DR: The characteristics of the three architecture paradigms and the business drivers for their applications are described, with the goal of deriving some practical principles and strategies to best deal with them in software engineering practices.
Abstract: Object-oriented architecture (OOA), component-based architecture (CBA), and service-based architecture (SBA) represent three technical architecture paradigms in current software systems object, component, and service are three key concepts in distributed software systems From implementation point of view, a service is implemented by one or more components, which in turn are often implemented in object-oriented programming languages like C+ + and Java Distributed component-based software systems can be structured in any of the architecture paradigms, some have more advantages than others depending on business requirements Understanding the characteristics, features, benefits, and concerns of the architecture paradigms is crucial to the successful design, implementation and operation of a distributed system In this paper, we describe the characteristics of the three architecture paradigms and the business drivers for their applications The parallel evolution of architecture paradigms and software development methodologies is discussed in the context of practical business needs Component-based software developers for distributed systems should decide on the architecture paradigms based on business requirements The evolution of architecture paradigms and the selection of architecture paradigms have profound influences and impacts on component-based distributed systems, in the way components are designed and in the way component interactions are implemented We discuss these influences and impacts with the goal of deriving some practical principles and strategies to best deal with them in software engineering practices

51 citations

Proceedings ArticleDOI
01 May 2014
TL;DR: A development process that defines how reference architectures can be exploited for building robotic applications, and the HyperFlex software toolchain, which has been developed for supporting the design and the reuse of reference architectures are provided.
Abstract: During the last years robotic researchers have been able of developing extremely complex applications. The complexity of these applications is reflected by the variety of functionalities involved, which are provided by a significant number of components. Although the reuse of software components is becoming a best-practice, the reuse of reference architectures, which model sub-systems providing functionalities common to a great number of applications, is still uncommon. This paper provides two contributions to this topic: (a) a development process that defines how reference architectures can be exploited for building robotic applications, (b) the HyperFlex software toolchain, which has been developed for supporting the design and the reuse of reference architectures. The idea presented in this paper is simple yet powerful: instead of building complex applications by reusing single components, even more complex applications can be developed by reusing reference architectures of mature sub-systems.

50 citations

ReportDOI
01 Jun 2000
TL;DR: The application of the Architecture Tradeoff Analysis Method (ATAM) to evaluate a reference architecture for ground-based command and control systems and the results are explored, including the benefits of performing an ATAM-based architecture evaluation both to the acquirer and to the developer.
Abstract: : The software architecture of a system is a major determinant of software quality and one of the earliest artifacts available for evaluation. For a government acquisition organization, the ability to evaluate software architectures can have a favorable impact on the delivered system. This technical note describes the application of the Architecture Tradeoff Analysis Method (ATAM) to evaluate a reference architecture for ground-based command and control systems. The use of the term reference architecture in the context of this application is presented. A general overview of the ATAM process is provided and the results of the ATAM are explored, including the benefits of performing an ATAM-based architecture evaluation both to the acquirer and to the developer.

50 citations

Journal ArticleDOI
TL;DR: In this paper, a grounded theory study based on 15 semi-structured interviews was conducted in order to find out about the wide spectrum of architecture practices in software product developing organizations, which indicated that a chief architect or central developer acts as a "walking architecture" devising changes and discussing local designs while at the same time updating his own knowledge about problematic aspects that need to be addressed.

49 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