3 - Etwrf

UNIT 1: Fundamentals of Database Systems
UNIT
0 THE ENHANCED ENTITY

RELATIONSHIP MODEL
3
Unit 3 introduces the extension of the basic
Entity-Relationship Diagram (ERD). This unit
introduces new notation, the supertype/subtype
relationship, to best represent the increasing
complexity of computing world. The discussion
includes the methods on creating the
supertype/subtype relationship, EERD constraints
and the subtype discriminator used in both disjoint
and overlap rules.
IT 202: INFORMATION MANAGEMENT 98

PRETEST
WHAT DO YOU ALREADY KNOW?
Name: __________________________________ Date: ____________________

Course & Section: ________________________ Result: __________________
I. Multiple Choice. Encircle the LETTER of the best answer.
1. It specifies that every entity instance of the supertype must be a member

of at least one subtype.
A. Overlap Rule B. Total Specialization Rule
C. Disjoint Rule D. Partial Specialization Rule
2. It specifies that an entity instance of a supertype is allowed to be a

member of more than one subtype simultaneously.
3. It means that the attribute of the supertype is automatically attributes of its

subtypes.
A. Generalization B. Specialization
C. Attribute inheritance D. Attribute acceptance
4. It is an attribute of the supertype whose values determine the target

subtype(s).
A. Subtype B. Supertype
C. Subtype Discriminator D. Entity Cluster
5. It refers to the sub-groupings of entity types.


PRETEST
WHAT DO YOU ALREADY KNOW?
Name: __________________________________ Date: ____________________

Course & Section: ________________________ Result: __________________
6. It specifies that an entity instance of the supertype is allowed not to belong

to any subtype.
7. It refers to a generic or general entity type.

8. It is a process of creating a general entity type from specialized entities.

9. It is a process specialized entities from a more general entity type.

10. It states that an instance of the supertype is required to be part of one or

more subtypes.
A. Partial completeness constraint B. Total completeness constraint
C. Disjointness constraint D. Overlap constraint

LESSON 1:
THE SUPERTYPE/SUBTYPE NOTATION
OBJECTIVES:
At the end of this lesson, the student will be able to:
▪ Define the Enhanced Entity-Relationship (EER) model, supertype,

subtype, and attribute inheritance.
▪ Determine when to use supertype/subtype relationships in data

modeling.
▪ Identify the difference in connecting the relationship to supertype

and subtype.
Duration: 2 hours

Enhanced Entity Relationship Model
The enhanced entity-relationship model (EERD), otherwise known as the

extended entity-relationship model, is the result of extending the original E-R model's
functionality by incorporating new modeling construct. The supertype/subtype
relationship is an essential concept added to the ER model as a response to the
increasing need to capture more information due to the more complex application
software requirements of application software. The supertype/subtype notation
allows us to model a more general entity type and show its sub-components, the
subtypes (Hoffer, Ramesh, & Topi, 2016).
The supertype is a generic type that has at least two subtypes. A subtype is a
subgrouping of the entities that are valuable to the organization. The subtypes share
common attributes, but each subtype possesses attributes or relationships distinct
from other subgroupings.
The supertype/subtype notation depicts the parent-child relationship. In the

context of entity-relationship diagraming, the supertype contains the shared
attributes, while the subtype includes unique attributes. Figure 3.1 illustrates
examples of the supertype/subtype.
Supertype PERSON
STUDENT
Supertype/Subtype EMPLOYEE
Subtype
UNDERGRADUATE_ GRADUATE_STUDENT
ACADEMIC ADMINISTRATOR
STUDENT
Figure 3.1. Illustration of the Supertype/Subtype Notation
Figure 3.1 shows the subgroupings of persons in a typical university set-up.

In the model, the PERSON entity type is considered a supertype, and its subtypes
are EMPLOYEE and STUDENT entity types. Notice that the EMPLOYEE entity
type acts as one of the subtypes of supertype PERSON; however, in relation to
ACADEMIC and ADMINISTRATOR entity types, it is considered a supertype.
Similarly, the STUDENT entity type is a supertype in relation to its subtype entities
UDERGRADUATE_STUDENT and GRADUATE_STUDENT.

BASIC NOTATION OF SUPERTYPE / SUBTYPES

The basic notation of the supertype/subtype relationship in the traditional EER
notation is shown in figure 3.2.
Figure 3.2. Basic Notation for Supertype/Subtype Relationships in EER Notation

