1. ANALYSIS PHASE Requirements Determination Use Case Analysis
Process Modeling
Data Modeling
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

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

3. Key Definitions Data model
A formal way of representing the data that are used and created by a business system
Shows the people, places and things about which data is captured and the relationships among them.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

4. Key Definitions Logical data model Physical data model
shows the organization of data without indicating how it is stored, created, or manipulated.
Physical data model
shows how the data will actually be stored in databases or files.
Normalization is the process analysts use to validate data models.
Data models should balance with process models (data model  process model)
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

5. THE ENTITY-RELATIONSHIP DIAGRAM (ERD)
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

6. What Is an ERD?
A picture showing the information created, stored, and used by a business system.
Entities generally represent similar kinds of information
Lines drawn between entities show relationships among the data
High level business rules are also shown, e.g:
“a patient can schedule many appointments”
“a person must make at least one appointment before he/she is considered a patient”
Business rules are constraints that are followed when the system is in operation.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

7. Using the ERD to Show Business Rules
ERD symbols can show when one instance of an entity must exist for an instance of another to exist
A doctor must exist before appointments the doctor can be made
ERD symbols can show when one instance of an entity can be related to only one or many instances of another entity
One doctor can have many patients; each patient may have only one primary doctor
ERD symbols show when the existence of an entity instance is optional for a related entity instance
A patient may or may not have insurance coverage
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

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

9. CREATING AN ENTITY-RELATIONSHIP DIAGRAM (ERD)
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

10. ERD Basics
Drawing the ERD is an iterative process of trial and revision
ERDs can become quite complex
Steps in building ERD:
Identify the entities
Add appropriate attributes for each entity
Draw the relationships that connect associated entities
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

11. Step 1: Identify the Entities
Identify major categories of information
If available, check the process models for data stores, external entities, and data flows
Check the major inputs and outputs from the use cases
Verify that there is more than one instance of the entity that occurs in the system
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

12. Step 2: Add Appropriate Attributes
Identify attributes of the entity that are relevant to the system under development
Check the process model repository entries for details on data flows and data stores
Check the data requirements of the requirements definition
Interview knowledgeable users
Perform document analysis on existing forms and reports
Select the entity’s identifier
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

13. Step 3: Draw the Relationships
Start with an entity and identify all entities with which it shares relationships
Describe the relationship with the appropriate verb phrase
Determine the cardinality and modality by discussing the business rules with knowledgeable users
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

14. An ERD Example relationship entity identifier
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

15. Reading ERD
DOCTOR is scheduled for APPOINTMENT, APPOINTMENT includes DOCTOR
PATIENT schedules APPOINTMENT, APPOINTMENT is scheduled by PATIENT
APPOINTMENT generates BILL, BILL is generated by APPOINTMENT
PATIENT makes PAYMENT, PAYMENT is made by PATIENT
INSURANCE COMPANY insures PATIENT, PATIENT is insured by INSURANCE COMPANY
INSURANCE COMPANY makes PAYMENT, PAYMENT is made by INSURANCE COMPANY
BILL is paid by PAYMENT, PAYMENT pays BILL
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

16. Entity A person, place, event, or thing about which data is collected
Must be multiple occurrences to be an entity
Example: If a firm has only one warehouse, the warehouse is not an entity. However, if the firm has several warehouses, the warehouse could be an entity if the firm wants to store data about each warehouse instance.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

17. Attributes Information captured about an entity
Entity name
Information captured about an entity
Only those used by the organization should be included in the model
Attribute names are nouns
Sometimes entity name is added at the beginning of the attribute name for clarity, example:
Entity : Patient
Attribute: Patient_name
Patient_ID
attribute
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

18. Identifiers
One or more attributes can serve as the entity identifier, uniquely identifying each entity instance
Concatenated identifier consists of several attributes
An identifier may be ‘artificial,’ such as creating an ID number
Identifiers may not be developed until the Design Phase – to be added later
identifier
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

19. Relationships Associations between entities
The first entity in the relationship is the parent entity; the second entity in the relationship is the child entity
Relationships should have active verb names
Relationships go in both directions
child
parent
parent
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

20. Entity
Entity type – A collection of entities that share common properties or characteristics
Type Entity
Example
People
STAF, PELAJAR, PENSYARAH, PATIENT
Place
DAERAH, BANDAR, NEGERI, STORE
Object/Thing
Event
Concept
BANGUNAN, PERALATAN, PRODUCT
KURSUS, AKAUN, APPOINTMENT, BILL
PENDAFTARAN, PERMOHONAN, ORDER
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2nd Edition
Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.

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

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

23. 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.

24. 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.

25. 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.

26. 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.

27. 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.

28. 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.

29. 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.

30. 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.

31. 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.

32. 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.

33. 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.

34. 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.

35. 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.

36. 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.

37. 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.

38. 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.

39. 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.

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