1 / 77

Third RMSIG Workshop

Third RMSIG Workshop. Basic Modeling Concepts. Wolfram Höpken. Workshop Objective. first and second workshop discuss and agree upon methodology and process discuss white paper evaluate prototype third workshop identify basic modeling concepts and mechanisms

sayala
Download Presentation

Third RMSIG Workshop

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. Third RMSIG Workshop Basic Modeling Concepts Wolfram Höpken

  2. Workshop Objective • first and second workshop • discuss and agree upon methodology and process • discuss white paper • evaluate prototype • third workshop • identify basic modeling concepts and mechanisms • specify tourism specific modeling language • forth workshop • specify reference model building blocks • fifth workshop • agree upon first release of reference model

  3. Agenda • methodology of the reference model • market participants and requirements • domain analysis – survey • specification of tourism modeling language • Tourtags.org • process of the RMSIG and next activities • conclusion

  4. Agenda • methodology of the reference model • market participants and requirements • domain analysis – survey • specification of tourism modeling language • Tourtags.org • process of the RMSIG and next activities • conclusion

  5. Motivation • drawbacks of current standardization initiatives • lack of flexibility and extendibility • fix standards are hard to maintain • no possibility for suppliers to differentiate their offer • lack of expressiveness • description languages (e.g. XML) can not express all information, necessary for interoperability • lack of semantic information (e.g. relationships), process information, constraints,...

  6. Methodology • framework for modeling electronic tourism markets • uniform language with standardized building blocks as vocabulary for describing electronic tourism markets • conceptual, abstract modeling of tourism markets • modeling based on the Unified Modeling Language (UML)

  7. UML – Unified Modeling Language • graphical language for describing and visualizing models of systems • UML 1.3 adopted as standard by the OMG • enables the modeling of • static structure of a system • entities, their internal structure • relationships between entities • behavior of a system • interactions between entities (scenarios) • state sequences, activity sequences

  8. UML model Distributed object model XML model Modeling Levels

  9. UML model UML DTDs XMI documents Meta level XML DTDs XML documents Data level XML Perspective

  10. XMI documents XMI documents Meta level XML DTDs IDL descriptions XML documents BOs Data level Distributed Object Perspective UML model (concept) UML model (BOI)

  11. Modeling Language • tourism specific modeling language based on the UML • extends the UML by domain specific concepts and mechanisms • composition mechanism • market interface descriptions • provides building blocks as specific modeling elements • enables the flexible description of specific models

  12. Modeling Language (2) UML Common meta level Domain model concrete level

  13. Modeling Language (2) UML Common meta level Tourism modeling language Domain specific meta level Domain model concrete level

  14. Building Blocks • building blocks as specific modeling elements • building blocks are provided on different levels of granularity • elementary building blocks (date, location,...) • tourism services (flight, hotel,...) • process building blocks (searching, booking,...)

  15. Process layer Searching Booking Criteria Service Customer Customer ResultList Date Entity layer Hotel Flight Customer Name Time Name Category Route Address Room Class Age Base layer Name Route Date StartLocation Address Time EndLocation Location Facilities Building Blocks

  16. Building Concrete Models • concrete models with specific entities are described or modelled by the UML-based tourism modeling language • the provided building blocks can be used as basic modeling elements • composition: describe a specific entity as a composition of building blocks • inheritance: describe a specific entity as a refinement of a building block

  17. Hotel Name Time CureServices Name Category Class Category MealPlan Room Room Route compose compose derive Specific model CureHotel XYFlight Time Name MoonFlight Category Route Category Room Class Room Time MealPlan CureServices Building Concrete Models (2) Reference model

  18. XYFlight XYFlight Time Time Route Route Time Route Class Class Time Time Route Route 2 1 4 3 5 Class MealPlan MealPlan MealPlan Class Class MealPlan MealPlan lookup Supplier Customer Interoperability Reference model

  19. Advantages • flexibility and adaptability for suppliers • flexibility for change • low entrance barriers to electronic markets for suppliers (SMEs) • easy access of customers to a wide range of services • separation of semantic aspects and technical aspects • interoperability is supported on all possible communication levels

  20. Agenda • methodology of the reference model • market participants and requirements • domain analysis – survey • specification of tourism modeling language • Tourtags.org • process of the RMSIG and next activities • conclusion

  21. Agenda • methodology of the reference model • market participants and requirements • domain analysis – survey • specification of tourism modeling language • Tourtags.org • process of the RMSIG and next activities • conclusion

  22. Market Participants and Requirements • identification of participants of electronic tourism markets (customer, supplier,...) • identification of their requirements to each other: • functional requirements • non-functional requirements use cases of electronic tourism markets

  23. Market Participants

  24. search requests vague requests similar results service composition availability requests booking execution booking of services status request cancelling a booking further information (descriptions, pictures) user profiles feedback management request metadata security support of different languages and currencies Requirements Customer/Broker to Supplier

  25. Use Cases Customer/Broker to Supplier

  26. Requirements Customer to Broker • request for market data (e.g. list of suppliers and available services) • periodical and event triggered requests • auction services

  27. Use Cases Customer to Broker

  28. RequirementsFront-end Supplier to Broker • supply of tourism services • creation and modification of services • definition of flexible services • substitution services • composition services • booking processing • request user profiles

  29. Use CasesFront-end Supplier to Broker

  30. Agenda • methodology of the reference model • market participants and requirements • domain analysis – survey • specification of tourism modeling language • Tourtags.org • process of the RMSIG and next activities • conclusion

  31. Agenda • methodology of the reference model • market participants and requirements • domain analysis – survey • specification of tourism modeling language • Tourtags.org • process of the RMSIG and next activities • conclusion

  32. Agenda • methodology of the reference model • market participants and requirements • domain analysis – survey • specification of tourism modeling language • Tourtags.org • process of the RMSIG and next activities • conclusion

  33. Tourism Modeling Language • tourism specific modeling language • provides basic concepts and mechanisms for modeling electronic tourism markets • enables the uniform description of specific market components • approach • metalevel extends the UML by domain specific modeling elements • building blocks are provided as common vocabulary

  34. Concepts and Mechanisms • composition mechanism for the flexible construction of tourism services • elementary tourism services out of service components(e.g. hotel out of room and meal plan) • composition services out of elementary services(e.g. package tour out of flight and hotel) • availability • flexible management of the availability of tourism services or their components

  35. Concepts and Mechanisms (2) • selection criteria • modeling selection relevant characteristics of tourism services in a flexible way • depending on the components of a tourism service • evaluated dynamically out of the attributes • selection hierarchies • comfortable selection process (fuzzy requests, similar results) • flexible derivation of building blocks

  36. Concepts and Mechanisms (3) • views on tourism services • consideration of different interfaces (views) of tourism services, depending on • the role of the observer (market participant) • the market, in which the service is offered • service states • modeling different states of tourism services during their lifecycle (offered, booked, used) and state transitions

  37. Concepts and Mechanisms (4) • multi language support • consideration of different languages for all language-dependent information • country-specific formats • integration of different country-specific formats for date, time, currency etc. and transformation between different formats

  38. Concepts and Mechanisms (5) • market processes • concept for describing market component interfaces, consisting of market processes • interface descriptions understandable for other market participants

  39. Reference Model Architecture Metalevel Types Common entities Tourism services Service states Processes Building blocks Process layer Information processes Booking processes Entity layer Common entities Service components Elementary tourism services Composition services Base layer Common types Base classes Data main-tenance Session manage-ment Lookup service

  40. Reference Model Metalevel Metalevel Types Common entities Tourism services Service states Processes • extends the UML • provides a virtual metamodel • adds tourism specific modeling elements • described as UML profile • stereotypes • tagged values • constraints

  41. Reference Model Metalevel Metalevel Types Common entities Tourism services Service states Processes • types: metaclasses for modeling tourism- specific basic types • common entities: metaclasses, which are used in different packages of the metamodel • tourism services: metaclasses, providing concepts for constructing tourism services • service states: metaclasses, for dealing with different states of tourism services • processes: metaclasses for describing market processes and interfaces

  42. Tourism Services Metalevel Types Common entities Tourism services Service states Processes Building blocks Process layer Information processes Booking processes Entity layer Common entities Service components Elementary tourism services Composition services Base layer Common types Base classes Data main-tenance Session manage-ment Lookup service

  43. Composition Mechanism • mechanism for the flexible construction of tourism services (composition mechanism) • complex services as composition of elementary services (e.g. package tour as composition of flight and hotel) • elementary services as composition of service components (e.g. hotel as composition of room and meal plan) • composition consists of • components (elementary components or compositions) • selection criteria (attributes) • constraints (restrict combination possibilities)

  44. Example Package Tour outward flight departure airport destination airport price package tour hotel point of departure name destination destination hotel name price price return flight Constraints: destination airport outward flight = hotel dest. departure airport return flight = hotel dest. arrival date outward flight = hotel check-in date departure date return flight = hotel check-out date departure airport destination airport price

  45. Composition Mechanism

  46. Example Hotel

  47. Example Train

  48. Selection Criteria • selection relevant characteristics of tourism services • represent a dynamic interface to the customer • evaluated from the attributes of service components

  49. Selection Criteria

  50. Views • concept for different views on tourism services • views depend on • the market in which the service is offered • the role of the observer (e.g. business or leisure traveller) • views provide additional selection criteria, evaluated by the selection criteria of the tourism service

More Related