Owl and Sysml

You might also like

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 12

OWL and SysML

Where does one end and the other


start?
SysML Meta Model Architecture
Layer Description Example
meta-metamodel The infrastructure for a metamodeling MetaClass, MetaAttribute,
architecture. Defines the language for MetaOperation
specifying metamodels.

metamodel An instance of a meta-metamodel. Class, Attribute, Operation,


Defines the language for specifying a Component
model.
model An instance of a metamodel. Defines HSUV, OffRoadWheel,
a language to describe an information DieselMotor XYZ are Names
domain. of <<Block>>s

user (run-time) An instance of a model. Defines a Joe’s HSUV,


objects specific information domain. Wheel SerNo 123,
(user data) DieselMotor XYZ SerNo
456
Customization for Stereotypes extend existing SysML <<Car>>, <<Wheel>>,
Specific Domains language concepts with additional <<Engine>> are
properties and constraints. specializations of
<<Block>>
SysML Meta Model hierarchy
OWL Architecture: Building Blocks
Element Description Example

Individuals Represent objects in the real Robert, USA, Fido


world.
Classes Sets of individuals. Classes may Person, Country, Pet,
be atomic or complex. Person and hasDaugther
some ( Rich and Lawyer)
Object Properties Represent relationships hasSister, hasParent,
between two individuals. worksFor

Data Properties Link individuals to concrete hasAge, hasName, hasSSN


values (e.g., XML Schema
datatypes, rdf:literal)
OWL Architecture: Assertions
Element Description Example

Class assertions Assert that an individual is an Robert: Person


instance of a class.
Object property Assert that two individuals are
assertions related via a given object
property.

Data property Assert that an individual an a


assertions concrete value are related via
the given data property.
OWL Architecture: (some) Axioms
Element Description Example

Subclass axioms Assert that a class is a subclass Man subClassOf Person


of another class.
Transitivity axioms Assert that a given object Transitive(hasAncestor)
property is transitive.

Functionality axioms Assert that a given property is Functional(hasSSN)


functional.

Domain/Range Assert that the domain/range hasPet domain Person


axioms of a given property is a given hasPet range Animal
class.
SysML Stereotype vs. Generalization 1/2
SysML Stereotype vs. Generalization 2/2
Mapping OWL to SysML
Generalization??
OWL SysML Notes

Class CarA <<block>> CarA

Class HSUVa <<block>> HSUVa

Class DieselMotor XYZ <<block>> DieselMotor XYZ

Object Property hasEngine Composition with role e

Individual Joe’s HSUV InstanceSpecification


Joe’s HSUV
Data Property serNo ValueProperty serNo
Mapping OWL to SysML
Customization??
OWL SysML Notes

Class CarA <<block>> CarA

Class Car stereotype <<car>>

Class Engine Stereotype <<engine>>

Class HSUVb <<car>> HSUVb

Class DieselMotor XYZ <<engine>> DieselMotor


ABC
Object Property hasEngine Composition with role e

Individual Jack’s HSUV InstanceSpecification


Jack’s HSUV
OWL Car Ontology
• TBD
SysML Stereotypes, etc
• Criteria when something is a SysML <<stereotype>> or a
Model Element?
– Is a Motor a <<block>> Motor or a <<motor>>
• Every Model Element shall be stereotyped according to the
domain specific ontology
• Criteria when a OWL class is mapped to a SysML
<<stereotype>> or a Model Element?
• When is a OWL object property a composition or reference
association?
• Does it make a difference if the intention of the SysML model
is to model one particular system (which exists only once) or
a product line (where several real-world objects exist)?

You might also like