Cycle

1.
INTRODUCTION
This project is a web based cycle shopping management system for an existing shop. The
project objective is to deliver the online cycle shopping management application into java
platform. This project is an attempt to provide the advantages of online shopping to customers of
a real shop. It helps buying the products in the shop anywhere through internet by using an
android device. Thus the customer will get the service of online shopping and home delivery
from his favorite shop. This system can be implemented to any shop in the locality or to
multinational branded shops having retail outlet chains. If shops are providing an online portal
where their customers can enjoy easy shopping from anywhere, the shops won’t be losing any
more customers to the trending online shops such as flipcart or ebay. Since the application is
available in the Smartphone it is easily accessible and always available. .
The central concept of the application is to allow the customer to shop virtually using the
Internet and allow customers to buy the items and articles of their desire from the store. The
information pertaining to the products are stores on an RDBMS at the server side (store). The
Server process the customers and the items are shipped to the address submitted by them. The
application was designed into two modules first is for the customers who wish to buy the articles.
Second is for the storekeepers who maintains and updates the information pertaining to the
articles and those of the customers. The end user of this product is a departmental store where the
application is hosted on the web and the administrator maintains the database. The application
which is deployed at the customer database, the details of the items are brought forward from the
database for the customer view based on the selection through the menu and the database of all
the products are updated at the end of each transaction. Data entry into the application can be
done through various screens designed for various levels of users. Once the authorized personnel
feed the relevant data into the system, several reports could be generated as per the security.
2. SYSTEM STUDY
A detailed study to determine whether, to what extent, and how automatic data
processing equipment should be used; it usually includes an analysis of the existing system and t
he design of the new system, including the development of system specifications which providea
basis for the selection of equipment.
2.1 PROJECT DESCRIPTION
This system can be implemented to any shop in the locality or to multinational branded
shops having retail outlet chains. The system recommends a facility to accept the orders 24*7
and a home delivery system which can make customers happy. If shops are providing an online
portal where their customers can enjoy easy shopping from anywhere, the shops won’t be losing
any more customers to the trending online shops such as flipchart or ebay. Since the application
is available in the Created application it is easily accessible and always available
2.1.1 Existing System

The current system for shopping is to visit the shop manually and from the available
product choose the item customer want and buying the item by payment of the price of the item .
1. It is less user-friendly.
2. User must go to shop and select products.
3. It is difficult to identify the required product.
4. Description of the product limited.
5. It is a time consuming process
6. Not in reach of distant users
2.1.2 Proposed System
In the proposed system customer need not go to the shop for buying the products. He can
order the product he wish to buy through the java application . The shop owner will be admin of
the system. Shop owner can appoint moderators who will help owner in managing the customers
and product orders. The system also recommends a home delivery system for the purchased
products.
3. REQUIREMENT ANALYSIS
During requirements analysis, the person assigned the issue will evaluate the impact of the
change, update the requirements documents, and advance the issue to the in-progress phase with
the make-change transition. Appropriate SHA and SRS reviews should be conducted. You may
want to “batch” these at periodic review intervals for software control documents.
3.1 Hardware Requirements
 Processor : Dual core processor 2.6.0 GHz
 RAM : 1GB
 Hard disk : 160 GB
 Compact Disk : 650 MB
 Keyboard : Standard keyboard
 Monitor : 15 inch color monitor
3.2 Software Requirement
Software requirements are a field within software engineering that deals with establishing
the needs of stakeholders that are to be solved by software. Elicitation is the gathering and
discovery of requirements from stakeholders and other sources. A variety of techniques can be
used such as joint application design (JAD) sessions, interviews, document analysis, focus
groups, etc. Elicitation is the first step of requirements development.
 Front End : JAVA

 IDE : Net Beans
 Back End : My SQL
JAVA
Java is a programming language that produces software for multiple platforms. When a
programmer writes a Java application, the compiled code (known as bytecode) runs on most
operating systems (OS), including Windows, Linux and Mac OS. Java derives much of its syntax
from the C and C++ programming languages.
Java was developed in the mid-1990s by James A. Gosling, a former computer scientist
with Sun Microsystems.
 It is simple and object oriented.
 It allows the programmers to create user friendly interfaces.
 It is very dynamic.
 Multithreading.
 Platform independent language.
 Provides security and robustness.
 Provides support for internet programming
