SINIOR PROJECT DOCUMENTATION

ON
SUPER MARKET MANAGEMENT SYSTEM
CHAPTER ONE

INTRODUCTION
 Supermarket management system is the system that
involves selling and managing the product.
 This system for Abay Ena Tanna supermarket is a web
based system that works by providing an opportunity for
different customer.
 It also allows different users to buy different products on
this Supermarket that are registered and pay with in a
system.
 The main purpose of this project is to make each
customers and employers activity in computerized
(automate) way rather than manually which because of its
time consuming, difficulty of integrating data and unable
to interest different user request.
 Background of Organization
 Abay EnaTanna supermarket (AETS) is one of the
largest and supermarket in Bahirdar. It established
in 2002 E.C. by partnership and has no branch in
Ethiopia.
 Abay EnaTanna supermarket due to providing
wide variety of foods, Banana and apple, fish, Oil
and other products, so it is larger in size and has a
wider selection.
 It is difficult to manage the stock of supermarket.
 The supermarket process was slow so, we
recommend to develop an automated supermarket
management system for AETS.
STATEMENT OF THE PROBLEM

 The existing working process for the supermarket

management has the following problems:-
 It is difficult to retrieve product and its information

when it is required.
 It needs huge human power.

 There is no centralized database system.

 There is loss of product data because they placed

product data in different places.

 Wastage of time ,money customers and working space

 It is difficult to manage product (to search and

announce the products information)

 It is difficult to managing repetitive and bulky activities.
 OBJECTIVES OF THE PROJECT
General objective
The main objective is to develop the web based
supermarket management system in order to
mange’s supermarket activity within effectively
and efficiently
 Specific objectives
After the successful completion of this project the
software will provide the following application
(services):-
To register new product

To record customer history(information)

To record employee history(information)

To view detail ordered report

To promote sales of product

To provide real time delivering service

To update product and customer information


 Scope of the project
 These scopes are the system able to manage
administrators, managers, employees and
customers login.
 The system gives notification for appropriate
transaction, the system generate report.
 The system advertise new products.
 The system provides all transactions are available
and easy for users.
LIMITATION

 It is not provide online access of information.

 It is power dependent system.
 METHODOLOGY

Data gathering techniques

Data about the organization will be collected using
 Observation.

Document Analysis and

 interview.

Because these methods help us to get full and clear

information about the organization in easy way.
TH
A
N
K
Y
O
U
CHAPTER TWO
REQUIREMENT ANALYSIS

Functional Requirements
The functional requirements in this system are listed
below.
Manager
 System allows to manages employees
(active/deactivate, create, update and delete).
 System allows accepting feedbacks.
 System allows viewing order and Delete ordered Item.
 System allows viewing report(order, employee,
customer and product).
Administrator

System allows to manage employee account (add,

active/deactivate, update).
System allows recovering database.

Customer
System allows registering.

System allows managing cart (View item, Add to cart, remove cart,

order item, and cancel order).

System allows performing payment

System allows sending feedback.

System allows viewing notification.

Employee
System allows to manage product (add/post, update, delete).

System allows managing customer order.

System allows to login/logout to site

 Non Functional Requirements
 The non-functional requirements of the system are presented below:
-
 User Interface
 Error handling Mechanism
 Security issue
 Maintainability
 Availability
 Backup and Recovery
 Portability
 performance
 Usability
 scalability
 Help and support (user manual)
System Requirement
Hardware requirement
Software requirement

User requirements
The following are user requirements:-
 Anyone may sign up for a customer account if he/she is not a member
before
 the user must fill required information correctly for all forms and the
user must confirm user name
 email and password are acceptable.
 Business rules
 Business rules can apply to people, processes, corporate
behavior and computing systems in an organization, and are
put in place to help the organization achieve its goals.
 BR1: The user has to login to do his/her business operation on
the system.
 BR2: It is not allowed to see all reports unless he/she is the
manager.
 BR3: It is not allowed to add, update, and delete items unless
he/she is the Warehouse employee.
 BR4: The customer must have logged in before order items.
 BR5: The customer cannot purchase unless enough money in
their hand.
 BR6: Admin or employees must have logged in to view order.
 BR7: Admin must have deactivated employees to prevent
illegal access.
TH
AN
K
YO
U
 CHAPTER THREE
SYSTEM MODELING

