| 1 › Department of Mathematics and Computing Science, Software Engineering and Architecture Group / Matthias Galster Describing Variability in Service- oriented Software Product Lines

| 2 Problem ›Build generic service-based architectures (“SaaS”) Variability (instead of “as is”) Architecture quality attributes (QA)

| 3 Variability as a viewpoint of its own ›Relating IEEE STD 1471 (ISO/IEC 42010) concepts Architecture description View Variability viewpoint Extension of H. Koning & H. van Vliet 2006 (A method for defining IEEE Std 1471 viewpoints, JSS 79(1), pp ) 1..* Stakeholder 1..* Variability concern 1..* Variability model 1..*

Stakeholders + concerns StakeholderWhere?Impact on QA?Interactions?Variation type? Architect  Maintainer  Operator  Software vendor  User  SOA infrastructure developer  SOA application generator  Core asset provider  Service vendor  Evaluator 

| 5 Architectural models to consider variability ›Variability mapping model (“C & C”) Link variability to location Example on next slide ›Variability dependency model (matrix) Link variability to its impact on quality attributes ›Variability interaction model (matrix) Describe interactions between variants

| 6 Example Variant type vParameter + variants Variant type vService + variants Service as variation point Parameter as variation point (requires newly introduced “interface”)

Next steps ›Further document architectures ›Define new models ›Derive set of viewpoints for a viewpoint catalogue ›“Enrich” models UML profile | 7

| 8 Thank you for your attention Comments welcome! Contact: Matthias Galster