Primary Goals
The five primary goals of the creation of the Java language are:
 The object-oriented programming methodology should be used.

 The same program should be allowed to execute on multiple operating systems.
 The built-in support should be provided for using computer networks.
 The code from remote sources should be executed securely.
 It should be easy to use by combining the good parts of other object-oriented
languages.
Different "Editions" Of The Platform
 Java ME (Micro Edition): Defines different sets of libraries (known as profiles) for
devices which are sufficiently limited that supplying the full set of Java libraries would take up
unacceptably large amounts of storage.
 Java SE (Standard Edition): to offer general purpose use on desktop PCs, servers and
other similar devices.
 Java EE (Enterprise Edition): Java SE and various APIs are useful for multi-tier client-
server enterprise applications.
The important components in the platform are the libraries, the Java compiler, and the
runtime environment where Java intermediate byte code is executed.
Java Virtual Machine
A Java virtual machine (JVM), an implementation of the Java Virtual Machine

Specification, interprets compiled Java binary code (called bytecode) for a
computer's processer (or "hardware platform") so that it can perform a Java
program's instructions. Java was designed to allow application programs to be built that could be
run on any platform without having to be rewritten or recompiled by the programmer for each
separate platform. A Java virtual machine makes this possible because it is aware of the specific
instruction lengths and other particularities of the platform.
JVM Linker
JVM spec defines it at best: Linking a class or interface involves verifying and preparing that
class or interface, its direct superclass, its direct superinterfaces, and its element type (if it is an
array type), if necessary. Resolution of symbolic references in the class or interface is an optional
part of linking.
JVM Verifier
 The JVM verifier checks the byte code of the class or interface before it is loaded.
 If any error occurs then it throws Verify Error exception.
Class loader subsystem
Class files
Runtime data areas

Method Heap Java Pre- Native
area stacks register method
stacks
Native method Native

Execution engine method
interface
libraries
Fig 1: JVM Architecture
Class Libraries
Most of the modern operating systems provide a large set of reusable code to simplify the
job of the programmer. This code is actually provided as a set of dynamically loadable libraries
that can be called at runtime by the applications. Java Platform is not dependent on any specific
operating system so the applications are not rely on any of the existing libraries. The Java
Platform provides a set of standard class libraries which contains most of the same reusable
functions commonly found in modern operating systems.
The Java class libraries provide three purposes within the Java Platform. They provide
the programmer a well-known set of functions to perform common tasks like other standard code
libraries. The class libraries provide an abstract interface to tasks that would normally depend
heavily on the hardware and operating system. Tasks such as file access and network access are
heavily dependent on the native capabilities of the platform. The required native code is
implemented internally by the Java java.io and java.net libraries, and then it provides a standard
interface for the Java applications to perform the file access and network access. If the
underlying platform does not support all of the features a Java application expects, then the class
libraries can either emulate those features or at least provide a consistent way to check for the
presence of a specific feature.
MY SQL
MySQL is the world's most used open source relational database management system
(RDBMS) as of 2008 that run as a server providing multi-user access to a number of databases.
The MySQL development project has made its source code available under the terms of the
GNU General Public License, as well as under a variety of proprietary agreements. MySQL was
owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned
by Oracle Corporation.
MySQL is a popular choice of database for use in web applications, and is a central component
of the widely used LAMP open source web application software stack—LAMP is an acronym
for "Linux, Apache, MySQL, Perl/PHP/Python." Free-software-open source projects that require
a full-featured database management system often use MySQL.
For commercial use, several paid editions are available, and offer additional functionality.
Applications which use MySQL databases include: TYPO3, Joomla, Word Press, phpBB,
MyBB, Drupal and other software built on the LAMP software stack. MySQL is also used in
many high-profile, large-scale World Wide Web products, including Wikipedia, Google(though
not for searches), ImagebookTwitter, Flickr, Nokia.com, and YouTube.
Interimages
MySQL is primarily an RDBMS and ships with no GUI tools to administer MySQL databases or
manage data contained within the databases. Users may use the included command line tools, or
use MySQL "front-ends", desktop software and web applications that create and manage
MySQL databases, build database structures, back up data, inspect status, and work with data
records. The official set of MySQL front-end tools, MySQL Workbench is actively developed by
Oracle, and is freely available for use.
4. SYSTEM DESIGN
System design is the process of designing the elements of a system such as the architecture,
modules and components, the different interfaces of those components and the data that goes
through that system.
4.1 Logical Design

