VISVESVARAYA TECHNOLOGICAL UNIVERSITY

Jnana Sangama, Belagavi-590018

A Database Management System Mini Project Report on

“MOBILE STORE MANAGEMENT SYSTEM”
Submitted in Partial fulfillment of the Requirements for the V Semester of the Degree of

Bachelor of Engineering in
Computer Science & Engineering
By
NITHIN C (1CR21CS412)

ADARSH PALANAKAR (1CR21CS400)

Under the Guidance of,

Dr. Sanchari Saha, Assistant Professor, Dept. of CSE

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CMR

INSTITUTE OF TECHNOLOGY
Affiliated to VTU, Approved by AICTE, Accredited by NBA and NAAC with “A++” Grade
ITPL MAIN ROAD, BROOKFIELD, BENGALURU-560037, KARNATAKA, INDIA
CMR INSTITUTE OF TECHNOLOGY
 Affiliated to VTU, Approved by AICTE, Accredited by NBA and NAAC with “A++” Grade
ITPL MAIN ROAD, BROOKFIELD, BENGALURU-560037, KARNATAKA, INDIA

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CERTIFICATE
This is to certify that the Database Management System Project work entitled “MOBILE
STORE MANAGEMENT SYSTEM” has been carried out by Nithin C (1CR21CS412)
and Adarsh Palanakar (1CR21CS400), bona fide students of CMR Institute of Technology,
Bengaluru in partial fulfillment for the award of the Degree of Bachelor of Engineering in
Computer Science and Engineering of the Visvesvaraya Technological University, Belagavi
during the year 2022-2023. It is certified that all corrections/suggestions indicated for the
Internal Assessment have been incorporated in the report deposited in the departmental
library. This Database Management System Project report has been approved as it satisfies the
academic requirements in respect of project work prescribed for the said Degree.

_____________________________ _____________________________
Signature of Guide Signature of HOD
(Dr. Sanchari Saha) (Dr. Shreekanth M Prabhu)
Assistant Professor Professor & HoD
Dept. of CSE, CMRIT Dept. of CSE, CMRIT
External Viva

Name of the Examiners Signature with date

1.

2.

ii
 DECLARATION

We, the students of V semester of Computer Science and Engineering, CMR Institute of
Technology, Bangalore declare that the project work entitled "Mobile Store Management
System" has been successfully completed under the guidance of Dr. Sanchari Saha, Assistant
Professor, Dept. of Computer Science and Engineering, and Mrs. Anjali Gupta, Assistant
Professor, CMR Institute of technology, Bengaluru. This project work is submitted in partial
fulfillment of the requirements for the award of the Degree of Bachelor of Engineering in
Computer Science and Engineering during the academic year 2022-2023. The matter embodied
in the project report has not been submitted previously by anybody for the award of any degree
or diploma to any university.

Place: Bangalore

Date: 12/01/2023
Team members:
NITHIN C (1CR21CS412)

ADARSH PALANAKAR (1CR21CS400)

iii
 ABSTRACT

The title of project is mobile shop management system. The main purpose of our project is to do
smart work and also, we can see that in this era of advanced technology we also have to do work
more smartly that’s why most of the shops need advanced techniques to do their work more
speedily and smartly that’s why storing or collecting important data on paper is not reliable and
also it has chance of missing that paper so we created this for storing most important data like
billing, customer information and product information. It will help to organize mobile shop data
in very systematic way.

Keywords: Management, Information, Billing, Data, Mobile

iv
 ACKNOWLEDGEMENT

I take this opportunity to express my sincere gratitude and respect to CMR Institute of
Technology, Bengaluru for providing me a platform to pursue my studies and carry out the
Database Management System Project.
It gives me an immense pleasure to express my deep sense of gratitude to Dr. Sanjay
Jain, Principal, CMRIT, Bengaluru, for his constant encouragement.
I would like to extend my sincere gratitude to Dr. Shreekanth M Prabhu, HOD,
Department of Computer Science and Engineering, CMRIT, Bengaluru, who has been a constant
support and encouragement throughout the course of this project.
I would like to thank my guide Dr. Sanchari Saha, Assistant Professor and
Mrs. Anjali Gupta, Assistant Professor, Department of Computer Science and Engineering,
for the valuable guidance throughout the tenure of the project work.
I would also like to thank all the faculty members of Department of Computer Science
and Engineering who directly or indirectly encouraged me.
Finally, I thank my parents and friends for all the moral support they have given me
during the completion of this work.

