Katharina Wolter

Configuration Knowledge Representation and Reasoning

Configuration models specify the set of possible configurations (solutions). A configuration model together with a defined set of (customer) requirements are the major elements of a configuration task (problem). In this chapter, we discuss different knowledge representations that can be used for the definition of a configuration model. We provide examples that help to further develop the understanding of the underlying concepts and include a UML-based personal computer (PC) configuration model that is used as a reference example throughout this book.

Comprehensive System for Systematic Case-Driven Software Reuse

Reuse of software artifacts (blueprints and code) is normally associated with organising a systematic reuse framework most often constructed for a specific problem domain. In this paper we present a system (language, tool, reuse process) where software reuse is based on building and retrieving of so-called software cases (large compound artifacts) that can be reused between domains. The system is opportunistic in that software cases result from usual (non-reuse oriented) activities where also semantic information is added. This information is used to support regular development but may serve later to retrieve software cases. Having this common semantic basis, we can organise a systematic cross-domain reuse process where application logic of one system can be reused for systems within different domains.

Using a structure-based configuration tool for product derivation

Because of the possibly large variability in families of software systems and the complex dependencies between individual software components, product derivation in the context of software-intensive systems is not a trivial task. In this demonstration, we show the domain-independent structure-based configuration tool KONWERK, extended with a knowledge base containing a configuration model representing the domain of car periphery supervision systems. Using this tool, reasoning methods known from structure-based configuration are applied in the area of software-intensive systems. Starting with i) a model describing the variability of already realized software components and ii) a concrete task specification for a specific product, during a knowledge-based product derivation process a description of the needed software components is derived. This description is to be used for realizing, i.e. compiling and linking the desired product. The applicability and usefulness of such an approach will be shown in the demonstration.

Beyond physical product configuration --Configuration in unusual domains

Configuration technologies are typically applied in domains with physical products. In this article, we determine characteristics of configuration technologies that are used to compose non-pure physical products. Starting from two case studies software-intensive systems and scene interpretation where we successfully applied configuration, we determine some characteristics of knowledge representation languages and configuration systems that enable to solve configuration tasks in domains beyond pure physical products. As such, the article provides thinking outside the box of physical product configuration.

Reusing Terminology for Requirements Specifications from WordNet

In order to make requirements comprehensible to humans and as unambiguous as possible, a glossary and/or domain model is needed for defining the terminology used. Unless these are available from related projects, however,they are hard to create. Therefore, we propose to reuse terminology and its definition for requirements specifications from the semantic lexicon WordNet. For making this useful, however, we had to deal with the issue of disambiguation of the general terminology there for a given domain of a requirements specification.

Smarthome Configuration Model

In this chapter, we present a configuration model taken from a building automation domain. It provides complex aspects of configuration models such as separation of features of a system from realizing system components and domain-dependent workflows for the configuration process.

Model-Based Configuration Support For Software Product Families

In this paper, we present main aspects of the ConIPF methodology which can be used to derive customer-specific software products. The methodology is based on software product families and model-based configuration. First results from using the methodology in an industrial context are presented.