A logical design is a conceptual, abstract design. You do not deal with the physical
implementation details yet; you deal only with defining the types of information that you
need. The process of logical design involves arranging data into a series
of logical relationships called entities and attributes.
Admin
Cycle shop
management
system
User
Fig 4.1 Logical design of the Cycle shop management system

The system contains the architectural design where the entire Cycle shop management system is
added here.
4.2 Database Design
Database design is the organization of data according to a database model. The designer
determines what data must be stored and how the data elements interrelate. With this
information, they can begin to fit the data to the database model.
Database design involves classifying data and identifying interrelationships. This theoretical
representation of the data is called an ontology. The ontology is the theory behind the database's
design.
Product table:
Field Type Null Default
id int(100) Yes NULL
product_name varchar(100) Yes NULL
brand varchar(100) Yes NULL
category varchar(100) Yes NULL
price varchar(100) Yes NULL
qty varchar(100) Yes NULL
gst varchar(100) Yes NULL

User purchase table:
user varchar(100) Yes NULL
product varchar(100) Yes NULL
type varchar(100) Yes NULL
price varchar(100) Yes NULL
qty varchar(100) Yes NULL
total varchar(100) Yes NULL
card varchar(100) Yes NULL
holder varchar(100) Yes NULL
exdate varchar(100) Yes NULL
ccv varchar(100) Yes NULL
status varchar(100) Yes NULL
report varchar(100) Yes NULL

User register table
name varchar(100) Yes NULL
contact varchar(100) Yes NULL
email varchar(100) Yes NULL
address varchar(100) Yes NULL
username varchar(100) Yes NULL
password varchar(100) Yes NULL
cdate varchar(100) Yes NULL
status varchar(100) Yes NULL
4.3 Program Design
Program design is both a verb and a noun. It is the process that organizations use to develop
a program. Ideally, the process is collaborative, iterative, and tentative stakeholders work
together to repeat, review, and refine a program until they believe it will consistently achieve its
purpose.
4.3.1 Module Description
 Admin
 User
4.3.1 Admin
(i) Admin login

The Login Module is a portal module that allows users to type a user name and password to log
in. If an administrator has allowed users to create accounts and turned on Portal Direct Entry, a
Create Account link appears in the Login Module. The module is no longer available to users
after they have logged in.
(ii) Add products
In product add module the admin will add the cycle product. The added products will be stored
in the database where the user can view, store, retrieve the products added. Here the product
name, product type, category will be added to the back end database.
(iii)View Product
In view product module the details of the product which are all added in the database. The
owner will update the details of the cycle which are going to be sold in the cycle shop
management system. The details are cycle name, prize of the cycle added and the total count of
the cycles.
(iv)Sales Details
In sales details module the details of the cycle which are sold to the customer. This helps for the
owner to maintain the database. Thus the sales details can be updated and deleted easily.
4.3.1 User
(i)User login
The user module allows users to register, log in, and log out. The user
module supports user roles, which can be set up with fine-grained permissions allowing each role
to do only what the administrator permits. Each user is assigned one or more roles.
(ii) User registration

User Registration plug-in provides you with an easy way to create frontend user registration form
and login form. Drag and Drop fields make ordering and creating forms extremely easy. The
plug-in is lightweight, extendible, and can be used to create any type of registration form.
(iii) User Search
User search module is used to search the products for user wish it is easy to search the products
and buy the products from the application.
(iv) User Buy
If the user selects the product then they will add their details to buy the product. They will select
the product they want to buy. After that they will purchase it through online payment or cash on
delivery.
5. SYSTEM DEVELOPMENT
The process of creating and maintaining information systems is called systems development or
systems analysis and design. This diagram shows that it involves all five components of an
information system. In addition to technical knowledge, it requires business knowledge and
management skill. Systems development is the process of defining, designing, testing, and
implementing a new software application or program. It could include the
internal development of customized systems, the creation of database systems, or the acquisition
of third party developed software.
5.1 PROGRAM DEVELOPMENT
<?xml version="1.0" encoding="UTF-8" ?>
<Form version="1.3" maxVersion="1.9"

