Subset, Equality, and Exclusion Rules
0 likes1,184 views
This document discusses subset, equality, and exclusion constraints in Object-Role Modeling (ORM) as part of conceptual schema design. It outlines various types of constraints, such as mandatory and exclusion constraints, and provides examples to illustrate their applications in business logic and data integrity. Additionally, the document includes references for further reading on ORM and related methodologies.
![2Jarrar © 2015
Watch this lecture and download the slides from
http://jarrar-courses.blogspot.com/2015/01/dataandbusinessprocessmodelling.html
Some diagrams in this lecture are based on [1]
Keywords: Subset, Equality, Exclusion, set-comparison constraints, Set Constraints, Rules,
Business Rules, Business logic derivation rules, integrity constraints
Slides And Videos - Download, Watch, Interact](https://image.slidesharecdn.com/jarrar-150405132036-conversion-gate01/85/Subset-Equality-and-Exclusion-Rules-2-320.jpg)
Subset, Equality, and Exclusion Rules
- 1. 1Jarrar © 2015 (Chapter 6) Subset, Equality, and Exclusion Rules In ORM Reference: Mustafa Jarrar: Lecture Notes on Subset, Equality, and Exclusion Rules in ORM Birzeit University, Palestine, 2015 Mustafa Jarrar Birzeit University, Palestine [email protected] www.jarrar.info
- 2. 2Jarrar © 2015 Watch this lecture and download the slides from http://jarrar-courses.blogspot.com/2015/01/dataandbusinessprocessmodelling.html Some diagrams in this lecture are based on [1] Keywords: Subset, Equality, Exclusion, set-comparison constraints, Set Constraints, Rules, Business Rules, Business logic derivation rules, integrity constraints Slides And Videos - Download, Watch, Interact
- 3. 3Jarrar © 2015 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 subtype relations and other constraints 7. Final checks, & schema engineering issues
- 4. 4Jarrar © 2015 Role subset/equality constraint Subset constraint: Every Member booked an Hour should play sport. Equality constraint: Every Member ‘has’ ReactionTime should ‘has’ HeartRate, and every Member ‘has’ HeartRate should ‘has’ ReactionTime.
- 5. 5Jarrar © 2015 Role subset constraint Notice that this subset constraint is implied, and should be removed. That is, there is no need to say that every A playing r2 must also play r1 (subset), because the mandatory constraint here means that every A must play r1 (the Mandatory implies the subset).
- 6. 6Jarrar © 2015 Role equality constraint Also this quality constraint is implied, and should be removed.
- 7. 7Jarrar © 2015 Implication Who can explain the difference? The two constraints in the first model says: each A must play r1 or r2 (or both), and that if A plays r2 then it must play r1. This means that r1 must be always played (which is the second model)
- 8. 8Jarrar © 2015 Role Exclusion Constraint Exclusion constraint: Every Employee is allocated a ParkingSpace should not claim MoneyAmt.
- 9. 9Jarrar © 2015 Role Exclusion Constraint
- 10. 10Jarrar © 2015 Role Exclusion Constraint Each partner must be either a husband or wife (but not both at the same time). Called “Exclusive-or”
- 11. 11Jarrar © 2015 Exclusive-or (another example) Each Account must be OwnedBy a Person or a Company, but not both.
- 12. 12Jarrar © 2015 Role Exclusion Constraint Each person has at most one of three vices. i.e., from 0 to 3 vices. It can be written also as
- 13. 13Jarrar © 2015 Pair Exclusion Constraint How can we restrict that a person can drive a car only if he owns that car.
- 14. 14Jarrar © 2015 Pair-subset constraint An example of a tuple-subset constraint between sequences of three roles.
- 15. 15Jarrar © 2015 Equality Constraint
- 16. 16Jarrar © 2015 Pair Exclusion Constraint Same person can ‘own’ and ‘wants to buy’ the same car?
- 17. 17Jarrar © 2015 What is Wrong? Implies ImpliesImplies
- 18. 18Jarrar © 2015 References 1. Terry Halpin, Tony Morgan: Information Modeling and Relational Databases, Second Edition. 2nd Edition. The Morgan Kaufmann Series in Data Management Systems. ISBN: 0123735688 2. 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. Aug 2008. 3. Mustafa Jarrar: Mapping ORM Into The SHOIN/OWL Description Logic- Towards A Methodological And Expressive Graphical Notation For 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 4. 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 5. 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. 6. Mustafa Jarrar, Maria Keet, and Paolo Dongilli: Multilingual Verbalization Of ORM Conceptual Models And Axiomatized Ontologies. Technical eport. STARLab, Vrije Universiteit Brussel, Feb 2006. 7. 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. Larnaca, Cyprus. ISBN: 3540297391. November 2005.