v
 TABLE OF CONTENTS

Contents Page No.

Certificate i
Acknowledgement ii
Abstract iii
Table of contents iv
List of Figures v
List of Tables vi
1. Introduction 1

1.1 Objectives

1.2 Scope of Project 1

1.3 Introduction To Database 2
1.3.2 Components Of dbms 4

2. System Requirements 2

2.1 Hardware Requirements 2

2
2.2 Software Requirements
3. Design 3

3.1 Tables 3

3.2 Schema Diagram 9

3.3 ER Diagram 10
4. Implementation 11

4.1 Execution of the project 11

4.2 SQL 11

5. Screenshots 23

5.1 Result Output 23

6. Conclusion and Future Scope 30

vi
7. References 31

LIST OF FIGURES

Figure No. Figure Name Page No.

1.1 Components of DBMS 4

3.1 ER Diagram of Movie Ticket Booking System 12
3.2 Relational Schema 13
5.1 Home Page 19
5.2 Login Page 20
5.3 Sign Up Page 21
5.4 Booking Page 22
5.5 Book Now Page 23
5.6 Seat Selection Page 23
5.7 Admin Dashboard Page 24
5.8 Admin Movie Entry Page 25
5.9 Admin Movie Show Page 25
5.10 Admin Booking Entry Page 26
5.11 Admin Table 27
5.12 User Table 27
5.13 Movie Table 28
5.14 Booking Table 29

LIST OF TABLES
Table No Table Name Page no
1.1 Display the Tables_in_votesystem 22
1.2 Display the Candidates Table 22

vii
1.3 Display the Admin Table 23
1.4 Display the Position Table 23
1.5 Display the voters Table 24
1.6 Display the votes table 24

viii
MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 1

INTRODUCTION
In this rapid growing generation, technology is growing day by day. Our project is on mobile
shop management system for manage a mobile shop. In our project we have included billing
system, product, customer management, manage brands, manage sail details. We can add the
details of mobile, tablets, headphones and other products. Need of high speed data access is
necessary in today’s world. Record of employee and records of customers will be safely kept
in database. We can edit the data as well as retrieve the data whenever required. In existing
system details are maintained manually so it takes time to save and modify the data. It
becomes very difficult to maintain the data. So, we have prepared an enhanced system of
mobile shop management. This is a very useful for mobile shop to manage their shop easily.

1.1 Objectives
The specific objectives of the project include:

 To manage the details of Customers, Stock, Mobile, Payment, Sells.

 It manages all the information about Customers, Brands, Sells, Customers.
 The project is totally built at administrative end and thus only the administrator is
guaranteed the access.
1.2 Scope of the project

 This System has large scope for the Mobile Shop Management System& Mobile
Information.
 The System stores all information of the Mobiles.
 System can able to accept user request and manages information like Mobile’s as
well as the Customers and Clients
 System provides the facility of Mobile Information with their Prices.
 System Provide facility of payment and purchase Products

1.3 INTRODUCTION TO DATABASE

Databases and database technology have had a major impact on the growing use of
computers. A database is a collection of related data. By data, we mean known facts that can

Dept. of CSE,SJBIT 2022-2023 Page 1

MOBILE STORE MANAGEMENT SYSTEM

be recorded and that have implicit meaning. For example, consider the names, telephone
numbers, and addresses of the people you know. Nowadays, this data is typically stored in
mobile phones, which have their own simple database software. In other words, a database
has some source from which data is derived, some degree of interaction with events in the
real world, and an audience that is actively interested in its contents. A database can be of
any size and complexity. For example, the list of names and addresses referred to earlier may
consist of only a few hundred records, each with a simple structure. On the other hand, the
computerized catalogue of a large library may contain half a million entries organized under
different categories.
A database has the following implicit properties:

 A database represents some aspect of the real world, sometimes called the mini
world or the universe of discourse. Changes to the mini world are reflected in the
database.
 A database is a logically coherent collection of data with some inherent meaning. A
random assortment of data cannot correctly be referred to as a database.
 A database is designed, built, and populated with data for a specific purpose. It has