Source: Hoffer, J., Ramesh, V., & Topi, H. (2016) Modern Database Management, 12th Edition - Chap3 (p.116)
Pearson Prentice Hall
In the EER notation, we illustrate a supertype/subtype relationship by drawing

a line leading from the supertype to the circle. Another line from the circle leading to
each subtype defined. The U-shaped symbol added on each line connecting a
subtype to the circle emphasizes that the subtype is a supertype subset. It also
indicates the direction of the subtype/supertype relationship. However, since the
meaning and direction of the supertype/subtype relationship is typically obvious, the
U notation is optional. Figure 3.3 shows a real-world example of a supertype/subtype
relationship.
Figure 3.3. Example of Supertype/Subtype Relationship

As shown in figure 3.3, the supertype is the FACULTY entity type where the
attributes common to all subtypes (EmpName, BirthDate, HireDate, Address, and
ContactNo), including the identifier (Emp_ID), are placed in the supertype. On the
other hand, each subtype contains the attributes distinct only to it. Such that both
BasicSalary and RatePerHour are attributes particular to REGULAR_FACULTY,
RatePerHour is for PARTTIME_FACULTY, and ProfessionalFee is the distinctive
attribute of the GUEST_LECTURER.
In the EER notation, there is a concept known as attribute inheritance, where

all of its subtypes inherit all the supertype attributes. This means that aside from the
BasicSalary and RatePerHour, the attributes Emp_ID, EmpName, BirthDate,
HireDate, Address, and ContactNo are also attributes of the REGULAR_FACULTY
subtype. Besides, all instances of the subtypes are also considered instances of the
supertype entity. This means that if a concept is an instance of, let's say
REGULAR_FACULTY subtype; it is also considered an instance of the FACULTY
supertype.
When to use supertype/subtype?
The supertype/subtype notation may not always require in all ER diagraming

endeavors. Consider using this notation only when either or both condition exists:
• When there are attributes that are applicable only to some, but not all, of the
instances of an entity type; and
• When there is a relationship participated only by some, but not all, of the
instances of an entity type
RELATIONSHIPS AND SUBTYPES

The relationships in the EERD notation can be connected in the supertype
and in the individual subtype. Figure 3.3 shows an example of a relationship
connected to Supertype and Subtype.
Figure 3.4. Example of Relationship connected to Supertype and Subtype

Relationships at the supertype level indicate that all subtypes will participate
in the relationship. In figure 3.4, both the undergraduate and graduate students take
a program.
On the other hand, the relationship may be connected to the subtype level; as
such, only the instances of a subtype where the relationship is associated may
participate in a given relationship unique to that subtype. In the example, only the
undergraduate students may join in clubs

ACTIVITY FOR LESSON 1
WHAT HAVE YOU LEARNED?
Name: _______________________________ Date: _______________________

Course & Section: _____________________ Result: _____________________
I. Given the narrative, draw the equivalent EERD.

Different types of persons for its outreach projects support a local government
unit (LGU). The LGU is interested in the following attributes: CitizenNumber, Name,
Address (components: Barangay/City/Province/ZipCode), and ContactNumber.
There are three types of persons the LGU is interested most: employees, club
officers, and donors. Employees have distinct attribute EmployerCode while club
officers provide club affiliation information. Donors only have a relationship (named
Donates) with an ITEM entity type. A donor must have donated one or more items,
and an item may have no donors or one or more donors. The LGU records the date
when a donor donates an item. It also records in the donor’s table the date when the
donor first donates an item.

GRADING RUBRICS
HOW WELL DID YOU PERFORM?
Name: _______________________________ Date: _______________________

Rubrics:
Weight Actual
No. Items
Score
1. The list and representation of the attributes in the
4
supertype is complete and correct.
2. The identification of the distinct attribute in each

3
subtype is proper and concise.
3. The connection of the relationship is properly

2
identified.
4. The relationship label is consistent with the design

2
standard.
5. The cardinality of the relationship identified on both

sides is correct and reflects deep understanding of 4
ERD and EERD.
6 The representation of the connected entity and its

attributes is correct and consistent with the design 5
standard.

LESSON 2:
METHODS IN DEVELOPING SUPERTYPE/SUBTYPE
RELATIONSHIPS GENERALIZATION AND
OBJECTIVES:
▪ Illustrate the Generalization process.
▪ Illustrate the Specialization process.
▪ Determine the difference between generalization and specialization

