1 / 26

Engineering Self-adaptive Service Mashups

Engineering Self-adaptive Service Mashups. Mahdi Bashari LS3 Colloquium May 7 th 2014. Outline. Background Motivation SASEM Framework. Service Mashup. A service mashup is a new service that uses functionalities or data of more than one service to provide a new functionality. 

albina
Télécharger la présentation

Engineering Self-adaptive Service Mashups

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. Engineering Self-adaptive Service Mashups Mahdi Bashari LS3 Colloquium May 7th 2014

  2. Outline • Background • Motivation • SASEM Framework

  3. Service Mashup • A service mashup is a new service that uses functionalities or data of more than one service to provide a new functionality.  • Service mashups allow rapid development of simple yet efficient customized application for a specific context. • Goal:  building the service without having technical knowledge about the constituting services and with the least effort.

  4. Difference with Service Composition • Service mashups can be reused more easily. • Service mashups usually use web technologies and standards. • Service mashup are light weight in the sense that mashup itself usually use external functionality and have minimal functionality-related code. • The service should be possible to build by a non-expert, without using complex development environment.

  5. Why Service Mashup • Popularity online services: • more and more companies provide their application API through online services • Ease of use of services: • service can be well-defined interface which allow to use their functionality at high-level without concerning about the details of how the functionalities are provided • =>Provide user with tools to  compose their needed services.

  6. Example: Padmapper

  7. Example: Trendsmap

  8. Self-adaptation • Self-Adaptation is ability of a system to change of propertiesand behavior of itself at runtime in response to dynamically varying user needs and context. • Example: Your cellphone • Goal: maintaining desirable service in a dynamic context

  9. Why Self-adaptation • To maintain service. • To perform optimally. • To prevent from failure. • …

  10. Software Product Line (SPL) • The Software Product Line Engineering (SPLE) paradigm suggests an effective way to deal with the variability of similar products especially when satisfying requirements of different operating environments and users.  • Goal: Mass production and mass customization at the same time

  11. Why Software Product Line? • Reduce effort • Increase Quality • Decrease time to market • Customer customization • How: by managing variability systematically

  12. Outline • Background • Motivation • SASEM Framework

  13. Problems with Service Mashup • Lack of reliability • Unguaranteed quality of service • Lack of versatility

  14. Solution: self-adaptation • There are usually alternative services providing same or similar functionality on the web. • Service mashup can adapt to use other available service in order to: • Maintain functionality when one of its services fail to provide its service • Maintain quality of service when current service mashup does not satisfy desirable QoS • Maintain service when current service mashup cannot provide requested service

  15. Problem with self-adaptation • Hard to implement (even for experts) • In many cases unreliable • In many cases inefficient

  16. Solution: SASEM •  SASEM is a process, a runtime engine and a supporting toolkit for building self-adaptive service mashups which adopts the methods and models mostly from DSPL in order to enable easy to implement self-adaptive service mashups by the non-expert user. 

  17. Research Statement • Self-adaptation in service-mashup can help their reliability, efficiencyand flexibility. Dynamic Software Product Line is well-suited for development of self-adaptive service mashups. It provide methods and models which allow the non-expertuser with to easily develop reliable and efficient self-adaptive service mashups.

  18. Outline • Background • Motivation • SASEM Framework

  19. How SASEM works?

  20. Characteristics of SASEM • Is architecture-based • Uses Control Loop • Is non-invasive • Is centralized

  21. Howa SASEM is designed? • Through a three phase process: • Domain Engineering. • Application Engineering. • Runtime Adjustment.

  22. SASEM Process

  23. Model Perspective

  24. How SASEM adapts? • Trigger: • Change in user requirements • Change in service functionality or performance • Mechanism: • By changing used services • By changing how services are connected • How • Using a control loop

  25. SASEM Control Loop

  26. Thank you!

More Related