HAWASSA UNIVERSITY

INSTITUTE OF TECHNOLOGY, FACAULTY OF

INFORMATICS
SUPERMARKET MANAGEMENT DATABASE SYSTEM PROJECT.
SECOND YEAR, COMPUTER SCIENCE.
Group 11 Year 2 Computer Science students.

GROUP MEMBERS ID No.

1. KABASHI ROBIN………………………………..NaScR/3142/13
2. TSEDEY DEMISSIE……………………………NaScR/2476/13
3. EKRAM ZEINU…………………………………NaScR/0902/13
4. EBISE TESFA…………………………………....NaScR/0871/13
5. FIKRTE GETYA………………………………...NaScR/1096/13

Submitted to: Mr. Abebayew

Submission date: April 25th, 2022

Page 1
table of contents
Acknowledgement………………………………………………………………….……3
Abstract……………………………………………………………………………………….3

CHAPTER ONE
Introduction
1.1 Statement of the project………………………………………………………….4
1.2 Mission of the project ……………………………………………………………..5
1.3 Objectives of the project………………………………………………………….5
1.4 Scope of the project…………………………………………………………………6
1.5 Significance of the project………………………………………………………..6

CHAPTER TWO

Conceptual & logical Design

2.1 Identifying entities…………………………………………………………………..7

2.2 Identifying the attributes…………………………………………………………7
2.3 Identifying the key attributes…………………………………………………..8
2.4 Major Entity Relationships ……………………………………………………...9
2.5 ER diagram for the project……………………………………………………….10
2.6 Mapping Relational schema……………………………………………………..11
2.7 Unified Modelling Language Class Diagram……………………………….12

Page 2
ACKNOWLEDGEMENT

We wish to explain our sincere gratitude to our instructor Mr. Abebayew of the Institute of
Technology, Faculty of Informatics for his support, encouragement and the opportunity to design our database
project that will help us to understand and grasp the concepts of database design and application in the real
world.

We also acknowledge and thank each member in our group who have put in work effort so that we can
accomplish this database project.

ABSTRACT

The following project ‘Supermarket Management Project’ deals with automation of supermarkets. It
will help the salespersons in managing the various types of record pertaining to help his/her customers and
ensure a highly effective and efficient environment for a supermarket.

Page 3
CHAPTER ONE
1. INTRODUCTION
1.1 Statement of the project.
The salespersons have been recording the customer information in the past and even a few in the
present through their manual efforts of paper work and indeed, it consumes their considerable time
and energy that could be utilized in the better productive activities. Apart from that, with increasing
customer strength, the task of managing information of each individual customer is indeed a
cumbersome task. Therefore the project deals with such problems and tries to remove them in the
most suitable fashion.
Building a standard supermarket management system is not an easy task looking at the problems
existing in the manual system.

The factors for their difficulties are;

1. Time consumption.
Manual systems are time consuming as the business owner must keep tract of supermarket
sakes on a daily basis, while updating the system manually at the end of the day.

2. Poor communication.
A manual supermarket system requires employees and managers to write down each time
an item is removed from the supermarket. If one employee forgets to mention that in the
last coffee product has been removed from the supermarket, a manager expects the item to
still be available for a customer during a sale. Compared with a technical supermarket
system, a manual supermarket system does not help in the communication in the work
place.

3. Physical counts.
A manual system does not provide any number as all number from the supermarket is gained
through physical supermarket counts. One of the difficulties of running a manual
supermarket system is that physical supermarket counts must be performed frequently to
control the items in the supermarket. This is time consuming and can cost the business
money. As employees must come in to help out outside of the business hours.

4. Daily purchases.
Keeping track of daily purchase is another difficult controlling measure with manual
supermarket systems. A manual supermarket system requires the employees to write down
the items sold during a single work day. This can a difficult task, as one employee may lose
the list of the items sold or another may forget to write down a sale.

5. Ordering supplies.
A manual supermarket system does not update at the end of the day which is completely
different for supermarkets with database systems.

Page 4
1.2 Mission statement of the project.

This system is made to provide superior technology options that enhance information
management systems for supermarket.

1.3 Objectives of the project.

To design a computerized supermarket management system to ascertain stock level
of a supermarket, when to order for more goods, keep status & updates of transactions,
thereby helping progress level, stock taking and managerial decisions.

Therefore the objectives include the following;

 To study the functions of supermarket management system.

 To explore the challenges being faced by the manual system.

 To make a software fast in processing with good user interface.

 To ensure accurate statistics of product items.

 For easy record of goods in store and proper identification.

Page 5
1.4 Scope of the project.

This project work covers stock control, management and tends to correct anomalies
in supermarket businesses. It analyses opening of new stocks, stock updates and ability to
view existing ones. It provides quick way of operation by capturing the manual process and
automating them. This project is helpful to computerize the item transaction, sales activity
record keeping which is a very huge task & maintaining the stock.

1.5 Significance of the study.

The project is to make operation of supermarkets to be ran on accurate sales, vender
and stock information.

The project is to go a long way in improving on the provision of vital information to the right
especially the management at the right time for management purpose. Developing a
supermarket system would provide seamless and critical information which is a key
requirement.
The relevance of the project primarily focuses on management, stock recorders and sellers
who will be the core users. This will in turn lead to faster decision making, data entry and
viewing by reducing on data inconsistencies, improper storage & increased paper work.

Page 6
CHAPTER TWO: Conceptual Design.

2.1 Identifying Entities.

 Customer

 Supplier

 Employee

 Product

 Purchase

 Payment

2.2 Identifying the attributes.

 Customer
o Cust_id
o CustName
o CustAddress
o Tell
o DOB
o Sex
 Employee
o Emp_id
o EmpName
o EmpAdress
o Tell
o DOB
o Sex
 Supplier
o Sup_id
o SupName
o SupAddress
o SupDate
o Email

Page 7
 o Tell

 Product
o Prod_no
o ProdName
o ProdType
o ProdPrice
o ProdSupplier
o Expiry date

 Payment
o Pay_id
o PayCust_id
o PayDate
o PayAmount
o PayDecription

 Department
o Dept_id
o DeptEmp_id
o DeptType
o DeptName

2.3 Identifying the Key Attributes.

 Customer
 Primary Key: Cust_id

 Employee
 Primary Key: Emp_id

 Supplier
 Primary Key: Sup_id

 Product
 Primary Key: Prod_no

Page 8
  Payment
 Primary Key: Pay_id
 Foreign Key: PayCust_id

 Department
 Primary Key: Dep_id
 Foreign Key: DepEmp_id

2.4 Major Entity Relationships

Employee sells Product

buys
Customer Product

makes
Customer Payment

provides
Supplier Product

Serves
Employee Customer

Employee manages

Page 9
2.5 ER Diagram for the project.

Page 10
Logical Design
2.6 Mapping and Relational schema.

 Customer

cust_ id name address DOB sex Tell

 Payment

pay_ id amount description date cust_id

 Product

prod_id name type price expirydate sup_id cust_id

 Supplier

sup_id name address email Tell date

 Employee

emp_id name address salary DOB Tell email dept_id

 Department

dept_id name type No. of employees

Page 11
2.7 Unified Modelling Language (UML) Class Diagram of the project

Page 12