Projarun

Online Watch Shop system
1.1 ABOUT THE PROJECT
Computer technology makes a dramatic break with the past: Most companies are
designed and use their applications that which the application runs on the user access a
maintained manage file or database. The concept of computerized report has important
in the industry, which needs information to retrieve in the fast and efficient way.
Time is an essential element in our daily life so are watches Back in the
days, watches were essential tools that virtually everyone used. And they did so because it
was the only real way to keep track of time.. People couldn’t just take up their phone and
look at what time it was like you can today, and therefore, be carrying a watch was crucial
for living a smooth life – from showing up at work in time – to perfect timing and
synchronizing a military attack.
Online Watch Store is a store that helps a user or customer to purchase watches online.
It contains watches of different brands for men, women, and kids. Users can log in or
sign up with their email id, password, and phone number. An online watch store helps
the user choose a preferred watch from the given watches. Each watch has its price
mentioned with it. A user can select a preferred payment method. The address of users
can be mentioned so that the selected product can be delivered
Rajagiri College of Management and Applied Sciences Page No 1

2.1 SYSTEM STUDY
The study of existing system deals with the work needed to carry out preliminary
investigation. The study of system can be performed only on the existing system.
Previously the account maintained manually. It take long time, It invokes highest cost
If account books are missed it is difficult to retrieve the data. In existing system the
data are maintained manually. So retreving the information is very slow and also it
requires lot of manpower to the organize the data and to consolidate
System study refers to the process of examining a situation with the intent of
improving it through better process and methods. System study is therefore, the
process of gathering and interpreting facts, diagnosing problem and using the
information to recommend changes in the system, in other words, it means a detailed
explanation or description. Before computerizing a system under consideration, it
must be analysed. We need to study how it functions currently, what are its problems,
and what are the requirements that the proposed software should meet.
The main components of making software are:
• System and software requirement analysis
• Design and implementation of software
• Ensuring, verifying and maintaining software integrity

2.1.1. Existing System
The existing system to manage a watch shop is a manual system. In this system the
all work are performed manually. All the data entry is performed by writing data
manually into the system and paper the documentation. The record is manually
prepared thus there is chance for getting errors and calculation are not so accurate.
They maintain several registers for recording the entry of daily transactions such as
billing of the products to the clients, etc. They keep the bill book or cash book to
maintain the record for each sale of the product or transaction in the shop. Similarly,
they maintain a book for their vendors so they can pay the money to them after some
time. Thus, maintaining vendor information, sales information is done manually.
In current system billing is manual and time consuming. And use manual searching
of item on shelf because of manual based system. Also, there is a difficulty on store
to check the stock and retrieve the necessary data from the manually based data
system. So generally, the current system does not arrange the items in systematic
way, does not store the item appropriate data, security for the data is low, does not
indicate how much stock is left.
Disadvantages of existing system
• Difficult in Maintenance of Records.
• Time Consuming.
• No Security of Data.
• Mistakes Occurring in long Calculations.
• Proper Generation of Report.
• Lack of Efficiency and Man Power.

2.1.2. Proposed System
In the proposed system the daily sales of purchase transaction are stored in the tables
and retrieval of the data is also easy . the proposed system have been designed to
overcome these facilities.
The proposed system is interactive, highly user friendly and designed exclusively for
the Watch Store System. The system covers almost all the functional areas of the
store. The Online Watch Shop System is a database system used to store the
information regarding customer details, staff details, product details, purchase and
order details etc.
All the operations and activities related to The Online Watch Store System can be
carried out efficiently. The system manages a well-organized database for storing the
resources that they are providing by the Online Watch Store System. This helps us to
eliminate the entering of invalid data. Most problems of manual system can be solved
by this system.
The computerization of the system allows the easy maintenance of the details. Large
amount of data can be stored easily. In addition, updating and other changes can be
done easily. The information can be retrieved with high speed and accuracy. The use
of GUI oriented software makes the system user friendly.
Advantages of Proposed System
• High processing speed.
• Easy to enter data
•User friendly.
• Minimal workload.
• Quick retrieval of data.

