VISVESVARAYA TECHNOLOGICAL UNIVERSITY

"Jnana Sangama", Belagavi - 590 018, Karnataka

A Database Management Systems Mini Project

report on

“EYECON”
Submitted in partial fulfillment of the requirement for the award of Degree of
Bachelor of Engineering
In
Computer Science & Engineering

Submitted by

SESHANKOTI DHANASANJAY 1AY20CS137

SHAMANTH K V 1AY20CS140

Under the guidance of

Mrs. SNEHA N P
Asst Professor, Dept. of CSE

AIT,Bangalore

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

ACHARYA INSTITUTE OF TECHNOLOGY
(AFFILIATED TO VISVESVARAYA TECHNOLOGICAL UNIVERSITY, BELAGAVI.APPROVED BY AICTE, NEW DELHI,
ACCREDITED BY NAAC, NEW DELHI )
Acharya Dr. Sarvepalli Radhakrishnan Road, Soldevanahalli, Bengaluru-560107

2022-23
 DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
ACHARYA INSTITUTE OF TECHNOLOGY
(AFFILIATED TO VISVESVARAYA TECHNOLOGICAL UNIVERSITY, BELAGAVI.APPROVED BY AICTE, NEW DELHI, ACCREDITED
BY NAAC, NEW DELHI)
Acharya Dr. Sarvepalli Radhakrishnan Road, Soldevanahalli, Bengaluru-560107

Certificate
This is to Certify that the mini-project work entitled “EYECON” is a bonafide work
carrieout by Seshankoti Dhanasanjay(1AY20CS137) and Shamanth K
V(1AY20CS140) 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-23. It is certified that all
corrections/suggestions indicated for Internal Assessment have been incorporated in the
report deposited in the departmental library. The project has been approved as it
satisfies the academic requirements in respect of mini project work prescribed for the
Bachelor of Engineering Degree.

Mrs. SNEHA N P Prof. Ajith Pandyana

Asst Prof, Dept. of CSE HOD, Dept of CSE

Name of the Examiners Signature with date

1.

2.
 ACKNOWLEDGEMENT

We express our gratitude to our institution and management for providing us with
good infrastructure, laboratory, facilities and inspiring staff whose gratitude was of immense
help in completion of this seminar successfully.

We express our sincere gratitude to Dr. Rajath Hegde M M, Principal, Acharya

Institute of Technology for providing required environment and valuable support for
developing this mini project.

Our sincere thanks to Dr. Ajith Padyana, Asso.professor ,Head of the Department,
Computer Science and Engineering, Acharya Institute of Technology for his valuable support
and for rendering us resources for this mini project work.

We express our gratitude to Mrs. Sneha N P, Asst. Professor Dept. Computer Science
and Engineering, Acharya Institute of Technology who guided us with valuable suggestions in
completing this mini-project at every stage.

Our gratitude should be rendered to many people who helped us in all possible ways.

SESHANKOTI DHANSANJAY(1AY20CS137)

SHAMANTH K V(1AY20CS140)

(i)
 ABSTRACT

A spectacles management system is a software application that is used to track and manage
the inventory, sales, and distribution of eyeglasses and other eyewear. It is typically used by
opticians, eyewear retailers, and other businesses that sell and distribute eyewear. The system
includes features for storing and organizing information about the different types of eyewear
available, including the frame style, lens type, and other features. It may also include tools for
tracking the inventory levels of different eyewear products, as well as sales and order data , In
addition to managing the inventory and sales of eyewear, a spectacles management system
may also include features for managing customer information and orders, generating reports
and analytics, and automating key business processes. It can help businesses to streamline
their operations, improve customer service, and increase efficiency.

(ii)
 TABLE OF CONTENTS

Acknowledgement (i)
Abstract (ii)
Table of contents (iii)
Table of Figure (iv)

CHAPTER 1: INTRODUCTION…………………………………………..1
1.1 Introduction to DBMS 1
1.1.1 Why DBMS? 1
1.1.2 Database applications 2
1.1.3 Advantages of DBMS 2
1.1.4 Components of DBMS 3
1.1.5 Three-Schema architecture 4

CHAPTER 2: SYSTEM REQUIREMENTS………………………………5

