MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management

1. MIS 385/MBA 664Systems Implementation with DBMS/Database Management Dave Salisbury salisbury@udayton.edu (email) 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. Entity symbols Elements of an E-R diagram - Hoffer Attribute symbols A special entity that is also a relationship Relationship symbols Relationship degrees specify number of entity types involved Relationship cardinalities specify how many of each entity type is allowed

8. Elements of an E-R diagram – Chen* ASSOCIATIVE ENTITY ENTITY WEAK ENTITY ATTRIBUTE MULTIVALUED ATTRIBUTE DERIVED ATTRIBUTE RELATIONSHIP INDENTIFYING RELATIONSHIP *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 • ShouldNOT be: • A user of the database system • An output of the database system (e.g. a report)

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

11. 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 Attributes

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. An attribute broken into component parts Composite Attributes

15. An attribute broken into component parts Composite Attributes

16. The identifier is boldfaced and underlined Key attributes

17. Simple key attribute The key is underlined

18. The key is composed of two subparts Composite Key

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

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

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

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

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 type Relationship instances Relationship types and instances

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

26. Relationship degree Binary – two differententity types Unary – related to same entity type Ternary – three differententity 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

31. Unary

32. Binary

33. Binary

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

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

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

37. Hierarchical Relationships • Occur frequently • Model as multiple 1:M relationships Division Firm 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 & weak entities Identifying relationship Strong entity Weak entity

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

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 Associative entity is like a relationship with an attribute, but it is also considered to be an entity in its own right.

43. Associative entity 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

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

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

46. Ternary as Associative Entity

47. Ternary as Associative Entity

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

49. A project must be assigned to at least one employee, and may be assigned to many An employee can be assigned to any number of projects, or may not be assigned to any at all 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