an intended group of users and some preconceived applications in which these users
are interested.
A database management system (DBMS) is a computerized system that enables users to
create and maintain a database. The DBMS is a general-purpose software system that
facilitates the processes of defining, constructing, manipulating, and sharing databases
among various users and applications. Defining a database involves specifying the data
types, structures, and constraints of the data to be stored in the database. The database
definition or descriptive information is also stored by the DBMS in the form of a database
catalogue or dictionary; it is called meta-data. Constructing the database is the process of
storing the data on some storage medium that is controlled by the DBMS. Manipulating a
database includes functions such as querying the database to retrieve specific data, updating
the database to reflect changes in the mini world, and generating reports from the data.
Sharing a database allows multiple users and programs to access the database
simultaneously.
1.3.1 ADVANTAGES OF DBMS:

Dept. of CSE,SJBIT 2022-2023 Page 2

 MOBILE STORE MANAGEMENT SYSTEM

Compared to the File Based Data Management System, Database Management System has
many advantages.

1.Reducing Data Redundancy

The file-based data management systems contained multiple files that were stored in many
different locations in a system or even across multiple systems. Because of this, there were
sometimes multiple copies of the same file which leads to data redundancy. This is prevented
in a database as there is a single database and any change in it is reflected immediately.
Because of this, there is no chance of encountering duplicate data.
2.Data Integrity
Data integrity means that the data is accurate and consistent in the database. Data Integrity is
very important as there are multiple databases in a DBMS. All of these databases contain data
that is visible to multiple users.
So, it is necessary to ensure that the data is correct and consistent in all the databases and for
all the users.

3.Data Security
Data Security is vital concept in a database. Only authorised users should be allowed to
access the database and their identity should be authenticated using a username and
password. Unauthorised users should not be allowed to access the database under any
circumstances as it violates the integrity constraints.
4.Privacy
The privacy rule in a database means only the authorized users can access a database
according to its privacy constraints. There are levels of database access and a user can only
view the data he is allowed to. For example - In social networking sites, access constraints
are different for different accounts a user may want to access.
5.Backup and Recovery
Database Management System automatically takes care of backup and recovery. The users
don't need to backup data periodically because this is taken care of by the DBMS. Moreover,
it also restores the database after a crash or system failure to its previous condition.
6.Data Consistency
Data consistency is ensured in a database because there is no data redundancy. All data
appears consistently across the database and the data is same for all the users viewing the

Dept. of CSE,SJBIT 2022-2023 Page 3

 MOBILE STORE MANAGEMENT SYSTEM

database. Moreover, any changes made to the database are immediately reflected to all the
users and there is no data inconsistency.
1.3.2 COMPONENTS OF DBMS

Fig 1.1 Components of DBMS

The figure 1.1 shows the components of DBMS which describe the different parts that work
together for creating, managing the database that forms a complete system named
DBMS(database management system).

 Users:

Users may be of any kind, such as data base administrators, system developers or database
users.

 Database application:

Database application may be Departmental, Personal, Organizational and /or Internal.

 DBMS:

Software that allows users to create and manipulate database access

 Database:
Collection of logical data as a single unit.

Dept. of CSE,SJBIT 2022-2023 Page 4

MOBILE STORE MANAGEMENT SYSTEM

1.3.3 INDICATIVE AREAS FOR THE USE OF DBMS

SECTOR USE OF DBMS

For customer information, account

BANKING
activities, payments, deposits, loans, etc.

For reservations and schedule

AIRLINES
information.

For student information, course

UNIVERSITIES
registrations, colleges, and grades.

It helps to keep call records, monthly

TELECOMMUNICATION
bills, maintaining balances, etc.

For storing information about stock, sales,

FINANCE and purchases of financial instruments
like stocks and bonds.

Use for storing customer, product & sales

SALES
information.

It is used for the management of supply

MANUFACTURING chain and for tracking production of
items. Inventories status in warehouses

For information about employees,

HR MANAGEMENT salaries, payroll, deduction, generation of
pay checks, etc
Table 1.1 Indicative areas for the use of DBMS

1.4 CONSTRAINTS
Mainly Constraints on the relational database are of 4 types:

 Domain constraints
 Key constraints
Entity Integrity constraints

Dept. of CSE,SJBIT 2022-2023 Page 5

MOBILE STORE MANAGEMENT SYSTEM

 Referential integrity constraints

DOMAIN CONSTRAINTS:

 Every domain must contain atomic values (smallest indivisible units) it means composite
and multivalued attributes are not allowed.
 We perform datatype check here, which means when we assign a data type to a column
we limit the values that it can contain.
 Eg. If we assign the datatype of attribute age as int, we can’t give it values other than int
datatype.

KEY CONSTRAINTS OR UNIQUENESS CONSTRAINTS:

 These are called uniqueness constraints since it ensures that every tuple in the relation
