1 / 8

Describing Variability in Service-oriented Software Product Lines

Describing Variability in Service-oriented Software Product Lines. Department of Mathematics and Computing Science, Software Engineering and Architecture Group / Matthias Galster. Problem. Build generic service-based architectures (“SaaS”) Variability (instead of “as is”)

hilel-stanley
Download Presentation

Describing Variability in Service-oriented Software Product Lines

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  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 1..* Variability model 1..* 1..* 1..* Architecture description View 1..* 1..* 1..* 1..* 1..* Variability concern Variability viewpoint Stakeholder Extension of H. Koning & H. van Vliet 2006 (A method for defining IEEE Std 1471 viewpoints, JSS 79(1), pp. 120-131)

  4. Stakeholders + concerns

  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. Service as variation point Example Variant type vParameter + variants Variant type vService + variants Parameter as variation point (requires newly introduced “interface”)

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

  8. Thank you for your attention Comments welcome! Contact: Matthias Galster m.r.galster@rug.nl

More Related