1 / 39

INTRA-SERVICE ADAPTABILITY FOR ECA-CENTRIC WEB SERVICES USING CONTRACT AND ASPECT

Syed Saif ur Rahman 1 , Azeem Lodhi 2 , Nasreddine Aoumeur 2 , Claus Rautenstrauch 2 , Gunter Saake 1. INTRA-SERVICE ADAPTABILITY FOR ECA-CENTRIC WEB SERVICES USING CONTRACT AND ASPECT.

gretchen-torres
Download Presentation

INTRA-SERVICE ADAPTABILITY FOR ECA-CENTRIC WEB SERVICES USING CONTRACT AND ASPECT

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. Syed Saif ur Rahman1, Azeem Lodhi2, Nasreddine Aoumeur2, Claus Rautenstrauch2, Gunter Saake1 INTRA-SERVICE ADAPTABILITY FOR ECA-CENTRIC WEB SERVICES USING CONTRACT AND ASPECT 1Database Research Group, 2Business Informatics Group, School of Computer Science, University of Magdeburg, Germany {srahman, mkhanlod, aoumeur, claus.rautenstrauch, saake} @iti.cs.unimagdeburg.de

  2. Agenda • Motivation • Approach • Implementation • Conclusion

  3. Motivation • Business domain • Competitive • Changing • Managed through information systems • Information system • Need to adapt to changes in business • Adaptability

  4. Motivation • Adaptive Information system • Information system developer • User requirements change • Business processes and activities are not well documented • Information system customization • For heterogeneous domains with unique business processes • Information system maintenance • Precisely identify the impact of change • High maintenance cost

  5. Case Study: Scenario Business Systems Banking Hotel Management Airline Travel Agency 5

  6. Case Study: Scenario Banking System Business Processes Account Opening Cash Management With Draw Deposit Cash Transfer Domestic Foreign Personal Management Payroll Costing 6

  7. Case Study: Scenario Banking Cash With Draw Activity Balance Check Account Type Check Credit Limit Interest Rate With Draw Tax Debit May trigger cash deposit activity for interest deposit 7

  8. Case Study: Scenario Banking System Customer-tailored services Cash Withdraw activity Participating partners Customer Account Bank 8

  9. Case Study: Scenario Customer Can own one or more account Each account can be of different category VIP Can enjoy credit limit Normal No credit limit 9

  10. Approach • Adaptive information system • Service-oriented computing • Web services • Workflow management system • Rule-based • ECA (Event-Condition-Action) centric • Contract • Aspect-oriented programming • Information system adaptability • At finer granularity i.e. Activity level • At coarser granularity i.e. Process level

  11. Approach: Workflows • A workflow is the automation of a business process, in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules • Rules-based predictable execution of activities/operations

  12. Approach: Workflows • Intra-activity • Within single activity • Defines how activity is executed internally in terms of operations • Inter-activity • Across several activities • Defines how multiple activities are executed with in process

  13. Approach: Workflows

  14. Approach: Workflows Rules defined as ECA Event Condition Action 14

  15. Approach: Workflow Management System Interpret workflows Creates and manages execution We propose the use of Workflow Management System to control intra-activity operations execution Workflow rules are updatable at runtime 15

  16. Approach: Contract • Relationship between • Partners • Within process or activity • Instantiated during workflow execution • Based on • Participating partners • Rules • Contract can be canceled • Customer can have different contract with account • For each rule • i.e. Different credit limit and interest rates

  17. Approach: Contract

  18. Case Study: Contract Instantiation

  19. Approach: Aspect-Oriented Programming • Aim to separate cross-cutting concerns • Prevents • Code tangling • Code scattering • Ensures • Scalability • Maintenance • Separates cross-cutting code as Aspect • Aspect weaver brings program code and Aspect together • Using join-points, point-cuts and advice information

  20. Aspectual Adaptation • Adaptation • Operations defined as aspect • Weaving decision based on rules • Benefits • Adaptable operation execution • Cleaner implementation • Operation loaded when needed • Better performance and easy upgrade

  21. Aspectual Adaptation Account Aspect Weaver (Workflow Engine) Aspects Debit DeductInterest() WithDrawTax() … Debit Code … RecalcualteBalance() ECA (Weaving Details) DeductInterest ReCalculateBalance WithDrawText 21

  22. Case Study: Aspectual Adaptation

  23. Case Study: Aspectual Adaptation

  24. Case Study: Aspectual Adaptation

  25. Case Study: Aspectual Adaptation

  26. Compliant Mapping of ECA to .NET/J2EE 26

  27. Compliant Mapping of ECA to .NET/J2EE 27

  28. Compliant Mapping of ECA to .NET/J2EE 28

  29. Compliant Mapping of ECA to .NET/J2EE 29

  30. Compliant Mapping of ECA to .NET/J2EE 30

  31. Compliant Mapping of ECA to .NET/J2EE 31

  32. Case Study: Implementation Technologies • .NET Web Services • Windows Workflow Foundation • Spring .NET AOP Framework

  33. Case Study: Implementation

  34. Case Study: Implementation

  35. Case Study: Implementation • Services used to implement activities • Each service executes activity workflow based on • Contract • Instantiated based on executed rule • Rules • Add/remove cross-cutting or optional operations 35

  36. Case Study: Implementation

  37. Case Study: Implementation

  38. Summary • Adaptive information system • Service oriented architecture • Simplicity • Interoperability • Workflows at intra-activity execution • Based on ECA Rules • Contract • Instantiation at Rule level • Aspect-oriented programming • Adaptability • Clean and scalable implementation

  39. Questions

More Related