should be unique.
 A relation can have multiple keys or candidate keys(minimal superkey), out of which we
choose one of the keys as primary key, we don’t have any restriction on choosing the
primary key out of candidate keys, but it is suggested to go with the candidate key with
less number of attributes.
 Null values are not allowed in the primary key, hence Not Null constraint is also a part of
key constraint.

ENTITY INTEGRITY CONSTRAINTS:

Entity Integrity constraints says that no primary key can take NULL value, since using
primary key we identify each tuple uniquely in a relation.

REFERENTIAL INTEGRITY CONSTRAINTS:

 The Referential integrity constraints is specified between two relations or tables and used
to maintain the consistency among the tuples in two relations.
 This constraint is enforced through foreign key, when an attribute in the foreign key of
relation R1 have the same domain(s) as the primary key of relation R2, then the foreign
key of R1 is said to reference or refer to the primary key of relation R2.

Dept. of CSE,SJBIT 2022-2023 Page 6

 MOBILE STORE MANAGEMENT SYSTEM

 The values of the foreign key in a tuple of relation R1 can either take the values of the
primary key for some tuple in relation R2, or can take NULL values, but can’t be empty.

1.5 NORMALISATION
Normalizing tables accordingly based on the normal forms.

NORMAL FORMS:
Of a relation refers to the highest normal form condition that it meets and hence indicates the
degree to which it has been normalized.
 First NF:
States that the domain of the attribute must only include atomic values and the value of any
attribute in a tuple must be a single value.
 Second NF:
Is based on the concept of full functional dependency I.e. if removal of any attribute A from
X in FD X->Y the dependency does not hold anymore.
 Third NF:
A relation schema R is in 3NF if, whenever a non-trivial functional dependency X->A holds
in R either: X is a super key of R or A is prime attribute of R.
 Boyce-Codd NF:
A relation schema R is in BCNF if whenever a non-trivial functional dependency X->A holds
in R, then X is a super key of R.
 Fourth NF:
A relation schema R is in 4NF w.r.t a set of dependencies F if, for every non-trivial
multivalued dependency X->>Y in F+ ,X is a super key for R.

Dept. of CSE,SJBIT 2022-2023 Page 7

 MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 2

SYSTEM REQUIREMENTS
The system requirements for a project outline the necessary hardware and software resources
for development, deployment, and operation. It is important to carefully consider and plan for
the system requirements of a project, as the wrong choices can lead to performance issues,
compatibility problems, or other issues that can impact the success of the project.

2.1 Hardware Requirements

Server-side requirements include:

• Minimum dual core CPU, recommended quad core or above

• Minimum 8GB RAM

• 20GB Hard Drive Space

Client-side requirements are any device that is capable of connecting to the internet and
running a web browser.
2.2 Software Requirements

Server-side software requirements are:

● Client: Operating System

● Web Server: Apache Tomcat

● Database Server: MYSQL Server

● Languages: HTML, PHP, CSS

Client-side software can run on any device that supports an internet connection and a web
browser.

Dept. of CSE,SJBIT 2022-2023 Page 8

MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 3
DESIGN
The design chapter of this project report outlines the process and considerations that went
into the design of the project. This includes the identification of design goals and objectives,
the collection and analysis of data, the development of the system or product design, and the
validation and testing of the design. The design chapter provides a comprehensive
understanding of the project's design, and is based on established principles and practices.

This project as following tables :

1. BRANDS
2. CART
3. CATEGORIES
4. CLIENTS
5. INVENTORY
6. ORDER_LIST
7. ORDERS
8. PRODUCTS
9. SALES
10. SUB_CATEGORIES
11. SYSTEM_INFO
12. USERS

The table details are as follows:

Table 3.1 BRANDS

Dept. of CSE,SJBIT 2022-2023 Page 9

MOBILE STORE MANAGEMENT SYSTEM

Table 3.2 CART

Table 3.3 CATEGORIES

Table 3.4 CLIENTS

Dept. of CSE,SJBIT 2022-2023 Page 10

MOBILE STORE MANAGEMENT SYSTEM

Table 3.5 INVENTORY

Table 3.6 ORDERS

Dept. of CSE,SJBIT 2022-2023 Page 11

MOBILE STORE MANAGEMENT SYSTEM

Table 3.7 ORDER_LIST

Table 3.8 PRODUCTS

Table 3.9 SALES

Dept. of CSE,SJBIT 2022-2023 Page 12