process.
Duration: 2 hours

Methods in Developing Supertype/Subtype Relationship
In real-world modeling objects, we often come up with a list of entities.

However, as we do further analysis, we recognize the opportunity to exploit the
supertype/subtype relationships. The generalization and specialization are the
methods we can use to develop the supertype/subtype relationships.
Generalization
Generalization is a process of identifying the common attributes from a set of

entities and creating a generalized entity. Two or more entity types can be
generalized if there are attributes common to them; that is why the generalization
process is considered a bottom-up approach. Figures 3.5 and 3.6 illustrate the
generalization process.
Figure 3.5. Example of Entities with Common Attributes
Figure 3.6. Generalized Citizen Entity Type
Figure 3.5 shows three entities with common attributes, which are CitizenID,
EmpName, BirthDate, and Address. Figure 3.6 shows the generalized attribute
CITIZEN. The supertype holds the attributes shared or common to all entities, while
those distinct to each entity remain to the individual subtype. SELF_EMPLOYED
entity does not have a distinctive attribute; thus, it is not anymore model in the
EERD.
Specialization
Specialization is a process of dividing an entity type into two or more sub-

entities due to two primary reasons. First, some attributes apply to some, but not to
all instances of the entity type. Second, some relationships are participated in by
some, but not to all instances of the entity type. Specialization thus is considered a
top-down process. Figures 3.7 and 3.8 illustrate the specialization process.
Figure 3.7. Student Entity Type
Figure 3.8. Specialized Graduate and Undergraduate Students
Figure 3.7 shows an example of an entity type student. As we perform further

analysis, and probably after trying to insert some possible values, we noticed several
observations. The Bachelor's degree and year graduated do not apply to students
who are currently taking up a program; however, they are applicable to those who
are pursuing higher knowledge, which we called graduate students. On the other
hand, career track and club affiliation (assuming these assumptions will continue in
the future) are not appropriate for graduate students but are distinct to the

undergraduate student. To control the nulls in our database, the student entity
should be sub-divided into graduate and undergraduate students. The process we
perform is specialization.
Differences between Generalization and Specialization
Table 3.1 illustrates the primary differences between generalization and

specialization (Yambadwar, 2020).
Table 3.1. Differences between Generalization and Specialization

Source: Yambadwar, S. (2020). Difference between Generalization and Specialization in DBMS [Web log post]. Retrieved 2020, from
https://www.geeksforgeeks.org/difference-between-generalization-and-specialization-in-dbms/
Table 3.1 shows a summary of the characteristics of both the generalization

and the specialization. Although generalization and specialization are two different
methods, they are both essential techniques in developing supertype/subtype
relationships. The question of which method is better depends on the problem
domain and, most of the time, personal preference.

Name: _______________________________ Date: _______________________

I. Provide what is required.
1. Think of at least three entity types with common attributes similar to figure 3.5
and create specialized attribute to form the supertype/subtype relationship such
as in figure 3.6.
ANSWER:
2. Think of one entity types where you can apply the specialization process to
come up with the supertype/subtype relationship similar to figure 3.8.
ANSWER:

GRADING RUBRICS
Name: _______________________________ Date: _______________________

Rubrics:
Weight Actual
No. Items
Score
1. The attributes identified for each entity type are
5
realistic and consistent with the design standard.
2. Entities (with common attributes) identified reflect

5
profound understanding of the topic on generalization.
3. The design of supertype/subtype relationship is

5
correct and consistent with the design standard.
4. Process done to identify the subtypes while applying

5
specialization is reliable and satisfactory.

LESSON 3:
CONSTRAINTS IN
SUPERTYPE/SUBTYPE RELATIONSHIPS
OBJECTIVES:
▪ Determine the primary constraints in a supertype/subtype

relationship.
▪ Differentiate total from partial specialization constraint.
▪ Differentiate the disjoint from the overlapping rule.
IT 202: INFORMATION MANAGEMENT Duration: 1.5 hours 114

Constraints Supertype/Subtype Relationship

