Joint Language and Domain Engineering

Joint Language and Domain Engineering Tobias Walter Fernando Silva Parreiras (WeST) Steffen Staab (WeST) Jürgen Ebert ECMFA 2010

Objectives
Scenario
Foundations
Language Engineering
Domain Engineering
Joining Language and Domain Engineering
Combination with Description Logics
Conclusion

Scenario
Modeling physical devices, e.g. Cisco network devices
Cisco 7603:

Scenario
Modeling of Devices
Describe the domain of physical devices
by domain instances, e.g. cisco7603, supervisor720
by domain types, e.g. Cisco, CiscoSlot, SuperVisor
Prescribe the structure of the domain and its models
Device -> Slot -> Card

Roles in Language and Domain Engineering Language Engineering and Use Domain Engineering Language User Language Designer Language Metamodel uses specifies Domain Model builds Domain Designer builds

Language Engineering and Language Use
M2 layer :
Language Engineering
Prescriptive Metamodel
class Device{ reference hasSlot [1-*]: Slot; } class Slot{ reference hasCard [0-*]: Card; } class Card{ }
M1 layer:
Language Use
Domain Model
instance cicso7603 instanceOf Device{ hasSlot slot1; } instance slot1 instanceOf Slot{ hasCard supervisor360; } instance supervisor360 instanceOf Card{ } linguistic instanceOf Language Designer Language User

Domain Engineering
O2 layer:
Domain types
Type hierarchies
instance cicso7603 { hasSlot slot1; } instance slot1 hasCard supervisor360; }
O1 layer:
Domain instances
Use of explicit hasType -relation
ontological hasType type Supervisor extends CiscoCard { } instance supervisor360 hasType CiscoCard{ } hasType CiscoSlot{ type Cisco { reference hasSlot [1-*]: CiscoSlot; } type CiscoSlot { reference hasCard [0-*]: CiscoCard; } type CiscoCard { }
Descriptive domain model
Domain Designer

Challenges (1)
Combination of Language Engineering and Domain Engineering
Language prescribes design and structure of domain models
Dynamically extending the set of domain types in domain models
type Cisco { reference hasCard [1-*]: CiscoCard; } type CiscoCard { } Inconsistent structure of domain models for physical devices

Join of Language and Domain Engineering class Device{ reference hasSlot [1-*]: Slot: } class Slot{ } type Cisco { reference hasSlot [1-*]: CiscoSlot; } type CiscoSlot { } metatype Device{ } metatype Slot{ } metainstance SlotInstance { } metainstance DeviceInstance { } instance cicso7603 hasType Cisco{ hasSlot slot1; } instance slot1 { }
M2 layer
M1 layer
hasMetatype Device hasMetatype Slot metareference hasSlot [1-*]: Slot; linguistic instanceOf linguistic instanceOf Domain Designer Language Designer

Joint Model Hierarchy Ontology-based Metamodeling Language with concepts for metatypes , metainstances , types , instances … M3 Layer Metametamodel M2 Layer Metamodel M1 Layer Domain model metatype metainstance type instance O2 ontological type layer O1 ontological instance layer linguistic instanceOf linguistic instanceOf ontological hasType ontological hasMetaType linguistic instanceOf

Challenges (2)
Services and Constraints in Language Metamodels and Domain Models
Classify existing domain instances in domain models to find a possible domain type
Consistency Checking
Underlying semantics for hasType and instanceOf relation
 Semantic Expressions covering type and instance layer
instance cicso7603 { hasSlot slot1; } What domain type does an instance have?

Description Logics
Description Logics (DLs) are logics designed to represent and reason on structured knowledge
The domain of interest is structured into ( TBox ):
concepts, which correspond to classes, and denote sets of individuals
roles, which correspond to associations, and denote binary relations on individuals
The knowledge is asserted through so-called assertions ( ABox )
They provide formal semantics
DLs provide the foundations for standard ontology languages, like OWL2
Knowledge Base TBox ABox Inference Engine Application

Integrated Semantic Expressions (1)
Language metamodel
metatype Device metareference hasSlot [1-*]: Slot; } metatype Slot { metareference hasCard [0-*]: Card; } metatype Card { } metainstance DeviceInstance hasMetatype Device { metalink hasSlot [1-*]: SlotInstance; } metainstance SlotInstance hasMetatype Slot { metalink hasCard [0-*]: CardInstance; } metainstance CardInstance hasMetatype Card { } { { { equivalentWith restrictionOn hasSlot with some restrictionOn hasCard with some Card { DSL Designer

Integrated Semantic Expressions (2)
Domain Model
type Cisco equivalentWith reference hasSlot [1-*]: CiscoSlot; } type CiscoSlot { reference hasCard [0-*]: CiscoCard; } type CiscoCard { } type Supervisor instance cicso7603 { hasSlot slot1; } instance cisco7604 } instance slot1 hasType CiscoSlot { hasCard supervisor360; } instance supervisor720 hasType CiscoCard { } instance supervisor360 hasType CiscoCard { } restrictionOn hasSlot with some restrictionOn hasCard with some Supervisor { { equivalentWith oneOf (supervisor720, supervisor360) { } { } hasType restrictionOn hasSlot with some restrictionOn hasCard with some Supervisor { {

Services
Domain Model
type Cisco equivalentWith restrictionOn hasSlot with some restrictionOn hasCard with some Supervisor { reference hasSlot [1-*]: CiscoSlot; } type CiscoSlot { reference hasCard [0-*]: CiscoCard; } type CiscoCard { } type Supervisor equivalentWith oneOf (supervisor720, supervisor360) { } instance cicso7603 hasSlot slot1; } instance slot1 hasType CiscoSlot { hasCard supervisor360; } instance supervisor720 hasType CiscoCard { } instance supervisor360 hasType CiscoCard { } instance cisco7604 hasType restrictionOn hasSlot with some restrictionOn hasCard with some Supervisor { } Classify individuals to get its type hastype Cisco { { Check consistency of instances instance cisco7604 hasType restrictionOn hasSlot with some restrictionOn hasCard with some Supervisor { }

Benefits of DL in Domain and Language Engineering
Open World Assumption
assumes incomplete information by default
guidance and validation of incomplete models
Joint semantic definitions at 2 layers
O1/M1- and O2/M2 layer affect each other
simultaneously reasoning at two layers possible
Debugging and reasoning explanation
identifying debugging-relevant facts (e.g. model elements) which lead to inconsistency with regard to the metamodel
explanations of errors in domain models

Future Work & Conclusion
Designing language metamodels by metatypes and metainstances
Prescribing structure and design of domain models
Using explicit hasType relation in domain models
Semantic expressions and services
Design metamodeling language for
n-dimensional modeling
arbitrary depth of instantiations
In the future Domain Designer Language Designer

Finally
Thanks for your attention
supported by
www.most-project.eu

M3 Metametamodel

Joint Language and Domain Engineering

by Tobias Walter on Feb 06, 2011

Accessibility

Tags

Upload Details

Usage Rights

Statistics

Joint Language and Domain Engineering — Presentation Transcript