conceptual analyses - conceptual schema design · pdf fileconceptual analyses conceptual...

21
Jarrar © 2011 1 Conceptual Schema Design Steps Knowledge Engineering (SCOM7348) © Mustafa Jarrar Lecture Notes, Knowledge Engineering (SCOM7348) University of Birzeit 1 st Semester, 2011 Dr. Mustafa Jarrar University of Birzeit [email protected] www.jarrar.info (Chapter 3)

Upload: duongcong

Post on 11-Feb-2018

249 views

Category:

Documents


4 download

TRANSCRIPT

Jarrar © 2011 1

Conceptual Schema Design Steps

Knowledge Engineering (SCOM7348)

© Mustafa JarrarLecture Notes, Knowledge Engineering (SCOM7348)

University of Birzeit1st Semester, 2011

Dr. Mustafa JarrarUniversity of [email protected]

www.jarrar.info

(Chapter 3)

Jarrar © 2011 2

More Online Courses at: http://www.jarrar.info/courses/

Course Page: http://www.jarrar.info/courses/KnowledgeEngineering/

Watch this lecture and download the slides

Jarrar © 2011 3

Conceptual Analyses

• Given an application domain, e.g. hospital, and three information modelers, what steps do you suggest them to start with, to build the hospital’s conceptual model?

• There is no strict or perfect modeling process or procedure!

• You may start with any step you think suitable, taking into account the complexity of the domain, available resources, modelers’ prior knowledge about the domain, etc.

• It is recommended that you modularize the domain into sub-domains, build a conceptual schema for each sub-domain , then integrate all sub-schemes into one conceptual schema.

• The following procedure (7 steps) is to help you model a sub-domain, but you don’t have to strictly follow these steps.

Jarrar © 2011 4

Conceptual Schema Design Steps

1. From examples to elementary facts

2. Draw fact types and apply population check

3. Combine entity types

4. Add uniqueness constraints

5. Add mandatory constraints

6. Add set, subtype, & frequency constraints

7. Final checks, & schema engineering issues

Jarrar © 2011 5

Elementary Facts and Fact Types

– Person smokes.– Person drives car.– Person was born in a city.– Person smokes and drives car.– If a Person was born in a city and this City is part of a

country, then this person was born in that country.

What is a fact type?

What is a fact?– Rami smokes.– Rami drives car.– Rabab was born in Ramallah.– Rami smokes and drives car.– If Rabab was born in Ramallah and Ramallah is part of

Palestine, then Rabab was born in Palestine.

è A fact must be either true or false

Jarrar © 2011 6

Elementary Facts and Fact Types

– Person smokes.– Person drives car.– Person was born in a city.– Person smokes and drives car.– If a Person was born in a city and this City is part of

a country, then this person was born in that country.

What is an elementary fact type?

û

üû

üü

à An elementary fact type cannot be spited.

Jarrar © 2011 7

1. From examples to elementary facts

Conceptual Schema Design Steps

Jarrar © 2011 8

1. Make elementary facts from examples

• Mustafa teaches Knowledge Engineering.• Rami is enrolled in Knowledge Engineering.• Knowledge Engineering is offered by the University of Birzeit.

v The Person (ID4514) that has the name Mustafa teaches the course (SC242)that has the title Knowledge Engineering.

v The Person (ID123) Rami is enrolled in the course (CS242) that has the has the title Knowledge Engineering.

v The course (CS242) that has the title Knowledge Engineering is offered by the university that has the name University of Birzeit.

Ø The Person that has the name Mustafa teaches the course that has the title Knowledge Engineering.

Ø The Person Rami is enrolled in the course that has the has the title Knowledge Engineering.

Ø The course that has the title Knowledge Engineering is offered by the university that has the name University of Birzeit.

More precise

From examples to fact types

Jarrar © 2011 9

1. From examples to elementary facts

2. Draw fact types and apply population check

Conceptual Schema Design Steps

Jarrar © 2011 10

2. Draw fact types and apply population check

University(Name)

Person(nr)

Course(Code)

