MIS 340: Data Modeling 2

1. MIS 340:Data Modeling 2 Yong Choi School of Business CSUB

2. Entities??? • Made up for the class…….ambiguous… ANG Laboratory has several chemists who work on one or more projects. Chemists also may use certain kinds of equipment on each project. The organization would like to store the chemist’s employee identification number, his/her name, up to three phone numbers, his/her project identification number and the date on which the project started. Every piece of equipment, the chemist uses, has a serial number and a cost.

3. Entities Project Chemist Equipment

4. Entities’ Attributes??? ANG Laboratory has several chemists who work on one or more projects. Chemists also may use certain kinds of equipment on each project. The organization would like to store the chemist’s employee identification number, his/her name, up to three phone numbers, his/her project identification number and the date on which the project started. Every piece of equipment, the chemist uses, has a serial number and a cost.

5. Start-Date Proj# Project Phone# Emp# Chemist Serial# Equipment cost entities, attributes and identifiers

6. How to find relationships? • Relationship: • Association between entities • Two entities can have more than one type of relationship • look for a verb or a verb phrase between entities • A couple of sentences to describe a relationship between two entities.

7. More about Relationship • Usually, a relationship can be described by a couple of sentences between two entities. • Operate in both directions • Relationship between Student and Curriculum • A student is enrolled in many curriculums. • Each curriculum is being studied by many students.

8. Relationships ??? ANG Laboratory has several chemists who work onone or more projects. Chemists also may use certain kinds of equipment on each project. The organization would like to store the chemist’s employee identification number, his/her name, up to three phone numbers, his/her project identification number and the date on which the project started. Every piece of equipment, the chemist uses, has a serial number and a cost.

9. Entities/Relationships& their Attributes Start-Date Proj# Works-On Project Phone# Emp# Date-Assigned Chemist Uses Serial# Equipment cost Assign-Date

10. Steps for creating an ERD • Identify the entities • Beginner: look for nouns • Identify the attributes • Beginner: look for entity descriptions • Identify the relationships • Beginner: look for a verb or a verb phrase between entities

11. Degree of Relationship • Degree of a Relationship describes the number of entity participation • Unary (Recursive) Relationship: One instance related to another of the same entity type • Binary Relationship: Instances of two different entities related to each other • Ternary Relationship: Instances of three different types related to each other

12. Degree of Relationship …

13. Type of Relationships (Cardinality) • One – to – One (1:1) • Each instance in the relationship will have exactly one related member on the other side • One – to – Many (1:M) • A instance on one side of the relationship can have many related members on the other side, but a member on the other side will have a maximum of one related instance • Many – to – Many (M:N) • Instances on both sides of the relationship can have many related instances on the other side

14. 1:1 relationship in Set notation

15. Example of 1:1 relationship • A one-to-one (1:1) relationship is when at most one instance of an entity A is associated with one instance of entity B. • Each employee is assigned to one workstation. • Not all workstations are assigned to employees.

16. 1:M relationship in Set notation

17. Example of 1:M relationship • A one-to-many (1:N) relationships is when for one instance of entity A, there are zero, one, or many instances of entity B, but for one instance of entity B, there is only one instance of entity A. • A department is responsible for many projects. • Each project is the responsibility of one department.

18. M:N relationship in Set notation

19. Example of M:N relationship • A many-to-many (M:N) relationship, sometimes called non-specific, is when for one instance of entity A, there are zero, one, or many instances of entity B and for one instance of entity B there are zero, one, or many instances of entity A. • Employees are assigned to many projects. • Every project has assigned at least one employee.

20. Type of Relationship (Cardinality) The organization would like to store the date the chemist was assigned to the project and the date an equipment item was assigned to a particular chemist working on a particular project. A chemist must be assigned at least to one (or more) project and one (or more) equipment.Projects and equipments must be managed by only one chemist. A given project need not be assigned an equipment.

21. Complete ER Diagram Start-Date Proj# Works-On 1 N Project Phone# Emp# Date-Assigned Chemist Uses Serial# 1 N Equipment cost Assign-Date

