Institute of Southern Punjab
Department of Computer Science & IT
Theory Assignment - Top Sheet
Class Section Semester
Student’s Registration Number
B THIRD
ADPCS-023A21-17 ADP-CS
Course Title Course Code
DATABASE SYSTEM
Student's Full Name
USAMA AHMAD
Assign Date: Submission Deadline:
04-11-2022 13-11-2022
Course Teacher Name
SIR NOUMAN FAROOQ
Class Assignment No. Assignment Details: CLO/PLO
Institute of Southern Punjab
Department of Computer Science & IT
2 Part 1
Classify the following attributes of an Entity type EMPLOYEE
(CLO 3) (PLO 3)
EmployeeId
EmployeeHobby
EmployeePassword
Part 2
Design/Draw an ERD in Information Engineering Style as per
Conceptual Data Modeling of the following above Entity type along with
the given Attributes in Part 1. (CLO 3) (PLO 3)
Part 3
Is it possible to further transform the following abovecreated ERD in
Part 2 as per Logical Data Modeling?
If Yes; Than Design a transformed ERD in Information Engineering
Standard.
(PLO 3)
Instructions to Student:
Please Note: Work presented in an assessment must be your own. Plagiarism is where a
student copies work from another source, published or unpublished (including the work of
another student) and fails to acknowledge the influence of another’s work or to attribute
quotes to the author. Plagiarism is an academic offence and the penalty can be serious. To
detect possible plagiarism we may submit your work to the national plagiarism detection
facility. This searches the Internet and an extensive database of reference material including
other students’ work to identify.
I have read the above information and I confirm that this work is my own and
that it may be processed and stored in the manner described.
Signature:.................................................................... Date: .................................................................
Please leave sufficient time to meet the given deadline and do not leave the handing-in of assignments to the last
inute. You are being allowed meaningfull time for any system problems or other issues.
Part 1
Institute of Southern Punjab
Department of Computer Science & IT
Classify the following attributes of an Entity type EMPLOYEE
ANSWER
Attributes in ER Diagram-
Attributes are the descriptive properties which are owned by each entity of
an Entity Set.
There exist a specific domain or set of values for each attribute from where the
attribute can take its values.
Types of Attributes-
In ER diagram, attributes associated with an entity set may be of the following types-
1. Simple attributes
2. Composite attributes
3. Single valued attributes
4. Multi valued attributes
5. Derived attributes
6. Key attributes
1. Simple Attributes-
Simple attributes are those attributes which can not be divided further.
Institute of Southern Punjab
Department of Computer Science & IT
Example-
Here, all the attributes are simple attributes as they can not be divided further.
2. Composite Attributes-
Composite attributes are those attributes which are composed of many other simple
attributes.
Example-
Here, the attributes “Name” and “Address” are composite attributes as they are
composed of many other simple attributes.
3. Single Valued Attributes-
Institute of Southern Punjab
Department of Computer Science & IT
Single valued attributes are those attributes which can take only one value for a given
entity from an entity set.
Example-
Here, all the attributes are single valued attributes as they can take only one specific
value for each entity.
4. Multi Valued Attributes-
Multi valued attributes are those attributes which can take more than one value for a
given entity from an entity set.
Example-
Here, the attributes “Mob_no” and “Email_id” are multi valued attributes as they can take
more than one values for a given entity.
Institute of Southern Punjab
Department of Computer Science & IT
5. Derived Attributes-
Derived attributes are those attributes which can be derived from other attribute(s).
Example-
Here, the attribute “Age” is a derived attribute as it can be derived from the attribute
“DOB”.
6. Key Attributes-
Key attributes are those attributes which can identify an entity uniquely in an entity set.
Example-
Here, the attribute “Roll_no” is a key attribute as it can identify any student uniquely.
Classification of attributes
Institute of Southern Punjab
Department of Computer Science & IT
key
simple
stored
EmployeeId
require
d
single
Non-
key
simple
stored
EmployeeHobby
optiona
l Multi
valued
Non-
key
Institute of Southern Punjab
Department of Computer Science & IT
simple
stored
Employeepassword
require
d Single
valued
Part 3
Is it possible to further transform the following abovecreated ERD in Part 2 as per Logical
Data Modeling?
If Yes; Than Design a transformed ERD in Information Engineering Standard
Answer
A logical data model (LDM) is a type of data model that describes data elements in
detail and is used to develop visual understandings of data entities, attributes, keys, and
relationships. This kind of model is uniquely independent from a specific database in order
to establish a foundational structure for components of the semantic layer in data
management systems. Think of an LDM as a blueprint:
It represents the definitions and characteristics of data elements that stay the same
throughout technological changes.
defines how a system has to be implemented and is not specific to
a database
Users who generally create LDMs are data architects and business analysts. These models
are used as a foundation for physical data models because they distinguish the relationships
and attributes for each entity.
Institute of Southern Punjab
Department of Computer Science & IT
Logical Data Model Examples
Below are a few examples of LDMs found from a variety of sources. You’ll
probably notice pretty quickly that while the design of the LDMs can look
different, the template and arrangement of figures are the same. You can
see different components of the data model, too, including datasets (boxes)
and the connection between them (arrows).
Institute of Southern Punjab
Department of Computer Science & IT
In the GoodData LDM Modeler, you can distinguish what type of
component you are handling by the color label.
The green datasets represent facts;
the yellow datasets are the attributes;
the blue dataset represents the date.
This simply designed LDM includes informational elements of normal, day-
to-day business. You can access the time, product, and store datasets.
logical data model components:
Dates: can include day of the week, month, quarter, year, and more
Institute of Southern Punjab
Department of Computer Science & IT
Facts: numerical values or pieces of data
In the LDM Modeler, there can be three types of facts:
Additive: facts used for calculations, such as adding together
Non-additive: facts that cannot be summed together
Semi-additive: facts that can be added, but only in certain contexts
Attributes: names of a characteristic or type of entity
A set of attributes is called a dimension, which is stored in tables. For
example, “address,” “city,” “state,” and “zip code” may all be attributes that
belong to a dimension labeled “location.”
Datasets: organizational units for set of facts and/or attributes
Relationships can be drawn between datasets to showcase associations.
As mentioned previously, in the GoodData LDM Modeler, datasets are
distinguished in boxes and by types with the color of the label.
Connection points: the primary keys for your database
Connection points are used for emphasizing uniqueness in a dataset. This
process of building relations and connections between datasets is
important in telling the system what can be sliced, and by what, when
producing your own metrics.
https://www.gooddata.com/blog/how-build-logical-data-models-
scale-analytical-applications/
part 2
Design/Draw an ERD in Information Engineering Style as per Conceptual Data Modeling of
the following above Entity type along with the given Attributes in Part 1?
Conceptual Data Model
The conceptual data model is the very first and the most abstract data
model in the data modeling process. It is a high-level diagram that we use
to define, describe, organize, and present data elements and their
relationships with relatively few details. Conceptual data models contain
only:
Institute of Southern Punjab
Department of Computer Science & IT
1. The real-world entities that are our main data elements.
2. Their relationships.
This model does not have technical details, such as attributes, data types,
etc
Implement a Conceptual Data Model
Let ERD online data modeler to demonstrate how to implement a
conceptual data model. Its easy-to-use interface and modern features
make creating an ER diagram for a basic purchasing model quite simple.
Two types of diagrams: a LOGICAL DIAGRAM and a physical diagram. You
can create both conceptual and logical models in the logical diagram
because there is no clear line between those two models. When we add
the technical details, we’ll have a logical data model, which we could use to
create the physical data model – but we’ll save that for another article.
Conceptual Data Model Examples, with ER Diagrams
1. Simple Employee Management System
This is an ER diagram of a conceptual data model for a simple employee
management system. In this company, there are many departments and
many employees in each department. Employees are assigned to different
Institute of Southern Punjab
Department of Computer Science & IT
projects and can only work on one project at a time; some employees may
not have been assigned to any projects. Each employee has a role (i.e. a
job role); many employees can have the same role. Also, there may be
vacant roles. Each employee has a login to access the company’s common
network, but there are different user privileges.
To support these business requirements, I have designed the conceptual
data model shown above. It has five entities (Employee, Department,
Project, Role, and Login) that reflect the real-world entity information in the
physical database. There are four relationships that support the described
business scenario:
Department_Employee : A one-mandatory-to-many-mandatory relationship.
Project_Employee : A one-optional-to-many-mandatory relationship.
Role_Employee : A one-mandatory-to-many-optional relationship.
Employee_Login : A one-mandatory-to-one-mandatory relationship.
Design/Draw Conceptual Data Modeling
EmployeeHOBBY_Employee: : A one-mandatory-to-many-mandatory
relationship.
EmployeeID_Employee : : A optional-mandatory-to-one-mandatory
relationship.
Employeepassword_Employee : A one-mandatory-to-one-mandatory
relationship
https://vertabelo.com/blog/conceptual-data-model/
BEST OF LUCK!!!
Institute of Southern Punjab
Department of Computer Science & IT
