Pal gov.tutorial1.session3 2.mandatoryrules


Published on

Published in: Education, Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Pal gov.tutorial1.session3 2.mandatoryrules

  1. 1. ‫أكاديمية الحكومة اإللكترونية الفلسطينية‬ The Palestinian eGovernment Academy www.egovacademy.psTutorial 1: Data and Business Process Modeling Session 3.2 Mandatory Rules Prof. Mustafa Jarrar Sina Institute, University of Birzeit Reviewed by Prof. Marco Ronchetti, Trento University, Italy PalGov © 2011 1
  2. 2. AboutThis tutorial is part of the PalGov project, funded by the TEMPUS IV program of theCommission of the European Communities, grant agreement 511159-TEMPUS-1-2010-1-PS-TEMPUS-JPHES. The project website: www.egovacademy.psProject Consortium: Birzeit University, Palestine University of Trento, Italy (Coordinator ) Palestine Polytechnic University, Palestine Vrije Universiteit Brussel, Belgium Palestine Technical University, Palestine Université de Savoie, France Ministry of Telecom and IT, Palestine University of Namur, Belgium Ministry of Interior, Palestine TrueTrust, UK Ministry of Local Government, PalestineCoordinator:Dr. Mustafa JarrarBirzeit University, P.O.Box 14- Birzeit, PalestineTelfax:+972 2 2982935 mjarrar@birzeit.eduPalGov © 2011 2
  3. 3. © Copyright NotesEveryone is encouraged to use this material, or part of it, but should properlycite the project (logo and website), and the author of that part.No part of this tutorial may be reproduced or modified in any form or by anymeans, without prior written permission from the project, who have the fullcopyrights on the material. Attribution-NonCommercial-ShareAlike CC-BY-NC-SAThis license lets others remix, tweak, and build upon your work non-commercially, as long as they credit you and license their new creationsunder the identical terms. PalGov © 2011 3
  4. 4. Tutorial Map Intended Learning Objectives Topic TimeModule 1 (Conceptual Date Modeling) Module I: Conceptual Data ModelingA: Knowledge and Understanding11a1: Demonstrate knowledge of conceptual modeling notations and concepts Session 0: Outline and Introduction11a2: Demonstrate knowledge of Object Role Modeling (ORM) methodology. Session 1.1: Information Modeling 111a3: Explain and demonstrate the concepts of data integrity & business rules Session 1.2: Conceptual Data Modeling using ORM 1B: Intellectual Skills Session 1.3: Conceptual Analyses 111b1: Analyze application and domain requirements at the conceptual level, Session 2: Lab- Conceptual Analyses 3and formalize it using ORM. Session 3.1: Uniqueness Rules 1.511b2: Analyze entity identity at the application and domain levels. Session 3.2: Mandatory Rules 1.511b4: Optimize, transform, and (re)engineer conceptual models. Session 4: Lab- Uniqueness & Mandatory Rules 311b5: Detect &resolve contradictions & implications at the conceptual level. Session 5: Subtypes and Other Rules 3C: Professional and Practical Skills Session 6: Lab- Subtypes and Other Rules 311c1: Using ORM modeling tools (Conceptual Modeling Tools). Session 7.1: Schema Equivalence &Optimization 1.5Module 2 (Business Process Modeling) Session 7.2: Rules Check &Schema Engineering 1.5A: Knowledge and Understanding Session 8: Lab- National Student Registry 312a1: Demonstrate knowledge of business process modeling notations and concepts. Module II: Business Process Modeling12a2: Demonstrate knowledge of business process modeling and mapping.12a3: Demonstrate understand of business process optimization and re-engineering. Session 9: BP Management and BPMN: An Overview 3B: Intellectual Skills Session 10: Lab - BP Management 312b1: Identify business processes. Session 11: BPMN Fundamentals 312b2: Model and map business processes. Session 12: Lab - BPMN Fundamentals 312b3: Optimize and re-engineer business processes. Session 13: Modeling with BPMN 3C: Professional and Practical Skills Session 14: Lab- Modeling with BPMN 312c1: Using business process modeling tools, such as MS Visio. Session 15: BP Management & Reengineering 3 Session 16: Lab- BP Management & Reengineering 3 PalGov © 2011 4
  5. 5. Session ILOsAfter completing this session students will be able to: 11a3: Explain and demonstrate the concepts of data integrity and business rules. 11b1: Analyze application and domain requirements at the conceptual level, and formalize it using ORM. PalGov © 2011 5
  6. 6. Conceptual Schema Design Steps1. From examples to elementary facts2. Draw fact types and apply population check3. Combine entity types4. Add uniqueness constraints5. Add mandatory constraints6. Add set, subtype, & frequency constraints7. Final checks, & schema engineering issues PalGov © 2011 6
  7. 7. Mandatory Versus Optional Any problem with this table?By default, all roles are optional.How can we say that a role is mandatory? each Patient Has at least one PatientName PalGov © 2011 7
  8. 8. Mandatory Roles Mandatoriness is implied with Value Types (by default).For example: it is assumed that “eachPhoneNr is for at least one Patient”, becausePhoneNr is a Value Type. ?? PalGov © 2011 8
  9. 9. Mandatory DefinitionRole r is mandatory (for the population of A)Each instance of type A that is recorded in the database isalso recorded to play rpop( r) = pop( A) PalGov © 2011 9
  10. 10. Mandatory RolesHow can we decide to make a role mandatory?Recall our discussion on (Conceptual data modeling) versus (conceptual modeling)If a role is mandatory in the real world, it may be optional in the model. PalGov © 2011 10
  11. 11. Disjunctive Mandatory How to say that it is mandatory for each member to (PlaysFor | Coaches) a team, or both. We cannot have both roles optional, at least one role should be played.Disjunctive mandatory constraint:Each Member coaches or plays (or both). PalGov © 2011 11
  12. 12. Disjunctive MandatoryAlternative notations for disjunctive mandatory role constraint. PalGov © 2011 12
  13. 13. Definition of Disjunctive MandatoryDisjunctive mandatory role constraintThe inclusive disjunction of roles r1...rn is mandatory for Ai.e., each member of pop(A) plays r1 or r2 ...or rn (or all)i.e., each member of pop(A) plays at least one of r1 … rn PalGov © 2011 13
  14. 14. Another Example Each person must be a parent or a child. PalGov © 2011 14
  15. 15. Back to Uniqueness PalGov © 2011 15
  16. 16. External UniquenessHow to say that the combination of (Discipline, YearLevel, SerialNr) isunique for each subject? The Subject code might be generated from this combination PalGov © 2011 16
  17. 17. Another Example PalGov © 2011 17
  18. 18. Reference SchemesIn data modeling, each entity (i.e., Object Type) must have an identity.The identity is achieved if an entity has a mandatory and unique roleThis is not important (i.e. implicit) in ontology modeling. PalGov © 2011 18
  19. 19. DiscussionSummarize what you learned? And what you think about it?Compare what you learned with EER and UML?Questions & Suggestions? PalGov © 2011 19
  20. 20. References1. Information Modeling and Relational Databases: From Conceptual Analysis to Logical Design, Terry Halpin (ISBN 1- 55860-672-6) – Chapter 5. PalGov © 2011 20