IsOf/Has

Name

TitleTeaches/

EnrolledIn/

Has/IsOf

OfferedBy /Offers

v The Person (ID4514) that has the name Mustafa teaches the course (SC242)that has the title Knowledge Engineering.

v The Person (ID123) Rami is enrolled in the course (CS242) that has the has the title Knowledge Engineering.

v The course (CS242) that has the title Knowledge Engineering is offered by the university that has the name University of Birzeit.

Draw Fact Types

Jarrar © 2011 11

2. Draw fact types and apply population check

Person(nr)

Course(Code)

IsOf/Has

Name

TitleTeaches/

EnrolledIn/

Has/IsOf

v The Person (ID4514) that has the name Mustafa teaches the course (SC242)that has the title Knowledge Engineering.

v The Person (ID123) Rami is enrolled in the course (CS242) that has the has the title Knowledge Engineering.

v The course (CS242) that has the title Knowledge Engineering is offered by the university that has the name University of Birzeit.

Test with population

Mustafa ID4154

Rami ID123

SC242 Knowledge Engineering

SC242 Birzeit University

ID4154 SC242

ID123 SC242

University(Name)

OfferedBy /Offers

Jarrar © 2011 12

Basic ORM Constructs and Syntax

• Object and Value Types

• Roles and relations

• Unary relations

• Ternary relations

• Nested Fact Types

• Ring Fact Types

Jarrar © 2011 13

Object and Values Types

Person Car

Adams B 235PZN

Jones E 235PZN

Jones E 108AAQ

Person

has

PersonName

Car

RegNr

refers to

has

refers to

drives / is driven by

‘Adams B’‘Jones E’

‘235PZN’‘108AAQ’

drivesCarPerson

has has

PersonName RegNr

Value Type (lexical)It is always a value of an Object Type.

Object Type (non lexical)You cannot lexicalize, or refer to a person without using a value ofits properties.

Jarrar © 2011 14

Roles and Relations

Called Binary RelationIt consists of two roles

(“drives” and “is driven by”)

Called Rolewhich is part of a relation

Called Rolewhich is part of a relation

Jarrar © 2011 15

Unary Relations

Pat smokesLee smokesShir does not smoke

Called Unary Relationas it has one role

(“smokes”)

You can transform unary fact types into binary:

Jarrar © 2011 16

Ternary Relations

Called Ternary Relationas it has three roles

(“smokes”)

Jarrar © 2011 17

Nested Fact Types

Called Nested Fact TypeThe fact type “Student enrolled in

Subject” is objectified, i.e., the wholeFact type is seen as an Object Type

Jarrar © 2011 18

Ring Fact Types

Same object type is connected to two roles in the same relation

Jarrar © 2011 19

The ORM Syntax (Test)

An object type can be only connected with roles.Each role can be connected with only one object type.

û ü

ü

ü

üü

ü

û

û

û

ûû

Jarrar © 2011 20

Project 1

Model the following 3 cases using ORM, in both Arabic and English. Each student is expected to deliver (through Ritaj) his/her model in PDF format, each case in a different file. Any ORM tool can be used. Deadline: 18/2/2018 midnight. Each student is expected to bring his laptop next lecture, so to present his/her models to all students.

According to the Ministry of Higher Education:A University consists of a set of faculties, each faculty offer several Bachelor and Master programs. Each program consists of a set of courses. Same courses might be offered by different programs.

According the Israeli ID Card that each Palestinian must hold: Each Person has a ID Number, First Name, Father Name, Grandfather Name, BirthDate, Birth Place, Religion, Gender, and Address. A Person maybe a father/mother of one or more persons, and wife/husband of another person.

Case I:

Case II:

Each person should be either a male or a female. A person may have a name, birth date, passport number, and born in country. A person may works for and manages a company, and may have a bank account.

Case III:

Jarrar © 2011 21

References[1] Terry Halpin, Tony Morgan: Information Modeling and Relational Databases, Second Edition. Second Edition. The Morgan Kaufmann