The constraint in the supertype/subtype relationship is essential to capture
some of the critical business rules deemed necessary in the relationships. The
completeness and disjointness constraints are among the most vital constraint we
will discuss in this section.
Completeness Constraints
Completeness constraints address whether an instance of a supertype is
required to be a member of at least one subtype. The completeness constraint may
be total or partial.
Total Completeness Rule
The total completeness rule, also known as total specialization rule, specifies
that each occurrence of an entity in the supertype must be a member of a subtype or
more. To denote the total completeness rule, we create a double line from the
supertype to the circle. Figure 3.9 shows an example of a total completeness rule.
Total Specialization
(Double Line)
Figure 3.9. Example of a Total Completeness Rule
Figure 3.9 shows an example of the total completeness rule. The diagram clearly
informs us that there are no other kinds of faculty except regular faculty, part time
faculty and guest lecturer.
Partial Completeness Rule
The partial completeness rule, also known as partial specialization rule,

specifies that the occurrence of an entity in the supertype is not required to be a
member or part of the subtype identified under it. To denote the partial completeness

rule, we create a single line from the supertype to the circle. Figure 3.10 shows an
example of a partial completeness rule.
Partial Specialization
(Single Line)
Figure 3.10. Example of a Partial Completeness Rule
Figure 3.10 shows an example of a partial completeness rule. The diagram

tells us that there are still other kinds of citizens aside from those who are employed
in the government or a private institution such as in our example in figure 3.5. Self-
employed citizens are neither government nor privately employed citizens, but can
still be considered a citizen.
Disjointness Constraints
Disjointness constraints address whether an instance of a supertype is
allowed to be a member of more than one subtype simultaneously. The disjointness
constraint may be overlap or disjoint.
Disjoint Rule
The disjoint rule does not allow overlapping subtypes; thus, it specifies that an
instance of the supertype may only exist as one of the subtypes. A small letter "d" is
placed inside the circle to denote that the constraint exists is disjoint. Figure 3.11
shows an example of a disjoint rule.
Disjoint Rule
(small letter “d”)

Figure 3.11. Example of a Disjoint Rule
Figure 3.11 tells us that an occurrence of a faculty instance should either be

regular, part-time, or guest lecturer but should not be part of two out of three or all of
the subtypes simultaneously.
Overlap Rule
The overlap rule allows the overlapping subtypes; thus, it specifies that an
instance of the supertype may be part of more than one subtypes simultaneously. A
small letter “o" is placed inside the circle to denote that the constraint exists is
overlap. Figure 3.12 shows an example of a disjoint rule.
Overlap Rule
(small letter “o”)
Figure 3.12. Example of an Overlap Rule
Figure 3.12 tells us that an employee instance should any of the following:
administrator, academic, or non-academic employee. Also, the employee instance is
allowed to be part of more than two subtypes. For example, an employee is both an
administrator at the same time an academic employee if he or she is teaching a
course and, at the same time, holding a position such as a department director.

Name: _______________________________ Date: _______________________

I. Given the narratives, draw the equivalent EERD.

Different types of persons for its outreach projects support a local
government unit (LGU). The LGU is interested in the types of persons: employees,
club officers, and donors. Draw a different EER diagram segment for each of the
following situations:
a. At a given time, a person must be exactly one of these subtypes.
ANSWER:
b. A person may or may not be one of these subtypes. At the same time, a
person who is one of these subtypes can also be one of the other subtypes
simultaneously.
ANSWER:

GRADING RUBRICS
Name: _______________________________ Date: _______________________

Rubrics:
Weight Actual
No. Items
Score
1. The completeness constraint identified is correct and
4
consistent with the design standard.
2. The disjointness constraint identified is correct and

4
consistent with the design standard
3. Proper naming of ERD components is precise and

reflects profound understanding of the topic on EERD 2
and its constraints.

LESSON 4:
SUBTYPE DISCRIMINATORS
OBJECTIVES:
▪ Define subtype discriminator.
▪ Model the subtype discriminator for the disjoint rule.
▪ Model the subtype discriminator for overlap rule.

Duration: 1.5 hours
Subtype Discriminator
Subtype discriminator is an attribute added to the supertype whose values
determine which subtype a particular entity instance is connected.
Subtype Discriminator for Disjoint Rule

The subtype discriminator for the disjoint rule is a simple attribute with
alternative values to indicate the possible subtypes. Figure 3.13 shows how to use
subtype discriminator for the disjoint rule.
(simple attribute)
Figure 3.13. Example of a Subtype Discriminator for Disjoint Rule
Figure 3.13 shows an example of how to use a subtype discriminator. The