MOBILE STORE MANAGEMENT SYSTEM

Table 3.10 SUB_CATEGORIES

Table 3.11 SYSTEM_INFO

Table 3.12 USERS

Dept. of CSE,SJBIT 2022-2023 Page 13

MOBILE STORE MANAGEMENT SYSTEM

3.1 Schema Diagram

Figure 3.1 Schema Diagram

Dept. of CSE,SJBIT 2022-2023 Page 14

MOBILE STORE MANAGEMENT SYSTEM

3.2 ER Diagram
The Entity Relationship (ER) diagram is a visual representation of the data model of the
Mobile store management project. It illustrates the entities, attributes, and relationships
between the different elements of the data model, and provides a clear overview of the
organization and structure of the data. The ER diagram is an important tool for understanding
the underlying data model of the Mobile store management project, and for identifying the
relationships and dependencies between different data entities.

Figure 3.2: ER Diagram

Entities (System_info,Inventory,order_list,client,categories,band,cart,sub_cattegories,order).

Dept. of CSE,SJBIT 2022-2023 Page 15

 MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 4
IMPLEMENTATION
The implementation section of this project report outlines the steps and processes involved in
the development and deployment of the Mobile Store Management System project. This
includes the selection and configuration of tools and technologies, the design and coding of the
system, the testing and debugging of the system, and the deployment of the system to a
production environment. The implementation chapter provides a detailed description of the
project's implementation, and documents the challenges and successes encountered during the
development process. The purpose of the implementation chapter is to provide insight into the
project's technical execution and the rationale behind the implementation decisions.

4.1 Execution of the project

To execute the project, first start the Xampp server, run Apache and MySQL, then run the
below commands in the chrome extension:

• Localhost/phpmyadmin

• Create database

• Import tables

• Localhost/mobile_store

4.2 SQL Stored procedures

Table structure for table `brands`

