1 / 19

Towards a Services-based Process Platform

Towards a Services-based Process Platform. Mathias Weske Hasso Plattner Institut of IT Systems Engineering University of Potsdam. BPM Lifecycle. Design and Analysis Process modeling, validation, verification Configuration Implementation of BP Integration of ext apps Enactment

kory
Download Presentation

Towards a Services-based Process Platform

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. Towards a Services-basedProcess Platform Mathias Weske Hasso Plattner Institut of IT Systems Engineering University of Potsdam

  2. BPM Lifecycle • Design and Analysis • Process modeling, validation, verification • Configuration • Implementation of BP • Integration of ext apps • Enactment • BP instance enactment • Evaluation • Process mining, execution analysis

  3. Service-Oriented Computing • Goals • Provide re-usable and well specified business functionality through services • Create new solutions and adapt existing ones using loosely coupled services • SOA • Based on roles and their interaction [Burbeck: The Tao of e-business services (2000)]

  4. Static and Dynamic Binding • Static binding • Service implementation bound at design time • Ambiguities in service description resolved by programmer • Dynamic binding • Service implementation discovered and bound at run time • Unambiguous specification of services required

  5. Domain Ontology

  6. ServiceParameter Mapping • Annotate services • Map parameters to concepts of adomain ontology • Example: Call-center application • I have: Customer Phone number (precondition) • I need: Customer Order (post-condition)

  7. Semantic Service Annotations: Functionality • Specify Functionality • Relationships between input and output parameters • Services specified by Preconditions and Postconditions • Sample Query • Find a service that takes customer address as input and returns order of that particular customer

  8. Service Composition • Idea • Business processes realized by service compositions • Service composition modelling with semantic assistance Precondition: Phone No Post-condition: Order

  9. Adaptive Services Grid Overview • Project Data • EU-funded IP in FP6, coordinated by UP / HPI • 21 partners: D(9), PL(6), A(2), IRE, N, FIN, AUS • Goal • Research concepts for semantic service platform • Flexible service landscapes • Automatic service composition • Flexible enactment and dynamic re-binding

  10. Sample Integration Scenario Tourist Services Application EuroTel : GetPhoneLocation Attraction Booking XHTML Application HRS: I want to book a Semantic Service Request GetAttractionInformation cultural event for this evening! HRS ASG Facade (Basic Service Provider) End Service Consumer Composition Deployment Map24: Negotiation Monitoring GetRouteDescription pubish new And Matchmaking Discovery services in ASG Contracting Profiling Map24 (Basic Service Provider) Invocation Replanning Services Grid Infrastructure SOAP Amex : ASG Service PayInvoice ASG Platform Management Tools Amex EuroTel (End Service Provider, Basic Service Provider) (Basic Service Provider)

  11. ASG Architecture

  12. Typical Application Flow Semantic service call:“Find all attractions for my location using my search criteria” Semantic service call: “I want to have a description of a route from my current position to the selected attraction.”

  13. ServiceLandscape

  14. Service Composition to beplanned initialstate goal available services

  15. Service Composition (optimized) to beplanned

  16. Re-planning Is Triggeredif a Service Fails Error

  17. Service Provisioning

  18. Major results of the project • Results • Architecture framework and reference implementation • Validation by use case scenarios • Questions • Where do we need the flexibility? • Balance between the investment in ontology/service modelling and obtainable level of automation? • Not addressed • Interacting processes / choreographies • Services with complex interaction behaviour • Complex service enabling

  19. Conclusions • BP in SOA pose questions to research community • Process design and analysis • Assisted process modelling • Process analysis including interaction behaviour • Configuration: Dynamic binding • Flexible process execution environments • Re-binding and Re-planning • Service enabling and service granularity • Multi disciplinary effort • BP persons • Business / application engineers • Software engineers • Ontology engineering / Semantics

More Related