2.1.3. Feasibility Study
Feasibility study is made to see if the project on completion will serve the purpose of
the organization for the amount of work, time and effort spent on it.
Study lets the developer foresee the future of the project and its usefulness. Finding
out whether a new system is required or not.
The study is carried out to the best system that meet performance requirement. This
entails identification, description and evaluation of candidate system and selection of
the best system for the best system for the job. It simply identifies whether the
proposed system is feasible to the organization or not.
There are three aspects in the feasibility study portion of the preliminary investigation
• Technical feasibility
• Economic feasibility
• Operational feasibility

2.1.3.1. Technical Feasibility
The system must be evaluated from technical viewpoint first. The assessment of this
feasibility must be based on outline design of the system requirement in the terms of
input, output, programs and procedure having identified an outline system, the
investigation must go on to suggest the type of equipment, required method of
developing the system, method of running the system once it has been designed. The
project should be developed such that the necessary functions and performance are
achieved within the constraints. The project is developed with latest technology.
There are only minimal constraints involved in this project.
2.1.3.2. Economic Feasibility
Here an evaluation of development cost weighted against the ultimate income or

benefit derived from the developed system. The cost for the development of the
project has been evaluated and we want to check that the cost does not exceed
beneficial cost of the system. The economic and financial analysis is used for
evaluating the effectiveness of the candidate system. This project also undergone
economic feasibility study and found that it is feasible. So, the cost for development
does not exceed its beneficial cost. This brought to as the conclusion that the system
is economically feasible in the context.
2.1.3.3. Operational Feasibility
In operational feasibility the entire application is checked whether the system will be
used if it is developed and implemented. Also, it is checked whether there will be
resistance from user that may undermine the possible application benefits. There is no
barrier for implementing the system. The system also helps to access the information
immediately as need arises. Thus, the system is found to be operational feasible.

2.2 USER CHARATERISTICS
The system has three users
2.2.1 Administrator
2.2.2 Staff
2.2.3 Customer
2.2.4 courier
2.2.1 Administrator
Administrator or admin has all privileges on every process performed in the system.
Admin can add, edit or view the details of product and supplier, make purchases and
view all activity performed on the system. The administrator is responsible for
managing the details of about the employees.
2.2.2 Staff
Staff has less privileges than admin but has more privileges as compared to customer.
Staff can add, edit and view the details about the product and vendors, manage
purchase details and view all those activities performed by staff in the system. The
administrator is responsible for managing the details of about his employees.
2.2.3 Customer
The customer can only use the system to see the product details, price etc and add
their desired items into the cart and make purchase using debit or credit cards. The
customer later can view and edit the items in the cart before purchasing the product.
The customer logs into the system by registering himself.

2.2.4 Courier
Courier has less privileges compared to admin and staff. Courier is used to show the
customer about the delivery details. The status details of product will be updated till
the product has been delivered.
2.3 SYSTEM SPECIFICATION
2.3.1 Hardware Specification
The selection of hardware is very important for the existence and proper working of
any software. When selecting the hardware, the size and capacity requirements are
also noted. Below are the hardware details required by the system.
Processor Intel Core i5-3220 (3.3 GHz) or above
RAM 4 GB
Storage 512 GB and above
Key Board Normal or multimedia
Monitor 15’’CRT or LCD monitor
Mouse Compatible Mouse
2.3.2 Software specification

Operating System Windows 7/8/8.1/10
Front End PHP5
Back End MySQL
2.3.3 About The Software Tools And Platform
FRONT END SPECIFICATION: PHP
The PHP Hypertext Pre-processor (PHP) is a programming language that allows web

developers to create dynamic content that interacts with databases. PHP is a server-
side scripting language that is embedded in HTML. It is used to manage dynamic
content, databases, session tracking, even build entire e-commerce sites. It is
integrated with a number of popular databases, including MySQL, PostgreSQL,
Oracle, Sybase, Informix, and Microsoft SQL Server. PHP supports a large number
of major protocols such as POP3, IMAP, and LDAP. PHP4 added support for Java
and distributed object architectures (COM and CORBA), making n-tier development
a possibility for the first time.
BACKEND SPECIFICATION: MYSQL
A database is a separate application that stores a collection of data. Each database has
one or more distinct APIs for creating, accessing, managing, searching and
replicating the data it holds.

Other kinds of data stores can also be used, such as files on the file system or large
hash tables in memory but data fetching and writing would not be so fast and easy
with those type of systems.
Nowadays, we use relational database management systems (RDBMS) to store and