2.1 Hardware Requirements 5
2.2 Software Requirements 5

CHAPTER 3: DESIGN……………………………………………………...6
3.1 ER Diagram 6
3.2 Schema Diagram 7

CHAPTER 4: IMPLEMENTATION……………………………………….8
4.1 Tables 8
4.1.1 ADMIN 8
4.1.2 CUSTOMER 9
4.1.2 BILLLING 10
4.1.3 RETURN_ORDER 11
4.1.4 PRODUCTS 12
4.1.5 ORDERS 13
4.2 Triggers and routines 12
4.3 frontend design 13

CHAPTER 5: SNAPSHOTS………………………………………………..18
Conclusion & Future Enhancements………………………………………26
Bibliography…………………………………………………………………27

(iii)
 TABLE OF FIGURES

1.1 Components of Database Management System 3

1.2 Architecture of database system 4
3.1 Entity Relationship Diagram 6
3.2 Schema Diagram 7
5.1 Snapshot of admin login page 18
5.2 Snapshot of admin dashboard 19
5.3 Snapshot of product page 10
5.4 Snapshot of customers page 21
5.5 Snapshot of orders page 22
5.6 Snapshot of billing page 23
5.7 Snapshot of return order page 24
5.8 Snapshot of admin page 25

(iv)
 EYECON

CHAPTER 1
INTRODUCTION
Spectacle management system is a type of database management system (DBMS) that
allows admin to access and manage their data over the internet. It is a cloud-based solution
that allows admin to store, retrieve, and analyze large amounts of data in real-time. It
eliminates the need for expensive hardware and maintenance costs as the infrastructure is
maintained by the provider. It is designed to be highly scalable and can handle a large number
of concurrent requests. Spectacle management system offers advanced features such as
automatic data replication, data backup and recovery, and security features to protect data
against unauthorized access. It is a flexible and cost-effective solution for businesses of all
sizes, as it can be scaled to meet the specific needs of the organization.
1.1 Introduction to DBMS
DBMS stands for Database Management System. We can break it like this DBMS =
DataBase + Management System. The database is a collection of data and a Management
System is a set of programs to store and retrieve those data. Basically, DBMS is a software
tool to organize (create, retrieve, update and manage) data in a database.

The main aim of a DBMS is to supply a way to store up and retrieve database
information that is both convenient and efficient. By data, we mean known facts that can be
recorded and that have embedded meaning. Normally people use software such as DBASE IV
or V, Microsoft ACCESS, or EXCEL to store data in the form of a database. A datum is a unit
of data. Meaningful data combined to form information. Hence, information is interpreted
data – data provided with semantics. MS. ACCESS is one of the most common examples of
database management software.

Database systems are meant to handle large collections of information. Management

of data involves both defining structures for the storage of information and providing
mechanisms that can do the manipulation of those stored information. Moreover, the database
system must ensure the safety of the information stored, despite system crashes or attempts at
unauthorized access.

1.1.1 Why DBMS?

● To develop software applications in less time.

Dept. of CSE, AIT, Bangalore 1

 EYECON

● Data Independence and efficient use of data.

● For uniform data administration.
● For data integrity and security.
● For concurrent access of data, and data recovery from crashes.
● To use user-friendly declarative query language.

1.1.2 Database applications

● Telecom: There is a database to keep track of the information regarding calls made,
network usage, customer details, etc. Without the database systems, it is hard to
maintain that huge amount of data that keeps updating every millisecond.
● Industry: Where it is a manufacturing unit, warehouse, or distribution center, each
one needs a database to keep the records of ins and outs. For example, distribution
centers should keep a track of the product units that are supplied into the centre as well
as the products that got delivered out from the distribution centre on each day; this is
where DBMS comes into the picture.
● Education sector: Database systems are frequently used in schools and colleges to
store and retrieve the data regarding student details, staff details, course details, exam
details, payroll data, attendance details, fees details etc. There is a hell lot of
interrelated data that needs to be stored and retrieved efficiently.
● Online shopping: You must be aware of the online shopping websites such as
Amazon, Flipkart etc. These sites store the product information, your addresses and
preferences, credit details and provide you the relevant list of products based on your
query. All this involves a Database management system.
● Banking system: For storing customer info, tracking day to day credit and debit
transactions, generating bank statements etc. All this work has been done with the help
of Database management systems.

