4 Hafta

Introduction to
System Analysis
Week 4 – Entity Modelling & Entity Relationship
Diagrams
Assis. Prof. Dr. Zeynep İdil ERZURUM ÇİÇEK
1
Content
• Entity Modelling
• Entity Relationship Diagrams
2
(Structured System Analysis & Design
Methodology - SSADM)
Data Flow Diagrams (DFD)
• DFDs show the processes, or functions, involved in a system.
• They don’t tell us much about the structure of the data.
3
Entity Modelling
• Entity Models
– Real data
– How the data connected?
4
Entities
• things we might want to keep information about
– People like CUSTOMER
– Objects like PRODUCT
5
Is it an «entity»?
1. An entity must be important to the organization.
2. An entity must have at least one attribute
3. An entity must occur more than once
4. Each entity occurrence must be uniquely identifiable
MEMBER Membership number

RECIPE Recipe number
6
Representation form for entitites
• rectangles with rounded corners in Entity Models
• The name of the entity is always singular!!
• RECEIPT
• DRINK
• PATIENT
7
Attribute
Attributes are bits of data associated with the entity
Entity: MEMBER
Attributes:
– Member Name
– Membership Number
– Member Address
– Date of Birth
– Type
– Seconder
– Renewal Date
8
Attribute
• An employee of an organization is an entity.
• If “Peter” is a programmer (an employee) at Microsoft, he can
have attributes (properties) like name, age, weight, height, etc.
9
A full membership record
10
Keys
A key is a way of identifying something
My key: Zeynep Çiçek (It’s how other people identify me)

• Brilliant ??
Zeynep Çiçek (Asiss. Prof. Dr. Eskisehir Teknichal University)
Zeynep Çiçek (X Bank)
Zeynep Çiçek (Dr. Y Hospital)
t.r. identity number 11

Keys
• An entity is made up of a number of attributes. To identify
that entity, we need a key.
• Unique...primary key
– it’s made up of just one attribute.
Member Name + Member addresss Membership number
Composite key Primary key

12
Relationships
• Entities have relationships with other entities
13
Relationships
• The entities are joined together by a verb which describes
the relationship between them.
• In an entity model, related entities are joined by a line
14
Relationships types
• one-to-one (1:1)
• one-to-many (1:M)
• many-to-many (M:N)
15
Relation types
• one-to-one (1:1)
16
Relation types
17
Relation types
18
Relation types
• many-to-many (M:N)
19
M:M
many-to-many (M:M)
20
M:M
•Sadly, many-to- many relationships are

not good for databases. They cannot be
implemented effectively.
•So many-to-many relationships have to
be resolved.
21
Resolving many-to-many relationships
1. Find a link entity
• we have to split many-to-

many relationships into two
one-to-many relationships.
• This requires us to find a
link entity which is a single
occurrence of the many-to-
many relationship.
22
2. Consider the attributes
• When we create a new link

entity in this way, we need to
consider which attributes will
make up the new entity.
• There will be one or two from
the original two entities, but
there may be some completely
new ones.
23
Foreign key
24
Simple steps in entity modelling
1. List the possible entities.
2. Check that the entities listed are really entities.
3. Draw a basic entity model, with boxes around the entities.
4. Identify which entities are related. Draw a line between them.
5. Give the relationship a name in each direction.
25
Simple steps in entity modelling
6. Identify the relationship type.

(1:1, 1:M or M:N)
7. Resolve any one-to-one relationships.
8. Resolve any many-to-many relationships.
Add in link entities.
9. Add the attributes, including primary keys and foreign keys.
26
Resolution and naming the relationships
27
Entity Modelling
• The systems analyst will need to communicate regularly with
the user
• during this process in order to check that all necessary
entities have been identified and that the relationships are
accurate.
28
CASE: Entity modelling at
Swillbuckets
29
Case: Swillbuckets
It is a club for the people of West Yorkshire.

1. There is an entertainment at each weekend.
2. The entertainments are booked by Jack Trout, the
Swillbuckets Secretary.
30
Case: Swillbuckets
Jack’s tasks are: booking the artistes, enrolling
new members, producing pay slips to pay the acts,
advertising future events and chasing up
subscriptions. Sometimes choosing the meat
dishes at the events.
31
Case: Swillbuckets
The problem background:
• Two or three shoeboxes for the card to keep the