22. Steps for creating an ERD • Find out candidate entities • Identify the entities • Identify the attributes • Identify the relationships • Beginner: look for participation related words and phrases such as zero, none, a, one, several, many….. • Optional relationship:look for auxiliary verbs such as may, might, can and based upon own judgment..) • Finalize business rules

23. 1-to-1 relationship 1-to-M relationship M-to-N relationship weak entity relationship optional relationship recursive relationship Original IE Notations(minor differences with the textbook – pp.223) Employee

24. Type Minimum Instances Maximum Instances Graphic Notation Exactly one 1 1 Zero or one 0 1 Many (>1) One or many 1 0 Many (>1) Zero or many

25. 1:1 relationship A person must have one and only one DNA pattern and that pattern must be applied to one and only one person.

26. 1:1 with optional relationship (OR)on one side A person might not or might be a programmer, but a programmer must be a person.

27. 1:M relationship Each department hires many employees, and each employee is hired by one department.

28. 1:M with OR on many side A person might be a member or might not, but could be found multiple times (if the member entity represents membership in multiple clubs, for instance). A member must have only a single person.

29. 1:M with OR on both side A person might have no phone, one phone or lots of phones, and that a phone might be un-owned or can only be owned by a person.

30. M:N relationship Each student takes many classes, and a class must be taken by many students. STUDENT CLASS IS_TAKEN_BY TAKE **Many-to-many relationships cannot be used in the data model because they cannot be represented by the relational model (see the next slide for the reason) **

31. Example of M:N Many-to-many relationships is a second sign of complex data. When x relates to many y's and y relates to many x's, it is a many-to-many relationship. In our example schema,a color swatch can relate to many types of sweaters and a type of sweater can have many color swatches. 

32. Example M:N Relationship Table to represent Entity 3 to 3 30 to 30 300 to 300 3000 to 3000 30,000 to 30,000 300, 000 to 300, 000

33. CLASS ENROLL STUDENT Transformation of M:N • When transform to relational model, many redundancies can be generated. • The relational operations become very complex and are likely to cause system efficiency errors and output errors. • Break the M:N down into 1:N and N:1 relationships using bridge entity (weak entity).

34. EMP DEP Weak Entity relationship • A weak entity is an entity that cannot be uniquely identified and existed by itself alone. • Thus, a weak entity is an entity that exists only if it is related to a set of uniquely determined entities (owners of the weak entity). • More examples on the textbook • Each employee might have none or multiple dependents. However, dependents must belong to at least one employee. weak entity notation

35. Converting M:N Relationship to Two 1:M Relationships Bridge Entity

36. Bridge Entity • ENROLL entitybecomes a weak entity of both STUDENT entity and CLASS entity • MUST have a composite (unique) identifier • STU_NUM (from STUDENTentity) and CLASS_CODE (from CLASSentity)

37. M:N with optionality on both side • A person might or might not work for an employer, but could certainly moonlight for multiple companies. An employer might have no employees, but could have any number of them. After broken down, optional relationship notation on both side of associative entity

38. Employee Recursive relationship 1 • A recursive relationship is an entity is associated with itself. • Each employee is supervised directly by at most one supervisor (manager). Each supervisor (manager) can manage many employees. manages is managed by

39. Student Recursive relationship 2 • Each student is taught by aSTA (student teaching assistant). Each STA can teach several students. teaches is taught by

40. Data Modeling Errors • In general, there are two classes of E-R modeling errors that lead to normalization problems: • Incomplete data model error • Miss-modeled problem domain error • Read next two slides…

41. In Complete Data Model • Occur in situations where the systems analysts is tasked to build a computer-based information system that is limited in scope. A key objective for successful information system project management is the definition of a limited, yet adequate project scope--a scope that enables the production of system deliverables within a reasonable time period. Limiting a project's scope often results in information systems that are based on limited data models. Limited information systems are fairly common throughout the IS world where dissimilar technologies prevent data sharing and work against the concept of a shared, enterprise-wide database.

42. Miss-modeled problem domain error • The miss-modeled problem domain error is actually a class of errors including those that arise whenever systems analysts lack a complete understanding of the problem domain. These include errors such as depicting an attribute as single-valued when, in fact, the attribute is multi-valued, or depicting a single entity which includes attributes that should be assigned to two separate entities, or miss-modeling the connectivity or degree of a relationship.