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: The article outlines a framework for classifying, evaluating, and comparing process architecture methods from four different views: contents, form, purpose, and lifecycle, and suggests how it might be refined.
Abstract: Piecemeal identification, development, and support of an organisation's processes may lead to problems: first, it may be difficult to identify which processes should be supported, and, second, it is unlikely that processes developed piecemeal will either optimise the achievement of an organisation's objectives, or work well together. One solution involves identifying and modelling an organisation's process architecture, and then using it to develop and subsequently support the constituent processes. However, this solution leads to a new challenge: a number of different types of process architecture method have been proposed, but it is not clear which should be used in a given situation. To address this challenge, the article outlines a framework for classifying, evaluating, and comparing process architectures. Following the work of Rolland et al.(1998), the proposed framework considers process architecture methods from four different views: contents, form, purpose, and lifecycle. To partially validate the framework, it was used to classify and evaluate Riva (Ould 2005), a particular process architecture method. The result of this application of the framework suggests how it might be refined. It could then be used for comparing other process architecture methods. Such a comparative analysis should help practitioners choose between process architecture methods. Copyright © 2005 John Wiley & Sons, Ltd.
27 citations
•
01 Jan 1999
TL;DR: This paper develops categorizations for the evolution of requirements, the product-line architecture and product- line architecture components and analyzes and presents the relations between these categorizations.
Abstract: Product-line architectures present an important approach to increasing software reuse and reducing development cost by sharing an architecture and set of reusable components among a family of products. However, evolution in product-line architectures is more complex than in traditional software development since new, possibly conflicting, requirements originate from the existing products in the product-line and new products that are to be incorporated. In this paper, we present a case study of product-line architecture evolution. Based on the case study, we develop categorizations for the evolution of requirements, the product-line architecture and product-line architecture components. Subsequently, we analyze and present the relations between these categorizations.
27 citations
••
20 Jun 2012TL;DR: Kynoid is the first extension of Android which enables the sharing of resources while respecting individual security policies for the data-items stored in these resources.
Abstract: We introduce Kynoid, a real-time monitoring and enforcement framework for Android. Kynoid is based on user-defined security policies which are defined for data-items. This allows users to define temporal, spatial, and destination constraints which have to hold for single items. We introduce an innovative approach to allow for the real-time tracking and enforcement of such policies. In this way, Kynoid is the first extension of Android which enables the sharing of resources while respecting individual security policies for the data-items stored in these resources. We outline Kynoid's architecture, present its operation and discuss it in terms of applicability, performance, and usability. By providing a proof-of-concept implementation we further show the feasibility of our framework.
27 citations
••
TL;DR: In new product development situations or in re-engineering projects, system architects could use this method in the early design stages to predetermine cohesive modules and integrative elements and to simulate a domain architecture by propagating architecture choices from another domain.
Abstract: Modular product design has received great attention for about 10 years, but few works have proposed tools to either jointly design the functional and physical architectures or propagate the impact of evolutions from one domain to another. In this paper, we present a new method supporting the product architecture design. In new product development situations or in re-engineering projects, system architects could use this method in the early design stages to predetermine cohesive modules and integrative elements and to simulate a domain architecture by propagating architecture choices from another domain. To illustrate our approach, we present an industrial case study concerning the design of a new automobile powertrain.
27 citations
••
01 May 1996TL;DR: This paper introduces the architecture language of Clock, a language for the development of interactive, multiuser applications that possesses three properties supporting the easy restructuring of software architectures: restricted scoping supported by a constraint-based communication system, automatic message routing, and easy hierarchical restructuring of architectures.
Abstract: As a program's functionality evolves over time, its software architecture should evolve as well so that it continues to match the program's design. This paper introduces the architecture language of Clock, a language for the development of interactive, multiuser applications. This architecture language possesses three properties supporting the easy restructuring of software architectures: restricted scoping supported by a constraint-based communication system, automatic message routing, and easy hierarchical restructuring of architectures. Clock's architecture language has a visual syntax, supported by the Clock-Works programming environment.
26 citations