Eelco Rommes

Multi-view Variation Modeling for Scenario Analysis

We propose an approach using scenarios to describe a spectrum of possible futures and analyze them to assess and improve the ease of accommodating new requirements by a system architecture. Variation modeling forms an important part of the analysis. This paper focuses on an approach to variation modeling across multiple architectural views. The models do not only display the variability in these views, but also the relationships between them. In particular, they can show how choices in one view influence choices in the other views.

Scenario-based decision making for architectural variability in product families

In this paper, we present a systematic approach towards decision making for variability in product families in the context of uncertainty. Our approach consists of the following ingredients: a suitable set of architectural views that bridge the gap between customer needs and available technology, a multi-view variation modeling technique, the selection of several scenarios of different kinds, and a quantitative analysis of quality aspects for these scenarios.

Implementing a Reuse Strategy: Architecture, Process and Organization Aspects of a Medical Imaging Product Family

Product family engineering is one form of strategic re-use that can be particularly effective. However, establishing a product family is not a simple matter. Technical and non-technical aspects have to be dealt with to reap the benefits of organization-wide software reuse. Especially if the scope surpasses that of a single product domain, this can be challenging. The family may then span several product groups, each of which might have its own product family installed. Product variability and the number of people involved will be larger, calling for appropriate measures. We present a strategy for software reuse in complex, software-intensive medical systems. We describe its implementation in a platform architecture, an organization and its processes, as well as its evolution in response to strategic changes. The case presented here is especially interesting because it deals with a hierarchical product family for a wide range of complex systems, in a large organization.

Measuring Architecting Effort

The amount of architecting effort is a factor in a software development project’s efficiency. Before steps can be taken to optimize this factor, its current position must be know. We have measured the amount of architecting done in two industrial cases relating to the development of medical imaging systems.We discuss these cases and some of the problems that we encountered.