manage huge volume of data. This is called relational database because all the data is
stored into different tables and relations are established using primary keys or other
keys known as Foreign Keys.
3.1 MODULE AND DESCRIPTION
Online Watch shop System provides us facilities to manage the activities taking place in
watch shop. This system is developed to manage the work flow in a Watch shop. There
are 8 modules in this project. They are:
3.1.1. Staff management
In this module we manage the details of all staffs working in the shop. The admin can
add, update and view the details of employ in this module. The details about employ
stored in more secured way which can be only accessed by the administrator.
3.1.2. Customer registration
In this module, we manage the registration of customers. The customer himself can
register into the system. The customer also has the privilege to edit and view his
profile after registration. While the admin and staff are given the privilege to view the
detail entered by the customer.
3.1.3. Vendor management
Rajagiri College of Management and Applied Sciences Page No

10
This module deals with the details of vendors who provides the product to the watch
shop. Both the staff and admin manage this module. They can add the new vendor
edit the details of existing vendor and view the existing vendor
3.1.4 Courier management
In this module we mainly deal with the information about the courier service for the
watch shop. The is assigned to the courier service
3.1.5 Product management
This module manages details of the product. These details include the category, type
and brand of the watch. This module is mainly supervised by the staff but the admin
has the main power. Both these entities can add the product, edit the existing product
and view the details on the product. This module is further divided into:
3.1.5.1 Category management
This modules stores the information about the category of product. The basic
categories of this watch store are men, women, kids, unisex and other . The user can
select then product based on the category preferred.
3.1.5.2 Type management
This module stores the information on the type of product. The type of watches
include smart watch, wrist band, leather watch, metal strap, and so on. The user can
select product based on the type preferred
3.1.5.3 Brand management
This module stores the information on various brands of watches these brand includes
fastrack , casio , rado, rolex , fossil, hubolt etc. The user can choose his preferred
product based on the given brands
3.1.5.4 Item management

11
This module manages the products on the website. An item can be viewed by the user
and all the details can be added or edited by the admin or staff
3.1.6 Purchase management
This module deals with purchase made by staff to order products from the vendor.
This module is managed by both staff and admin they can add the products edit and
view them.
3.1.7 Cart management
The main aim of developing this module is to manage the order of customers.
Customers can see the different products and add items to cart. The cart shows
informations such as the price of the product, the quantity selected and the date and
time of order.
3.1.8 Sales management
This module deals with the sales information such as order placements and shipping
details. Its is further divided into order ,payment and delivery.
3.1.8.1 Order management
This module deals with orders made by customer once the customer wants to buy the
desired product the he can order the product, cancel the order and view the order.
3.1.8.2 Payment management
This module manages the payment of the product. The customer can make payment
by using debit or credit card and view the payment details.

12
3.1.8.3 Delivery management
This module deals with the delivery of the product. The delivery management deals
with the status updation of courier service .
3.2. DATA FLOW DIAGRAM
A data flow diagram is graphical tool used to describe and analysis movement of data
through a system. These are central tool and the basis from which the other
components are developed. The transformation of data from input to output, trough
processed, may be described logically and independently of physical components
associated with the system. These are known as the logical data flow movement of
data between people, departments and workstations. A full description of a system
actually consists of a set of data flow diagrams.
A DFD is also known as a “bubble chart” has the purpose of clarifying system
requirements and identifying major transformations that will become programs in
system design. So, it is the starting point of the design to the lowest level of detail. A
DFD consists of a series of bubbles joined by data flows in the system.
In the DFD, there are four symbols
Process that transforms data flow
Source of destination of data

13
Data store
Information or Dataline
Rules for drawing data flow diagrams
Rule 1: Establish the context of the data flow diagram by identifying all of the net
input and output data flows.
Rule 2: Select a starting point for drawing the DFD.
Rule 3: Give meaningful labels to all data flow lines.
Rule 4: Label all processes with action verbs that relate input and output data flows.
Rule 5: Omit insignificant functions routinely handled in the programming process.
Rule 6: Do not include control or flow of control information.
Rule 7: Do not try to put too much information in one DFD.
Rule 8: Be prepared to start over.

