chapter 2 modeling data in the organization
DESCRIPTION
Chapter 2 Modeling Data in the Organization. Jason C. H. Chen, Ph.D. Professor of MIS School of Business Administration Gonzaga University Spokane, WA 99258 [email protected]. Review Q : (#11; 101) Four types of cardinality constraints are: (Fig 2-26). - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/1.jpg)
1
Chapter 2 Modeling Data in the Organization
Jason C. H. Chen, Ph.D.Professor of MIS
School of Business AdministrationGonzaga UniversitySpokane, WA [email protected]
![Page 2: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/2.jpg)
Review Q: (#11; 101) Four types of cardinality constraints are: (Fig 2-26)
![Page 3: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/3.jpg)
Q: (#11; 101) Four types of cardinality constraints are:
a. Optional one:
b. Mandatory one:
![Page 4: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/4.jpg)
Q: (#11; 101) (cont.)
c. Optional Many:
d. Mandatory Many
![Page 5: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/5.jpg)
Review Q: (#12; p.101) Another example of Weak Entity
Phone Call (see below) is an example of a weak entity because a phone call must be placed by a PERSON. In this simple example, PHONE CALL is related to only one other entity type, thus, it is not necessary to show the identifying relationship; however, if this data model were ever expanded so that PHONE CALL related to other entity types, it is good practice to always indicate the identifying relationship.
![Page 6: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/6.jpg)
Review Q: (#13; 101) Degree of Relationship?a. Unary (one entity type):
b. Binary (two entity types):
![Page 7: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/7.jpg)
Q: (#13; 101)Degree of Relationship (cont.)
c. Ternary (three entity types):
![Page 8: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/8.jpg)
Problems and Exercises
![Page 9: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/9.jpg)
#7) Exercise: Note: Assume Student Name is unique and available to be used as the identifier.
![Page 10: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/10.jpg)
#7 (version b).
Notes: Assume that Student_Name is the identifier.Age cannot be calculated without date-of-birth.
![Page 11: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/11.jpg)
#10 – Figure 2-26 (p. 103)
What tables are needed in order to produce the report?• Student• Course/ Course_Section• Instructor
![Page 12: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/12.jpg)
NOTE: The addition of Semester and Year attributes on the Registers_for relationship allows this diagram (and resulting database) to reflect multiple semesters of data.
#10
![Page 13: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/13.jpg)
STUDENT
Student_idName
AddressMajor
COURSE
Course_idTitle
Instructor_id
INSTRUCTOR
Instructor_idInstructor_Name
Office
Register-for
Grade Semester
Year
teaches
![Page 14: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/14.jpg)
QUESTIONS:1. John Smith is taking five courses (BMIS441, ACCT464, ACCT363, BFIN422 and MGMT400) in Fall 2013, can we create the course information in either STUDENT or COURSE table?2. If Yes/How? If No/Why and how to solve the problem?
Issues to discuss:1. Can we insert additional records with other information (e.g., grades etc.) directly to “STUDENT” entity or “COURSE” entity directly? 2. If Yes/How? If No/Why and how to solve the problem?
![Page 15: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/15.jpg)
STUDENT
Student_idName
AddressMajor
COURSE
Course_idTitle
Instructor_id
INSTRUCTOR
Instructor_idInstructor_Name
Office
Register-for
Grade Semester
Year
teaches
![Page 16: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/16.jpg)
STUDENT
Student_idName
AddressMajor
COURSE
Course_idTitle
Instructor_id
INSTRUCTOR
Instructor_idInstructor_Name
Office
teachesREGISTRATION
Student_idCourse_id
GradeSemester
Year
![Page 17: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/17.jpg)
STUDENT
Student_idName
AddressMajor
COURSE
Course_idTitle
Instructor_id
INSTRUCTOR
Instructor_idInstructor_Name
Office
teachesREGISTRATION
Student_idCourse_id
GradeSemester
Year
Register-for
was registered
![Page 18: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/18.jpg)
![Page 19: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/19.jpg)
#11) Exercise: Note: attributes are omitted from the ERD solutions for this Problem and Exercise (Part I: a-c)
a. Figure 2-5
b. Figure 2-10a
c. Figure 2-11b
![Page 20: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/20.jpg)
d.) Exercise: Figure 2-12Part II: d-f
![Page 21: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/21.jpg)
e) Figure 2-13c
f.) Figure 2-14
![Page 22: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/22.jpg)
12.) Part II. Exercise: (p.103)
![Page 23: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/23.jpg)
12.) Part II. Exercise: (cont.)
![Page 24: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/24.jpg)
Figure 2-11a A binary relationship with an attribute Attribute on a relationship (Link Attribute/Associative)
Q: (#15; 103) Degree of Relationship?
![Page 25: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/25.jpg)
#15 (p.103) Figure 2-11a (Modified)
![Page 26: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/26.jpg)
20.) HW: STUDENT and ADVISORs ERD
Course_IDStudent_IDAdvisor_IDAdvisor_ID (fk)
![Page 27: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/27.jpg)
20.) HW: STUDENT and ADVISORs ERD
Course_IDStudent_IDAdvisor_ID
![Page 28: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/28.jpg)
20.) HW: STUDENT and ADVISORs ERD
![Page 29: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/29.jpg)
20.) HW: STUDENT and ADVISORs ERD
Course_IDStudent_IDAdvisor_ID
Student_IDAdvisor_ID
ADVISING
SemeterYear
![Page 30: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/30.jpg)
20.) HW: STUDENT and ADVISORs ERD
Course_IDStudent_IDAdvisor_IDAdvisor_ID (fk)
![Page 31: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/31.jpg)
#21) Figure 2-4a Revised for Sarbanes-Oxley compliance purposes
Appropriate entities
![Page 32: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/32.jpg)
![Page 33: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/33.jpg)
13.
![Page 34: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/34.jpg)
17. a
Yes, the attribute names do generally follow the guidelines for naming attributes.
![Page 35: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/35.jpg)
17. b
Assignment: All three entities participate in the Assigned relationship that is modeled as an associative entity Assignment, since the Assign_Date for each Chemist’s assignment to a particular project and equipment item must be tracked. However, EQUIPMENT and PROJECT do not need to participate in any assignments. All entities can have multiple assignments.
![Page 36: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/36.jpg)
17. c
Note: SECTION is modeled as a weak entity. It could have been modeled as a multivalued attribute; however, using a weak entity is better, since SECTION may have a relationship with another entity. A multivalued attribute could not be used to show this relationship.
![Page 37: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/37.jpg)
17. d
Both Admits and Treats relationships were created since the patient could be treated by different PHYSICIANs than the admitting PHYSICIAN.
![Page 38: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/38.jpg)
17h. Note to Instructor: This problem and exercise is a good lead-in for Chapter 3 modeling notation for the Extended Entity Relationship Diagram (EERD). The P&E offers several chances to provide better representation in the EERD (with subtyping) than the ERD notation that is provided in Chapter 2. Using EERD notation, a single LEGAL ENTITY can be shown as a supertype, with subtypes of DEFENDANT and PLAINTIFF. The ‘type’ (person or Organization) characteristic of both DEFENDANT and PLAINTIFF may also be considered for further subtyping. The solution presented here is a valid answer to the P&E, given the limitations of basic ERD notation and what is currently known about the situation. This P&E also provides the instructor with an opportunity to discuss how history might be modeled if the business assumption regarding the tracking of Net Worth for both Plaintiff and Defendant was changed from only being concerned with Net Worth at the time of the CASE, to wanting to track the Net Worth over time of each party to the CASE. Refer to the chapter section on “Modeling Time-Dependent Data” and Figure 2-19 for more information on how this ERD could be revised.
![Page 39: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/39.jpg)
17h.
![Page 40: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/40.jpg)
17. i
![Page 41: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/41.jpg)
18. PVFC ERD
![Page 42: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/42.jpg)
19. Emerging Electric ERD
![Page 43: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/43.jpg)
22.
![Page 44: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/44.jpg)
22 (cont.)Entities:Employee: An employee of the firm. An employee works for one sales office and may manage one sales office. It is not explicitly indicated that the employee can only manage the office that he/she works for. This would require a business rule. Sales Office: The office where real estate is sold. Property: Buildings for sale, such as houses, condos and apartment buildings.
Owner: The individual who owns one or more properties. Attributes on Employee:Employee ID: A unique identifier for an employee. This attribute must be unique.
Employee Name: The name of the employee. Attributes on Sales Office:
Office Number: A unique identifier for the office.Office Location: The physical location of the sales office. This data may be made up of the city and state.
![Page 45: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/45.jpg)
22 (cont.)Attributes on Property:Property ID: The unique identifier for the property.Property Location: A composite attribute that consists of the street address, city, state, and Zip Code. Attributes on Owner:Owner ID: The unique identifier for the owner.Owner Name: The name of the owner. Relationship:Is Assigned: An employee is assigned to one sales office. A sales office may have many employees assigned but must have at least one employee.
Manages: An employee may manage one sales office or no sales office. Each sales office is managed by one employee. A business rule is needed here in order to indicate that an employee can only manage the sales office in which he or she works. Lists: Each property is listed by only one sales office. Each sales office can list one, none, or many properties. Owns: Each property has one or more owners. Each owner can own one or more properties. Percent Owned is an attribute on Owns; it tracks the percent of property that a particular owner owns.
![Page 46: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/46.jpg)
26. Stillwater Antiques ERD
![Page 47: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/47.jpg)
27. A.M. Honka School of Business ERD
![Page 48: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/48.jpg)
28. Wally’s Wonderful World of Wallcoverings ERD:
![Page 49: Chapter 2 Modeling Data in the Organization](https://reader034.vdocuments.net/reader034/viewer/2022042603/56816972550346895de146b3/html5/thumbnails/49.jpg)
29. Peck and Paw ERD