Conference Paper

Implementation of Interceptor Based Resource Server for Software Product Line.

DOI: 10.1109/CSCWD.2007.4281595 Conference: Proceedings of the 11th International Conference on Computer Supported Cooperative Work in Design, CSCWD 2007, April 26-28, 2007, Melbourne, Australia
Source: DBLP

ABSTRACT The responsibility of resource server is to store and manage the reusable and product-specific assets produced in the process of software development applying software product line principals. Separately designed for each specific resource type, classical resource server could not satisfy the demands for mass storage of various resource types in collaborative development environment. Interception design pattern is introduced as a novel means to implement resource server. Interceptors with specific functionalities are developed and configured for various resource types in domain to provide a uniform framework to deal with distinct types of resource, including customized resource type. The description of the resource handling process using Pi calculus demonstrates the validity of the approach.

  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns. The nice thing is, most experienced OOP designers will find out they've known about patterns all along. It's just that they've never considered them as such, or tried to centralize the idea behind a given pattern so that it will be easily reusable.
    Reading, MA: Addison-Wesley. 01/1995;
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Variability is the ability to change or customize a software system, i.e., software architects anticipate change and design architectures that support those changes. If the architecture is used for different product versions, e.g., in a software product line context, it becomes important to understand where change has to be planned and the options possible in particular situations. Three variability issues have been identified in a case study involving a software company specialized in product and system development for professional mobile communication infrastructure. These issues are discussed and analyzed and illustrate the need for handling variability in a more explicit manner. To address this need, this paper suggests a method to represent and normalize variability in industrial software systems. The method is exemplified by applying it to the software product line of the aforementioned company.
  • Source
    Datenbank-Spektrum. 01/2006; 19:5-14.