14
Level 0 DFD Showing Online Jewellery Shop System
request
customer online watch store
response

15
Level 1 DFD Showing Online Watch Shop System

16
1
staff tbl_staff
managemen sucessfully stored
t
customer details
ls
et
ai 2
customer
ils
d
tbl_customer
ta
ff
d
re
sta
de
managemen
sto
re
succesfully stored
er
sto
t
lly
sto
ly
fu
ul
cu
es
f
cc
es
vendor details
su
cc
su
ls
3.
ai
tbl_vendor
et
vendor
d
re
or
management sucessfully stored
sto
nd
ve
ly
ul
f
es
cc
su courier details
courier details 4.
courier tbl_courier
management succesfully stored
succesfullystored
product details
productdetails 5. tbl_item
user product
succesfully stored succesfully stored
management
purchase detail purchase details
6. sucessfully stord tbl_purchase

succesfully stored
purchase
ca
management
su
rt
cc
de
es
cart details
ta
f
ils
ul
sa
ly
le
tbl_cart
sto
sd
7.
su
re
et
sucessfully stored
d
ce
ai
cart
l
ss
fu
management
lly
sto
sales details
re
d
8. tbl_payment
sales sucessfully stord
management
Level 2 DFD Showing Staff Management

17
1.1.
add staff
staff id staff id
1.2 tbl_staff
customer edit staff updaed
updatd
1,3
view staff
Level 2 DFD Showing Customer Management

18
2.1 cu
il add sto
eta m
d customer er
er d su
ce de
m re ta
sto ts o ss
fu l
cu ly lly
f ul sto
ss re
uce d
s
customer id customr id
2.2 tbl_customer
customer edit updatd
updaed
customer
cu id
stm er
ei stm
su d cu r ed
ce sto
ss
fu lly
lly fu
sto 2.3 e ss
rd c
view su
customer
Level 2 DFD Showing Vendor Management

19
3.1
add vendor
ve
il
a
nd
et
rd
or
su
o
de
nd
ce
t
d
ail
ss
ve
re
fu
sto
lly
lly
sto
fu
re
ss
d
ce
vendr id
su
vendr id
tbl_vendor
customer 3.2 updatd
updatd edit vendor
d
ve
ri
nd
o
nd
rio
d
ve
re
d
su
sto
ce
ss
lly
fu
fu
lly
ss
3.3
ce
sto
su
view
re
d
vendor
Level 2 DFD Showing Courier Management

20
d i
ff_
tbl_staff
sta
succesfully stored
4.1
add courier
il
co
a
su
et
u
rd
ce
rie
ss
rie
rd
fu
u
et
lly
d
co
a
re
il
sto
sto
re
lly
d
fu
ss
ce
su
courierr id
courier id tbl_courier
4.2
customer updated
updated edit courier
co
u
d
rie
ri
ri
rie
d
u
co
d
re
sto
su
ce
lly
ss
fu
fu
ss
lly
ce
sto
su
re
4.3
d
view courier
Level 2 DFD Showing Product Management

21
Level 2 DFD Showing Purchase Management

22
Level 2 DFD Showing Cart Management

23
Level 2 DFD Showing Sales Management

24
order detail
8.1 tbl_order
order
management
sucessfully stored
l
ait
rde
de
or
d
re
sto
lly
fu
ss
ce
su
payment details
payment details
8.2
payment tbl_payment
user management
succesfully stored
succesfully stored
de
liv
er
y
de
t
ai
su st
ls
delivery details
cc ore
es d
fu
lly
8.3 tbl_delivery
delivery
mahagement succesfully stored
Level 3 DFD Showing Category Management
Level 3 DFD Showing Type Management

25
Level 3 DFD Showing Brand Management

26
Level 3 DFD Showing Item Management

27
Level 3 DFD Showing Order Management

28
Level 3 DFD Showing Payment Management

29
Level 3 DFD Showing delivery Management

30
3.3 ENTITY RELATIONSHIP DIAGRAM

The ER model is a conceptual data model that views the real world as a construct of
entities and associations or relationships between entities. A basic component of the
model is the Entity-Relationship diagram, which is used to visually represent data
objects. The ER modelling technique is frequently used for the conceptual design of
database applications and many database applications and many database design tools
employ its concepts.
Entity Type
Weak Entity Type
Relationship Type
Attribute
Key attribute
Multivalued Attribute