total specialization and disjoint rules are implemented in the diagram. Thus, each
student should be either undergraduate or graduate.
In the supertype student, a new attribute, StudentType is added to serve as a

subtype discriminator. When a new instance of the student is inserted, this attribute
is coded with either of the two values: “U” for undergraduate and “G” for graduate
students. The expression “StudentType =” is placed next to the line leading from the
supertype to the circle. The value of the attribute that selects the appropriate subtype
is placed adjacent to the line leading to that subtype. In our example, either “U” or
”G." Thus, for example, the condition StudentType=“U” causes an entity instance to
be inserted into the UNDERGRADUATE subtype.
Subtype Discriminator for Overlapping Rule

The subtype discriminator for the overlap rule is a composite attribute with
component parts that indicate the possible subtypes an instance of the supertype
belong. Figure 3.14 shows how to use subtype discriminator for the overlap rule.
(composite attribute)
Figure 3.14. Example of a Subtype Discriminator for Overlap Rule
An example, EMPLOYEE supertype with its overlapping subtypes implements

a subtype discriminator for overlap rule as shown in figure 3.14. Added to the
supertype attributes is composite attribute EmployeeType with component parts
Administrator?, Academic?, and Non_Academic?. Each of the EmployeeType
component is a Boolean variable that will only accept either “Y” for yes or “N” for no.
When a new instance is added to EMPLOYEE, these components are coded as
follows:
Table 3.2. Value of the subtype discriminator fro overlap rule with description
Administrator? Academic? Non-Academic? Type of Employee

“Y” “N” “N” Administrator only
“N” “Y” “N” Academic employee only
“N” “N” “Y” Non Academic employee only
“Y” “Y” “N” Academic and Administrator
“Y” “N” “Y” Non Academic and Administrator

Name: _______________________________ Date: _______________________

I. Draw the equivalent EERD describe in the narrative. Show all the
constraints needed. Make sure to add the appropriate subtype
discriminator.
Different types of persons for its outreach projects support a local government
unit (LGU). The LGU is interested in the following attributes: CitizenNumber, Name,
Address (components: Barangay/City/Province/ZipCode), and ContactNumber.
There are three types of persons the LGU is interested most: employees, club
officers, and donors. Employees have distinct attribute EmployerCode while club
officers provide club affiliation information. Donors only have a relationship (named
Donates) with an ITEM entity type. A donor must have donated one or more items,
and an item may have no donors or one or more donors. The LGU records the date
when a donor donates an item. It also records in the donor’s table the date when the
donor first donates an item.
There are persons other than described above, so that a person need not
belong to any of these three groups. On the other hand, at a given time a person
may belong to two or more of these groups.
ANSWER:

GRADING RUBRICS
Name: _______________________________ Date: _______________________

Rubrics:
Weight Actual
No. Items
Score
1. The list and representation of the attributes in the
5
supertype and subtypes is complete and correct.
2. The label and cardinality of the relationship follows the

4
correct format.
3. The completeness constraint is correct. 2
4. The disjointness constraint is correct. 2
5. The representation of subtype discriminator is

5
complete and correct
6 Proper naming of ERD components is precise. 2

Bulacan State University

Admission Test System
(Sample Case)
As a university offering various fields of discipline, the Bulacan State

University may accept admission of different kinds of examinees. There are
basically three groups of examinees (only college level is considered) that may be
identified: the freshmen, shifters and transferees. The examinee number, name,
address and contact number may be some of the common attributes present in all
kinds of examinees.
On the other hand, each of the three groups of examinee has at least one
attribute peculiar only to the group. The freshmen have highschool average grade
and honor received. Shifters has previous course attended and transferees has
school last attended.
Every examinee are categorize as any one of the three examinee groups
given. Aside from that it should be understood that an examinee must belong to one
(and only one) kind of examinee group.

LEARNING INSIGHTS/REFLECTIONS
Name: _______________________________ Date: _______________________

After working on the lessons under Unit 3 The Enhanced Entity

Relationship Diagram (EERD), in 1 to 2 paragraph, write your insight about
the things that you have learned. Write as well the topics that still need
clarifications.
Write your answer below:

POST-TEST FOR UNIT 1
HOW MUCH HAVE YOU LEARNED?

Name: _______________________________ Date: _______________________
Identification. Write the correct answer on the space provided.
1. It is a process of creating a general entity type from
specialized entities.
2. It is a process specialized entities from a more general

