Combining DSLs and Ontologies Using Metamodel Integration

Uploaded on

Talk at the IFIP Working Conference on Domain-Specific Languages, 14-17 June 2009, Oxford, United Kingdom.

Talk at the IFIP Working Conference on Domain-Specific Languages, 14-17 June 2009, Oxford, United Kingdom.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • - First start with a motivation of integrated modeling and using ontologies. The motivation is based on a scenario from an industrial partner of the MOST project. Foundations: Present all relevant DSLs and its metamodels which appear in the scenario. Further present some relevant parts of the ontology language OWL2. Stepwise presentation of the integration. In each step I will show which constructs of the different metamodels are combined. The result of applying all steps is the integrated metamodel. This can be used for integrated domain modeling. After each integration step I will give you the idea how both languages can be used together in one domain model and in a seamless manner.
  • Modeling of Business Entities on the one side, modeling of features on the other side. Idea: combine both languages and define which network devices are available for which operations. Furthermor define constraints and restrictions Solve this by annotating model elements and defining global constraints.
  • To provide integrated modeling integrate the metamodels of all relevant DSLs Result: Integrated Metamodel; allows for building one Domain Model containing parts of BEDSL, FODA and OWL2
  • - Metamodel of BEDSL
  • anpassen
  • Eventuell noch hasSupertype Association in M2 einfügen


  • 1. Combining DSLs and Ontologies using Metamodel Integration Working Conference on Domain-Specific Languages 16.07.2009, Oxford Tobias Walter Jürgen Ebert
  • 2. Objectives
    • Motivation
      • Scenario
    • Foundations
      • Metamodels
      • Ontologies
    • Integration
      • Integration of Domain Specific Languages
      • Integrated Domain Modeling
    • Conclusion
  • 3. Scenario
    • Combined Modeling of
      • Business Entities of Network Devices
      • Network Management Operation Features
    • Annotate Model Elements with Constraints
    AvailableFor AvailableFor
  • 4. Proposed Solution
    • Metamodel-based Integration of
      • Business Entities Domain-Specific Language (BEDSL)
      • Feature Oriented Domain Analysis Language (FODA)
      • Ontology Language (OWL)
    • Result: Integrated Metamodel
      • Allows for building one Domain Model containing:
        • Structure of Devices defined by BEDSL Language
        • Features defined by FODA Language
        • Constraints defined by Ontology Language
  • 5. Metamodel (BEDSL)
    • BEDSL – Business Entity Domain Specific Language
    • BEDSL Models (M1 layer) conform to Metamodel (M2 layer)
    M2 layer M1 layer BEDSL Metamodel BEDSL Model conformsTo conformsTo
  • 6. Metamodel (FODA)
    • FODA – Feature Oriented Domain Analysis
    • Describe Features and their Relationships
    • Domain Models (M1 layer) represented as Feature-Tree
    M2 layer M1 layer FODA Metamodel FODA Model conformsTo conformsTo
  • 7. Ontologies
    • Definition
      • An Ontology is a Set of Definitions in a formal Language for Terms describing the World
    • Capability to describe Classes in many different ways and to handle incomplete Knowledge
    • Allow for complete and sound Reasoning simultaneously on Model and Instance Layer
    • Different Languages and Syntaxes:
      • E.g.: OWL2 with Manchester Syntax
  • 8. Ontologies (Example) OWL Classes and Individuals: M1 layer OWL2 Model
  • 9. Ontologies (Example)
    • ObjectProperty: HasPort
    • Domain:
    • NetworkDevice
    • Range:
    • HasPort exactly 8 Port
    • ObjectProperty: HasState
    • Domain:
    • Port
    • Range:
    • HasState exactly 1 State
    • ObjectProperty : AvailableFor
    • Domain:
    • NetworkDevice
    • NetworkDevice and (hasPort some (Port and hasState some (FreePort)))
    • EquivalentTo:
    • NetworkDevice and AvailableFor value AllocatePorts
    OWL Object Properties: M1 layer OWL2 Model
  • 10. Metamodel of OWL2 (Excerpt) M2 layer OWL2 Metamodel
  • 11. Integration
    • Integration of BEDSL, FODA and OWL2
    • Consider Metamodels of BEDSL, FODA and OWL2
    • Identify Concepts for Integration
    • Apply Integration Transformations
      • Merge of Concepts
      • Create Specialization between Concepts
      • Create Super Class over Concepts
      • Create Association between Concepts
      • Extend Association by Concept
    • Result: Integrated Metamodel
  • 12. Integration (BEDSL – OWL)
    • Merge BEDSL Entity and OWL2 Class
    M2 layer M1 layer conformsTo
  • 13. Integration (BEDSL – OWL)
    • Create Association between IntegratedClass and ReferenceAttribute
    • Extend Association to Class ReferenceProperty
    • Create Specialization between ReferenceProperty and OWL ObjectProperty
    M2 layer M1 layer
  • 14. Integration (BEDSL – OWL – FODA)
    • Create Specialization between Feature and OWL Individual
    M2 layer M1 layer
  • 15. Conclusion
    • Consider Metamodels of BEDSL, FODA, OWL2 and identify Concepts
    • Stepwise Combination of DSL by integrating their Metamodels
    • Result is integrated Metamodel which allows for building Domain Models simultaneously using BEDSL, FODA and OWL2
  • 16. Finally
    • Thanks for your attention
    • supported by