type="org.netbeans.modules.form.forminfo.JFrameFormInfo">
<Properties>
<Property name="defaultCloseOperation" type="int" value="2"/>
</Properties>
<SyntheticProperties>
<SyntheticProperty name="formSizePolicy" type="int" value="1"/>
<SyntheticProperty name="generateCenter" type="boolean" value="false"/>
</SyntheticProperties>
<AuxValues>
<AuxValue name="FormSettings_autoResourcing" type="java.lang.Integer" value="0"/>
<AuxValue name="FormSettings_autoSetComponentName" type="java.lang.Boolean"
value="false"/>
<AuxValue name="FormSettings_generateFQN" type="java.lang.Boolean" value="true"/>
<AuxValue name="FormSettings_generateMnemonicsCode" type="java.lang.Boolean"
value="false"/>
<AuxValue name="FormSettings_i18nAutoMode" type="java.lang.Boolean" value="false"/>
<AuxValue name="FormSettings_layoutCodeTarget" type="java.lang.Integer" value="1"/>
<AuxValue name="FormSettings_listenerGenerationStyle" type="java.lang.Integer"
value="0"/>
<AuxValue name="FormSettings_variablesLocal" type="java.lang.Boolean" value="false"/>
<AuxValue name="FormSettings_variablesModifier" type="java.lang.Integer" value="2"/>
</AuxValues>
<Layout>
<DimensionLayout dim="0">
<Group type="103" groupAlignment="0" attributes="0">
<Group type="102" alignment="0" attributes="0">
<EmptySpace max="-2" attributes="0"/>
<Component id="jPanel1" max="32767" attributes="0"/>
</Group>
</Group>
</DimensionLayout>
</Group>
</Group>
</DimensionLayout>
</Layout>
<SubComponents>
<Container class="javax.swing.JPanel" name="jPanel1">
<Layout>
<EmptySpace min="-2" pref="196" max="-2" attributes="0"/>
<Component id="jLabel7" min="-2" max="-2" attributes="0"/>
<Component id="jLabel1" alignment="0" min="-2" max="-2"
attributes="0"/>
attributes="0"/>
attributes="0"/>
attributes="0"/>
</Group>
<Component id="jTextField4" min="-2" pref="161" max="-2"
attributes="0"/>
attributes="0"/>
attributes="0"/>
attributes="0"/>
</Group>
</Group>
<EmptySpace type="separate" max="-2" attributes="0"/>
attributes="0"/>
attributes="0"/>
<Component id="jButton1" alignment="0" min="-2" pref="161" max="-2"
attributes="0"/>
</Group>
</Group>
</Group>
<EmptySpace min="50" pref="147" max="32767" attributes="0"/>
</Group>
</Group>
</DimensionLayout>
<Group type="102" attributes="0">
<Component id="jTextField1" alignment="3" min="-2" pref="32" max="-2"
attributes="0"/>
attributes="0"/>
</Group>
attributes="0"/>
attributes="0"/>
</Group>
</Group>
attributes="0"/>
<Component id="jLabel4" alignment="3" min="-2" max="-2" attributes="0"/>
</Group>
</Group>
attributes="0"/>
</Group>
attributes="0"/>
</Group>
attributes="0"/>
</Group>
<Component id="jButton1" min="-2" pref="43" max="-2" attributes="0"/>
<EmptySpace pref="33" max="32767" attributes="0"/>
</Group>
</Group>
</DimensionLayout>
</Layout>
<SubComponents>
<Component class="javax.swing.JLabel" name="jLabel3">
<Properties>
<Property name="font" type="java.awt.Font"
editor="org.netbeans.beaninfo.editors.FontEditor">
<Font name="Tahoma" size="24" style="1"/>
</Property>
<Property name="text" type="java.lang.String" value="User Registration"/>
</Properties>
</Component>
<Properties>
<Font name="Times New Roman" size="14" style="1"/>
</Property>
<Property name="text" type="java.lang.String" value="Name :"/>
</Properties>
</Component>
<Properties>
</Property>
<Property name="text" type="java.lang.String" value="Contacat : "/>
</Properties>
</Component>
<Properties>
</Property>
<Property name="text" type="java.lang.String" value="Email : "/>
</Properties>
</Component>
<Properties>
</Property>
<Property name="text" type="java.lang.String" value="Address : "/>
</Properties>
</Component>
<Properties>
</Property>
<Property name="text" type="java.lang.String" value="User Name : "/>
</Properties>
</Component>
<Properties>
</Property>
<Property name="text" type="java.lang.String" value="Password : "/>
</Properties>
</Component>
<Component class="javax.swing.JTextField" name="jTextField1">
</Component>
</Component>
</Component>
</Component>
</Component>
</Component>
<Component class="javax.swing.JButton" name="jButton1">
<Properties>
<Property name="text" type="java.lang.String" value="Register"/>
</Properties>
<Events>
<EventHandler event="actionPerformed" listener="java.awt.event.ActionListener"
parameters="java.awt.event.ActionEvent" handler="jButton1ActionPerformed"/>
</Events>
</Component>
</SubComponents>
</Container>
</SubComponents>
</Form>

