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: An approach to writing requirements specifications for Internet-based control systems, from which architectures can be derived, is described in terms of a functional model, which is then extended to form an information architecture.
Abstract: The Internet is playing an important role in information retrieval, and additionally industrial process manipulation. This paper describes an approach to writing requirements specifications for Internet-based control systems, from which architectures can be derived. The requirements specifications developed are described in terms of a functional model, which is then extended to form an information architecture. Distinct from the functional model, the information architecture provides an indication as to the architectural structure of subsequently developed Internet-based control systems. Three general control structures are generated from the analysis of an information architecture. An integrated-distributed architecture is derived as an ideal implementation, in which a control system is linked to the Internet at all levels of a control system hierarchy.
12 citations
••
TL;DR: A case study from a global company developing a new generation of programmable controllers to replace several existing products shows that the component-based architecture effectively supports distributed development and that the effort required for implementing certain functionality has been substantially reduced while the system’s performance and other run-time quality attributes have been kept on a satisfactory level.
Abstract: This chapter presents a case study from a global company developing a new generation of programmable controllers to replace several existing products. The system needs to incorporate support for a large number of I/O systems, network types, and communication protocols. To leverage its global development resources and the competency of different development centers, the company decided to adopt a component-based software architecture that allows I/O and communication functions to be realized by independently developed components. The architecture incorporates a subset of a standard component model. The process of redesigning the software architecture is presented, along with the experiences made during and after the project. An analysis of these experiences shows that the component-based architecture effectively supports distributed development and that the effort required for implementing certain functionality has been substantially reduced while, at the same time, the system’s performance and other run-time quality attributes have been kept on a satisfactory level.
12 citations
••
17 May 1997TL;DR: This work motivates the need for architectural description languages in general, concentrating on Darwin, an architectural description language specifically designed for the specification and construction of distributed software systems.
Abstract: We motivate the need for architectural description languages in general, concentrating on Darwin, an architectural description language specifically designed for the specification and construction of distributed software systems.
11 citations
••
19 May 2003
TL;DR: Thales recently contributed this knowledge and experience in a joint submission regarding the OMG's Data Distribution Service (DDS) for Real-time systems.
Abstract: Over the past 10 years, Thales Naval Nederland (TNN) has successfully applied a pure data-centric architecture called SPLICE in its naval Combat Management Systems This fielded architecture provides the essential non-functional properties as demanded in these mission-critical environments such as (real-time) performance, scalability, fault-tolerance and evolveability. Thales recently contributed this knowledge and experience in a joint submission regarding the OMG's Data Distribution Service (DDS) for Real-time systems. The SPLICE architecture is characterized by autonomous applications with minimal dependencies where function and interaction are clearly separated and SPLICE-agents act as real-time information brokers. SPLICE thus offers a normalized environment that is designed once for all applications and which delivers 'the right information at the right place at the right time'.
11 citations
•
[...]
TL;DR: The architecture provides a way for caching responses from device and thereby increasing its efficiency and performance and yielding quick response times and can potentially be used to prevent security threats like Denial-of-Service (DoS) attacks on embedded devices attached to the web and increase its performance.
Abstract: "Web Of Things" evolved from "Internet Of Things". Lot of research has been done in designing architecture for "Web Of Things". Two main architectures are Smart gateway based architecture and embedded Web Server based architecture. These architectures address some of the basic and essential issues relating to Service Oriented Architecture for "Web Of Things". Taking into consideration the period of coexistence of IPv4 and IPv6 we propose an architecture using SOCKS protocol based IPv6/IPv4 gatewaying and refinements which facilitates smooth heterogeneous communications between the IPv6 and IPv4 enabled embedded nodes and can potentially be used to prevent security threats like Denial-of-Service (DoS) attacks on embedded devices attached to the web and increase its performance. Our architecture provides a way for caching responses from device and thereby increasing its efficiency and performance and yielding quick response times.
11 citations