1. MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury salisbury@udayton.edusalisbury@udayton.edu (email) http://www.davesalisbury.com/http://www.davesalisbury.com/ (web site)

2. Modeling reality A database must mirror the real world if it is to answer questions about the real world Data Modeling is a design technique for capturing reality STUDENT Social_Security_No Name Major

3. Business rules Statements that define or constrain some aspect of the business Assert business structure Control/influence business behavior Expressed in terms familiar to end users Automated through DBMS software

4. A good business rule is: Declarative – what, not how Precise – clear, agreed-upon meaning Atomic – one statement Consistent – internally and externally Expressible – structured, natural language Distinct – non-redundant Business-oriented – understood by business people

5. The conceptual model (ER diagram) Representation of structure and constraints of database independent of software Mainstream approach to conceptual modeling is ERD ease of use CASE support entities and relationships are “natural” No standard notation Building blocks are entities, attributes, relationships, and identifiers

6. E-R model constructs Entity instance - person, place, object, event, concept (often corresponds to a row in a table) Entity Type – collection of entities (often corresponds to a table) Attribute - property or characteristic of an entity type (often corresponds to a field in a table) Relationship instance – link between entities (corresponds to primary key-foreign key equivalencies in related tables) Relationship type – category of relationship…link between entity types

7. Relationship degrees specify number of entity types involved Entity symbols A special entity that is also a relationship Relationship symbols Relationship cardinalities specify how many of each entity type is allowed Attribute symbols Elements of an E-R diagram - Hoffer

8. Elements of an E-R diagram – Chen* ENTITY RELATIONSHIP WEAK ENTITY INDENTIFYING RELATIONSHIP ATTRIBUTE MULTIVALUED ATTRIBUTE ASSOCIATIVE ENTITY DERIVED ATTRIBUTE *Actually somewhat modified Chen.

9. What should an entity be? Should be: An object that will have many instances in the database An object that will be composed of multiple attributes An object that we are trying to model Should NOT be: A user of the database system An output of the database system (e.g. a report)

10. Inappropriate entities System user System output Appropriate entities Inappropriate/Appropriate Entities

11. Attributes A discrete data element Describes an entity (i.e., is a characteristic) Meaningful (for the system being modeled) Attributes are the items of interest to the organization -- the things being stored Customer_Number 12345 Last_Name Salisbury First_Name Dave Address 2425 Jasper Road City Xenia State OH Zip 45385 Phone 937-293-0258

12. Identifiers (keys) Identifier (Key) - An attribute (or combination of attributes) that uniquely identifies individual instances of an entity type Simple Key versus Composite Key Candidate Key – an attribute that could be a key…satisfies the requirements for being a key

13. Characteristics of Identifiers Will not change in value Will not be null No intelligent identifiers (e.g. containing locations or people that might change) Substitute new, simple keys for long, composite keys

14. Composite Attributes An attribute broken into component parts

15. Composite Attributes

16. Key attributes The identifier is boldfaced and underlined

17. The key is underlined Simple key attribute

18. The key is composed of two subparts Composite Key

19. Multi-valued & derived attributes Multivalued an employee can have more than one skill Derived from date employed and current date

20. Both multivalued & composite attribute This is an example of time-stamping

21. Derived from date employed and current date What’s wrong with this? Multivalued: an employee can have more than one skill Multi-valued & derived attributes

22. This is an example of time- stamping Multivalued & composite attribute

23. More on relationships Relationship Types vs. Relationship Instances The relationship type is modeled as the text on the lines between entity types…the instance is between specific entity instances Relationships can have attributes These describe features pertaining to the association between the entities in the relationship Two entities can have more than one type of relationship between them (multiple relationships) Associative Entity = combination of relationship and entity More on this later

24. Relationship types and instances Relationship type Relationship instances

25. Relationship degree Entities of three different types related to each other Entities of two different types related to each other One entity related to another of the same entity type

26. Relationship degree Unary – related to same entity type Binary – two different entity types Ternary – three different entity types

27. Cardinality Constraints Cardinality Constraints - the number of instances of one entity that can or must be associated with each instance of another entity. Minimum Cardinality If zero, then optional If one or more, then mandatory Maximum Cardinality The maximum number

28. Relationship cardinality notation Mandatory one Mandatory many Optional one Optional many

29. Relationship cardinality notation Mandatory one Mandatory many Optional one Optional many

30. Unary

32. Binary

34. Here, the date completed attribute pertains specifically to the employee’s completion of a course…it is an attribute of the relationship Binary relationship with an attribute

35. Ternary relationship (w/ attributes) (Relationships can have attributes of their own)

37. Hierarchical Relationships Occur frequently Model as multiple 1:M relationships Firm Division Dept

38. Strong vs. weak entities & identifying relationships Strong entities exist independently of other types of entities own unique identifier identifier underlined with single-line Weak entity dependent on a strong entity (identifying owner) cannot exist on its own no a unique identifier (only a partial identifier) Partial identifier underlined with double-line Entity box has double line Identifying relationship links strong entities to weak entities

39. Strong entity Weak entity Identifying relationship Strong & weak entities

40. Strong entity Weak entity Identifying relationship Strong & weak entities

41. Associative entities It’s an entity – it has attributes AND it’s a relationship – it links entities together When should a relationship with attributes instead be an associative entity? All relationships for the associative entity should be many The associative entity could have meaning independent of the other entities The associative entity preferably has a unique identifier, and should also have other attributes The associative may be participating in other relationships other than the entities of the associated relationship Ternary relationships should be converted to associative entities (p 112-113)

42. Associative entity is like a relationship with an attribute, but it is also considered to be an entity in its own right. Associative entity

43. Associative entity involves a rectangle with a diamond inside. Note that the many-to-many cardinality symbols face toward the associative entity and not toward the other entities Associative entity

44. This could just be a relationship with attributes…it’s a judgment call Associative Entity

45. This is the Bill of Materials laid out a different way. It could just be a relationship with attributes…it’s a judgment call Associative Entity

46. Ternary as Associative Entity

48. A patient must have recorded at least one history, and can have many A patient history is recorded for one and only one patient Mandatory cardinalities

49. An employee can be assigned to any number of projects, or may not be assigned to any at all A project must be assigned to at least one employee, and may be assigned to many 1 optional many, 1 mandatory many

50. A person is is married to at most one other person, or may not be married at all Optional Cardinality

51. Entities can be related to one another in more than one way Multiple relationships (entities can be related to one another in more than one way)

52. Employees and departments Multiple relationships (entities can be related to one another in more than one way)

53. Here, min cardinality constraint is 2 Professors & courses (fixed upon constraint)

54. Here,max cardinality constraint is 4 Professors & courses (fixed upon constraint)

55. simple composite Multivalued attribute vs. relationship

57. Sample E-R Diagram (Figure 3-1)

58. Sample E-R Diagram (Similar to figure 3-1 with different notation)

59. Pine Valley Furniture

61. Modified Chen notation used in an earlier edition of our textbook

62. Different notation CUSTOMER * Customer ID Customer name ORDER * Order ID Order Date

63. Third style of notation CUSTOMER ORDER SUBMITS 1 M Customer ID Customer name Order ID Order date

64. Oracle notation CUSTOMER #Customer_ID *Customer Name ORDER #Order_ID *Order Date

65. Access Notation