1 / 28

A Three-tier View-based Methodology for M-Services Adaptation

A Three-tier View-based Methodology for M-Services Adaptation. S.C. Cheung Dept. of Computer Science Hong Kong University of Science & Technology scc@cs.ust.hk. Dickson K.W. Chiu Senior Member, IEEE. Eleanna Kafeza

benito
Télécharger la présentation

A Three-tier View-based Methodology for M-Services Adaptation

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. A Three-tier View-based Methodology for M-Services Adaptation S.C. Cheung Dept. of Computer Science Hong Kong University of Science & Technology scc@cs.ust.hk Dickson K.W. Chiu Senior Member, IEEE Eleanna Kafeza Department of Marketing and Communications, Athens University of Economics & Business kafeza@aueb.gr Ho-fung Leung Dept. of Computer Science & Engineering Chinese University of Hong Kong lhf@cse.cuhk.edu.hk

  2. Motivation and Background • Often we have existing systems • Extend it to support programmatic interactions: B2B / agent • Extend/adapt it to support emerging mobile computing environment - SMS, WAP, PDA, … • Adapting human-agent collaboration system for mobile environment – e.g., workforce management • 3-tier architecture commonly adopted over Web • Extend our Process Viewmechanism into 3-tiers for adaptation • User Interface Views • Process Views • Database Views Dickson Chiu et al. TSMC 2003

  3. Project Background • B2B Process Views • D.K.W. Chiu, S.C.Cheung, K. Karlapalem, Q. Li, Sven Till, and E. Kafeza. Workflow View Driven Cross-Organizational Interoperability in a Web Service Environment, Information Technology and Management, 5(3/4):221-250, 2004. • D.K.W. Chiu, K. Karlapalem, Q. Li and E. Kafeza. Workflow Views Based E-Contracts in a Cross-Organization E-Service Environment. Distributed and Parallel Databases 12(2-3):193-216, 2002. • 3-tier View conference paper • D.K.W. Chiu, S.C. Cheung and E. Kafeza. Three-tier View-based Support for Mobile Workflow. First International Conference on Mobile Business, Athens, Greece, July 2002. Dickson Chiu et al. TSMC 2003

  4. Advantages of Views • Motivated by views in federated object databases / relational database • Help balance trust and security • Access in fully controlled manner • Minimize modification of existing process for interoperability • Interface with different organization with different views • Fast and manageable development • Process Views as the center mechanism Dickson Chiu et al. TSMC 2003

  5. A Process for Service Negotiation Service Provider User User evaluates options [with feasible options] Reply YES/NO for each option [without feasible options] [max round not exceeded] Send options to user [passive mode] User inputs request with service options Reply Counter Options [counter-offer mode] [constraint mode] Reply Constraints [no option found] Evaluate constraints and options [max round exceeded] [good option found] Inform chosen details Receive service details Inform failure Dickson Chiu et al. TSMC 2003

  6. User Features on Different Platforms Dickson Chiu et al. TSMC 2003

  7. 3-tier View Architecture Processes of Other Organizations PDA memory Internet Messenger SMS Gateway Service Process WAPGateway DBMS Web Server Users Process Views Data Views User Interface Views Dickson Chiu et al. TSMC 2003

  8. Meta-model for 3-tier Views * * * * * aggregation association Data View * User Table many to many association * * * * Role transition * * * * * * * User Interface View Process View Task * * Screen / Form * * * * * inheritance 1 Agent / B2B Process View SMS User Process View WAP User Process View Web User Process View Process Dickson Chiu et al. TSMC 2003

  9. Methodology Overview • Identify target platforms and the set of activities to be possibly adapted in the base process. • For each activity identified, elicit the capabilities required for enactment. • For each target platform, enlist its provided features. • Match capabilities against features. • Decide which activities need adaptation. Design process views accordingly. • Design data views for each of the data sources based on the requirements of the process views. • Design user interface views based on platform dependent restrictions. • Perform validation of view consistency. Dickson Chiu et al. TSMC 2003

  10. Contribution of 3-Tier Views toDifferent Platforms Dickson Chiu et al. TSMC 2003

  11. Process View - Introduction • Process view – structurally correct subset of process definition • Motivated by views in federated object databases • Originally for B2B interoperating processes among (different categories of) business partners to authorize external access to process • Same mechanisms now used for users of different platform access different subset of process Dickson Chiu et al. TSMC 2003

  12. Capabilities Required by Various Process Activities Dickson Chiu et al. TSMC 2003

  13. Features supported byVarious Platforms Dickson Chiu et al. TSMC 2003

  14. Meta-model for Matching Features Against Capabilities adapts Target Process Process View * Platform 1..* offers matches * * Feature * * Activity 1..* requires * * * FeatureSet Capability Realization Dickson Chiu et al. TSMC 2003

  15. Realization Table Matching Feature-Sets against Capabilities Dickson Chiu et al. TSMC 2003

  16. Process Views for Participants on Different Platforms Dickson Chiu et al. TSMC 2003

  17. User Interface Views for WAP users for PDA users Dickson Chiu et al. TSMC 2003

  18. User Interface Views Supporting the “Display Options” for WAP Users select View Request scroll down select available time slots viewing the first option continue until the last option select the next option select finish … Dickson Chiu et al. TSMC 2003

  19. User Interface Views Supporting the “Enter Counter Options” for WAP Users finish with no available time slots in any options No available time slots were selected in all options select YES for counter offer response mode enter venue and date select time slots Dickson Chiu et al. TSMC 2003

  20. User Interface View Implementation User Inputs XML Document Object Presentation Object Activity XML Processor Activity Activity Screen / Form User Interface View Workflow View XSL Style Sheet XML Schemas Dickson Chiu et al. TSMC 2003

  21. <?xml version=”1.0” encoding=”ISO-8859-1”?> <Proposal id=”mtg-fkn-01”> <description>Service Options.</description> <date>May 30</date> <time>14:00</time> <Proposer> <name>Franklin</name> <affiliation>CUHK</affiliation> </Proposer> <Option> <venue>Conference Room, 3/F, CUHK, Shatin</venue> <TimeSlot> <date>Jun 1</date> <startTime>9:00</startTime> <endTime>9:30</endTime> <status>Unconfirmed</status> </TimeSlot> <TimeSlot> <date>Jun 1</date> <startTime>9:30</startTime> <endTime>10:00</endTime> <status>Unconfirmed</status> </TimeSlot> </Option> ... </Proposal> <?xml version="1.0"?> <!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml"> <wml> <card id="start" title="Option Details"> <p><b>Venue:</b> Conference Room, 3/F, CUHK, Shatin</p> <p><b>Select Available Time Slots:</b></p> <p> <select name="slot1"> <option value="NULL">SLOT 1</option> <option value="0900">JUN 1 (9:00-9:30)</option> <option value="0930">JUN 1 (9:30-10:00)</option> <option value="0930">JUN 1 (10:00-10:30)</option> <option value="0930">JUN 1 (10:30-11:00)</option> <option value="0930">JUN 1 (11:30-12:00)</option> </select> </p> ... </card> </wml> XML Service Object and WAP Listing Dickson Chiu et al. TSMC 2003

  22. Data View vs. Complete Schema(Mobile Meeting Scheduler Example) Dickson Chiu et al. TSMC 2003

  23. Adaptation Consistency • By event trace semantics • Tracing the start and end event of each task • Based on process algebra and automata theory • Consistency of process view with respect to a process • a process view V not exhibiting any event sequences where no corresponding ones are found in the base process H. Dickson Chiu et al. TSMC 2003

  24. Variables: Day, Time, Place Domains: D(Day) = {Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday} D(Time) = {9am, 9:15am, 9:30am, …, 11:45pm, 12:00am} D(Place) = {CUHK, HKUST, HKU} Constraints: SuitableTime(Time) SuitableTime(Day) SuitablePlace(Place) Day-Place-Requirement(Day, Place) Time-Place-Requirement(Time, Place) Plus: other personal constraints on Time, Day and Place Extents of Constraints: SuitableTime = {9am, 11am, 2pm} SuitableDay = {Monday, Tuesday, Wednesday, Thursday, Friday} SuitablePlace = {CUHK, HKUST, HKU} Day-Place-Requirement = {<Monday, CUHK>, <Monday, HKUST>, <Monday, HKU>, <Tuesday, CUHK >, <Tuesday, HKUST>, <Tuesday, HKU>, <Wednesday, CUHK >, <Wednesday, HKUST>, <Thursday, CUHK >, <Thursday, HKUST>, <Thursday, HKU>, <Friday, CUHK >, <Friday, HKUST>, <Friday, HKU>, <Saturday, CUHK >, < Saturday, HKUST>, < Saturday, HKU>, <Sunday, CUHK >, < Sunday, HKUST>, < Sunday, HKU>} Time-Place-Requirement = {<9am, CUHK>, <11am, HKUST>, <2pm, HKU>} Constraint Satisfaction Problem (CSP) Dickson Chiu et al. TSMC 2003

  25. Adaptation Considerations for Constraint-Solving Application • Centralized open-calendar protocol not suitable - no privacy protection, too much unnecessary data is sent • Passive mode - inefficient protocol but simple, least data sent, suitable for SMS users • In between: reply counter-option mode or reply constraints – but more complicated user interface required • All these can be translated into constraints and therefore into a standard CSP problem Dickson Chiu et al. TSMC 2003

  26. Implementation Architecture View and Stylesheet Editor Process Specification and Capability Editor Consistency Checker XSLT Processor Web Front-end <<entity bean>> Data View <<session bean>> Server Process <<session bean>> Constraint Solver Public UDDI Registry End users on Multi-platform Devices Enterprises Web Services Programmatic Access Web / WAP Access User-Side Server-Side SMS Entity Adapter Web Service Interface publish Web Container External Interface Subsystem View Maintenance Subsystem XSLT Stylesheets <<session bean>> Process View Views & Stylesheets Repository Application Subsystem View Specifications in XML Enterprise Data EJB Container Dickson Chiu et al. TSMC 2003

  27. Conclusion • A three-tier view-based methodology for adapting applications to support multiple platforms • A novel approach of applying process views in adapting collaboration systems to a mobile environment • Details on the technologies for supporting such adaptations • Support for both human users and user delegated autonomous agents in a collaboration system • Use of constraints to limit data exchange in a collaboration system to reduce bandwidth consumption for mobile users • Demonstration of the applicability of our methodology in supporting flexible mobile collaboration systems through these features. • Rapid development and deployment of E-commerce systems (reuse and modular design) Dickson Chiu et al. TSMC 2003

  28. Further and Ongoing work • How do we design the views? Based on what?- Requirement engineering and e-Contracts • e-Contract enactment • e-Contract enforcement and exception handling • e-Contract Templates • e-Negotiation • Flows and Views • Real-life applications • e-Marketplace, workforce management, logistics, CRM, etc. • HCI – Human-Computer Interaction • m-Government service • m-Tourism service • Mobile workforce management, esp. for service outsourcing Dickson Chiu et al. TSMC 2003

More Related