information about members and artistes.
• Jack should open more shoeboxes or go computerized.
• Amanda Stone (assistant) helps Jack to collect the
subscriptions.
32
Case: Swillbuckets
• Jack checks all the entire shoeboxes to determine the

express dates of memberships’s subscriptions.
• Jack produces a monthly forthcoming events to send
them to a local media.
33
Case: Swillbuckets
• Jack gives orders for meal. But it is a surprise that the

supplier will give what kind of meat. So Jack has no real idea
what is in stock at any given time.Also the payment is made
with cash.
• This makes life difficult for freedom, the chef. Often the
menu has to be rewritten at the last minute.
• Fortunately, the local brewery, Cooper’s , is particularly
diligent when it comes to paperwork and deliveries are
punctual.
34
Case: Swillbuckets
After data flow modelling…
«Entity modelling»
35
CASE: Entity modelling at Swillbuckets
1.List the possible entities.
• An entity must be important to the
ARTISTE EVENT MEMBER organization.
• An entity must have at least one attribute.
• An entity must occur more than once.
DISH BREWERY DRINK • Each entity occurrence must be uniquely
identifiable.
RECIPE
SUPPLIER MEDIA
36
2.Check that the entities are really entities.
37
3. Draw the basic entity model
there may be more

entities to come when
we show the user our
entity model.
38
4. Identify the relationships.
ARTISTEs attend EVENTs
MEMBERs attend EVENTs
EVENTs provides DISHes
DISHes require RECIPEs
SUPPLIERs supply DRINKs
MEDIA cover EVENTs

39
4. Identify the relationships.
40
Swillbuckets
5. Give the relationships
a name, in each
direction!!
41
Swillbuckets
6. Identify the type of
relationship.
each EVENT will only ever offer one
dish (in order to keep Freddo Smitho
just the right side of sane) and each
dish will be offered at many EVENTs.
each RECIPE could require many

FOOD ORDERs and each FOOD
ORDER could be required for many
RECIPES.
42
7. Resolve any one-to-one relationships.
43
Find a link entity
44
45
9 Add the attributes and keys.
• Primary keys are underlined.
• Attribute names have been condensed into one word with no spaces –
– spaces can cause problems in some systems. Capital letters are used
to denote a new word in the name.
• An asterisk denotes a foreign key –
– an attribute which acts as a link to another entity by appearing in both. It’s a
primary key in one entity but not in the other.
• Address attributes are shown as just one attribute, but in reality they are
– usually made up of a number of attributes e.g. Street, Town, County,
Postcode.
46
47
Physical data store/entity cross-reference
1 List all the data stores, by checking the current
physical DFD
• M1 Membership shoebox
• M2 Artiste shoebox
• M3 Supplier shoebox
• M4 Events folder
• M5 Recipe book
48
2 Cross reference each data
store with corresponding
entities from the entity
model.
A data store can have more
than one entity
49
3 Check that each data store has at least one
entity.
4 Check that each entity is stored in a data store.
• We note that the entities EVENT TICKET and MEDIA
do not have data stores. The fact that EVENT TICKET
does not have a data store is expected.
50

4 Hafta

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4 Hafta

Uploaded by

Copyright:

Available Formats

Introduction to

Assis. Prof. Dr. Zeynep İdil ERZURUM ÇİÇEK

MEMBER Membership number

My key: Zeynep Çiçek (It’s how other people identify me)

t.r. identity number 11

– it’s made up of just one attribute.

Member Name + Member addresss Membership number

Composite key Primary key

•Sadly, many-to- many relationships are

• we have to split many-to-

• When we create a new link

6. Identify the relationship type.

It is a club for the people of West Yorkshire.

• Two or three shoeboxes for the card to keep the

• Jack checks all the entire shoeboxes to determine the

• Jack gives orders for meal. But it is a surprise that the

there may be more

MEMBERs attend EVENTs

EVENTs provides DISHes

DISHes require RECIPEs

SUPPLIERs supply DRINKs

MEDIA cover EVENTs

each RECIPE could require many

Find a link entity

You might also like