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
01 Dec 2009
TL;DR: This technical note proposes a structured approach for reviewing architecture documentation that is centered on the stakeholders of the artifact, engaging them in a focused, guided way to ensure that the documentation carries sufficient quality to enable them to do their jobs and to help them point out gaps and weaknesses.
Abstract: : This technical note proposes a structured approach for reviewing architecture documentation. Given the critical importance of architecture to software project success, it follows that the architecture cannot be effective unless it is effectively captured in documentation that allows the architecture's stakeholders to understand and use the architecture in the way it was intended. The approach does not assume a particular architecture methodology or a particular architecture documentation practice, although it was conceived in the context of the International Organization for Standardization (ISO) Recommended Practice for Architecture Description of Software-Intensive Systems and the SEI Views and Beyond approach to documenting software architectures. Like both of them, our approach is centered on the stakeholders of the artifact, engaging them in a focused, guided way to ensure that the documentation carries sufficient quality to enable them to do their jobs and to help them point out gaps and weaknesses. Our approach is not intended as a complete framework for architecture evaluation; rather it is meant to be used within such a framework, when one is available.
18 citations
TL;DR: How far the standard architecture evaluation method used at Capgemini sd&m already considers the GSD-specific good practices, and what extensions are necessary to achieve a comprehensive architecture evaluation framework for GSD are discussed.
Abstract: Due to ever increasing system complexity, comprehensive methods for software architecture evaluation become more and more important. This is further stressed in global software development (GSD), where the software architecture acts as a central knowledge and coordination mechanism. However, existing methods for architecture evaluation do not take characteristics of GSD into account. In this paper we discuss what aspects are specific for architecture evaluations in GSD. Our experiences from GSD projects at Capgemini sd&m indicate, that architecture evaluations differ in how rigorously one has to assess modularization, architecturally relevant processes, knowledge transfer and process alignment. From our project experiences, we derive nine good practices, the compliance to which should be checked in architecture evaluations in GSD. As an example, we discuss how far the standard architecture evaluation method used at Capgemini sd&m already considers the GSD-specific good practices, and outline what extensions are necessary to achieve a comprehensive architecture evaluation framework for GSD.
18 citations
Book•
11 May 2004
TL;DR: Research Papers.
Abstract: Research Papers.- Sotograph - A Pragmatic Approach to Source Code Architecture Conformance Checking.- Formal Analysis of Architectural Patterns.- Architectural Modelling in Product Family Context.- Reflection-Based, Aspect-Oriented Software Architecture.- Software Architecture Evolution through Dynamic AOP.- On the Role of Architectural Style in Model Driven Development.- UML 1.4 versus UML 2.0 as Languages to Describe Software Architectures.- From Acme to CORBA: Bridging the Gap.- Constraints of Behavioural Inheritance.- Experience Papers.- Software Architectures for Designing Virtual Reality Applications.- Generation and Enactment of Controllers for Business Architectures Using MDA.- Formalization of an HCI Style for Accelerator Restart Monitoring.- Experiences Using Viewpoints for Information Systems Architecture: An Industrial Experience Report.- Position Papers.- Software Architecture: The Next Step.- Using Architectural Models at Runtime: Research Challenges.- Maintainability through Architecture Development.- An Architecture Description Language for Mobile Distributed Systems.- Model Checking for Software Architectures.- Distilling Scenarios from Patterns for Software Architecture Evaluation - A Position Paper.- Invited Papers: European Projects in Software Architecture.- Towards an MDA-Based Development Methodology.- Correct Development of Embedded Systems.- Expressing Domain Variability for Configuration.- ArchWare: Architecting Evolvable Software.- The FABRIC Project.
18 citations
05 Nov 2000
TL;DR: This work focuses on the analysis of performance of an event-based middleware with two objectives in mind: to determine the design alternative that provides the best performance and to experience statistical analysis and simulation tools in order to understand their applicability to the evaluation of software architectures.
Abstract: A good architecture is a necessary condition to guarantee that the expected levels of performance, availability, fault tolerance, and scalability are achieved by the implemented system. While in the software architecture domain several approaches focus on checking static characteristics of software systems, a general approach to performance analysis, independent from a specific application domain, is still missing. In this paper we focus on the analysis of performances of an event-based middleware with two objectives in mind: first, to determine the design alternative that provides the best performances; second, to experience with statistical analysis and simulation tools in order to understand their applicability to the evaluation of software architectures.
18 citations
TL;DR: This paper considers how resource architecture emerges during design, the relationship of software and hardware resources, some classes of resource architecture, and what they can tell us about system performance.
Abstract: Performance is determined by a system's resources and its workload. Some of the resources are software resources which are an aspect of the software architecture; some of them are even created by the software behaviour. This paper describes software resources and resource architecture, and shows how resource architecture can be determined from software architecture and behaviour. The resource architecture is distinct from views of software architecture which describe software components, but it is related to the so-called "execution view" of architecture. The paper considers how resource architecture emerges during design, the relationship of software and hardware resources, some classes of resource architecture, and what they can tell us about system performance. Other uses of resource architecture are, to analyze deadlocks, to understand special software architectures developed for demanding situations, and to analyze how subsystems fit together when they share resources. Resource architecture can be described using description languages (ADLs) developed for software architecture.
18 citations