31
ER DIAGRAM FOR ONLINE WATCH SHOP SYSTEM

32
4.1 INPUT DESIGN
Input design is the process of converting a user-oriented description of the inputs to a

computer-based system into a programmer-oriented specification. The quality of
system input determines the quality of system output. Input specification describes
the manner in which data enter the system for processing. Input design features can
ensure the reliability of the system and produce result from accurate data or they can
result in the production of errors. The input design also determines whether the user
can interact efficiently with the system. Input design requires consideration of the
needs of the data entry operator. Three data entry considerations are: • The field
length must be documented • The sequence of fields must match the sequence of the
fields on the source document. • The data format must be identified to the data entry
operator. In our system almost all inputs are being taken from the databases. To
provide adequate inputs we have to select necessary values from the databases and
arrange it to the appropriate controls. Inaccurate input data are the most common
cause of errors in data processing. Errors entered by data entry can be controlled by
input design. Input design is the process of converting user-oriented inputs to a
computer-based format. There are three major approaches for entering data into the
computer. They are menus, formatted forms and prompts. A menu is a selection list
that simplifies computer data access or entry. Instead of remembering what to enter,
the user choices from the list of option. A formatted form is a preprinted form or a
template that request the user to enter data in appropriate location. It is a fill-in-the-
blank type form. The form is flashed on the screen as a unit. In prompt the system
displays one enquiry at a time, asking the user for a response.

33
Home Page
Description: This is the home page for all unauthenticated users.

34
Login Form
Description: This is the Login page for all the users.

35
User Registration
Form Description: This is the User Registration page for customers.

36
Category Add
Form Description: This form is used to add new category.

37
Category Edit
Form Description: This form is used to edit a category

38
Type Add Form

Description: This form is used to add new type.

39
Type Edit Form

Description: This form is used to edit a type.

40
Brand Add Form

Description: This form is used to add a brand.

41
Brand Edit Form

Description: This form is used to edit a brand.

42
Item Add Form

Description: This form is used to add a new item.

43
Item Edit Form

Description: This form is used to edit an item.

44
Staff Add Form

Description: This form is used to add a new staff.

45
Staff Edit Form

Description: This form is used to edit a staff.

46
Vendor Add Form

Description: This form is used to add a new vendor.

47
Vendor Edit Form

Description: This form is used to edit a vendor.

48
4.3 DATABASE DESIGN

49
4.3.1 Normalization
Designing a database is a complex task and the normalization theory is a useful aid in
this design process. The process of normalization is concerned with transformation of
conceptual schema into computer representation form.
A bad database design may lead to certain undesirable situations such as,
• Repetition of information
• Inability to represent certain information
• Loss of information
To minimize these anomalies, normalization may be used. If the database is in a
normalized form, the data can be restructured and can maintain it easily. This is
important that the databases using that we are using may free from data redundancy
and inconsistency. For this need we maintain the tables in a normalized manner.
First Normal Form
A relation is in first Normal Form (1NF), if and only if all its attributes are based on
single domain. The objective of normalizing a table is in to remove its repeating
groups and ensure that all entries of the resulting table have at most single value.
Second Normal Form
A table is said to be in second Normal Form (2NF), when it is in 1 NF and every
attribute in the record is functionally dependent upon the whole key, and not just a part
of the key.
Third Normal Form
A table is in third Normal Form (3NF), when it is in 2NF and every non-key attribute
Is functionally dependent on just the primary key.
TABLE DESIGN
1. Table Name: tbl_login
Table Description: login details
FIELD DATA TYPE CONSTRAINT DESCRIPTION
Username Varchar(05) Primary key Email
password Varchar(15) Not null Password
type Varchar(15) Not null Type of user

50
STATUS Not null Active/Inactive
Varchar(15)
2. Table Name: tbl_staff

