forth rmsig workshop n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Forth RMSIG Workshop PowerPoint Presentation
Download Presentation
Forth RMSIG Workshop

Loading in 2 Seconds...

play fullscreen
1 / 101

Forth RMSIG Workshop - PowerPoint PPT Presentation


  • 191 Views
  • Uploaded on

Forth RMSIG Workshop. Building B locks of the Reference Model. Wolfram Höpken. Workshop Objective. first and second workshop discuss and agree upon methodology and process third workshop identify basic modeling concepts and mechanisms specify tourism specific modeling language

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

Forth 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
    Presentation Transcript
    1. Forth RMSIG Workshop Building Blocks of the Reference Model Wolfram Höpken

    2. Workshop Objective • first and second workshop • discuss and agree upon methodology and process • third workshop • identify basic modeling concepts and mechanisms • specify tourism specific modeling language • forth workshop • specify reference model building blocks • prepare first version of reference model

    3. Agenda • The reference model • Elementary tourism services • Composition services • Market processes • Employment of the reference model • Tourtags.org • Tourism ontology building and management

    4. Agenda • The reference model • Elementary tourism services • Composition services • Market processes • Employment of the reference model • Tourtags.org • Tourism ontology building and management

    5. The reference model • 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)

    6. 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

    7. 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

    8. Modeling Language (2) UML Common metalevel Domain model concrete level

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

    10. 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,...)

    11. 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 (2)

    12. UML model Distributed object model XML model Modeling Levels

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

    14. Hotel Name Category Room XML Example UML diagram XML document <HOTEL> <NAME>Holiday Inn</NAME> <CATEGORY>5</CATEGORY> <ROOM> <TYPE>single</TYPE> <PRICE>1250 ATS</PRICE> </ROOM> </HOTEL> XML DTD <!ELEMENT HOTEL (NAME, CATEGORY, ROOM+)> <!ELEMENT NAME (#PCDATA)> <!ELEMENT CATEGORY (#PCDATA)> <!ELEMENT ROOM (TYPE, PRICE)> <!ELEMENT TYPE (#PCDATA)> <!ELEMENT PRICE (#PCDATA)>

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

    16. Architecture Metalevel Types Common entities Tourism services Service states Processes Syno-nyms Building blocks Process layer Information processes Booking processes Entity layer Common entities Elementary tourism services Composition services Base layer Basic types Base classes Basic elements Data main-tenance Session manage-ment Lookup service

    17. Metalevel Metalevel Types Common entities Tourism services Service states Processes Syno-nyms • 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 • synonyms: metaclasses for defining synonyms for entities of the reference model

    18. Building Blocks Base layer Basic types Base classes Basic elements Data main-tenance Session manage-ment Lookup service • Basic types: tourism specific types at the fringe of the reference model (e.g. room type, bed type, category) • Base classes: fundamental, abstract base classes (e.g. object, entity) • Basic elements: basic building blocks for the construction of tourism entities (e.g. climate, opening hours, address, etc.) • Data maintenance: maintain tourism service data • Session management: manage user sessions • Lookup service: request meta data (available services and their structure)

    19. Building Blocks (2) Entity layer Common entities Elementary tourism services Composition services • Common entities: entities used in different packages of the entity or process layer (e.g. tourism service, customer profile) • Elementary tourism services: elementary services like hotel, flight, etc. • Composition services: services composed of elementary services

    20. Building Blocks (3) Process layer Information processes Booking processes • Information processes: retrieval of information about tourism services (e.g. searching for tourism services, checking the availability) • Booking processes: booking tourism services, altering a booking, canceling a booking

    21. Current State • integrated are: • requirements and use cases • information and booking processes • most important tourism services (accommodation, transportation, event, institution, hired vehicle, destination) • general composition service • still missing: • XML and BOI model • selection hierarchies

    22. Agenda • The reference model • Elementary tourism services • Composition services • Market processes • Employment of the reference model • Tourtags.org • Tourism ontology building and management

    23. Agenda • The reference model • Elementary tourism services • Composition services • Market processes • Employment of the reference model • Tourtags.org • Tourism ontology building and management

    24. Composition Mechanism • 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) • composition consists of • components (collection of building blocks to enable combination possibilities) • attributes (depending of component attributes) • evaluation instruction for evaluating attribute values • constraints (restrict combination possibilities)

    25. Example

    26. Example (2)

    27. Service States Potential Service: • contains all variants and optional components • instruction for building a concrete service Offered Service: • variants are selected • attributes are evaluated

    28. Elementary Tourism Services • classification of tourism services (page 79) • accommodation (hotel, vacation apartment, campsite) • transportation (flight, train, bus, ship) • institution (exhibition, museum, sight, sport leisure) • event (conference, lecture, course, cultural, sport, film) • hired vehicle (car, bus, motorbike, bike, camper, boat) • destination (country, region, city) • gastronomy • shopping • cruise

    29. Surveys • general RMSIG survey • requirements for tourism markets • market processes and core data • necessary types of tourism services • specific surveys for tourism services • tourism services accommodation, transportation, hired car, institution • concrete tourism services and their characteristics/attributes

    30. Data Dictionary • reference list of terms or entities of the tourism domain (described by name, meaning and structure) • structured into • tourism services • basic components • basic types • specifies the basic structure and semantic of corresponding elements of the reference model

    31. Destination

    32. Destination (2)

    33. XML DTD <!ELEMENT DESTINATION (ACTIVITIES*, CHARACTERISTICS+)> <!ELEMENT ACTIVITIES (TYPE)> <!ELEMENT TYPE (#PCDATA)> <!ELEMENT CHARACTERISTICS (NAME, LANDSCAPE, CLIMATE, PRICE, LANGUAGES*)> <!ELEMENT NAME (#PCDATA)> <!ELEMENT LANDSCAPE (#PCDATA)> <!ELEMENT CLIMATE (#PCDATA)> <!ELEMENT PRICE (#PCDATA)> <!ELEMENT LANGUAGES (#PCDATA)>

    34. XML Document <DESTINATION> <ACTIVITIES> <TYPE>tennis</TYPE> </ACTIVITIES> <CHARACTERISTICS> <NAME>Tyrol</NAME> <LANDSCAPE>mountainous</LANDSCAPE> <CLIMATE>continental</CLIMATE> <PRICE>40 ATS</PRICE> <LANGUAGES>German</LANGUAGES> </CHARACTERISTICS> </DESTINATION>

    35. Accommodation

    36. Accommodation (2)

    37. XML DTD <!ELEMENT ACCOMMODATION (NUMBERPERSONS, PRICE INSTITUTIONS, LIVINGUNITCATEGORIES, LIVINGUNITS, PERIODSOFTIME)> <!ELEMENT NUMBERPERSONS (#PCDATA)> <!ELEMENT PRICE (#PCDATA)> <!ELEMENT INSTITUTIONS (NAME, ADDRESS, LOCATION, ACTIVITIES, TARGETGROUPS)> <!ELEMENT NAME (#PCDATA)> <!ELEMENT LOCATION (#PCDATA)> <!ELEMENT ACTIVITIES (#PCDATA)> <!ELEMENT TARGETGROUPS (#PCDATA)>

    38. XML DTD (2) <!ELEMENT ADDRESS (STREET, CITY, ZIPCODE, COUNTRY)> <!ELEMENT STREET (#PCDATA)> <!ELEMENT CITY (#PCDATA)> <!ELEMENT ZIPCODE (#PCDATA)> <!ELEMENT COUNTRY (#PCDATA)> <!ELEMENT LIVINGUNITS (UNITNUMBER)> <!ELEMENT UNITNUMBER (#PCDATA)> <!ELEMENT PERIODSOFTIME (BEGIN, END)> <!ELEMENT BEGIN (DATE, TIME)> <!ELEMENT END (DATE, TIME)> <!ELEMENT DATE (#PCDATA)> <!ELEMENT TIME (#PCDATA)>

    39. XML Document <ACCOMMODATION> <NUMBERPERSONS>1</NUMBERPERSONS> <PRICE>1250 ATS</PRICE> <INSTITUTIONS> ... </INSTITUTIONS> <LIVINGUNITCATEGORIES> ... </LIVINGUNITCATEGORIES> <LIVINGUNITS> ... </LIVINGUNITS> <PERIODSOFTIME> ... </PERIODSOFTIME> </ACCOMMODATION>

    40. XML Document (2) <INSTITUTIONS> <NAME> HolidayInn</NAME> <ADDRESS> <STREET>Luisenplatz 14</STREET> <CITY>Innsbruck</CITY> <ZIPCODE>65342</ZIPCODE> <COUNTRY>Austria</COUNTRY> </ADDRESS> <LOCATION>central</LOCATION> <ACTIVITIES>tennis</ACTIVITIES> <TARGETGROUPS>family</TARGETGROUPS> </INSTITUTIONS>

    41. XML Document (3) <LIVINGUNITS> <UNITNUMBER>205 </UNITNUMBER> </LIVINGUNITS> <PERIODSOFTIME> <BEGIN> <DATE> 26012001</DATE> <TIME>1500</TIME> </BEGIN> <END> <DATE> 27012001</DATE> <TIME>1200</TIME> </END> </PERIODSOFTIME>

    42. Hotel

    43. Hotel (2)

    44. XML DTD <!ELEMENT HOTEL (NUMBERPERSONS, PRICE, INSTITUTIONS, LIVINGUNITCATEGORIES, LIVINGUNITS, PERIODSOFTIME, MEALPLANS, EXTRABEDS*)> <!ELEMENT INSTITUTIONS (NAME, ADDRESS, LOCATION, ACTIVITIES, TARGETGROUPS, TYPE, CATEGORY)> <!ELEMENT TYPE (#PCDATA)> <!ELEMENT CATEGORY (#PCDATA)> <!ELEMENT LIVINGUNITCATEGORIES (TYPE, EQUIPMENT*)> <!ELEMENT TYPE (#PCDATA)> <!ELEMENT EQUIPMENT (#PCDATA)>

    45. XML DTD (2) <!ELEMENT MEALPLANS (TYPE, PRICE)> <!ELEMENT TYPE (#PCDATA)> <!ELEMENT PRICE (#PCDATA)> <!ELEMENT EXTRABEDS (BEDTYPE, PRICE)> <!ELEMENT BEDTYPE (#PCDATA)> <!ELEMENT PRICE (#PCDATA)>

    46. XML Document <HOTEL> <NUMBERPERSONS>3</NUMBERPERSONS> <PRICE>2100 ATS</PRICE> <INSTITUTIONS> ... </INSTITUTIONS> <LIVINGUNITCATEGORIES> ... </LIVINGUNITCATEGORIES> <LIVINGUNITS> ... </LIVINGUNITS> <PERIODSOFTIME> ... </PERIODSOFTIME> <MEALPLANS> ... </MEALPLANS> <EXTRABEDS> ... </EXTRABEDS> </HOTEL>

    47. XML Document (2) <INSTITUTIONS> <NAME> HolidayInn</NAME> <ADDRESS> <STREET>Luisenplatz 14</STREET> <CITY>Innsbruck</CITY> <ZIPCODE>65342</ZIPCODE> <COUNTRY>Austria</COUNTRY> </ADDRESS> <LOCATION>central</LOCATION> <ACTIVITIES>tennis</ACTIVITIES> <TARGETGROUPS>family</TARGETGROUPS> <TYPE>hotel</TYPE> <CATEGORY>5</CATEGORY> </INSTITUTIONS>

    48. XML Document (3) < LIVINGUNITCATEGORIES > <TYPE>double</TYPE> <EQUIPMENT>bath</EQUIPMENT> <EQUIPMENT>tv</EQUIPMENT> </LIVINGUNITCATEGORIES> <MEALPLANS> <TYPE>breakfast</TYPE> <PRICE>200 ATS</PRICE> </MEALPLANS> <EXTRABED> <BEDTYPE>single</BEDTYPE> <PRICE>400 ATS</PRICE> </EXTRABED>

    49. Transportation

    50. Transportation (2)