Actor specification
 Customer: - someone who buys product.
 Administrator: - a special user of the system
who can setup access right for other users.
 Employee: a user of the system who is
responsible for managing the catalog of the
products.
 Manager: who is manages the organization.
Use Case Diagram
 System use case description
Use case name Login
Participating Actor Customer, Administrator, employee, manager
Description Only the registered users can login, it may be the customer, Administrator,
employee or manager.
Precondition The user have to be already register
Basic Action:
First: should be activate homepage
1. The user clicks on login button
2. The system displays a login form
3. The user enters user name and password
4. The user clicks on submit button.
5. The system validates the data entered
6. The system displays successfully logged in message.
7. The use case end
Alternate Course A: Invalid data entered.
A.6. The system displays error massage
A.7. The system asks to re-enter valid data
A.8. The use case resume to step 4
Alternate Course B: If the user is not having an account
B.6. The system display your user name and password is incorrect
B.7. Create user account and use case resume to step 3
B.8. The use case end

Post condition A user is logged into the system

Sequence diagram
TH
AN
K
YO
U
 CHAPTER FOUR
SYSTEM DESIGN

Design goal
Some of the goals are listed below.
 Security: The system should be secured from unauthorized
user.
 Modifiability: The system should be modifiability.
 Efficiency: The system must do what it is supposed to do
efficiently without the problem.
 User friendly interface: Users can easily input and retrieve
their profile and history.
 End User Criteria: - The systems have their own helping
system when it uses the system or user manual.
 Database Design
 Database design is the process of producing a detailed
data model of a database.
 This data model contains all the needed logical and
physical design choices and physical storage
parameters needed to generate a design in a data
definition language, which can then be used to create
a database.
Physical Design
 Access control and security policy
Generally, all users have their own user names and
passwords to control security access levels and document
sensitivity level.

Actor Manage Manage Mange Accept View View Manage Manage

employee Customer produc feedback report order user cart
account t account

Admin yes yes

Manger yes yes yes yes

Employe yes yes yes

e

customer yes yes

CHAPTER FIVE
IMPLEMENTATION

Tools and Environments

When we are develop our system we use the following
tools in the development environment.
Personal computer to be able to run the system
PHP MYSQL(wamp,xamp),
Web browser (Mozilla Firefox, Google chrome),
 macromedia Dream Weaver,
Edrawmax (trial version).
Microsoft word 2013
 Algorithm (used)

Before you write one line of code in any language, it is a good idea to write
algorithms in a simple.
Algorithm for Login
1. Function login (username, password)
2. If password length =0
3. Display error message “Please fill out this field”
4. Return
5. Pass=Retrieve Password
6. If password! =username
7. Display error message “This user name and Password is Not Correct!”
8. Return
9. pass =Retrieve Password
10. If password == username

11. Display members page

12. //end of the function login

 U
Y O
N K
A
T H
CHAPTER SIX
TESTING

The approach of web application testing adopts the basic

principle for all software testing and applies a strategy and
tactics that have been recommended for object oriented
system. The following step summarizes the approach
 Unit Testing
 Integration
 System testing
 Acceptance testing(alpha and beta test)
CHAPTER SEVEN

CONCLUSION AND RECOMMENDATION

 Conclusion

 The project concept “Supermarket system” is something like the original

supermarket system that is used by the customer in selecting certain
products.
 Finally, after select on the customer confirms orders for all the
purchasing items and submits his/her details information with tax at the
checkout counter.
 Through this software, one can choose the purchasing item and the software
calculates the net amount for the order including taxes.
 The supermarket system provides automated supermarket management
system for AETS.
 It mange’s supermarket activity within effectively and efficiently.
 A reliable platform for keeping all sensitive information and use backup
system
 Notice
Some activity or function of the project not
accomplished because of lack of time and the
situation of Covid 19.
Not accomplished the Functions of the project are:-
 The system not includes all actors like Administrator

and Employee (is not full fill).

 Recommendation

Since this system for AETS concerned in local

area, also it has no branches in Ethiopian. If the
company extends new branches, so we are
recommended that to be done a linkage for all
branches by enhancing the feature of this system
and we recommended that, the system should
mode concerned on suppliers and also different
languages are included in this system. If the
system is include online transaction, it will be
reduce the customer crowded
 U
Y O
N K
A
T H