Table Description: Staff details
STAFF_ID Varchar(05) Primary Key Staff id
Username Varchar(15) Foreign Key Staff Email
STAFF_FNAME Varchar(15) Not Null Staff First name
STAFF_LNAME Varchar(10) Not null Staff last name
STAFF_CITY Varchar(15) Not null Staff City
STAFF_DIST Varchar(15) Not null Staff District
STAFF_PIN Int(6) Not null Staff Pin code
Staff phone
STAFF_PHONE numeric(10) Not null,Unique
number
STAFF_GENDER Varchar(7) Not null Staff gender
DOB Date Not null Staff Date of Birth
STATUS
Boolean Not null Active/Inactive
3.Table name: tbl_customer

Table description: customer details
CUST_ID Varchar(05) Primary Key Customer id

USERNAME Varchar(15) Foreign Key Customer Email

51
CUST_FNAME Varchar(10) Not Null Customer first

name
CUST_LNAME Varchar(10) Not Null Customer last
name
CUST_CITY Varchar(15) Not Null Customer street
CUST_DIST Varchar(20) Not Null Customer district
CUST_PIN Int(6) Not Null Customer pin
code
CUST_PHONE Numeric (10) Not Null, Customer Phone
Unique number
CUST_GENDER Varchar(10) Not Null Customer gender
STATUS Boolean Not null Active/Inactive
DOB Date Not Null Date of birth
4. Table Name: tbl_vendor

Table Description: vendor details
VENDOR_ID Varchar (05) Primary key Supplier id

52
VENDOR_NAME Varchar(15) Not null Supplier name
VENDOR_EMAIL Varchar(15) Not null Supplier email
Supplier Phone
VENDOR_PHONE Numeric(10) Not null
number
STATUS Boolean Not null Active/Inactive
5. Table Name: tbl_Courier

Table Description: Courier details
COURIER_ID Varchar(05) Primary key Courier id
USERNAME Varchar(15) Foreign Key Courier Email
COURIER_NAME Varchar(15) Not null Courier name
COURIER_PHNO Numeric(10) unique Courier phno
LOCATION Varchar(50) Not null Address
6. Table Name: tbl_category

53
Table Description: category details
CAT_ID Varchar(05) Primary Key category id
CAT_NAME Varchar(10) Foreign Key category name
DESCRIPTION Varchar(60) Not Null Description
7. Table Name: tbl_type

Table Description: type details
FIELD DATA TYPE CONSTRAINTS DESCRIPTION
TYPE_ID Varchar(05) Primary key Type id
TYPE_NAME Varchar(15) Not null Type name
8. Table Name: tbl_brand

Table Description: Brand details

54
BRAND_ID Varchar (05) Primary key Brand id
BRAND_NAME Varchar(25) Not null Brand name
9. Table Name: tbl_item

Table Description: Item details
ITEM_ID Varchar(05) Primary Key Item id
ITEM_NAME Varchar(15) Not Null Name of the Item
CAT_ID Varchar (05) Foreign key Category_id
TYPE_ID Varchar (06) Foreign key type_id
STOCK Int(11) Not null Stock
DESCRIPTION Varchar(50) Not null Description
ITEM_IMAGE Image Not null Image
Available or not
ITEM_STATUS Varchar(15) Not null
available
PRICE Decimal(10) Not null Product price

55
10. Table Name: tbl_purchasemaster

Table Description: Purchase master details
PURCHASE_ Purchase master

Varchar(5) Primary key
MID id
STAFF_ID Varchar (05) Foreign Key Staff id
VENDOR_ID Varchar (11) Foreign Key Vendor id
PURCHASE_ Date of
Date Not Null
DATE purchase
TOT_AMOUNT Int(10) Not Null Total Amount
11. Table Name: tbl_purhasechild

Table Description: Purchase child details
PURCHASE_
Varchar(5) Primary key Purchase child id
CID
PURCHASE_
Varchar(5) Foreign key Purchase master id
MID
ITEM_ID Varchar(5) Foreign Key Item id
SELL_PRICE Int(5) Not Null Sell price
QUANTITY Int(11) Not Null Item quantity

Rate at which
COST_PRICE Int(11) Not Null
purchased
Total purchase
TOT_PRICE Int(10) Not Null
amount

56
12 Table Name: tbl_cartmaster

Table Description: Cart master details
CART_MID Varchar (5) Primary Key Cart Master id
CUST_ID Varchar (05) Foreign Key Customer id
Total amount of
TOT_AMOUNT Int(11) Not Null all the items in
the Cart child
Status of the
STATUS Varchar(10) Not Null
Cart.
13. Table Name: tbl_cartchild