entity type.
3. It states that an instance of the supertype is required to

be part of one or more subtypes.
4. It specifies that every entity instance of the supertype

must be a member of at least one subtype.
5. It specifies that an entity instance of a supertype is

allowed to be a member of more than one subtype
simultaneously.
6. It means that the attribute of the supertype is

automatically attributes of its subtypes.
7. It is an attribute of the supertype whose values determine

the target subtype(s).
8. It refers to the sub-groupings of entity types.
9. It specifies that an entity instance of the supertype is

allowed not to belong to any subtype.
10. It refers to a generic or general entity type.


3 - Etwrf

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

3 - Etwrf

Uploaded by

Copyright:

Available Formats

UNIT 1: Fundamentals of Database Systems

0 THE ENHANCED ENTITY

IT 202: INFORMATION MANAGEMENT 98

WHAT DO YOU ALREADY KNOW?

Name: __________________________________ Date: ____________________

I. Multiple Choice. Encircle the LETTER of the best answer.

1. It specifies that every entity instance of the supertype must be a member

2. It specifies that an entity instance of a supertype is allowed to be a

3. It means that the attribute of the supertype is automatically attributes of its

4. It is an attribute of the supertype whose values determine the target

5. It refers to the sub-groupings of entity types.

IT 202: INFORMATION MANAGEMENT 99

WHAT DO YOU ALREADY KNOW?

Name: __________________________________ Date: ____________________

6. It specifies that an entity instance of the supertype is allowed not to belong

7. It refers to a generic or general entity type.

8. It is a process of creating a general entity type from specialized entities.

9. It is a process specialized entities from a more general entity type.

10. It states that an instance of the supertype is required to be part of one or

IT 202: INFORMATION MANAGEMENT 100

▪ Define the Enhanced Entity-Relationship (EER) model, supertype,

▪ Determine when to use supertype/subtype relationships in data

▪ Identify the difference in connecting the relationship to supertype

IT 202: INFORMATION MANAGEMENT 101

Enhanced Entity Relationship Model

The enhanced entity-relationship model (EERD), otherwise known as the

The supertype/subtype notation depicts the parent-child relationship. In the

Figure 3.1. Illustration of the Supertype/Subtype Notation

Figure 3.1 shows the subgroupings of persons in a typical university set-up.

IT 202: INFORMATION MANAGEMENT 102

BASIC NOTATION OF SUPERTYPE / SUBTYPES

Figure 3.2. Basic Notation for Supertype/Subtype Relationships in EER Notation

In the EER notation, we illustrate a supertype/subtype relationship by drawing

Figure 3.3. Example of Supertype/Subtype Relationship

IT 202: INFORMATION MANAGEMENT 103

In the EER notation, there is a concept known as attribute inheritance, where

When to use supertype/subtype?

The supertype/subtype notation may not always require in all ER diagraming

RELATIONSHIPS AND SUBTYPES

Figure 3.4. Example of Relationship connected to Supertype and Subtype

IT 202: INFORMATION MANAGEMENT 105

ACTIVITY FOR LESSON 1

WHAT HAVE YOU LEARNED?

Name: _______________________________ Date: _______________________

I. Given the narrative, draw the equivalent EERD.

IT 202: INFORMATION MANAGEMENT 106

HOW WELL DID YOU PERFORM?

Name: _______________________________ Date: _______________________

2. The identification of the distinct attribute in each

3. The connection of the relationship is properly

4. The relationship label is consistent with the design

5. The cardinality of the relationship identified on both

6 The representation of the connected entity and its

IT 202: INFORMATION MANAGEMENT 107

At the end of this lesson, the student will be able to:

▪ Illustrate the Generalization process.

▪ Illustrate the Specialization process.

▪ Determine the difference between generalization and specialization

IT 202: INFORMATION MANAGEMENT 108

Methods in Developing Supertype/Subtype Relationship

In real-world modeling objects, we often come up with a list of entities.

Generalization is a process of identifying the common attributes from a set of

Figure 3.5. Example of Entities with Common Attributes

Name: ______________ Date:

Name: ______________ Date:

Name: _________ Date: _

Name: _________ Date: _

Name: _________ Date: _

Name: _________ Date: _

Name: _________ Date: _

Name: _________ Date: _

Name: _________ Date: _