Series in Data Management Systems. ISBN: 0123735688[2] Mustafa Jarrar and Robert Meersman: Ontology Engineering -The DOGMA Approach. Book Chapter in "Advances in Web Semantics

I". Chapter 3. Pages 7-34. LNCS 4891, Springer.ISBN:978-3540897835. (2008).[3] Mustafa Jarrar, Anton Deik, Bilal Faraj: Ontology-Based Data And Process Governance Framework -The Case Of E-Government

Interoperability In Palestine . In pre-proceedings of the IFIP International Symposium on Data-Driven Process Discovery and Analysis (SIMPDA’11). Pages(83-98). ISBN 978-88-903120-2-1. Campione, Italy. June 30, 2011.

[4] Mustafa Jarrar: Mapping ORM Into The SHOIN/OWL Description Logic- Towards A Methodological And Expressive Graphical NotationFor Ontology Engineering . In OTM 2007 workshops: Proceedings of the International Workshop on Object-Role Modeling (ORM'07). Pages (729-741), LNCS 4805, Springer. ISBN: 9783540768890. Portogal. November, 2007

[5] Mustafa Jarrar: Towards Automated Reasoning On ORM Schemes. -Mapping ORM Into The DLR_idf Description Logic. In proceedings of the 26th International Conference on Conceptual Modeling (ER 2007). Pages (181-197). LNCS 4801, Springer. Auckland, New Zealand. ISBN 9783540755623. November 2007

[6] Mustafa Jarrar and Stijn Heymans: Unsatisfiability Reasoning In ORM Conceptual Schemes. In Current Trends in Database Technology - EDBT 2006: Proceeding of the IFIP-2.6 International Conference on Semantics of a Networked. Pages (517-534). LNCS 4254, Springer. Munich, Germany. ISBN: 3540467882. March 2006.

[7] Mustafa Jarrar and Stijn Heymans: Towards Pattern-Based Reasoning For Friendly Ontology Debugging . Journal of Artificial Intelligence Tools. Volume 17. No.4. World Scientific Publishing. August 2008.

[8] Mustafa Jarrar, Maria Keet, and Paolo Dongilli: Multilingual Verbalization Of ORM Conceptual Models And Axiomatized Ontologies. Technical report. STARLab, Vrije Universiteit Brussel, February 2006.

[9] Sergey Lukichev and Mustafa Jarrar: Graphical Notations For Rule Modeling . Book chapter in "Handbook of Research on Emerging Rule-Based Languages and Technologies". IGI Global. ISBN:1-60566-402-2. (2009)

[10] Mustafa Jarrar: Modularization And Automatic Composition Of Object-Role Modeling (ORM) Schemes .OTM 2005 Workshops: Proceedings of the Object-Role Modeling (ORM'05). Pages (613-625). LNCS 3762, Springer. ISBN: 3540297391. 2005.

[11] Mustafa Jarrar: Towards Methodological Principles For Ontology Engineering. PhD Thesis. Vrije Universiteit Brussel. (May 2005)[12] Mustafa Jarrar, Jan Demey, and Robert Meersman: On Using Conceptual Data Modeling For Ontology Engineering . Journal on Data

Semantics, Special issue on "Best papers from the ER/ODBASE/COOPIS 2002 Conferences". LNCS 2800. No 1. Springer. 2003.[13] Jan Demey, Mustafa Jarrar, and Robert Meersman: A Markup Language For ORM Business Rules . Proceedings of the International

Workshop on Rule Markup Languages for Business Rules on the Semantic Web (RuleML 2002). Pages(107-128). Volume 60. CEUR Workshop Proceedings. ISSN 1613-0073. June 2002

[14] Mustafa Jarrar: Towards Effectiveness And Transparency In E-Business Transactions, An Ontology For Customer Complaint Management . A book chapter in "Semantic Web Methodologies for E-Business Applications". chapter 7. IGI Global. (2008)

[15] Mustafa Jarrar: ORM Markup Language, Version 3 . Technical Report. STAR Lab, Vrije Universiteit Brussel, Belgium. January 2007