Table Description: Cart child details
CART_CID Varchar (5) Primary Key Cart Child id
CART_MID Varchar(5) Foreign Key Cart Master id
ITEM_ID Varchar (05) Foreign Key Item id
ITEM_NAME Varchar(15) Not Null Item name
QUANTITY Decimal(4,0) Not Null Quantity
PRODUCT_
Varchar(50) Not null Product details
DETAILS

57
DATE Date Not Null Date
14. Table Name: tbl_order

Table Description: Order details
ORDER_ID Varchar(5) Primary Key Order id
CART_MID Varchar(5) Foreign Key Cart Master id
O_DATE Date Not Null Order Date
15.Table Name: tbl_Card

Table Description: Card details
CARD_ID Varchar (5) Primary Key Card id
CUST_ID Varchar (05) Foreign Key Customer id
CARD_NO Int (12) Not Null Card number
Card holder
CARD_NAME Varchar(20) Not Null
name
BANK_NAME Varchar(20) Not Null Bank name
EXP_DATE Date Not Null Card expiry date

58
16. Table Name: tbl_payment

Table Description: Payment details
PAYMENT_ID Varchar (5) Primary key Payment id
ORDER_ID Varchar (5) Foreign Key Order id
CARD_ID Varchar (5) Foreign Key Card id
PAYMENT_
Date Not Null Date of payment
DATE
17 Table Name: tbl_delivery

Table Description: delivery details
DELIVERY_ID Varchar (5) Primary key Payment id
ORDER_ID Varchar (5) Foreign Key Order id
Varchar (5)
PAYMENT_ID Foreign Key Payment id

59

60

Projarun

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Projarun

Uploaded by

Copyright:

Available Formats

Online Watch Shop system

1.1 ABOUT THE PROJECT

Rajagiri College of Management and Applied Sciences Page No 1

2.1 SYSTEM STUDY

Rajagiri College of Management and Applied Sciences Page No 2

2.1.1. Existing System

Disadvantages of existing system

• Difficult in Maintenance of Records.

• Mistakes Occurring in long Calculations.

• Proper Generation of Report.

• Lack of Efficiency and Man Power.

Rajagiri College of Management and Applied Sciences Page No 3

2.1.2. Proposed System

Advantages of Proposed System

• High processing speed.

• Easy to enter data

• Quick retrieval of data.

Rajagiri College of Management and Applied Sciences Page No 4

2.1.3. Feasibility Study

Rajagiri College of Management and Applied Sciences Page No 5

2.1.3.1. Technical Feasibility

2.1.3.2. Economic Feasibility

Here an evaluation of development cost weighted against the ultimate income or

2.1.3.3. Operational Feasibility

Rajagiri College of Management and Applied Sciences Page No 6

2.2 USER CHARATERISTICS

The system has three users

Rajagiri College of Management and Applied Sciences Page No 7

2.3 SYSTEM SPECIFICATION

2.3.1 Hardware Specification

Processor Intel Core i5-3220 (3.3 GHz) or above

Storage 512 GB and above

Key Board Normal or multimedia

Monitor 15’’CRT or LCD monitor

Mouse Compatible Mouse

2.3.2 Software specification

Rajagiri College of Management and Applied Sciences Page No 8

Operating System Windows 7/8/8.1/10

Front End PHP5

Back End MySQL

2.3.3 About The Software Tools And Platform

FRONT END SPECIFICATION: PHP

The PHP Hypertext Pre-processor (PHP) is a programming language that allows web

BACKEND SPECIFICATION: MYSQL

Rajagiri College of Management and Applied Sciences Page No 9

Nowadays, we use relational database management systems (RDBMS) to store and

3.1 MODULE AND DESCRIPTION

3.1.1. Staff management

3.1.2. Customer registration

3.1.3. Vendor management

Rajagiri College of Management and Applied Sciences Page No

3.1.4 Courier management

3.1.5 Product management

3.1.5.1 Category management

3.1.5.2 Type management

3.1.5.3 Brand management

3.1.5.4 Item management

3.1.6 Purchase management

3.1.7 Cart management

3.1.8 Sales management

3.1.8.1 Order management

3.1.8.2 Payment management