CREATE TABLE brands (

id int(30) NOT NULL,
name varchar(250) NOT NULL,
description text DEFAULT NULL,
status tinyint(1) NOT NULL DEFAULT 1,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

Dept. of CSE,SJBIT 2022-2023 Page 16

 MOBILE STORE MANAGEMENT SYSTEM

INSERT INTO brands (id, name, description, status, date_created) VALUES

(1, 'Apple', 'Apple Company', 1, '2021-08-30 10:33:53');

Table structure for table `cart`

CREATE TABLE cart (
id int(30) NOT NULL,
client_id int(30) NOT NULL,
inventory_id int(30) NOT NULL,
price double NOT NULL,
quantity int(30) NOT NULL,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

Table structure for table `categories`

CREATE TABLE categories (

id int(30) NOT NULL,
category varchar(250) NOT NULL,
description text DEFAULT NULL,
status tinyint(1) NOT NULL DEFAULT 1,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO categories (id, category, description, status, date_created) VALUES

(1, 'Smart Phone', 'Smart Phone Products', 1, '2021-08-30 10:52:25');

Table structure for table clients

CREATE TABLE clients (

id int(30) NOT NULL,
firstname varchar(250) NOT NULL,
lastname varchar(250) NOT NULL,
gender varchar(20) NOT NULL,
contact varchar(15) NOT NULL,

Dept. of CSE,SJBIT 2022-2023 Page 17

 MOBILE STORE MANAGEMENT SYSTEM

email varchar(250) NOT NULL,

password text NOT NULL,
default_delivery_address text NOT NULL,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO client (id, firstname, lastname, gender, contact, email, password,
default_delivery_address, date_created) VALUES
(1, 'Claire', 'Blake', 'Female', '09123456789', '[email protected]',
'cd74fae0a3adf459f73bbf187607ccea', 'Sample Address', '2021-08-30 15:32:20');

Table structure for table `inventory`

CREATE TABLE inventory (

id int(30) NOT NULL,
product_id int(30) NOT NULL,
quantity double NOT NULL,
price float NOT NULL,
date_created datetime NOT NULL DEFAULT current_timestamp(),
date_updated datetime DEFAULT NULL ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO inventory (id, product_id, quantity, price, date_created, date_updated)

VALUES
(1, 1, 15, 74990, '2021-08-30 13:24:01', NULL);

Table structure for table `orders`

CREATE TABLE orders (

id int(30) NOT NULL,
client_id int(30) NOT NULL,
delivery_address text NOT NULL,
payment_method varchar(100) NOT NULL,
order_type tinyint(1) NOT NULL COMMENT '1= pickup,2= deliver',

Dept. of CSE,SJBIT 2022-2023 Page 18

 MOBILE STORE MANAGEMENT SYSTEM

amount double NOT NULL,

status tinyint(2) NOT NULL DEFAULT 0,
paid tinyint(1) NOT NULL DEFAULT 0,
date_created datetime NOT NULL DEFAULT current_timestamp(),
date_updated datetime DEFAULT NULL ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO orders (id, client_id, delivery_address, payment_method, order_type, amount,

status, paid, date_created, date_updated) VALUES
(1, 1, 'Sample Address', 'Online Payment', 1, 75340, 1, 1, '2021-08-30 15:57:01', '2021-08-30

16:06:19');

Table structure for table `order_list`

CREATE TABLE order_list (

id int(30) NOT NULL,
order_id int(30) NOT NULL,
product_id int(30) NOT NULL,
quantity int(30) NOT NULL,
price double NOT NULL,
total double NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO order_list (id, order_id, product_id, quantity, price, total) VALUES
(1, 1, 1, 1, 74990, 74990),
(2, 1, 3, 1, 350, 350);

Table structure for table `products`

CREATE TABLE products (

id int(30) NOT NULL,
brand_id int(30) NOT NULL,
category_id int(30) NOT NULL,
sub_category_id int(30) NOT NULL,

Dept. of CSE,SJBIT 2022-2023 Page 19

MOBILE STORE MANAGEMENT SYSTEM

name varchar(250) NOT NULL,

specs text NOT NULL,
status tinyint(1) NOT NULL DEFAULT 1,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO products (id, brand_id, category_id, sub_category_id, name, `specs`, status,
date_created) VALUES
(1, 1, 1, 0, 'iPhone Pro Max 12', '<ul class=\\\"techspecs-list\\\" role=\\\"list\\\"
style=\\\"margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding: 0px; list-style:
none;\\\"><li role=\\\"listitem\\\" style=\\\"margin: 0px; padding: 0px;\\\">Super Retina XDR
display</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding:
0px;\\\">6.7-inch (diagonal) all-screen OLED display</li><li role=\\\"listitem\\\"
style=\\\"margin: 0.4em 0px 0px; padding: 0px;\\\">2778-by-1284-pixel resolution at 458
ppi</li></ul><p class=\\\"typography-caption model-caption\\\" style=\\\"margin: 0.8em 0px
0px; padding: 0px; line-height: 1.33337;\\\">The iPhone 12 Pro Max display has rounded
corners that follow a beautiful curved design, and these corners are within a standard
rectangle. When measured as a standard rectangular shape, the screen is 6.68 inches
diagonally (actual viewable area is less).</p><p style=\\\"margin: 0.8em 0px 0px; padding:
0px; line-height: 1.33337;\\\"><br></p><ul class=\\\"techspecs-list\\\" role=\\\"list\\\"
style=\\\"margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding: 0px; list-style:
none;\\\"><li role=\\\"listitem\\\" style=\\\"margin: 0px; padding: 0px;\\\">HDR
display</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding: 0px;\\\">True
Tone</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding: 0px;\\\">Wide
color (P3)</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding:
0px;\\\">Haptic Touch</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding:
0px;\\\">2,000,000:1 contrast ratio (typical)</li><li role=\\\"listitem\\\" style=\\\"margin:
0.4em 0px 0px; padding: 0px;\\\">800 nits max brightness (typical); 1,200 nits max
brightness (HDR)</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding:
0px;\\\">Fingerprint-resistant oleophobic coating</li><li role=\\\"listitem\\\"

Dept. of CSE,SJBIT 2022-2023 Page 20

 MOBILE STORE MANAGEMENT SYSTEM

style=\\\"margin: 0.4em 0px 0px; padding: 0px;\\\">Support for display of multiple languages
and characters simultaneously</li></ul>', 1, '2021-08-30 12:19:22');

Table structure for table sales

CREATE TABLE sales (
id int(30) NOT NULL,
order_id int(30) NOT NULL,
total_amount double NOT NULL,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO sales (id, order_id, total_amount, date_created) VALUES

(1, 1, 75340, '2021-08-30 15:57:01');

Table structure for table `sub_categories`

CREATE TABLE sub_categories (

id int(30) NOT NULL,
parent_id int(30) NOT NULL,
sub_category varchar(250) NOT NULL,
description text NOT NULL,
status tinyint(1) NOT NULL DEFAULT 1,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO sub_categories (id, parent_id, sub_category, description, status, date_created)

VALUES
(1, 3, 'Batteries', 'Mobile Batteries', 1, '2021-08-30 11:28:40');

Table structure for table `system_info`

CREATE TABLE system_info (

id int(30) NOT NULL,

Dept. of CSE,SJBIT 2022-2023 Page 21

 MOBILE STORE MANAGEMENT SYSTEM

meta_field text NOT NULL,

meta_value text NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO system_info (id, meta_field, meta_value) VALUES

(1, 'name', 'Mobile Store Management System - PHP');

Table structure for table `users`

CREATE TABLE users(

id int(50) NOT NULL,
firstname varchar(250) NOT NULL,
lastname varchar(250) NOT NULL,
username text NOT NULL,
password text NOT NULL,
avatar text DEFAULT NULL,
last_login datetime DEFAULT NULL,
type tinyint(1) NOT NULL DEFAULT 0,
date_added datetime NOT NULL DEFAULT current_timestamp(),
date_updated datetime DEFAULT NULL ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO users (id, firstname, lastname, username, password, avatar, last_login, type,
date_added, date_updated) VALUES
(1, 'Adminstrator', 'Admin', 'admin', '0192023a7bbd73250516f069df18b500',
'uploads/1624240500_avatar.png', NULL, 1, '2021-01-20 14:02:37', '2021-06-21 09:55:07');

Indexes for table `brands`

ALTER TABLE brands

ADD PRIMARY KEY (id);
--
Indexes for table `cart’

Dept. of CSE,SJBIT 2022-2023 Page 22

 MOBILE STORE MANAGEMENT SYSTEM

ALTER TABLE cart

ADD PRIMARY KEY (id);
--
Indexes for table `categories`

ALTER TABLE categories

ADD PRIMARY KEY (id);
Indexes for table `clients`

ALTER TABLE clients

ADD PRIMARY KEY (id);
--
Indexes for table `inventory`

ALTER TABLE inventory

ADD PRIMARY KEY (id);
--
Indexes for table `orders`

ALTER TABLE orders

ADD PRIMARY KEY (id);
--
Indexes for table `order_list`

ALTER TABLE order_list

ADD PRIMARY KEY (id);
--
Indexes for table `products`

ALTER TABLE products

ADD PRIMARY KEY (id);
--
Indexes for table `sales`
ALTER TABLE sales
ADD PRIMARY KEY (id);

Dept. of CSE,SJBIT 2022-2023 Page 23

 MOBILE STORE MANAGEMENT SYSTEM

--
Indexes for table `sub_categories`

ALTER TABLE sub_categories

ADD PRIMARY KEY (id);
--
Indexes for table `system_info`

ALTER TABLE system_info

ADD PRIMARY KEY (id);
--
Indexes for table `users`

ALTER TABLE users

ADD PRIMARY KEY (id);

AUTO_INCREMENT for table `brands`

ALTER TABLE brands

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=9;

AUTO_INCREMENT for table `cart`

ALTER TABLE cart

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;

AUTO_INCREMENT for table `categories’

ALTER TABLE categories

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;

AUTO_INCREMENT for table `clients`

Dept. of CSE,SJBIT 2022-2023 Page 24

MOBILE STORE MANAGEMENT SYSTEM

ALTER TABLE clients

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

AUTO_INCREMENT for table `inventory`

ALTER TABLE inventory

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;

AUTO_INCREMENT for table `orders`

ALTER TABLE orders

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

AUTO_INCREMENT for table `order_list`

ALTER TABLE order_list

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;

AUTO_INCREMENT for table `products`

ALTER TABLE products

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
AUTO_INCREMENT for table `sales`

ALTER TABLE sales

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

AUTO_INCREMENT for table `sub_categories`

ALTER TABLE sub_categories

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;

Dept. of CSE,SJBIT 2022-2023 Page 25

MOBILE STORE MANAGEMENT SYSTEM

AUTO_INCREMENT for table `system_info`

ALTER TABLE system_info

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=15;

AUTO_INCREMENT for table `users`

ALTER TABLE users

MODIFY id int(50) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
COMMIT;

Dept. of CSE,SJBIT 2022-2023 Page 26

MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 5
SCREENSHOTS
5.1 RESULT OUTPUT
ADMIN LOGIN

Fig 5.1 Admin Login

 The figure 5.1 shows the screenshot of the Admin Login of our Project.
 This login page allows a Admin to enter their username and password to website.

ADMIN HOME

Fig 5.2 Admin Home

 The figure 5.2 shows the screenshot of the Admin Home of our Project.

Dept. of CSE,SJBIT 2022-2023 Page 27

MOBILE STORE MANAGEMENT SYSTEM

 From this window, the user can navigate to the various other windows (like Product
List, Inventory List, Maintance) using the navigation bar.

PRODUCT LIST

Fig 5.3 Shows Product List

 The figure 5.3 shows the screenshot of the Product List of our Project.
 It will show product details like as (name, Brand, specs,status).
INVENTORY LIST

Dept. of CSE,SJBIT 2022-2023 Page 28

MOBILE STORE MANAGEMENT SYSTEM

Fig 5.4 Shows Inventory list

 The figure 5.4 shows the screenshot of the Inventory List of our Project.
 It will show Inventory details like as (Product, Price, Stock,Action).
ORDER LIST

Fig 5.5 Shows Order list

 The figure 5.5 shows the screenshot of the Order list of our Project.
 It will show Order list details like as (Date Order, Client, Total
Amount,Paid,Status,Action).

Dept. of CSE,SJBIT 2022-2023 Page 29

 MOBILE STORE MANAGEMENT SYSTEM

SALES REPORT
Fig 5.6 Sales Report

 The figure 5.6 shows the screenshot of the Sales Report of our Project.
 It will show Sales Report details like as (DateTime, Product, Client, QTY, Amount).

BRAND LIST
Fig 5.7 Brand list

• The figure 5.7 shows the screenshot of the Brand list of our Project.

Dept. of CSE,SJBIT 2022-2023 Page 30

 MOBILE STORE MANAGEMENT SYSTEM

• It will show Brand list details like as (Date Create, Brand Name, Description, Status,
Action).
CATEGORY LIST

Fig 5.8 Category list

• The figure 5.8 shows the screenshot of the Brand list of our Project.
• It will show Category list details like as (Date Create, Brand Name, Description, Status,
Action).

USER LOGIN

Fig 5.9 User login

Dept. of CSE,SJBIT 2022-2023 Page 31

MOBILE STORE MANAGEMENT SYSTEM

 The figure 5.9 shows the User login page of the project.
 This signup page allows users to create a new account on a website or application.

USER HOME
Fig 5.10 User home Screen

 The figure 5.10 shows the screenshot of the User Home page of our Project.
 From this window, the user can navigate to the various other windows (like Smart Phone,
All Categories, About Us) using the navigation bar.

Dept. of CSE,SJBIT 2022-2023 Page 32

MOBILE STORE MANAGEMENT SYSTEM

SMART PHONE
Fig 5.11 Smart phone screen

 The figure 5.11 shows the screenshot of the Smart phone page of our Project.
 This page show the phone details.

ACCESSORIES
Fig 5.12 Accessories Screen

Dept. of CSE,SJBIT 2022-2023 Page 33

 MOBILE STORE MANAGEMENT SYSTEM

• The figure 5.12 shows the screenshot of the Accessories page of our Project.
• It will shows what type of Accessories.

PRODUCT CATEGORIES
Fig 5.13 Product Categories

• The figure 5.13 shows the screenshot of the Product Categories page of our Project.
• It will show the all the details of (Accessories, Mobile Hardware, Smart Phone, External
Storage)

Dept. of CSE,SJBIT 2022-2023 Page 34

 MOBILE STORE MANAGEMENT SYSTEM

USER CART
Fig 5.14 User Cart

• The figure 5.14 shows the screenshot of the User Cart page of our Project.
• It will shows the (Cart List, Grand Total).

Dept. of CSE,SJBIT 2022-2023 Page 35

MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 6

CONCLUSION AND FUTURE SCOPE

Conclusion

The “Mobile Store Management System” has been created with the intention of providing a
user with application which will suffice all needs for the details of mobile phones and other
updates.

All the requirements specifications were followed as far as possible and few additional
features were added that can make the application more users friendly and less complicated.

The project “Mobile Store Management System” has been developed with the proper
guidance from the client.

We hope that “Mobile Store Management System” fulfils all the needs in possible manner.

Future scope:

 More of number item details can be inserted into the database.

 It can be integrated with the web for universal access.
 E-payment.
 Upgrading the performance for better & faster search.
 System will be portable with shared database.

Dept. of CSE,SJBIT 2022-2023 Page 36