<Properties>
</Properties>
<AuxValues>
value="false"/>
value="false"/>
value="0"/>
</AuxValues>
<Layout>
</Group>
</Group>
</DimensionLayout>
</Group>
</Group>
</DimensionLayout>
</Layout>
<SubComponents>
<Layout>
<Component id="jLabel1" min="-2" pref="550" max="-2" attributes="0"/>
<EmptySpace min="10" pref="10" max="-2" attributes="0"/>
</Group>
</Group>
</Group>
<EmptySpace max="32767" attributes="0"/>
<Component id="l1" min="-2" pref="378" max="-2" attributes="0"/>
</Group>
</Group>
</DimensionLayout>
<Component id="l1" pref="185" max="32767" attributes="0"/>
attributes="0"/>
attributes="0"/>
</Group>
</Group>
</Group>
</DimensionLayout>
</Layout>
<SubComponents>
<Properties>
</Property>
<Property name="text" type="java.lang.String" value="CYCLE MANAGEMENT
SYSTEM "/>
</Properties>
</Component>
<Properties>
</Property>
<Property name="text" type="java.lang.String" value="ADMIN"/>
</Properties>
<Events>
</Events>
</Component>
<Properties>
</Property>
<Property name="text" type="java.lang.String" value="USER"/>
</Properties>
<Events>
</Events>
</Component>
<Component class="javax.swing.JLabel" name="l1">
</Component>
</SubComponents>
</Container>
</SubComponents>
</Form>

<Properties>
</Properties>
<AuxValues>
value="false"/>
value="false"/>
value="0"/>
</AuxValues>
<Layout>
</Group>
</Group>
</DimensionLayout>
</Group>
</Group>
</DimensionLayout>
</Layout>
<SubComponents>
<Layout>
<Group type="102" attributes="0">
</Group>
<Component id="jScrollPane2" min="-2" pref="614" max="-2" attributes="0"/>
</Group>
</Group>
</Group>
</Group>
</DimensionLayout>
<Component id="jScrollPane2" min="-2" pref="266" max="-2" attributes="0"/>
</Group>
</Group>
</DimensionLayout>
</Layout>
<SubComponents>
<Properties>
</Property>
<Property name="text" type="java.lang.String" value="My Product"/>
</Properties>
</Component>
<Container class="javax.swing.JScrollPane" name="jScrollPane2">
<AuxValues>
<AuxValue name="autoScrollPane" type="java.lang.Boolean" value="true"/>
</AuxValues>
<Layout
class="org.netbeans.modules.form.compat2.layouts.support.JScrollPaneSupportLayout"/>
<SubComponents>
<Component class="javax.swing.JTable" name="table1">
<Properties>
<Property name="model" type="javax.swing.table.TableModel"
editor="org.netbeans.modules.form.editors2.TableModelEditor">
<Table columnCount="0" rowCount="4"/>
</Property>
<Property name="tableHeader" type="javax.swing.table.JTableHeader"
editor="org.netbeans.modules.form.editors2.JTableHeaderEditor">
<TableHeader reorderingAllowed="true" resizingAllowed="true"/>
</Property>
</Properties>
</Component>
</SubComponents>
</Container>
</SubComponents>
</Container>
</SubComponents>
</Form>
5.1 SYSTEM TESTING
System Testing is a type of software testing that is performed on a complete integrated system to
evaluate the compliance of the system with the corresponding requirements. In system testing,
integration testing passed components is taken as input. The goal of integration testing is to
detect any irregularity between the units that are integrated together. System testing detects
defects within both the integrated units and the whole system. The result of system testing is the
observed behavior of a component or a system when it is tested. System Testing is carried out on
the whole system in the context of either system requirement specifications or functional
requirement specifications or in the context of both. System testing tests the design and behavior
of the system and also the expectations of the customer. It is performed to test the system beyond
the bounds mentioned in the software requirements specification (SRS).
5.1 Unit Testing
Unit testing is a level of software testing where individual units/ components of software are
tested. The purpose is to validate that each unit of the software performs as designed. A unit is
the smallest testable part of any software. It usually has one or a few inputs and usually a single
output. In procedural programming, a unit may be an individual program, function, procedure,
etc. In object-oriented programming, the smallest unit is a method, which may belong to a base/
super class, abstract class or derived/ child class. (Some treat a module of an application as a
unit. This is to be discouraged as there will probably be many individual units within that
module.) Unit testing frameworks, drivers, stubs, and mock/ fake objects are used to assist in
unit testing.
Fig 5.1 Unit testing is checked for the user registration
5.2 Integration Testing
Testing is which modules are combined and tested as a group. Modules are typically code
modules, individual applications, source and destination applications on a network, etc.
Integration Testing follows unit testing and precedes system testing. Testing after the product is
code complete. Betas are often widely distributed or even distributed to the public at large in
hopes that they will buy the final product when it is release.
Fig 5.2 the entire user details and the payment details is viewed in integration testing
5.3 Validation testing
In software testing, validation testing is the process of evaluating software during the
development process or at the end of the development process to determine whether it satisfies
specified business requirements. Validation Testing ensures that the product actually meets the
client's needs.
7. SYSTEM IMPLEMENTATION
Systems implementation is the process of: defining how the information system should be
built (i.e., physical system design), ensuring that the information system is operational and used,
ensuring that the information system meets quality standard (i.e., quality assurance)
7.1 SCREEN SHOT
Fig 7.1 cycle management home page

