College of Engineering and Technology

Department
Of
Computer Science

Fundamental of Database project

COURSE CODE: Cosc2071

Group member’s name Identification Number

1. Yomlata Abera…...........................................................RT10001/13
2. Ayantu Bullo………………………………………….RU/5728/12
3. Muluken Gezahegn…………………………………...RU/4679/12
4. Ababo Girmaye……………………………………….RU/4932/12
5. Burka Abdi…………………………………………....RU/4772/12

Submitted to:Mr. Amansisa E.

Summision date:June 5, 2021
Finance department ERD and LRM 2021

Acknowledgement
First of all, we want to say thank you to our creator. We also wish to thanks Finance department
all employees for their willingness to share information about their department. Then we are also
thankful for our teacher and also our mentor (Father) for encouraging us to perform this project.

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 1
Finance department ERD and LRM 2021

ABSTRACT

Finance department has a great role for every work that is done around the compound. Without the finance
department allocating budget to other department would be difficult. Not only allocating budget would be
difficult but also collecting the revenues would be difficult. As we have observed the finance department is
a soul not only to Mettu University but also to any compound. It is the basic need in formulating different
compound. Finance offices must be free of errors. Because the last thing customers want to have using
services from department which can’t do their work properly.

Mettu University finance department is one of the department that has many works and the overcrowded
one every day. Their day to day activity is the one that need a very high concentration and the one that
need a very high carefulness.

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 2
Finance department ERD and LRM 2021

Table of Contents
CHAPTER 1: OVER VIEW ...................................................................................................................... 4

1.1 Introduction ...................................................................................................................................... 4

1.2 Information gathering methods ......................................................................................................... 4

1.3 Hardware and software used ............................................................................................................. 4

CHAPTER 2: ER DIAGRAM.................................................................................................................... 5

2.1 Introduction ...................................................................................................................................... 5

2.2 Identifying Entities ........................................................................................................................... 5

2.3 Identifying Attributes ....................................................................................................................... 6

2.4 Types Attributes ............................................................................................................................... 6

2.5 Entity relationship ............................................................................................................................ 7

2.6 Cardinality........................................................................................................................................ 7

2.7 ER diagram ...................................................................................................................................... 8

CHAPTER 3: LOGICAL RELATIONAL MODEL ................................................................................... 9

3.1 Mapping of Strong Entity types ........................................................................................................ 9

3.2 Mapping Weak entity type ................................................................................................................ 9

Conclusions ............................................................................................................................................... 9

References ............................................................................................................................................... 10

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 3
Finance department ERD and LRM 2021

CHAPTER 1: OVER VIEW

1.1 Introduction
In this chapter we are going to see how we gathered information for our project, then we will see
in detail what materials we used in case of hardware and applications we used in case of
software.

1.2 Information gathering methods

We have gathered information by interviewing the employees and by observation. In the interview
method we have asked many questions about their department starting from the head to the
different hierarchy individuals. In our interview session they were so kind to answer all of our
questions.
The other way we gathered the information was by observation. We used this method of gathering
information by observing over all of their day-to-day activity. After that we have organized the
information that we have gathered from the employees.
1.3 Hardware and software used

We have used many hardware materials and software applications for this project some of them are:
1.3.1 Hardware materials
Laptop: We have used laptop computer for this project
Flash disk: We have used flash disk to transfer data and different information from one place to desired
area.
1.3.2 Software applications
Edraw max 7: we used it to draw an ER diagram.
Microsoft Access 2019: To prepare logical relational database model.
Microsoft Word 2019: We used it to rearrange this document.

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 4
Finance department ERD and LRM 2021

CHAPTER 2: ER DIAGRAM

2.1 Introduction

In this chapter we are going to see how to draw ER diagram, identify the entities and attributes of
Finance department of Mettu University. After we finish this chapter we identify which type
entity, attribute and relationship we have used. We are also going to elaborate the relationship
between the Entities. We also determine the cardinality of the related entities.

2.2 Identifying Entities

Our ER diagram consists five entities. We can list them as below:

 Department: Our first Entity is department. Our department entities instance is Mettu University
Finance department. This department consists many attributes. Such as: Address, name and extra.
 Manager: The manager is another entity. It controls everything inside that department as the
manager is the sole responsibility. Some of the attributes are Name, Address and extra.
 Employee: The ER diagram also consists the employees in the finance department. This entity has
his own attributes like name, age and extra.
 Cashier: The other entity is cashier. The cashiers are the one that are responsible with money
things. This entity has attributes like identification number, address and extra.
 Customer: The customers are the one that uses the services provided by the finance department.
The attributes of these entities are address, name and extra.
Note: all the entities are strong (normal) entity as they have their own key attributes.

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 5
Finance department ERD and LRM 2021

2.3 Identifying Attributes

 Identification Number: This attribute is key attribute for the Entities it is representing. As it is
known key attributes can’t be null and it should be unique. So, it is represented by the ellipse with
underlining the instance.
 Phone number: This attribute has multi values. So, it is represented by double ellipse.
 Name: It is represented by simple(single) attribute. It is represented by single ellipse.
 Age: Is a derived attribute (derived from Date of birth in the database). It is represented by dotted
