ERD Notation: Entity & Attribute OR PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

ERD Notation: Relationship or PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Cardinality Cardinality - refers to the number of times instances in one entity can be related to instances in another entity One instance in an entity refers to one and only one instance in the related entity (1:1)  “one-to-one” One instance in an entity refers to one or more instances in the related entity (1:N)  “one-to-many” One or more instances in an entity refer to one or more instances in the related entity (M:N)  “many-to-many” Modality - Refers to whether or not an instance of a child entity can exist without a related instance in the parent entity Not Null means that an instance in the related entity must exist for an instance in another entity to be valid Null means that instance in the related entity is not necessary for an instance in another entity to be valid PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Relationship Cardinality …an example 1 : 1 one-to-one satu orang staf ( contoh ketua jabatan) akan menguruskan satu jabatan dan satu jabatan akan hanya mempunyai satu ketua jabatan sahaja 1 : N one-to-many satu orang pelanggan boleh membuat banyak tempahan tetapi bagi satu tempahan adalah untuk satu pelanggan sahaja M : N many-to-many satu orang pelajar boleh mendaftar banyak kursus dan satu kursus boleh ambil ramai pelajar PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Relationship Cardinality Mandatory 1 cardinality (1,1) or Mandatory many (M) cardinality (1, 2,…,many), n is a number for an upper limit) (1,n) or Optional 0 or 1 cardinality (0,1) or Optional zero-many cardinality (0,1,2,…many) (0,n) or PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Entity-Relationship Diagram: MISville Library ERD : Contoh Entity-Relationship Diagram: MISville Library This is the entity-relationship diagram for the MISville Library: Attributes B #1:  ISBN Number B #2:  Title B #3:  Subject(s) B #4:  Author(s) B #5:  Date of Publication B #6:  Acquisition Number LC #1:  Name LC #2:  Address LC #3:  Phone LC #4:  DOB LC #5:  SSN LC #6:  Card Number AJ #1:  ISBN Number AJ #2:  Title AJ #3:  Subject(s) AJ #4:  Author(s) AJ #5:  Date of Publication AJ #6:  Acquisition Number CC #1:  Book Title CC #2:  Author(s) CC #3:  Subject(s)  Data Modeling - ERDPowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Patient Doctor Insurance Claim Insurance Agent Whenever new patients are seen for the first time, they complete a patient information form that asks their name, address, phone number, and insurance agent, all of which is stored in the patient information file. Patients can be signed up with only one agent. Each time a patient visits its doctor, an insurance claim is sent to the agent for payment. The claim must contain information about the visit, such as the date, purpose, and cost. It would be possible for a patient to submit two claims on the same day. Draw an ERD for the situation. address name # phone Patient Doctor Insurance name visit submit sign (0, 2) date Insurance Claim Insurance Agent cost send (0, 2) (0, 1) purpose PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Practice: Food Order System Read the situation given below, Food Order System is used by Yummy Restaurant to manage every order from their customers. The Food Order System has few functions and very user friendly. It begins when the system receives order from the customer. The system will produce receipt by referring to the order. The order is also sent to the kitchen department. The system also used the information from the order to update their inventory as well as their sales. The system also has function to generate reports for the top management, i.e. sales report and inventory report. Food Order System digunakan oleh Yummy Restaurant untuk mengurus setiap tempahan dari pelanggan. Food Order System ini mempunyai beberapa fungsi dan ramah pengguna. Ia bermula apabila sistem menerima tempahan dari pelanggan. Sistem akan mengeluarkan resit dengan merujuk kepada tempahan. Tempahan juga dihantar kepada bahagian dapur. Sistem juga menggunakan maklumat dari tempahan untuk mengemaskini inventori serta jualan. Sistem juga mempunyai fungsi untuk menghasilkan laporan-laporan bagi pihak pengurusan, iaitu laporan jualan dan laporan inventori Draw ERD for the situation given. PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Update inventory and sales DFD Level 0 Order information Order information 1.0 Receive order CUSTOMER KITCHEN DEPARTMENT receipt Order information D1 Order file 2.0 Produce receipt Order information Order information 3.0 Update inventory and sales Order information D2 Inventory file D3 Sales file Updated information Updated information 4.0 Generate reports MANAGEMENT Inventory & sales Reports PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

ERD CUSTOMER make ORDER Send to KITCHEN DEPARTMENT update receive RECEIPT INVENTORY SALES generate generate INVENTORY REPORT SALES REPORT submit submit MANAGEMENT PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

ERD Building Tips Data stores of the DFD should correspond to entities Only include entities with more than one instance of information Don’t include entities associated with implementation of the system (they will be added later) – physical model of ERD PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Exercise For each pair of sentences, identify entities and the relationship representing the sentences. "Each Student must take one or more Modules" "Each Module must be taken by one or more Students" "Each Customer must receive at least one Delivery" "Each Delivery must be for only one Customer" "A Client my have an Account Manager" "Each Account Manager has only one Client" PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Patient Doctor Insurance Claim Insurance Carrier Whenever new patients are seen for the first time, they complete a patient information form that asks their name, address, phone number, and insurance carrier, all of which is stored in the patient information file. Patients can be signed up with only one carrier. Each time a patient visits its doctor, an insurance claim is sent to the carrier for payment. The claim must contain information about the visit, such as the date, purpose, and cost. It would be possible for a patient to submit two claims on the same day. Draw an ERD for the situation. address name # phone Patient Doctor Insurance name visit submit date Insurance Claim Insurance Carrier cost send (0, 2) (0, 1) purpose PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Associative Entity An entity type that associates the instances of one or more entity types and contains attributes that are peculiar to the relationship between those entity instances Example: Date_completed is not a property of entity EMPLOYEE or COURSE, it is a property of the relationship between EMPLOYEE and COURSE. Employee_id Course_Name PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

SHIPMENT Entity Type (an Associative Entity) PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Type of Attribute Derived Attribute Composite Attribute Alamat STAF No_Staf Nama Umur Tarikh_lahir Jalan Bandar Poskod No_rumah Negeri Multivalued Attribute STAF No_Staf Nama Nama_tanggungan Create weak entity to separate the repeating data STAF No_Staf Nama TANGGUNGAN mempunyai 1 M PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Degree of a Relationship PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Sample of ERD SUPPLIER SHIPMENT ITEM PRODUCTION PLAN MASTER SCHEDULE PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

Final E-R Diagram for Hoosier Burger’s Inventory Control System PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.