The breakout session discussed approaches to capturing variability in architectural views, including integrating variability directly into views or using a separate variability view, as well as combinations. It also addressed traceability between separate variability and architecture models, views with embedded variability, and views and other artifacts. The research agenda focused on combining separation of concerns and integration regarding variability, representation without overhead, and automation opportunities around consistency, product derivation, and traceability.

1. VARSA 2012
Breakout session
Topic: variability and traceability

2. Variability
Approaches to capturing variability in
architectural views:
● Integrated into views
● Easier, but little traceability.
● Separated (= orthogonal), in a variability view
● Easier to trace (mapping to other views), but
added complexity and up-front investment.
● Combination of both
● Including case-by-case decisions and
heterogeneous views.

3. Traceability
Traceability between:
● Separate variability models and architecture
models.
● Architecture views with embedded variability
● Views and other artifacts (e.g. code, tests)

4. Research agenda (1 of 2)
● How to combine Separation of Concerns and
integration with respect to variability
● Look at stakeholders' needs, nature of domain
● “No silver bullet” in variability representation
● Don't add too much overhead
● Use cost-based reasoning
● Manage many options with abstraction – or
avoid them

5. Research agenda (2 of 2)
● Automation opportunities:
● Checking consistency of models
● Deriving products
● Creating traceability links
● Integration of different variability management
approaches in heterogeneous organizations
● Traceability through a single metamodel that
is used to generate architectural views