1.1.3 Advantages of DBMS

A DBMS manages data and has many advantages.
● Data Independence: Application programs should be as free or independent as
possible from details of data representation and storage. DBMS can supply an abstract
view of the data for insulating application code from such facts.

Dept. of CSE, AIT, Bangalore 2

 EYECON

● Efficient data access: DBMS utilizes a mixture of sophisticated concepts and

techniques for storing and retrieving data competently and this feature becomes
important in cases where the data is stored on external storage devices.
● Data integrity and security:  If data is accessed through the DBMS, the DBMS can
enforce integrity constraints on the data.
● Data administration: When several users share the data, integrating the
administration of data can offer major improvements. Experienced professionals
understand the nature of the data being managed and can be responsible for organizing
the data representation to reduce redundancy and make the data to retrieve efficiently.
● Providing backup and recovery: A DBMS must provide facilities for recovering
from hardware or software failures. The backup and recovery subsystem of the DBMS
is responsible for recovery.
● Permitting inferencing and actions using rules: Some database systems provide
capabilities for defining deduction rules for inferencing new information from the
stored database facts.
1.1.4 Components of DBMS

Fig-1.1: Components of a Database Management System

● Users: Users may be of any kind such as DB administrator, System developer or

database users.

Dept. of CSE, AIT, Bangalore 3

 EYECON

● Database application: Database application may be Departmental, Personal,

organization’s and / or Internal.

● DBMS: Software that allows users to create and manipulate database access.
● Database: Collection of logical data as a single unit.
● Database access language: This is used to access the data to and from the database,
to enter new data, update existing data, or retrieve required data from databases. The
user writes a set of appropriate commands in a database access language, submits
these to the DBMS, which then processes the data and generates and displays a set of
results into a user readable form.
1.1.5 Three-Schema architecture

Fig-1.2: Architecture of database system

The levels form a three-level architecture that includes an external, a conceptual, and an
internal level. The way users recognize the data is called the external level. The way the
DBMS and the operating system distinguish the data is the internal level, where the data is
actually stored using the data structures and file. The conceptual level offers both the mapping
and the desired independence between the external and internal levels.

Dept. of CSE, AIT, Bangalore 4

 EYECON

CHAPTER 2
SYSTEM REQUIREMENTS
2.1 Hardware Requirements
 Processor: Intel Core2 Quad @ 2.4Ghz on Windows® Vista 64-Bit / Windows® 7
64-Bit / Windows® 8 64-Bit / Windows® 8.1 64-Bit.
 RAM: 2GB of RAM
 Memory: 256GB Hard drive
 Keyboard: MS-compatible keyboard
 Mouse: MS-compatible mouse

2.2 Software Requirements

 Operating system: Windows® Vista 64-Bit / Windows® 7 64-Bit / Windows® 8 64-
Bit / Windows® 8.1 64-Bit.
 Front end: HTML, BOOTSTRAP,CSS, JAVASCRIPT
 Back end: MySQL and PHP
 IDE:VS Code
 Text Editor: VS Code
 Database: MySQL
 Server: XAMPP enabled with Apache and MySQL
 Browser: Chrome etc.

2.3 Functional Requirements

 New Customer Registration: The system should allow a new customer to added by
filling the required details.
 Admin Login: The admin can login to his/her account and view the details of every
customer and also the product and modify it.
 Automatic update to database once a new customer registered. Also, if a customer
places an order or returns the order , it gets automatically updated to the database.

2.4 Non-functional Requirements

 Performance Requirements: Performance of the system should be fast and

 accurate. System shall handle expected and unexpected errors. Should be able
 to handle large amount of data.
 Safety Requirements: Must be two servers, one main server and one backup server.
 Security Requirements: Admin authentication and validation of members using their
password. Proper accountability which includes not allowing a member to see other
member’s account. Only admin will see and manage all user’s account. Proper user
authentication should be provided.

Dept. of CSE, AIT, Bangalore 5

 EYECON

