1 / 10

Model Driven Engineering for Software Product Lines

Model Driven Engineering for Software Product Lines. ICSE PLEASE 23 May 2011. Group Members. <MDE4SPL>. Aaron Wolfson Gary Chastek Hassan Gomaa Harvey Siy Maurice ter Beek Patricia Aliseri Stefania Gnesi Steve Livengood Vinay Kulkarni. SPLE characteristics. SPLA

jerrod
Download Presentation

Model Driven Engineering for 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. Model Driven EngineeringforSoftware Product Lines ICSE PLEASE 23 May 2011

  2. Group Members <MDE4SPL> • Aaron Wolfson • Gary Chastek • Hassan Gomaa • Harvey Siy • Maurice ter Beek • Patricia Aliseri • Stefania Gnesi • Steve Livengood • Vinay Kulkarni

  3. SPLE characteristics • SPLA • Variability management • Resolution management • Composition • Semantics • Domain models, Ontologies • Life cycle management • Specification • Construction • Evolution <MDE4SPL>

  4. Variability management • Several mechanisms exist • Feature models, Decision models etc • Traceability from features to software artefacts implementing them is missing • Hard to operationalize in practice • Variability models should be treated as principal SDLC artefacts <MDE4SPL>

  5. Resolution management • Seveal mechanisms exist • Configurators based on boolean logic (for feature models) • Processors for DSLs • Traceability from features to software artefacts implementing them is missing • Hard to operationalize in practice • Resolution models should be treated as principal SDLC artefacts <MDE4SPL>

  6. Composition • Several composition mechanisms exist at programming language level, but, may not be, • Most intuitive • Sufficient • Furthermore, composition needs to be effected at, • Design time • Installation time • Run time • Seems there is a need for more abstract mechanism to address these issues <MDE4SPL>

  7. Semantics • Need traceability from PL specs to the domain to which the PL belongs • Semantically rich models of domain like ontologies etc will help, • Entire SDLC operations • Perform richer analyses <MDE4SPL>

  8. SDLC • Several approaches exist to “do SPLE” but, • Don’t necessarily cover the entire SDLC • Whole lot of work needed to use these approaches <MDE4SPL>

  9. MDE • Model-driven approaches address product line requirements in platform space, • Platform-independent models being targeted to multiple platforms But need to be extended for, • Specifying product lines / application families • Modeling variability  Extend existing meta models • Deriving a family member • Resolving variability  Use existing mechanisms but applied to models • Composition • Abstraction + algebra + model transformation • Supporting analyses • Semantic compatibility / Equivalence • Better visualization of variability

  10. Next Steps <MDE4SPL> We hope to report on some of the identified issues in PLEASE 2012

More Related