Fig 7.2 User registration page
Fig 7.3 user login page
Fig 7.4 User home page
Fig 7.5 Admin login
Fig 7.6 Admin home page

Fig 7.8 Admin add product
Fig 7.9 User search product

Fig 7.10 User product view
Fig 7.11 user buy product
Fig 7.12 Admin view the payment details

Fig 7.13 Admin view user details
BIBLIOGRAPHY
Book Reference
[1] Doug Lowe, “Java All-in-One For Dummies”, 2005
[2] Ken Kousen, Modern Java Recipes: Simple Solutions to Difficult Problems in Java 8 and
9, 2017
[3] Maurice Naftalin, “Java generics and collections”, 2006
[4] Rogers Cadenhead, “Sams Teach Yourself Java in 24 Hours”, 2002
Web reference:
https://www.java.com/en/
https://www.geeksforgeeks.org/java/
https://www.guru99.com/java-tutorial.html

Cycle

Uploaded by

Document Information

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

Cycle

Uploaded by

Copyright:

Available Formats

1.

2.1 PROJECT DESCRIPTION

2.1.1 Existing System

 Front End : JAVA

 The object-oriented programming methodology should be used.

Different "Editions" Of The Platform

A Java virtual machine (JVM), an implementation of the Java Virtual Machine

Runtime data areas

Native method Native

Fig 1: JVM Architecture

4.1 Logical Design

Fig 4.1 Logical design of the Cycle shop management system

4.2 Database Design

Field Type Null Default

id int(100) Yes NULL

product_name varchar(100) Yes NULL

brand varchar(100) Yes NULL

category varchar(100) Yes NULL

price varchar(100) Yes NULL

qty varchar(100) Yes NULL

gst varchar(100) Yes NULL

Field Type Null Default

id int(100) Yes NULL

user varchar(100) Yes NULL

product varchar(100) Yes NULL

type varchar(100) Yes NULL

price varchar(100) Yes NULL

qty varchar(100) Yes NULL

total varchar(100) Yes NULL

card varchar(100) Yes NULL

holder varchar(100) Yes NULL

exdate varchar(100) Yes NULL

ccv varchar(100) Yes NULL

status varchar(100) Yes NULL

report varchar(100) Yes NULL

Field Type Null Default

id int(100) Yes NULL

name varchar(100) Yes NULL

contact varchar(100) Yes NULL

email varchar(100) Yes NULL

address varchar(100) Yes NULL

username varchar(100) Yes NULL

password varchar(100) Yes NULL

cdate varchar(100) Yes NULL

status varchar(100) Yes NULL

4.3 Program Design

4.3.1 Module Description

(i) Admin login

(ii) Add products

(ii) User registration

(iii) User Search

(iv) User Buy

5.1 PROGRAM DEVELOPMENT

<?xml version="1.0" encoding="UTF-8" ?>

<Form version="1.3" maxVersion="1.9"

<?xml version="1.0" encoding="UTF-8" ?>

<Form version="1.3" maxVersion="1.9"

<?xml version="1.0" encoding="UTF-8" ?>

<Form version="1.3" maxVersion="1.9"

5.1 SYSTEM TESTING

7.1 SCREEN SHOT

Fig 7.1 cycle management home page

Fig 7.6 Admin home page