CHAPTER 3
DESIGN
3.1 ER Diagram

Fig-3.1: Entity Relationship Diagram

1:N
 1 admin can register many customer
 1 admin can calculates N number of customers.
 N customers can be registered.
M:N
 M customers can order N products
 M customers can place N return_order

Dept. of CSE, AIT, Bangalore 6

 EYECON

3.2 Schema Diagram

Fig-3.2: Schema diagram

Dept. of CSE, AIT, Bangalore 7

 EYECON

CHAPTER 4
IMPLEMENTATION
4.1 TABLES
4.1.1 ADMIN
CREATE TABLE `admin` (
`username` varchar(20) NOT NULL,
`password` varchar(20) NOT NULL
);

INSERT INTO `admin` (`username`, `password`) VALUES

('shamanth', '05052003'),
('dhansanjay', '07052003');
COMMIT;

ENTITY NAME ATTRIBUTES CONSTRAINTS

username PRIMARY KEY

ADMIN

password Not null

4.1.2 CUSTOMER
CREATE TABLE `customer` (
`cid` int(20) NOT NULL,
`cname` varchar(255) NOT NULL,
`address` varchar(255) NOT NULL,
`phone_no` int(20) NOT NULL,
`purchase` varchar(255) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;

ALTER TABLE `customer`

ADD PRIMARY KEY (`cid`);

INSERT INTO `customer` (`cid`, `cname`, `address`, `phone_no`, `purchase`) VALUES

(5, 'sharath', 'karnataka', 934325235, 'returned'),
(6, 'sanjay', 'andra pradesh', 2147483647, NULL);

ENTITY NAME ATTRIBUTES CONSTRAINTS

Dept. of CSE, AIT, Bangalore 8

 EYECON

cid PRIMARY KEY

CUSTOMER cname Not null

address Not null

phone_no Not null

purchase Not null

4.1.3 BILLING
CREATE TABLE `billing` (
`bid` int(20) NOT NULL,
`cid` int(20) NOT NULL,
`warranty` int(20) NOT NULL,
`date` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp(),
`quantity` int(20) NOT NULL,
`id` int(20) NOT NULL);

ALTER TABLE `billing`

ADD PRIMARY KEY (`bid`),
ADD KEY `cid` (`cid`),
ADD KEY `id` (`id`);

ALTER TABLE `billing`

MODIFY `bid` int(20) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;

INSERT INTO `billing` (`bid`, `cid`, `warranty`, `date`, `quantity`, `id`) VALUES
(3, 5, 3, '2023-01-22 10:11:52', 1, 4),
(4, 6, 2, '2023-01-22 10:12:07', 4, 5);

ENTITY NAME ATTRIBUTES CONSTRAINTS

bid PRIMARY KEY

cid Not null

Dept. of CSE, AIT, Bangalore 9

 EYECON

BILLING date Not null

warranty Not null

quantity Not null

id Not null

4.1.4 RETURN_ORDER
CREATE TABLE `return_order` (
`rid` int(20) NOT NULL,
`reason` varchar(225) NOT NULL,
`cid` int(20) NOT NULL,
`date` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp(),
`id` int(20) NOT NULL,
`bid` int(20) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;

ALTER TABLE `return_order`

ADD PRIMARY KEY (`rid`),
ADD KEY `cid` (`cid`),
ADD KEY `id` (`id`),
ADD KEY `bid` (`bid`);

INSERT INTO `return_order` (`rid`, `reason`, `cid`, `date`, `id`, `bid`) VALUES
(3, 'damaged product delivered', 5, '2023-01-22 10:21:38', 4, 3);

ENTITY NAME ATTRIBUTES CONSTRAINTS

rid PRIMARY KEY

reason Not null

RETURN_ORDER cid Not null

id Not null

date Not null

Dept. of CSE, AIT, Bangalore 10

 EYECON

4.1.5 PRODUCTS
CREATE TABLE `products` (
`id` int(20) NOT NULL,
`name` varchar(255) NOT NULL,
`price` int(20) NOT NULL,
`image` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
ALTER TABLE `products`
ADD PRIMARY KEY (`id`);
INSERT INTO `products` (`id`, `name`, `price`, `image`) VALUES
(4, 'spects', 345, 'adminloginbg.jpg'),
(5, 'titan', 700, 'bckg.png');

ENTITY NAME ATTRIBUTES CONSTRAINTS

id PRIMARY KEY

name Not null

PRODUCTS price Not null

image Not Null

4.1.6 ORDERS
CREATE TABLE `orders` (
`oid` int(20) NOT NULL,
`cid` int(20) NOT NULL,
`date` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp(),
`id` int(20) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;

ALTER TABLE `orders`

ADD PRIMARY KEY (`oid`),
ADD KEY `cid` (`cid`),
ADD KEY `id` (`id`);

INSERT INTO `orders` (`oid`, `cid`, `date`, `id`) VALUES

Dept. of CSE, AIT, Bangalore 11

 EYECON

(18, 5, '2023-01-22 10:08:16', 4),

(19, 5, '2023-01-22 10:08:27', 5);

ENTITY NAME ATTRIBUTES CONTSTRAINTS

oid PRIMARY KEY

ORDERS

cid Not null

date Not null

id Not null

4.2 TRIGGERS AND ROUTINES

4.2.1 TRIGGERS
Trigger to update purchase status of the customer when he place an order
 CREATE TRIGGER
`chng_status` AFTER INSERT ON `orders`
FOR EACH ROW UPDATE customer set purchase='ordered' WHERE cid=new.cid;

Trigger to update purchase status of the customer when he place a return order
 CREATE TRIGGER
`ret_status` AFTER INSERT ON `return_order`
FOR EACH ROW UPDATE customer set purchase='returned' WHERE cid=new.cid;

4.2.2 ROUTINES
Routine to retrieve data of customer who placed atleast one order.
CREATE DEFINER=`root`@`localhost` PROCEDURE ‘ordered customer details’()
Select c.*,o.oid from customer c ,orders o where c.cid=o.oid.

Routine to retrieve data of product which has been orderes.

Dept. of CSE, AIT, Bangalore 12

 EYECON

CREATE DEFINER=`root`@`localhost` PROCEDURE ‘ordered customer details’()

Select p.*,o.oid from products p,orders o where p.cid=o.oid.

4.3 FRONT END DESIGN:

4.3.1 adminconnection.php
<?php

$conn=mysqli_connect("localhost","root","","eyeconstore");

if(mysqli_connect_error()){

echo"cannot connect to datbase";

exit();

?>

4.3.2 adminlogin.php

<?php require("adminconnection.php")?>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Admin login</title>
<link rel="stylesheet" href="adminlogin.css">
</head>
<body>
<div class="container">
<div class="myform">
<form method="post"action="<?php echo( $_SERVER['PHP_SELF'])?>">
<h2>
ADMIN LOGIN
</h2>
<input type="text" name="username"placeholder="name" required>
<input type="password"name="password" placeholder="password" >
<button type="submit" name="login">login</button>
</form>
</div>
<div class="image">
<img src="adminloginbg.jpg" width="300px">

Dept. of CSE, AIT, Bangalore 13

 EYECON

</div>
</div>
<?php
function input_filter($data)
{
$data=trim($data);
$data=stripslashes($data);
$data=htmlspecialchars($data);
return $data;
}
if(isset($_POST['login']))
{
$username= input_filter($_POST['username']);
$password=input_filter($_POST['password']);
$username=mysqli_real_escape_string($conn,$username);
$password=mysqli_real_escape_string($conn,$password);

$query= "SELECT * FROM `admin` WHERE `username`=? AND `password`=?";

if($stmt=mysqli_prepare($conn,$query))
{
mysqli_stmt_bind_param($stmt,"ss",$username,$password);
mysqli_stmt_execute($stmt);
mysqli_stmt_store_result($stmt);
if(mysqli_stmt_num_rows($stmt)==1)
{
session_start();
$_SESSION['AdminLoginId']=$username;
header("location:adminpanelz.php");
}
else{
echo"<script>alert('invalid adminname or password');</script>";
}
mysqli_stmt_close($stmt);
}
else{
echo"<script>alert('sql query wrong');</script>";
}
}
?>
</body>
</html>

4.3.3 product.php

Dept. of CSE, AIT, Bangalore 14

 EYECON

<?php
@include 'adminconnection.php';
if(isset($_POST['add_product'])){
$product_name = $_POST['product_name'];
$product_price = $_POST['product_price'];
$product_image = $_FILES['product_image']['name'];
$product_image_tmp_name = $_FILES['product_image']['tmp_name'];
$product_image_folder = 'uploaded_img/'.$product_image;
if(empty($product_name)||empty($product_price)||empty($product_image)){
$message[] = 'please fill out all';
}else{
$insert = "INSERT INTO products(name, price, image) VALUES('$product_name',
'$product_price', '$product_image')";
$upload = mysqli_query($conn,$insert);
if($upload){
move_uploaded_file($product_image_tmp_name, $product_image_folder);
$message[] = 'new product added successfully';
}else{
$message[] = 'could not add the product';
}
}
};
if(isset($_GET['delete'])){
$id = $_GET['delete'];
mysqli_query($conn, "DELETE FROM products WHERE id = $id");
header('location:product.php');
};
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>admin page</title>
<!-- font awesome cdn link -->
<link rel="stylesheet”
href=https://cdnjs.cloudflare.com/ajax/libs/fontawesome/5.15.4/css/all.min.css>
<!-- custom css file link -->
<link rel="stylesheet" href="product.css">
</head>
<body>
<?php
?>

Dept. of CSE, AIT, Bangalore 15

 EYECON

<div class="container">
<div class="admin-product-form-container">
<form action="<?php $_SERVER['PHP_SELF'] ?>"
method="post"enctype="multipart/form-data">
<h3>add a new product</h3>
<input type="text" placeholder="enter product name" name="product_name"
class="box">
<input type="number" placeholder="enter product price" name="product_price"
class="box">
<input type="file" accept="image/png, image/jpeg, image/jpg" name="product_image"
class="box">
<input type="submit" class="btn" name="add_product" value="add product">
<a href="adminpanelz.php" class="btn">go back!</a>
</form>
</div>
<?php
$select = mysqli_query($conn, "SELECT * FROM products");
?>
<table class="product-display-table">
<thead>
<tr>
<th>product id</th>
<th>product image</th>
<th>product name</th>
<th>product price</th>
<th>action</th>
</tr>
</thead>
<?php while($row = mysqli_fetch_assoc($select)){ ?>
<tr>
<td><?php echo $row['id']; ?></td>
<td><img src="uploaded_img/<?php echo $row['image']; ?>" height="100"
alt=""></td>
<td><?php echo $row['name']; ?></td>
<td>$<?php echo $row['price']; ?>/-</td>
<td>
<a href="product_update.php?edit=<?php echo $row['id']; ?>" class="btn"> <i
class="fas fa-edit"></i> edit </a>
<a href="product.php?delete=<?php echo $row['id']; ?>" class="btn"> <i class="fas
fa-trash"></i> delete </a>
</td>
</tr>
<?php } ?>
</table>

Dept. of CSE, AIT, Bangalore 16

 EYECON

</div>
</body></html>

CHAPTER 5
SNAPSHOTS

The following snapshot contains the login page

Dept. of CSE, AIT, Bangalore 17

 EYECON

Fig-5.1: Snapshot of Admin login page

1. The login page screen contains an input text box for username and password
2. Admin can input his name and password to login.

Validators Given:
1. Admin needs to enter id and a password.
2. Admin will be able to sign in only when he has been registered.
3. Id validation is given by a validating with a regex expression.

Dept. of CSE, AIT, Bangalore 18

 EYECON

Fig-5.2: Snapshot of admin dashboard

As soon as the admin has successfully signed in, he is forwarded to this page.
This page contains information about
 No of spectacle updated
 number of customer listed
 total no of orders
 total no of return orders

Dept. of CSE, AIT, Bangalore 19

 EYECON

Validators given:
1. The following page will not be rendered if the user is not successfully logged in.
2. This information is available to him only if he is a admin.

Fig-5.3: Snapshot of product page

This page shows details of all the spectacle whch have been registered. the admin can either
edit or delete details of a spectacle. The admin can also add new spectacle by clicking on the
add spectacle .
.
Validators given:
1. Spectacle id is auto generated.
2. During edit the attributes cannot be empty.
3. During delete there will be a pop up that confirms the delete request.

Dept. of CSE, AIT, Bangalore 20

 EYECON

Fig-5.4: Snapshot of customer page

The above snapshot shows the details of the customers .

● Admin can view the platform of the customer.
● Admin can also edit or delete the customer.
● The admin can add new customer by clicking add customer button.

Validators given:
 The following page will not be rendered if the admin is not successfully logged in.

Dept. of CSE, AIT, Bangalore 21

 EYECON

Fig-5.5: Snapshots of orders page

The is a snapshot of the orders page

 Here admin accounts the order ordered by customer.
 He can view the platform before order is registered.

Validators given:
1. The following page will not be rendered if the admin has not successfully
logged in.
2. Order id is updated automatically for each order .
3. During edit the attributes cannot be empty.
4. During delete there will be a pop up that confirms the delete request.

Dept. of CSE, AIT, Bangalore 22

 EYECON

Fig-5.6: Snapshot of billing page

The is a snapshot of billing page.

● The admin can see which order has be billed.
● It shows the customer id and order.
Validators given:
4. The following page will not be rendered if the admin has not successfully registered.
5. Billing invoice id is created automatically.
6. During edit the attributes cannot be empty.
7. During delete there will be a pop up that confirms the delete request.

Dept. of CSE, AIT, Bangalore 23

 EYECON

Fig-5.7: Snapshot of return_order page

The is a snapshot of the return order page.

 The admin can register a return order placed by cutomer.
 He can also mention the reason for returning the order.

Validators given:
1. The following page will not be rendered if the admin has not successfully registered.
2. During edit the attributes cannot be empty.
3. During delete there will be a pop up that confirms the delete request.

Dept. of CSE, AIT, Bangalore 24

 EYECON

Fig-5.8: admin page

● The following page shows the admin page.
Validators given:
1. The following page will not be rendered if the admin has not successfully registered.
2. The admin can add new admin for the websites.
3. During edit the attributes cannot be empty.
4. During delete there will be a pop up that confirms the delete request.

Dept. of CSE, AIT, Bangalore 25

 EYECON

CONCLUSION & FUTURE ENHANCEMENT

Conclusion:
In conclusion, a spectacle management system can greatly improve the efficiency and
effectiveness of managing an spectacle store . It can automate many tasks such as inventory
management, order processing, and customer management. By providing a user-friendly and
streamlined system, it can also enhance the customer experience and potentially increase
sales. Overall, implementing an spectacle management system can be a valuable investment
for any online spectacle store.
Future Enhancement:
There are several potential future enhancements for an online spectacle store management
system. Some possibilities include:
 Integrating virtual try-on technology, which would allow customers to virtually try
on different frames and see how they look on them before making a purchase.
 Adding a personalized recommendation system that suggests products to
customers based on their browsing and purchase history.
 Implementing a virtual optometrist feature that allows customers to get their eyes
checked online and receive a prescription that they can use to purchase glasses.
 Incorporating augmented reality technology which allows customers to see how a
particular pair of glasses would look on them in a virtual environment before
making a purchase.
 Enhancing the mobile and voice-enabled support, which would allow customers to
use voice commands to search for products and place orders, providing a more
convenient shopping experience.
 Implementing automation for the supply chain management to improve the speed,
efficiency and cost of delivery.
These are just a few examples of potential enhancements that could be made to an online
spectacle store management system in the future. The technology is rapidly advancing, and
there will be many more possibilities as the technology continue to evolve.

Dept. of CSE, AIT, Bangalore 26

 EYECON

BIBLIOGRAPHY

Web References:
1. https://www.w3schools.in/dbms/intro/
2. https://beginnersbook.com/2015/04/dbms-introduction/
3. https://getbootstrap.com/
4. https://developer.mozilla.org/en-US/
5. https://www.google.com/
6. http://www.youtube.com/

Book References:
1. Fundamentals of Database Systems, RamezElmasri and Shamkant B. Navathe, 7th Edition,
2017, Pearson.

Dept. of CSE, AIT, Bangalore 27