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
••
04 May 2015TL;DR: The dynamic reconfiguration support provided by π-ADL is introduced, a formal, well-founded theoretically language for describing dynamic software architectures under structural and behavioral viewpoints and integrated with the Go programming language, thus enabling to automatically generate implementation code from architectural descriptions, thus tackling the existing gap between them.
Abstract: Dynamic software architectures are those that describe how components and connectors can be created, interconnected, and/or removed during system execution Most existing architecture description languages (ADLs) provide a limited support to expressively describe these architectures and entail architectural mismatches and inconsistencies between architecture and implementation due to their decoupling from implementation In this paper, we introduce the dynamic reconfiguration support provided by p-ADL, a formal, well-founded theoretically language for describing dynamic software architectures under structural and behavioral viewpoints p-ADL provides architectural-level primitives for specifying programmed dynamic reconfigurations, ie, Foreseen changes described at design time and triggered at runtime In addition, p-ADL allows enacting dynamic reconfiguration by means of: (i) an exogenous approach, in which it is possible to control all elements of the software architectures and to apply the changes on the whole structure, and (ii) an endogenous approach, in which the architectural elements can manage dynamic reconfiguration actions Furthermore, p-ADL is integrated with the Go programming language, thus enabling to automatically generate implementation code from architectural descriptions, thus tackling the existing gap between them We hereby use a real-world flood monitoring system as an illustrative example of how to describe dynamic software architectures in p-ADL and automatically generate source code in Go
38 citations
••
TL;DR: An implementation of this architecture is shown, as well as its benefits in terms of autonomy, scalability, deployment and security, and the proposed implementation is based on existing interfaces, allowing for standardization.
38 citations
••
16 Feb 2004TL;DR: This paper presents a synthesis tool which preserves the full flexibility of the architecture description language LISA, while being able to generate the complete architecture on RT-level using systemC.
Abstract: Architecture description languages are widely used to perform architecture exploration for application-driven designs, whereas the RT-level is the commonly accepted level for hardware implementation. For this reason, design parameters such as timing, area or power consumption cannot be taken into consideration accurately during design space exploration. Design automation tools currently used to bridge this gap are either limited in the flexibility provided or only generate fragments of the architecture. This paper presents a synthesis tool which preserves the full flexibility of the architecture description language LISA, while being able to generate the complete architecture on RT-level using systemC. This paper also presents two real world architecture case studies to prove the feasibility of our approach.
38 citations
••
24 Jun 1998TL;DR: The framework is applied to analyze the actual software architecture of 6 subsequent releases of a 15MLoc telecommunications product and shows that the framework can provide much insight on the actual implementation of a system with a layered architecture.
Abstract: This paper presents the results of an empirical study. The study aims at evaluating the ability to understand the coherence between design documents that describe the layered architecture of large scale systems, and the actual structure of the software source file organization. A clear set of objectives to be addressed for achieving a good understanding of a layered architecture is defined. The objectives are focused on identifying the interfaces between layers, in terms of cross-layer file dependencies. An analysis framework for achieving these objectives is proposed. The framework is applied to analyze the actual software architecture of 6 subsequent releases of a 15MLoc telecommunications product. Results of that experiment show that the framework can provide much insight on the actual implementation of a system with a layered architecture.
38 citations
••
04 Apr 2005TL;DR: ARM provides a method to determine when an architecture model is complete in that the level of details represented by the architecture design is sufficient, and applies to a real-life industry case retrospectively to demonstrate how ARM can overcome issues surrounding traceability and verifiability.
Abstract: Architecture modeling is practiced extensively in the software industry but there is little attention paid to the traceability, verifiability and completeness of architecture designs. Deficiencies in any of these three areas in an architecture model can be costly and risky to projects. We propose the architecture rationalization method (ARM), which is based on architecture rationale, to overcome these issues. ARM makes use of both qualitative and quantitative rationales for selecting architecture designs. Quantitative rationale uses a model based on costs, benefits and risks in the selection process. ARM provides a method to determine when an architecture model is complete in that the level of details represented by the architecture design is sufficient. We apply ARM to a real-life industry case retrospectively to demonstrate how ARM can overcome issues surrounding traceability and verifiability.
38 citations