attribute.
 Address: Simply we can say the address of one person is not expressed by only one method. So,
we can say that it is a composite attribute.

2.4 Types Attributes

 Key Attribute: Is the one that is unique and can’t be null. In case it has similar instances for
another attribute it uses to differentiate it and identify and choose the one that you desire. It is
represented by an ellipse with having underlined instances. We can take an example from our ER
diagram it is Identification number.
 Multi valued Attribute: It is a type of attribute that has multiple values as instance. It is
represented by double ellipse. Example: we can take phone number. As some one can have
multiple phone numbers know adays.
 Simple Attribute: It is a type of attribute that take a single instance with simple form. It is
represented by single ellipse. From our ER diagram name attribute is a simple attribute.
 Derived Attribute: It is the one that is derived from other attributes. As an example, we can take
Age from our ER diagram. It is derived from date of birth attribute. Derived attribute is denoted by
dotted ellipse.
 Composite Attribute: It is a type attribute that is represented by integrated parts of the attribute. It
is represented by attribute with other attribute as it parts. For example we can take Address from
our ER diagram, as it has different parts which come together and form full form attribute.

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 6
Finance department ERD and LRM 2021

2.5 Entity relationship

▪ Manages: Is instance of a relationship which is between Manager and Department. It shows that
the manager manages the finance department. This relationship is a binary relationship. Its
cardinality ratio is 1-1. Which implies that one manager stands for one department.
▪ Works Under: Is instance of a relationship which is between Employee and department. It shows
that an Employee works under a department. This relationship type is a binary relationship. Its
cardinality ratio is many-to-one. This implies that many employees work under one department.
▪ Works for: Is instance of a relationship which is between Cashier and department. It shows that a
cashier works for a department. This relationship type is a binary relationship. Its cardinality ratio
is many-to-one. This implies that many cashiers work for one department.
▪ Supervise: Is instance of a relationship which is between Manager and cashier. It shows that the
manager supervise cashiers. This relationship type is a binary relationship. Its cardinality ratio is
one -to-many. This implies that one manager supervises many cashiers.
▪ Gives service to: Is instance of a relationship which is between Employee and customer. It shows
that an employee gives service to customers. This relationship type is a binary relationship. Its
cardinality ratio is one -to-many. This implies that one employee gives service to many customers .
▪ Receives money from: Is instance of a relationship which is between cashier and customer. It
shows that the cashier receives money from customers. This relationship type is a binary
relationship. Its cardinality ratio is one -to-many. This implies that one cashier can receive money
from many customers.

2.6 Cardinality

 1-1(One to one): It is a type of cardinality when one instance of the entity has a relationship with
another entity with one instance. From our ER diagram the relationship between department and
manager has 1-1 cardinality ratio. This happens because the manager manages department.
 1-N (One-to-many): It is a type of cardinality that has a relationship between single values of an
entity with many values of another entity. From our ER diagram the relationship between manager
to cashier, Employee to customer and Cashier to customer have One-to-many cardinality ratio.
 N-1 (Many-to-one): It is a type of cardinality ratio which happens when many instances of the
entity has a relationship with a single instance of another entity. In our ER diagram the relationship
between Employee and department and cashier and department has many-to-one cardinality ratio.
 M-N (Many-to-many): It is a type of cardinality ratio which happens when many instances of one
entity relates to many instances of another entity. In our ER diagram there is no such cardinality
ratio between our entities.

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 7
Finance department ERD and LRM 2021

2.7 ER diagram

Figure 1: ER diagram

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 8
Finance department ERD and LRM 2021

CHAPTER 3: LOGICAL RELATIONAL MODEL

3.1 Mapping of Strong Entity types

Entities with their own key attribute are called strong Entities. Key attributes are with unique and not null
attributes. This key attributes are used to identify which data is needed when there are similar data. As key
attributes are unique there will be different instance for the two similar data. From our ER diagram the
Strong entities are shown below. By mapping them the logical relational model for the strong entities is:

Manager
Id number Address Name Age Phone number

Employee
Id number Address Name Phone number Age

Cashier
Id number Address Name Phone number Age

3.2 Mapping Weak entity type

Weak entity are the one that doesn’t have their own key attribute. But they can use other entity key
attributes as foreign key. From our ER diagram we have weak entities and we have mapped them as the
following:
Department
Manager Id no. Address Name Phone number

Customer
Employee Id no. Name Address Phone number

Conclusions
The main purpose of this project is to know how the finance department works. This will help us also in
our future working life. It simplified every obstacle that is in front of us and helps us to have knowledge
about it. Most of all it helped us to have deep knowledge about ER diagram and Logical relational model.

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 9
Finance department ERD and LRM 2021

References
The main source of our information is:

Mettu university Finance department Employees

Internet source
Lecture note
Document analysis from the existing project

Complied by Group 1(Singeten) computer science 2nd year students 2012 Batch Page 1
0
Preparedby2ndyearComputerScienceGroupThree 5