Car FurnishingFInal

An Online Shopping
Centre
INTRODUCTION
1
Online Car Furnishing is an online shopping website which deals in all kinds of car
furnishing items. The main objective of this project is to maintain the online shopping for
all those people who has cars and wanted to buy the furnishing items for their cars so that
they can save their time and money and get benefited.
Shopping has long been considered a recreational activity by many. Shopping online is no
exception. The goal of this application is to develop a web based interface for online
retailers. The system would be easy to use and hence make the shopping experience
pleasant for the users. This project is basically belong to E-Commerce.
Electronic commerce, commonly known as e-commerce,
Consists of the buying and selling of product or services over electronic systems such as
the Internet and Other computer networks. The amount of trade conducted electronically
has grown extraordinarily since the spread of the Internet. A wide variety of commerce is
conducted in his way, spurring and drawing on innovations in electronic funds transfer,
supply chain management, Internet marketing, online transaction processing, electronic
data Interchange (EDI), inventory management system, and Automated data collection
system. Modern electronic commerce typically uses the World Wide Web at some point
in the transaction’s lifecycle, although it can encompass a wider range of technologies
such as e-mail as well.
A large percentage of electronic commerce is conducted entirely electronically for virtual

items such as access to premium content on a website, but most electronic commerce
involves the transportation of physical items in some way. Online retailers are sometimes
known as e-trailers and online retail are sometimes known as e-tail.
The goal of this application is:
• To develop an easy to use web based interface where users can search for
products, view a complete description of the products and order the products.
• A search engine that provides an easy and convenient way to search for products
specific to their needs. The search engine would list a set of products based on the
search term and the user can further filter the list based on various parameters.
• An AJAX enabled website with the latest AJAX controls giving attractive and
interactive look to the web pages and prevents the annoying post backs.
• Drag and Drop feature which would allow the users to add a product to or
remove a product from the shopping cart by dragging the product in to the
shopping cart or out of the shopping cart.
• A user can view the complete specification of the product along with various
images and also view the customer reviews of the product. They can also write
their own reviews.
Objective of the application

2
This project is aimed at developing an on-line (web-based) mobile shop for a
company. Some features of this system will be login name and password for the staff
member as well as user, advertisement of the new mobile handset, downloading the
mobile software - ring tones, themes, wallpapers, and videos. Sale and purchase of the
mobile handsets and mobile accessories, comments on the user for the handsets they use
or know.
Thus summary of my project’s objective is as follows:-
To provide the complete description of a mobile handset.
 To provide a large range of car furnishing accessories.
 To provide secure mode of payment for purchase of car furnishing accessories.
 To provide free downloading of a large variety of car designing themes,

wallpaper, videos.
 To provide space for the user to comment on the features of car furnishing
accessories.
 To provide communication between staff members with other branches of the

company.
PROJECT CATEGORY
3
This project comes under RDBMS Category. This is a database-oriented project. All the
operations are revolving around data. Data is entered, retrieved, processed and displayed
in report format. Since the emphasis is on data, which is stored in tables, which are
related, this is definitely under Relational Database Management System (RDBMS).
This project Covers MYSQL.
Analysis
4
This involves analyzing the present system and documenting it. Also documenting
the proposed system, including producing, requirement specification, Data Flow
Diagrams, story board of the Site, ER diagrams and the Data Dictionary etc.
1. Problem Definition
This project is aimed at developing an on-line (web-based) mobile shop for a company.
Some features of this system will be login name and password for the staff member as
well as user, advertisement of the new mobile handset, downloading the mobile software
- ring tones, themes, wallpapers, and videos. Sale and purchase of the mobile handsets
and mobile accessories, comments on the user for the handsets they use or know.
2. Requirement Specification
To analyze the requirements of proposed system is one of the major sub – stage in
any system’s Development Life Cycle (SDLC). Unless we know the requirements of a
system’s users we cannot think of even staring the project. To understand the
requirements of any system, only its users can specify better. They know what are the
requirements of their system, and what are the deficiencies in the present system. To
analyze the problem and defining the problem are the steps of initial investigation. In
initial investigations facts are found and users requirements are analyzed.
2.1 Present System

Electronic commerce is conducted between business is referred to as business-to-business
or B2B. B2B can be open to all interested parties or limited to specific, pre-qualified
participants
2.2 Application Area
The information system cum Database management system, which we are
planning, has a huge application area which covers the “VR Consultant”, its various
branches in various cities, thousands of job –seekers and hundreds of employers. The site
can be used by thousands of job seekers to search for the job of their choice and place
their details to be accessed by the companies interested in hiring the candidates for their
jobs. The companies can place their jobs and interview details online with the site which
can be accessed by the candidates of right qualification and experience, again looking for
the job.
5
2.3 The proposed site

Users
As the described, the job site will be targeted or used by the persons seeking job
in various type of industries and companies looking for the suitable candidates with
required skills. The final and most importantly the Consultant itself is the Big user of the
site which helps it to manage that database Online and administering the whole site with
authorization to all login id and password or the registration procedure and their access to
the related information.
2.4 Main output Required
To provide the complete description of a Car Furnishing accessories.

To provide a large range Car Furnishing accessories.
To provide secure mode of payment for purchase of Car Furnishing accessories.
To provide free downloading of a large variety of Car Furnishing accessories themes,
wallpaper, videos.
To provide space for the user to comment on the features of Car Furnishing accessories.
To provide communication between staff members with other branches of the company.
3. Software Design
The purpose of the design phase is to plan a solution of the problem specified by the
requirements documents. This phase is the first step in moving from the problem domain
to the solution domain. Starting with what is needed; design takes us toward how to
satisfy the needs. The design of a system is perhaps the most critical factor affecting the
quality of the software. It has a major impact on the later phases, particularly testing and
maintenance
The design activity is divided into two phases: System Design and Detailed Design. In
system design the focus is on identifying the modules, whereas during detailed design the
focus is on designing the logic for each of the modules.
4. Coding
The goal of the coding phase is to translate the design of the system into code in a given
programming language. Hence during coding, the focus should be on developing
6
programs that are easy to read and understand, and not simply on developing programs
that are easy to write.
5. Te s t i n g
Testing is the major quality control measure used during software development. Its basic
function is to detect errors in the software. Testing not only uncover errors introduced
during coding, but also errors introduced during the previous phases. Thus, the goal of
the testing is to uncover requirement, design and coding errors in the programs.
Therefore, different levels of testing are used. Testing is an extremely critical and time-
consuming activity. It requires proper planning of the overall testing process. The output
of the testing phase is the test report and the error report. Test report contains the set of
test cases and the result of executing the code with these test cases. The error report
describes the errors encountered and the action taken to remove the errors.
6. Support and Maintenance

The System will undoubtedly undergo change after it is implemented to the customer
error have been encountered because the software must be adapted to accommodated
changes in its external environment. The linear sequential model is the oldest and most
widely used paradigm for software engineering.
Read project rarely follow the sequential flow that the model proposes. Although the
linear model can accommodate iteration, it does so indirectly. As a result, changes can
cause confusion as the project team proceeds.
It is often difficult for the customers to state all requirements explicitly. The linear
sequential requires this and has difficulty accommodating the natural uncertainly that exit
at the beginning of many project.
The customer has patience. A working version of the program will not be available until
late in the project time span.
7. FEASIBILITY-STUDIES
Feasibility is the determination of whether or not a project is worth doing.
The process followed in making this determination is called a feasibility study. Feasibility
study determines if a project can and should be done. Generally, feasibility studies are
undertaken within tight time constraints and normally culminate in a written and oral
feasibility report. The contents and recommendations of such a study will be used as a
sound basis for deciding whether to proceed, postpone or cancel the project. Thus, since
the feasibility study may lead to the commitment of large resources, it becomes necessary
that it should be conducted competently and that no fundamental errors of judgment are
made.
DATA FLOW DIAGRAMS

7
A graphical tool used to analyze the moment of data through a system manual or
automated including process, stores of data, and delays in the system. Data Flow
Diagrams are the central tool and the basis from which other components are developed.
The transformation of data from input to output, through processes, may be described
logically and independently of the physical components associated with the system. The
DFD is also known as dataflow graph or a bubble chart.
Context Diagram:
The top-level diagram is often called a “Context Diagram”. It contains a

single process, but plays a very important role in studying the current system. The context
diagram defines the system that will be studied in the sense that it determines the
boundaries. It defines entire software element as single Bubble with input and output data
indicated by incoming and out going arrows respectively. There are two types of data
flow diagrams
1. Physical DFD:
The physical DFD is the model of the current system and is used to
ensure that the current system has been clearly understood. Physical
DFD’s show actual devices, departments, etc involved in the current
system.
1. Logical DFD:
Logical DFD’s are the model of the proposed system. They clearly should
show the requirements on which the new system should be built.
Later during design activity this is taken as the basis for drawing the system’s
architecture.
 DATA FLOWDIAGRAMS
8
CONTEXT DIAGRAM
ADMINISTRATO CUSTOMER
R
Online Car
Furnishing
FRANCHISE VENDOR
DATA FLOW DIAGRAM OF ADMINISTRATOR MODULE
9
AIN
WEB
APPLICATIO
ADMINISTRATOR N
LOGOUT
ADD
PRODUCT
S LOOKUP
USER
TRANSACTIO
N
DELETE
PRODUC INVENTOR
TS UPDATE DAY TO Y
PRODUC DAY LOOKUP
T TRANSACTI
DETAILS ONS
DATASTORE
DATA FLOW DIAGRAM OF CUSTOMER
10
REGISTRATION
CUSTOMER
LOGIN
TRANSAC
TIONS
LOGOUT
REQUEST EDIT
USER
S PROFILES CHANGE
PASSWORD
PRODUC
T
STATUS
Proceed for
transactions on
selected items
ADD
ITEMS TO
CART
LOGIN
DATA DLOW DIAGRAM OF FRANCHISE
11
FRANCHISE
REGISTRATI
ON
LOGIN
UPDATE
PROFILE
VERIFICATIO LOGOUT
N OF
VENDORS
12
VENDORS DATA FLOW DIAGRAM
VENDOR REGISTRATION
LOGIN
UPDATE
PROFILE
LOGOUT
DELIVERY
OF
PRODUCTS
Franchis
e details
13
OVERALL DATAFLOW
E - R DIAGRAM
14
ENTITY-RELATIONSHIP Diagrams
E-R (Entity-Relationship) Diagram is used to represent the relationship between

entities in table. An E-R Diagram allows us to describe the data involved in real-world
enterprise in terms of objects and their relationships and is widely used to develop an
initial database design. It provides useful concepts that allow us to move from an
informal description of what users want from their database.
The symbols used in E-R diagrams are:
SYMBOL PURPOSE
An E-R Diagram allows us to describe the data involved in real-world enterprise

in terms of objects and their relationships and is widely used to develop an initial
database design. E-R Diagram is a tool for structured analysis.
An entity is an object in the real world that is distinguishable from other objects.
An entity is described using a set of attributes. .A relationship is an association among
two or more entities. Collection of similar entities is called an entity set. A key is a
minimal set of attributes whose values uniquely identify an entity in the set. There could
be more than one candidate key. We designate one of them as the primary key. A
15
relationship is an association among two or more entities. Collection of set of similar
relationships is known as relationship T set.
ENTITY: Product
Pd_price Pd_qty
Pd_des Pd_date
Pd_name Pd_last_update
Pd_id Pd_type
Product
ENTITY: Category
16
Cat_name
Cat_id
Cat_des
Category
ENTITY: Shopping Cart
Cart_qty
Cart_id
Cart_date
Shopping Cart
17
ENTITY: Customer
Cust_occupation
Cust_dob
Cust_email
Cust_name Cust_setDate
Cust_nationality
Cust_id yyyyyyty
Cust_mailupdate
Customer
ENTITY: Administrator
18
Ad_address
Ad_email
Ad_name
Ad_id Ad_phone
Administrator
Entity: Wish-List
19
Pd_name Cust_name
e
Wish-List
Entity: Query
query_des
query_id query_ans
Query
E-R Diagram:
20
1
1 Administrator
1
Shopping Cart
1
1 answers
manages holds
Views
N N
1
1 N
Category has Product ha
1 N N
s
Wish-list
selects N
1 Queries
M
Adds
1 N
to Customer Poses
DATABASE SCHEMA
21
DATA STRUCTURES:
This part of the Design consists the overall database schema or we can say that tables which
consists various types of records. Table of a database consist attributes, entities tuples for storing
and manipulating records
Database design
Table definitions of Customer:
Table No.: Cust1

Table Name: Cust_info
Table Description: This table contains the personal information of the Customer.
Column Column Null/ Remarks
S.No Column Name
Description Type Not Null
1 10 digit alpha
Cust_id Unique Id Varchar Not Null
numeric num
2 Cust_firstname Varchar
3 Cust_lastname Surname Varchar
4 Cust_dob Date of Birth Varchar Valid Date
5 Cust_gender Male/Female Varchar
6 Cust_occupation Name Varchar
7 Cust_mailid Mail Id Varchar
8 Cust_address Address1 Varchar
9 Cust_nationality Nationality Varchar
10 Cust_phone Phone Residence Number
10 Digit
11 Cust_mobile Mobile No Varchar
Number
12 Cust_setDate Date Varchar
13 Cust_mail update Date Varchar
CONSTRAINTS:
Primary Key: Cust_id
Table definitions of Administrator:
22
Table No.: Admin1
Table Name:
Administrator_info
Table Description: This table contain the information of the Administrator
Seq. # Column Column Column Type Null/ Remarks
Name Description Not Null
1 Ad_id Unique identifier Varchar Not Null 10 digit alpha
numeric num
2 Ad_firstname Varchar Not Null
3 Ad_lastname Surname Varchar
4 Ad_mailid Mail Id Varchar
5 Ad_phone Phone Varchar 10 Digit Num
CONSTRAINTS:
Primary Key: Ad_id.
Table definitions of Product:
Table No.: Prod1

Table Name:
Product_info
Table Description: This table contain the information of products..
Seq. # Column Column Column PK/FK? Null/ Remarks
Name Description Type Not Null
1 Pd_id Unique identifier Varchar PK Not Null 10 digit alpha numeric
num
2 Pd_name product Varchar
3 cat_id Unique identifier Varchar FK
4 Pd_des Description Varchar
23
product
5 Pd_price Amount Varchar
6 Pd_qty Quantity Varchar
7 Pd_date date Varchar
8 Pd_lastupdate date Varchar
9 Pd_type Type of product varchar
CONSTRAINTS:
Primary key: Pd_id
Foreign key : Cat_id.
Table definition of Category:
Table no: Category1

Table Name: Category_Info
Table description: This gives the info about Categories.
Seq. # Colum Column Column Null/ Remarks
1 Cat_id Unique identifier Varchar Not Null 10 digit alpha
numeric num
2 Cat_name Name of category Varchar
3 Cat_des Description Varchar
CONSTRAINTS:
Primary key: Cat_id
24
Table description for shopping cart:
Table Description: This table contains information of shopping cart.

Seq. # Column Column Column Null/ Remarks
1 Cart_id Unique identifier Varchar Not Null 10 digit alpha
numeric num
2 Cart_qty Quantity Varchar
3 Cart_date Date Varchar
CONSTRAINTS:
Primary key: cart_id
Table description for wish list
Table No.: Wish list1
Table Name:
WISH_LIST
Table Description: This table contains information about wish list
1 Cust_name Name varchar

2 Pd_name Product name varchar
Table description for query list
Table No.: Query1
Table Name:
Query_table
Table Description: This table contains information about queries
25
1 Query_usid Unique number Varchar Not Null
2 Query_id Query id Varchar
3 Query_des Query Description Varchar
4 Query_ans Query answer Varchar
CONSTRAINTS:
Primary key: Query_id.
Module description
Modules description
MODULES AND THEIR DESCRIPTION
 Product:
In this module, product will have id, name, description, price,
quantity, date, last update, type. Products will all the description
which will satisfy the user.
 Category:
Through this module, it will have id, name, description’s. User
will be much satisfied by this module.
 Shopping cart:
Through this module cart will have its own id, quantity, date. It
will complete description of the shopping cart.
 Customer:
26
In this module, user will have an id, name, date of birth,
occupation, email address, set date, nation. It will have a
mail update. User can browse the site easily with its
account. He/she will be able to browse and download the
requirements.
 Administrator:
In this module, administrator will have an id, name,

address email account, phone no... It will comprise of
complete description of the administrator.
 Wish list:
This module will provide product name and the customer

name. This module will provide the customer to
purchase the product with complete description.
 Query:
In this module, there will be some query which will arise

to the user. Query will have an id, description, answer.
Solutions to the user will satisfy the user.
27
Tools Platform Used
Software and Hardware Tools
SYSTEM REQUIREMENTS
Software Recommended:
 Microsoft Windows 7
 Java JSP
 Internet Explorer 6.0 or Above
 MSSQL
PLATFORM USED:
 Windows 7
28
Report Generation
Report generation is an important parts any system because it provides information to

users which help in decision making. Online shopping website also generates some report
according to its user type. Some of the record are follow below with its user type.
Reports generated for Administrator:
Product detail
 Products availability information with different category.
User or customers
 Number of customers.
Sales Report
 Total sales report of given interval.
 Total COD sales.
 Total online sales.
Manufactures report
 Different manufactures of different products.
29
Security mechanism
Security mechanisms should be taken for secure and reliable software. These mechanisms
are not only required for proper implementation and working of the system but also
ensure a systematic development. The security mechanisms undertaken for this project
will be as follows:
Development Time Security

Passwords for folders:
The folders and files for development will be password protected. Many types of
software are available for password protection. These will be installed in the computer
wherein the development will be taking place. Inspire of the security provided by
Windows XP, these installation of softwares will give an added advantage as the
developer might leave the terminal for a while then the folders if not protected can be
manipulated by any one else.
Use of Antivirus:
A good antivirus like Norton, McAfee or quick heal will be used during development.
This will protect that the files won’t get corrupt and the development work won’t get
hampered due to any virus infecting the computer. Viruses are a threat for computers.
They slow the development procedure by slowing the computers and also corrupt the
systems and
Hamper files and thus development.
30
Implementation Time Security
Security for accessing:

This will consist of user name and passwords for using the software. There will be two
types of user. Later on according to requirements, many user types can be added for using
the software. These will be according to requirement and inline with security provisions.
At present only two types of users have been decided for the project. One user will be
Administrator, other will be normal. Administrator will get the privileges to manipulate
all data, view all reports and create new users , modify or delete existing ones.
Administrator can manipulate database also. Any additions of hotel, or membership offers
and new venues will be undertaken by the Administrator. Normal users will be only
entering the data and will be able to view selected reports.
Use of AntiViruses:
Use of antivirus will be recommended at the implementation end also. Though these will
not be provided by the developer, but the client would be advised to procure them from
vendors.
Security for database:
The passwords of database will be changed by the administrator and should be changed
on regular basis. This will ensure that tables can not be mishandled by any one.
31
LIMITATIONS: -
 This project does not Edit the date of connection or store the date of
transfer in case of connection transfer.
 System date for the project is like as backbone for the human, i.e.
proposed system is depends on system date so it must be correct.
 Cannot be connected to the Internet.

 There are some inherent problems like time, finance etc. to elaborate
further study.
Future scope and further

enhancement
Today the internet and its boom have created a new economic scenario that not only
stresses on the classical concept of the “product” but also on the modern concept of “service”.
It is this level of service that dictates whether a commercial venture will succeed or not in the market.
To provide a high accessibility of service we will design the online shopping website, so that potential
customers need not go to a physical shop to buy products or services. There are several objective of
this websites are following given bellows.
• This site is gives all the information about the e-shopping to provide better service for the
customer.
•It provides the facility to the customers who want to shop on-line due to lock of time.
•It provides facility to the customer to payment by the cash and cheque and DD also.
•It’s providing the full details about the product and related information about the product like cost, size
etc.
•With the help of it we can save the time and money also.
•It provides the remote shopping by the cash, or DD, or Debit card also
Building a project is just a first step toward its development. By time improvement and
upgrade is necessary According to demand and choice. In future an android client
application can be develop to make it fast accessible from user mobile handsets. With the
32
technology development new features can be added which make it more user friendly
then before.
User feedback is a key source for making any system form better to best. Enhancement
will be carried out according to feedback data from users.
33
PROJECT
REPORT
34
An Online Shopping
Centre
INTRODUCTION
35
Online Car Furnishing is an online shopping website which deals in all kinds of car
furnishing items. The main objective of this project is to maintain the online shopping for
all those people who has cars and wanted to buy the furnishing items for their cars so that
they can save their time and money and get benefited.

The goal of this application is:
• To develop an easy to use web based interface where users can search for
products, view a complete description of the products and order the products.
• A search engine that provides an easy and convenient way to search for products
specific to their needs. The search engine would list a set of products based on the
search term and the user can further filter the list based on various parameters.
• An AJAX enabled website with the latest AJAX controls giving attractive and
interactive look to the web pages and prevents the annoying post backs.
• Drag and Drop feature which would allow the users to add a product to or
remove a product from the shopping cart by dragging the product in to the
shopping cart or out of the shopping cart.
• A user can view the complete specification of the product along with various
images and also view the customer reviews of the product. They can also write
their own reviews.
Objective of the application
36
or know.

wallpaper, videos.
accessories.

company.
PROJECT CATEGORY
37
This project comes under RDBMS Category. This is a database-oriented project. All the
operations are revolving around data. Data is entered, retrieved, processed and displayed
in report format. Since the emphasis is on data, which is stored in tables, which are
related, this is definitely under Relational Database Management System (RDBMS).
This project Covers MYSQL.
38
TOOLS PLATFORM USED
Software and Hardware Tools
SYSTEM REQUIREMENTS
Software Recommended:
 Microsoft Windows 7
 Java JSP
 Internet Explorer 6.0 or Above
 MSSQL
PLATFORM USED:
 Windows 7
JAVA DATABASE CONNECTIVITY (JDBC)
JDBC OVERVIEW :
JDBC is a Java API for executing SQL statements. (JDBC is a
trademarked name and is not an acronym; nevertheless, JDBC is often thought of as
understanding for "Java Database Connectivity".) It consists of a set of classes and
interfaces written in the Java programming language. JDBC provides a standard API
for tool/database developers and makes it possible to write database applications using
a pure Java API.
Using JDBC, it is easy to send SQL statements to virtually any relational
database. In other words, with the JDBC API, it is not necessary to write one program to
39
access a Sybase database, another program to access a Oracle database, another program
to access a Informix database, and so on.. One can write a single program using the
JDBC API, and the program will be able to send SQL statements to the appropriate
database. And with in an application written in Java programming language, one also
doesn't have to worry about writing different applications to run on different platforms.
The combination of Java and JDBC lets a programmer to write it once run it anywhere.
Java, being robust, secure, easy to understand, and

automatically downloaded on a network, is an excellent language basis for
database applications. What is needed is a way for Java applications to walk
to a variety of different databases. JDBC is the mechanism for doing this.
JDBC extends the concepts, which can be done in Java. For
example, with Java and JDBC API, it is possible to publish a web page
containing an applet that uses information obtained from a remote database
or an enterprise can use JDBC to connect all this employees (even if they are
using conglomeration of Windows, Macintosh, and Unix machines) to one
or more internal databases via an Internet. With more and more
programmers using the Java programming language, the need for easy
database access from Java is continuing to grow.
MIS managers like the combination of Java and JDBC because

it makes disseminating information easy and economical. Businesses can
continue to use their installed databases and access information easily even
of it is stored on different database management systems. Development time
for new applications is short. Installation and version controls are greatly
simplified. A programmer can write an application or an update once, put it
on the server, and everybody has access to the latest version. And for
40
business selling information services, Java and JDBC offer a better way of
getting out information updates to external customers.
WHAT DOES JDBC DO ?

Simply put, JDBC makes it possible to do three things:
1. Establish a connection with the database
2.Send SQL statements
3.Process the results
The following code fragment gives a basic example of these three steps:
Connection con = DriverManeger.getConnection( “Jdbc: odbc: omega”, “login”,
“password”);
Statement stmt = con.createStatement();
ResultSet rs = stmt.executeQuery (“select a, b, c from Table1”);
while (rs.next ())
{
int x = getInt (“a”);
String s = getString(“b”);
Float f = getFloat(“c”);
}
USING JDBC INSTEAD OF CGI :
Until now, the only way to access a database through Java has
been to use streams in Java to call and access Common Gateway Interface
(CGI) programs. Calling a CGI script from Java lets you call a separate
program that accesses the database and returns results.
41
Using this approach is slow and lets more bugs creep into applications.
Developing into two different development languages requires the knowledge of two
technologies. When we use JDBC we need to know only the Java language, whereas
when we use CGI we must use Java and another language.
Another reason to use JDBC is that it is noticeably

faster than CGI approach. Using CGI usually requires that
you call another program that must be executed by the
computer. This separate program then accesses the database
and processes the data, returning it to the calling program
in a stream. This requires multiple levels of processing,
which in turn increases wait time as well s enables more
bugs to appear. The following figure displays how CGI
program is executed.
Java Web Server CGI Databas

Applicati Scri e
Fig. Calling a CGI script.
Whereas calling a CGI script involves actually executing a new script,

usually through a web server, executing a JDBC statement against the database requires
only some sort of server that passes the SQL commands through the database. This
speeds up dramatically the time it takes to execute SQL statements. Whereas the CGI
script must actually connect to the database and process the results, the JDBC solution
lets your Java application have the connection to the database so that thew application
can perform all of the processing. The following figure displays how a JDBC statement is
executed.
Java Application JDBC Server Database
42
Fig. Executing a JDBC statement
JDBC IS A LOW-LEVEL API AND A BASE FOR

HIGER-LEVEL APIs :
JDBC is a “low-level” interface, which means that it is used to invoke (or
“call’) SQL commands directly. It works very well in this capacity and is easier to use
than other database connectivity. JDBC APIs, were also designed to be a base upon which
to build higher-level interfaces and tools. A higher-level interface is “user-friendly”, using
a more understandable or more convenient API that is translated behind the scenes into a
low-level interface such as JDBC. At present, two kinds of higher-level APIs are under
development on top of JDBC:
1. An embedded SQL for Java: At least one vendor plans to build this. DBMS
implement SQL, a language designed specifically for use with databases. JDBC
requires that SQL statements be passed as strings to Java methods. An embedded
SQL processor allows a programmer to instead mix SQL statements directly with
Java: for ex: a Java variable can be SQL statement to receive or provide SQL mix
into Java with JDBC calls.
2. A direct mapping of a relational database tables to Java classes: JavaSoft and others
have announced plans to implement this. In this “object/relational” mapping, each
row of the table becomes an instance of that class, and each column value
corresponds to an attribute of that instance. Programmers can then operate directly on
Java objects; the required SQL calls to fetch and store data are automatically
generated “beneath the covers”. More sophisticated mappings are also provided, for
example, where rows of multiple tables are combined into Java class.
43
2.1 As interest in JDBC has grown, more developers have been working
in JDBC based tools to make building programs easier, as well.
Programmers have also been writing applications that make accessing
a database easier for the end-user. For eg, an application might
present a menu of database tasks from which to choose. After a task is
selected, the application presents prompts and blanks for filling in
information needed to carry out the selected task. With the required
input typed in, the application then automatically invokes the
necessary SQL command. With the help of such an application, users
can perform database tasks even when they have little or no
knowledge of SQL syntax.
JDBC Vs ODBC AND OTHER APIs :

At this point, Microsoft’s ODBC (Open Database Connectivity) API is
the most widely used programming interface for accessing relational databases. It offers
the ability to connect to almost all databases on almost all platforms. So why not use
ODBC form Java?
The answer is that you can use ODBC from Java, but this is best done with
the help of JDBC in the form of the JDBC-ODBC Bridge. The question now becomes
‘Why do you need JDBC’? There are several answers to this question:
1. ODBC is not appropriate for direct use from Java, because it uses a C interface.Calls
from Java to native C-code have a number of drawbacks in the security,
implementation robustness and automatic probability of applications.
2. A literal translation of the ODBC C API into a Java API would not be desirable. For
eg, Java has no pointers, and ODBC makes copious use of them, including the
44
notoriously error-prone generic pointer “void *”. You can think of JDBC ac ODBC
translated into an object-oriented interface that is natural for Java programmers.
3. ODBC is hard to learn. It mixes simple and advanced features together, and it has
complex options even for simple queries. JDBC, on the other hand was designed to
keep simple things simple while allowing more advanced capabilities where required.
4. A Java API like JDBC is needed in order to enable a “pure Java” solution. When
ODBC is used, the ODBC driver manager and drivers must be manually installed on
every client machine. When the JDBC driver is written completely in Java, however,
JDBC code is automatically installable, portable, and secure on all Java platforms
from network computers to mainframes.
In summary, the JDBC API is a natural Java interface to the basic SQL
abstractions and concepts. It builds on ODBC rather than starting from scratch, so
programmers familiar with ODBC will find it very easy to learn JDBC. JDBC returns
the basic design features of ODBC; in fact both interfaces are based on the (X/Open
SQL CLI (Call Level Interface). The big difference is that JDBC builds on end
reinforces the style and virtues of Java, and, of course it is easy to use.
More recently, Microsoft has introduced new APIs beyond ODBC: RDO,
ADO, and OLE dB. These designs move in the same direction as JDBC in many
ways, that is, in being an object-oriented database interface based on classes that can
be implemented on ODBC. However, there is no compelling functionality in any of
these interfaces to make them an alternative basis to ODBC, especially with ODBC
driver market well established. Mostly they represent a thin veneer on ODBC. This is
not to say that JDBC does not need to evolve from the initial release; however, the
general feeling is that most new functionality belongs in higher-level APIs such as the
object/relational mappings and embedded SQL mentioned in the previous section.
45
Analysis
This involves analyzing the present system and documenting it. Also documenting
the proposed system, including producing, requirement specification, Data Flow
Diagrams, story board of the Site, ER diagrams and the Data Dictionary etc.
1. Problem Definition
This project is aimed at developing an on-line (web-based) mobile shop for a company.
Some features of this system will be login name and password for the staff member as
well as user, advertisement of the new mobile handset, downloading the mobile software
- ring tones, themes, wallpapers, and videos. Sale and purchase of the mobile handsets
and mobile accessories, comments on the user for the handsets they use or know.
2. Requirement Specification
To analyze the requirements of proposed system is one of the major sub – stage in
any system’s Development Life Cycle (SDLC). Unless we know the requirements of a
system’s users we cannot think of even staring the project. To understand the
requirements of any system, only its users can specify better. They know what are the
requirements of their system, and what are the deficiencies in the present system. To
analyze the problem and defining the problem are the steps of initial investigation. In
initial investigations facts are found and users requirements are analyzed.
2.1 Present System

46
Electronic commerce is conducted between business is referred to as business-to-business
or B2B. B2B can be open to all interested parties or limited to specific, pre-qualified
participants.
2.2 Application Area

The information system cum Database management system, which we are
planning, has a huge application area which covers the “Car Furnishing Elements”, its
various branches in various cities, thousands of job –seekers and hundreds of employers.
The site can be used by thousands of job seekers to search for the job of their choice and
place their details to be accessed by the companies interested in hiring the candidates for
their jobs. The companies can place their jobs and interview details online with the site
which can be accessed by the candidates of right qualification and experience, again
looking for the job.
2.2.1.1 The proposed site

Users
As the described, the job site will be targeted or used by the persons seeking job
in various type of industries and companies looking for the suitable candidates with
required skills. The final and most importantly the Consultant itself is the Big user of the
site which helps it to manage that database Online and administering the whole site with
47
authorization to all login id and password or the registration procedure and their access to
the related information.
2.3 Main output Required
To provide the complete description of a Car Furnishing accessories.

To provide a large range Car Furnishing accessories.
To provide secure mode of payment for purchase of Car Furnishing accessories.
To provide free downloading of a large variety of Car Furnishing accessories themes,
wallpaper, videos.
To provide space for the user to comment on the features of Car Furnishing accessories.
To provide communication between staff members with other branches of the company.
3. Software Design
The purpose of the design phase is to plan a solution of the problem specified by the
requirements documents. This phase is the first step in moving from the problem domain
to the solution domain. Starting with what is needed; design takes us toward how to
satisfy the needs. The design of a system is perhaps the most critical factor affecting the
quality of the software. It has a major impact on the later phases, particularly testing and
maintenance
The design activity is divided into two phases: System Design and Detailed Design. In
system design the focus is on identifying the modules, whereas during detailed design the
focus is on designing the logic for each of the modules.
4. Coding
The goal of the coding phase is to translate the design of the system into code in a given
programming language. Hence during coding, the focus should be on developing
programs that are easy to read and understand, and not simply on developing programs
that are easy to write.
48
5. Te s t i n g
Testing is the major quality control measure used during software development. Its basic
function is to detect errors in the software. Testing not only uncover errors introduced
during coding, but also errors introduced during the previous phases. Thus, the goal of
the testing is to uncover requirement, design and coding errors in the programs.
Therefore, different levels of testing are used. Testing is an extremely critical and time-
consuming activity. It requires proper planning of the overall testing process. The output
of the testing phase is the test report and the error report. Test report contains the set of
test cases and the result of executing the code with these test cases. The error report
describes the errors encountered and the action taken to remove the errors.
6. Support and Maintenance

The System will undoubtedly undergo change after it is implemented to the customer
error have been encountered because the software must be adapted to accommodated
changes in its external environment. The linear sequential model is the oldest and most
widely used paradigm for software engineering.
Read project rarely follow the sequential flow that the model proposes. Although the
linear model can accommodate iteration, it does so indirectly. As a result, changes can
cause confusion as the project team proceeds.
It is often difficult for the customers to state all requirements explicitly. The linear
sequential requires this and has difficulty accommodating the natural uncertainly that exit
at the beginning of many project.
The customer has patience. A working version of the program will not be available until
late in the project time span.
7. FEASIBILITY-STUDIES
49
made.
FEASIBILITY-STUDIES
made.
DIFFERENT TYPES OF FEASIBILITY
1) Technical feasibility
2) Operational feasibility
3) Economic feasibility
4) Social feasibility
5) Management feasibility
6) Legal feasibility
7) Time feasibility
1) Technical Feasibility :-
This is concerned with specifying equipment and software that will successfully the user
requirement. The technical needs of the system may vary considerably, but might include:
 The facility to produce outputs in a given time.
 Response time under certain conditions.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distant location.
In examining technical feasibility, configuration of the system is given more

importance than the actual make of hardware. The configuration should give the
50
complete picture about the system’s requirements: How many workstations are
required, how these units are interconnected so that could operate and
communicate smoothly. What speeds of input and output should be achieved at
particular quality of printing. This can be used as a basis for the tender document
against which dealers and manufacturers can later make their equipment bids.
At the feasibility stage, it is desirable that two or three different configurations
will be pursued that satisfy the key technical requirements but which represent
different levels of ambition and cost. Investigation of these technical alternatives
can be aided by approaching a range of suppliers for preliminary discussions. Out
of all types of feasibility, technical feasibility generally is the most difficult to
determine.
2) Operational feasibility :-
It is mainly related to human organization and political aspects. The points to be
considers are:-
 What changes will be brought with the system?
 What organizational structures are disturbed?
 What new skills will be required? Do the existing staff members have these
skills?
If not, can they be trained in due course of time?
Generally project will not be rejected simply because of operational infeasibility but such
considerations are likely to critically affect the nature and scope of the eventual
recommendations. This feasibility study is carried out by a small group of people who are
familiar with information system techniques, who understand the parts of business that
are relevant to the project and are skilled in system analysis and design process.
3) Economic Feasibility :-
Economic analysis is the most frequently used technique for evaluating the effectiveness
of a proposed system. More commonly known as cost/benefit analysis; the procedure is
to determine the benefits and savings that are expected from a proposed system and
compare them with costs. If benefits outweigh costs, a decision is taken to design and
implement the system. Otherwise, further justification or alternative in the proposed
51
system will have to be made if it is to have a chance of being approved. This is an
ongoing effort that improves in accuracy at each phase of the system life cycle.
4) Social feasibility :-
Social feasibility is a determination of whether a proposed project will be acceptable to
the people or not. This determination typically examines the probability of the project
being accepted by the group directly affected by the proposed system change.
5) Management feasibility :-
It is determination of whether a proposed project will be acceptable to management. If
management does not accept a project or gives a negligible support to it, the analyst will
tend to view the project as a non-feasible one.
6) Legal feasibility :-
Legal feasibility is a determination of whether a proposed project infringes on known
Acts, Statutes, as well as any pending legislation. Although in some instances the project
might appear sound, on closer investigation it may be found to infringe on several legal
areas.
7) Time feasibility :-
Time feasibility is a determination of whether a proposed project can be implemented

fully within a stipulated time frame. If a project takes too much time it is likely to be
rejected.
52
Project Planning
The planning, design, and installation of a system termed a project and is directed by a
project leader who uses the available to resources to produce a new or better system for
the organization.
In large companies, the installation of a computer system may take years and involves
thousands of people, planning for smaller projects also requires effective management
control to realize the desired results. Thus, project planning for any company has the
following four main steps:
1. Organization the resources available for the project.

2. Scheduling the events of the project.
3. Evaluating the progress.
4. Establishing standards for the project.
An effective manager is essential for successful project planning. The techniques of
project planning are not a substitute for good management, but merely a tool to be used
by managers to achieve better results. Only effective management can complete the
project on time, within budget, and with satisfactory results.
To achieve a goal, there should be strong determination and it should always be in one’s
mind. Consequently, defining the objective is the first action taken in any project. Along
with defining objectives, corporate management must assign priorities to various project
that are underway and clarify the relationship between system projects and existing
system. A system project requires extensive interaction between developers and users.
Users are of courses, preoccupied with day to day operations, and it cannot be assumed
that they will be enthusiastic about participating in a system study. However, only when
management clearly defines the importance of users participation in systems
development, then the necessary co-operation can be expected from users.
Many system are designed and implemented through project teams headed by a project
leader. The team may be relatively small during the feasibility stage, consisting of a few
highly qualified systems people, users and manager. During the design phase, when more
detailed work is required, the size of the team normally increases, supported by junior
53
analysts, programmers. When the project has been completed, the team is disbanded and
each member is reassigned to another project.
To organize a project, the project leader must determine who all are required for the
project, when they are available, and for how their services can be expected. The key
people required in a systems project are often the key people in the day to day operation
of an organization, and they probably will have to continue their efforts, the project
leader must avoid scheduling important project activities when the users are very busy
with normal duties. For users who are “always busy”, plan must be made to utilize
overtime or/and shift personnel, to free the key systems users for participation in the
project.
It is important when organization a project to ensure that every person knows his or
her role in the project and is aware of corporate objectives. This is accomplished through
formal training as well as informal conversation.
The project leader is responsible for the completion of a project, but obviously cannot do
it alone. Responsibilities must be defined precisely, and overlapping responsibilities
avoided. When the phase of a project breaks down, is behind schedule, or is over budget,
the leader of a well- organized project will be able to identify the person who can provide
information and, perhaps, the solution to the problem.
Besides organizing people, the project leader must budget money and order equipment.
Acquainting people with their responsibilities and enabling them to discharge these
responsibilities is the essence of leadership.
54
SOFTWARE REQUIREMENT SPECIFICATIONS (SRS)
SRS is a complete document of the requested software. It is prepared by the developer
and provides after detailed communication with the user. It define external interface of
the system that identify the information flow ‘from the start and to the development of
the system’ it also combine designing tools and represent the functional and non-
functional requirements of the software. The Software requirement Specification is
produced at the culmination of the analysis task. The function and performance allocated
to software as part of system engineering are refined by establishing a complete
information description, a detailed functional and behavioral description, an indication of
performance requirements and design constraints, appropriate validation criteria.
I. Introduction
The introduction states the goal and objectives of the software, describing it in
the context of the computer-based system
 Goal and objectives

The main objective of the project is clearly to improve the manual tedious work of the
online book shop by converting the manual work into a fast computerized software. By
means of computerization we have tried to automate the overall management of a book
shop. The project is very helpful for the music book to deal with daily cassettes
transactions and fulfill all the requirements.
The main objective behind the development of online book shop is to develop an
information system that will increase the effectiveness and efficiency of the planning and
the functions of the library by providing more timely, relevant and accurate information.
Advantages of the system:

 Faster book monitoring
 Reliable operation
 Time saving in comparison to manually maintenance of cassettes
records
55
 Justified / specified data view
 Easy administration
 Report generation
II. Information Description

It provides a detailed description of the problem that the software must solve. Information
content and relationships, flow and structure are documented. Hardware, software, and
human interfaces are described for external system elements and internal software
functions
Topics that have been dealt under this heading are:
 Identification of need
 Preliminary investigation
 Hardware and software specification
 Feasibility study
III. Functional Description

In this a description of each function required to solve the problem is presented. Design
constraints are stated and justified, performance characteristic
Are stated and solved, one or more diagrams are included to graphically represent the
overall structure of the software.Topics that has been dealt under this heading are:
 Functional Partioning
 Functional Description
 Data Flow Diagram Data description
IV. Data Description
In data description, information is represented at a high level of abstraction(user view of
data). The structure of data has always been an important part of software design.
 Data dictionary
 Table
 ER diagram
V. Behavioral Description
56
It examines the section of the specification which examines the operation of the software
as a consequence of external events and internally generated control characteristics.
Topics that has been dealt under this heading are
 Control Description
 Control Specification
 Design Constraints
 System Activity
V. Validation and criteria

In this classes of tests must be conducted to validate function, performance and
constraints. It act as a implicit review of all other requirements.
Topics that has been dealt under this heading are
 Classes of Tests
 Performance Bounds
 Special Considerations
VII Bibliography and Appendix

Bibliography
It contains references to all documents that relate to the software.
Software books, vendor literature etc.
Appendix
Tabular data, detailed description of algorithm, charts and graphs
are presented in it.
INFORMATION DESCRIPTION
Online Car Furnishing has been designed to cater all the functional requirements of a
music cassette shop, which contains all types of book shop. The system maintains the list
of books, their copies available as well as the list of issued books, list of customers to
whom the books has been sold and the list of dealers also to whom books have been
purchased. It gives upto date information regarding the books in the shop. The system has
the following salient features: -
1. The system is modular in design.
57
2. It is user friendly menu driven
3. The system performs extensive validation checks to ensure error free data.
IDENTIFICATION OF NEED
It is expected that each institution will have reviewed the State Strategic Plan and the
DTAE Strategic Plan and will have developed a Strategic Plan for its own operations. No
project should be considered which does not further the goals and objectives of the
institutions Strategic Plan, as well as the State and DTAE Strategic Plan. The Project
Programming Plan should include a short statement of the goals and objectives of the
institution and an explanation of how the proposed project will further those goals and
objectives.
PRELIMINARY INVESTIGATION
In this we would investigate in a institute search the entire requisite of a system that is
going to be developed. The Drawbacks of the present system and the future system or the
computerized system that is going to be developed. We investigate about the pros and
cons of the system that is going to be developed with the present system.
FEASIBILITY STUDY
Here we see that specifications and estimations that we have made is feasible or not. All
throughout the analysis and fact-findings that we have done is going to work out or not.
TECHNICAL
TECHNICAL FEASIBILTY
FEASIBILTY
ECONOMIC
ECONOMIC FEASIBILITY
FEASIBILITY
OPERATIONAL
OPERATIONAL FEASIBILTY
FEASIBILTY
58
It deals with the feasibility related to hardware and software which would be
available or not. Hardware that we use would be available and software that we would
use would support all the desired functions needed.
We need to determine the budget needed for the project and finance available
with us. Here we make cost estimations for each and everything required in the project.
For example: Hardware cost:
Software cost:
Books:
How the system would operate under certain conditions, whether users
would be able to operate the system. Whether User nterfaces are designed according to
the need of users. Preparing User Manuals for the users so that it would guide them
through the working of the system.
USER CONSTRAINTS
User constraints are those constraints, which would make user working inconvenient if
the user do not have following required knowledge:
. He /she must have minimum computer knowledge.
. He must know clicking on which button would generate what report.
. He must have clear idea of the whole system.
DEVELOPERS CONSTRAINTS
 He should have open-mind towards whatever is going all round in the project
 He must have proper communication and analytical skills.
 Infrastructural constraints at the developers end comprise of hardware & Software
availability, which according to our project are the following:
59
SOFTWARE ENGINEERING PARADIGM APPLIED
The basic objective of software engineering is to: develop methods and procedures for
software development that can scale up for large systems and that can be used to
consistently produce high quality software at low cost and with a small cycle time. That
is, the key objectives are consistency, low cost, high quality, small cycle time, and
scalability.
The basic approach that software engineering takes is to separate the development
process from the software. The premise is that the development process controls the
quality, scalability, consistency, and productivity. Hence to satisfy the objectives, one
must focus on the development process. Design of proper development process and their
control is the primary goal of the software engineering. It is this focus on the process that
distinguishes it from most other computing disciplines. Most other computing disciplines
focus on some type of the product-algorithms, operating systems, databases etc. while
software engineering focuses on the process for producing products.
To better manage the development process and to achieve consistency, it is essential that
the software development be done in phases.
An accurate and through understanding of software requirements is essential to the
success of software development. All further stages of system development life cycle like
analysis, system design, coding will depend on how accurate well prepared and
thoroughly understood the requirement specification is. Poorly analysis and specified
requirements will disappoint the user no matter how well designed and well coded the
software is.
Requirements specification appears to be a relatively simple task, but chances of
misinterpretation are very high. Ambiguity is probable and communication gap between
customer and developer is bound to bring confusions.
Requirements specification begins with a clear and concise heading starting in a sentence
the task to be performed.
For this, we have to be identifying the problem. First problem specification serves as a
basic of identifying work objectives that helps in describing the requirements in technical
and precise statement. After the initial section reports are received, they are analysed and
60
refund through customer developer interaction, system analysis follows to determine
feasibility and profit loss analysis.
Wa t e r F a l l M o d e l
The classic life cycle or the water fall model, the linear sequential model, suggests a
systematic, sequential approach to software development that begins at the system level
and progress through analysis, design, coding, testing and support. Modeled after a
conventional engineering cycle, the linear sequential model encompasses the following
activities.
System / Information Engineering
61
WATERFALL S
WATERFALL OS
MODEL FO
MODEL TF
Theme of the
Theme of the WT
project defined AW
project defined
RA
ER
E
E
NE
Preliminary GN
Preliminary
investigation I G
investigation NI
EN
EE
RE
I R
Requirements of NI
theRequirements
project of GN
the project G
P
AP
RA
AR
Feasibility study DA
Feasibility study I D
GI
MG
M
Design
Design
Development
of Development
software
of software
System testing
System testing
Documentation
Documentation
62
Here the linear order of these activities is critical. End of the phase and the output of one
phase is the input of another phase. The output of each phase has to be consistent with the
over all requirement of the system water fall model was being chosen because all the
requirements were known before hand and the objectives of over software development is
the computerization/automation of an already existing manual working system.
S O F T WA R E R I S K A N A LY S I S A N D M A N A G E M E N T
Software Risk
The Software Risk always involves two characteristics:-
 Uncertainty : The risk may or may not happen; that is, there are no 100%
probable risk.
 Loss: If the risk becomes a reality, unwanted consequences or losses will occurs.
Risk has to do with failure. You cannot have risk without the possibility of failure. In
the context of software development, there are four kind of risk:
 Project Risk: Project risk threatens the project plan. That is, if project
risk become real, it is likely that project schedule will slip and that cost will
increase.
 Technical Risk : Technical risk threaten the quality and timeliness of the
software to be produced. If a technical risk become a reality, implementation
may become difficult or impossible.
 Schedule Risk : The risk of failing to produce deliverable according to the
production schedule.
 Cost Risk : The risk of failing to produce deliverables according to the
budget for such production of new system.
Risk Analysis
Risk analysis is the process of studying our processes and deliverables to identify
technical, schedule and cost risks. By identifying known and predictable risks, the project
manager takes a first step toward avoiding them when possible and controlling them
when necessary.
63
Risk Management
Risk management is the process of determining approaches to developing the policies
that will bring the overall risk of the project down to an acceptable level. After
identifying the major risks, we decide how best to go about reducing their impact or the
probability of failure. We can also decide to live with the risk, of course: the amount of
risk our organization and we are willing to live with is your risk tolerance. These tasks
are risk management techniques. They are all way to prevent failure or to ameliorate the
impact of failure. Risk is not limited to the software project itself. Risks can occur when
the software has been developed successfully developed put on Online. These risks are
typically associated with the consequences of failure of the application being developed.
Risks In Our Project

 Any bug found in the existing code may cause delay in the data transmission.
 Modification in existing code might be required in order to meet the efficiency.
 Unknown bugs in the existing code may affect the output of the new code and
make debugging difficult.
Software and Hardware Requirement

Specification
Software requirements:
OS : Windows 7
Web Server : Internet Information Server
Web Browser : Internet Explorer 6.0 and above.
Languages:
PHP, Java Script HTML

Client Side Language : JSP , HTML
Server Side Language : JAVA
Database:
64
RDBMS : SQL Server
Hardware Specifications:
Server Client
Processor P IV P IV
Memory 256 MB RAM 128 MB RAM
80 GB HDD 20 GB HDD
Output Device Monitor, Printer, Monitor
Input Device Keyboard, Mouse Keyboard, Mouse
Removable Device Floppy, CD-ROM Floppy, CD-ROM
65
DATA FLOW DIAGRAMS
A graphical tool used to analyze the moment of data through a system manual or
automated including process, stores of data, and delays in the system. Data Flow
Diagrams are the central tool and the basis from which other components are developed.
The transformation of data from input to output, through processes, may be described
logically and independently of the physical components associated with the system. The
DFD is also known as dataflow graph or a bubble chart.
Context Diagram:
The top-level diagram is often called a “Context Diagram”. It contains a

single process, but plays a very important role in studying the current system. The context
diagram defines the system that will be studied in the sense that it determines the
boundaries. It defines entire software element as single Bubble with input and output data
indicated by incoming and out going arrows respectively. There are two types of data
flow diagrams
1. Physical DFD:
The physical DFD is the model of the current system and is used to
ensure that the current system has been clearly understood. Physical
DFD’s show actual devices, departments, etc involved in the current
system.
1. Logical DFD:
Logical DFD’s are the model of the proposed system. They clearly should
show the requirements on which the new system should be built.
Later during design activity this is taken as the basis for drawing the system’s
architecture.
66
 DATA FLOWDIAGRAMS
CONTEXT DIAGRAM
ADMINISTRATO CUSTOMER
R
Online Car
Furnishing
FRANCHISE VENDOR
67
DATA FLOW DIAGRAM OF ADMINISTRATOR MODULE
AIN
WEB
APPLICATIO
N
ADMINISTRATOR
LOGOUT
ADD
PRODUCT LOOKUP
S USER
TRANSACTIO
N
DELETE
PRODUC INVENTOR
TS UPDATE DAY TO Y
PRODUC DAY LOOKUP
T TRANSACTI
DETAILS ONS
DATASTORE
68
69
DATA FLOW DIAGRAM OF CUSTOMER
REGISTRATION
CUSTOMER
LOGIN
TRANSAC
TIONS
LOGOUT
REQUEST EDIT
USER
S PROFILES CHANGE
PASSWORD
PRODUC
T
STATUS
Proceed for
transactions on
selected items
ADD
ITEMS TO
CART
LOGIN
70
DATA DLOW DIAGRAM OF FRANCHISE
FRANCHISE
REGISTRATI
ON
LOGIN
UPDATE
PROFILE
VERIFICATIO LOGOUT
N OF
VENDORS
71
VENDORS DATA FLOW DIAGRAM
VENDOR REGISTRATION
LOGIN
UPDATE
PROFILE
LOGOUT
DELIVERY
OF
PRODUCTS
Franchis
e details
72
OVERALL DATAFLOW
73
E - R DIAGRAM
ENTITY-RELATIONSHIP Diagrams
E-R (Entity-Relationship) Diagram is used to represent the relationship between

entities in table. An E-R Diagram allows us to describe the data involved in real-world
enterprise in terms of objects and their relationships and is widely used to develop an
initial database design. It provides useful concepts that allow us to move from an
informal description of what users want from their database.
The symbols used in E-R diagrams are:
SYMBOL PURPOSE
An E-R Diagram allows us to describe the data involved in real-world enterprise

in terms of objects and their relationships and is widely used to develop an initial
database design. E-R Diagram is a tool for structured analysis.
An entity is an object in the real world that is distinguishable from other objects.
An entity is described using a set of attributes. .A relationship is an association among
two or more entities. Collection of similar entities is called an entity set. A key is a
74
minimal set of attributes whose values uniquely identify an entity in the set. There could
be more than one candidate key. We designate one of them as the primary key. A
relationship is an association among two or more entities. Collection of set of similar
relationships is known as relationship T set.
ENTITY: Product
Pd_price Pd_qty
Pd_des Pd_date
Pd_name Pd_last_update
Pd_id Pd_type
Product
ENTITY: Category
75
Cat_name
Cat_id
Cat_des
Category
ENTITY: Shopping Cart
Cart_qty
Cart_id
Cart_date
Shopping Cart
76
ENTITY: Customer
Cust_occupation
Cust_dob
Cust_email
Cust_name Cust_setDate
Cust_nationality
Cust_id yyyyyyty
Cust_mailupdate
Customer
ENTITY: Administrator
77
Ad_address
Ad_email
Ad_name
Ad_id Ad_phone
Administrator
Entity: Wish-List
78
Pd_name Cust_name
e
Wish-List
Entity: Query
query_des
query_id query_ans
Query
E-R Diagram:
79
1
1 Administrator
1
Shopping Cart
1
1 answers
manages holds
Views
N N
1
1 N
Category has Product ha
1 N N
s
Wish-list
selects N
1 Queries
M
Adds
1 N
to Customer Poses
80
Complete Structure
Modules description
MODULES AND THEIR DESCRIPTION
 Product:
In this module, product will have id, name, description, price,
quantity, date, last update, type. Products will all the description
which will satisfy the user.
 Category:
Through this module, it will have id, name, description’s. User
will be much satisfied by this module.
 Shopping cart:
Through this module cart will have its own id, quantity, date. It
will complete description of the shopping cart.
 Customer:
In this module, user will have an id, name, date of birth,
occupation, email address, set date, nation. It will have a
mail update. User can browse the site easily with its
account. He/she will be able to browse and download the
requirements.
 Administrator:
81
In this module, administrator will have an id, name,
address email account, phone no... It will comprise of
complete description of the administrator.
 Wish list:
This module will provide product name and the customer

name. This module will provide the customer to
purchase the product with complete description.
 Query:
In this module, there will be some query which will arise

to the user. Query will have an id, description, answer.
Solutions to the user will satisfy the user.
82
DATABASE SCHEMA
DATA STRUCTURES:
This part of the Design consists the overall database schema or we can say that tables which
consists various types of records. Table of a database consist attributes, entities tuples for storing
and manipulating records
Database design
Table definitions of Customer:
Table No.: Cust1

Table Name: Cust_info
Table Description: This table contains the personal information of the Customer.
Column Column Null/ Remarks
S.No Column Name
Description Type Not Null
1 10 digit alpha
Cust_id Unique Id Varchar Not Null
numeric num
2 Cust_firstname Varchar
3 Cust_lastname Surname Varchar
4 Cust_dob Date of Birth Varchar Valid Date
5 Cust_gender Male/Female Varchar
6 Cust_occupation Name Varchar
7 Cust_mailid Mail Id Varchar
8 Cust_address Address1 Varchar
9 Cust_nationality Nationality Varchar
10 Cust_phone Phone Residence Number
10 Digit
11 Cust_mobile Mobile No Varchar
Number
12 Cust_setDate Date Varchar
13 Cust_mail update Date Varchar
CONSTRAINTS:
83
Primary Key: Cust_id
Table definitions of Administrator:
Table No.: Admin1

Table Name:
Administrator_info
Table Description: This table contain the information of the Administrator
Seq. # Column Column Column Type Null/ Remarks
Name Description Not Null
1 Ad_id Unique identifier Varchar Not Null 10 digit alpha
numeric num
2 Ad_firstname Varchar Not Null
3 Ad_lastname Surname Varchar
4 Ad_mailid Mail Id Varchar
5 Ad_phone Phone Varchar 10 Digit Num
CONSTRAINTS:
Primary Key: Ad_id.
84
Table definitions of Product:
Table No.: Prod1

Table Name:
Product_info
Table Description: This table contain the information of products..
Seq. # Column Column Column PK/FK? Null/ Remarks
1 Pd_id Unique identifier Varchar PK Not Null 10 digit alpha numeric
num
2 Pd_name product Varchar
3 cat_id Unique identifier Varchar FK
Pd_des Description Varchar
4 product
5 Pd_price Amount Varchar
6 Pd_qty Quantity Varchar
7 Pd_date date Varchar
8 Pd_lastupdate date Varchar
9 Pd_type Type of product varchar
CONSTRAINTS:
Primary key: Pd_id
Foreign key : Cat_id.
85
Table definition of Category:
Table no: Category1

Table Name: Category_Info
Table description: This gives the info about Categories.
Seq. # Colum Column Column Null/ Remarks
1 Cat_id Unique identifier Varchar Not Null 10 digit alpha
numeric num
2 Cat_name Name of category Varchar
3 Cat_des Description Varchar
CONSTRAINTS:
Primary key: Cat_id
Table description for shopping cart:
Table Description: This table contains information of shopping cart.

1 Cart_id Unique identifier Varchar Not Null 10 digit alpha
numeric num
2 Cart_qty Quantity Varchar
3 Cart_date Date Varchar
CONSTRAINTS:
Primary key: cart_id
Table description for wish list
Table No.: Wish list1
86
Table Name:
WISH_LIST
Table Description: This table contains information about wish list
1 Cust_name Name varchar

2 Pd_name Product name varchar
Table description for query list
Table No.: Query1
Table Name:
Query_table
Table Description: This table contains information about queries
1 Query_usid Unique number Varchar Not Null
2 Query_id Query id Varchar
3 Query_des Query Description Varchar
4 Query_ans Query answer Varchar
CONSTRAINTS:
Primary key: Query_id.
User Interface Design
87
88
89
90
91
92
Coding
Index
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Car Furnishing</title>
<link rel="stylesheet" href="style.css" />
</head>
<body>
<div class="main">
<div class="hea">
<h1>Online Car Furnishing</h1>
</div>
<div id="menu"><!-div for menu--->
93
<ul>
<li><a href="index.jsp">Home</a></li>
<li><a href="about.jsp">About</a></li>
<li><a href="service.jsp">Services</a></li>
<li><a>Product</a></li>
<li><a>News</a></li>
<li><a>Contact</a></li>
</ul>
</div><!menu div close-->
<div id="slider">
<img alt="car furnishing" src="image/car.jpg" width="1068px"
height="300px" />
</div>
<div id="left">
<img alt="car furnishing" src="image/1.jpg" width="270px" height="210px" />
<img alt="car furnishing" src="image/2.jpg" width="270px" height="210px"/>
</div>
<div id="centre">
Online Car Furnishing is an online shopping website which deals in all kinds of
car furnishing items. The main objective of this project is to maintain the online shopping
for all those people who has cars and wanted to buy the furnishing items for their cars so
that they can save their time and money and get benefited.
94
</div>
<div id="right">
</div>
</div>
<div style="background-color:black;">
95
<center><font color="white">@2017</font></center>
</div>
</body>
</html>
About
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<html>
<head>
</head>
<body>
<div class="main">
96
<div class="hea">
</div>
<ul>
<li><a>Home</a></li>
<li><a>About</a></li>
<li><a>Services</a></li>
</ul>
<div id="slider">
height="300px" />
</div>
<div id="left">
</div>
<div id="centre">
97
or know.
wallpaper, videos.
accessories.
company.
98
</div>
<div id="right">
</div>
</div>
</div>
</body>
</html>
Services
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
99
<html>
<head>
</head>
<body>
<div class="main">
<div class="hea">
</div>
<ul>
<li><a>Home</a></li>
<li><a>About</a></li>
<li><a>Services</a></li>
</ul>
<div id="slider">
100
height="300px" />
</div>
<div id="left">
</div>
<div id="centre">
Online Car Furnishing is an online shopping website which deals in all kinds of
car furnishing items. The main objective of this project is to maintain the online shopping
for all those people who has cars and wanted to buy the furnishing items for their cars so
that they can save their time and money and get benefited.
101
</div>
<div id="right">
</div>
</div>
</div>
</body>
</html>
Admin
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%@ page import="java.sql.*" %>
102
<%
String Ad_id=request.getParameter("Ad_id");
String Ad_firstname=request.getParameter("Ad_firstname");
String Ad_lastname=request.getParameter("Ad_lastname");
String Ad_mailid=request.getParameter("Ad_mailid");
String Ad_phone=request.getParameter("Ad_phone");
Connection con = null;
try
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con =DriverManager.getConnection("Jdbc:Odbc:Test", "", "");
Statement st=con.createStatement();
int i=st.executeUpdate("insert into
admin(Ad_id,Ad_firstname,Ad_lastname,Ad_mailid,Ad_phone)
values('"+Ad_id+"','"+Ad_firstname+"','"+Ad_lastname+"','"+Ad_mailid+"','"+Ad_phone
+"')");
out.println("Data is successfully inserted!");
catch(Exception e)
System.out.print(e);
103
e.printStackTrace();
%>
<html>
<head>
</head>
<body>
<div class="main">
<div class="hea">
</div>
<ul>
<li><a href="home.jsp">Home</a></li>
<li><a href="customer.jsp">Customer Info</a></li>
<li><a href="Admin.jsp">Administrator Info</a></li>
104
<li><a href="product.jsp">Product Info</a></li>
<li><a href="categ.jsp">Categories Info</a></li>
<li><a href="spcart.jsp">Shopping Cart</a></li>
<li><a href="wish.jsp">Wish List</a></li>
<li><a href="query.jsp">Query</a></li>
</ul>
<div id="slider">
<img alt="car furnishing" src="car.jpg" width="1068px" height="300px" />
</div>
<div id="left">
</div>
<div id="centre">
<form method="post" action="">
<table align="center">
<tr>
<td colspan="2" align="center"><font size="15px"
color="blue">Administrator</font></td>
</tr>
<tr>
<td>Admin Id</td>
<td><input type="text" name="Ad_id" /></td>
105
</tr>
<tr>
<td>Customer name</td>
<td><input type="text" name="Ad_firstname" /></td>
</tr>
<tr>
<td>First name</td>
<td><input type="text" name="Ad_firstname" /></td>
</tr>
<tr>
<td>Email</td>
<td><input type="email" name="Cust_mailid" /></td>
</tr>
<tr>
<td>Mobile</td>
<td><input type="text" name="Cust_mobile" /></td>
</tr>
<tr>
<td colspan="2" align="right"><input type="submit" name="submit"
value="submit" /></td>
</tr>
</table>
106
</form>
</div>
<div id="right"> </div>
<div style=""><center>@2017</center></div>
</div>
</body>
</html>
Cart
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Cat_id=request.getParameter("Cat_id");
String Cat_name=request.getParameter("Cat_name");
String Cat_des=request.getParameter("Cat_des");
try
107
int i=st.executeUpdate("insert into categories(Cat_id,Cat_name,Cat_des)
values('"+Cat_id+"','"+Cat_name+"','"+Cat_des+"')");
catch(Exception e)
%>
<html>
<head>
</head>
<body>
<div class="main">
108
<div class="hea">
</div>
<ul>
<li><a href="qurey.jsp">Query</a></li>
</ul>
<div id="slider">
</div>
<div id="left">
</div>
<div id="centre">
109
<tr>
color="blue">Categories</font></td>
</tr>
<tr>
<td>Categories Id</td>
<td><input type="text" name="Cat_id" /></td>
</tr>
<tr>
<td>Categories name</td>
<td><input type="text" name="Cat_name" /></td>
</tr>
<tr>
<td>Description</td>
<td><input type="text" name="Cat_des" /></td>
</tr>
<tr>
</tr>
</table>
110
</form>
</div>
</div>
</body>
</html>
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Cat_id=request.getParameter("Cat_id");
String Cat_name=request.getParameter("Cat_name");
String Cat_des=request.getParameter("Cat_des");
try
111
int i=st.executeUpdate("insert into categories(Cat_id,Cat_name,Cat_des)
values('"+Cat_id+"','"+Cat_name+"','"+Cat_des+"')");
catch(Exception e)
%>
<html>
<head>
</head>
<body>
<div class="main">
<div class="hea">
112
</div>
<ul>
<li><a href="qurey.jsp">Query</a></li>
</ul>
<div id="slider">
</div>
<div id="left">
</div>
<div id="centre">
<tr>
113
color="blue">Categories</font></td>
</tr>
<tr>
<td>Categories Id</td>
<td><input type="text" name="Cat_id" /></td>
</tr>
<tr>
<td>Categories name</td>
<td><input type="text" name="Cat_name" /></td>
</tr>
<tr>
<td><input type="text" name="Cat_des" /></td>
</tr>
<tr>
</tr>
</table>
</form>
114
</div>
</div>
</body>
</html>
Customer
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Cust_id=request.getParameter("Cust_id");
String Cust_firstname=request.getParameter("Cust_firstname");
String Cust_lastname=request.getParameter("Cust_lastname");
String Cust_dob=request.getParameter("Cust_dob");
String Cust_gender=request.getParameter("Cust_gender");
String Cust_occupation=request.getParameter("Cust_occupation");
String Cust_mailid=request.getParameter("Cust_mailid");
String Cust_address=request.getParameter("Cust_address");
String Cust_nationality=request.getParameter("Cust_nationality");
115
try
customer(Cust_id,Cust_firstname,Cust_lastname,Cust_dob,Cust_gender,Cust_occupation
,Cust_mailid,Cust_address,Cust_nationality)
values('"+Cust_id+"','"+Cust_firstname+"','"+Cust_lastname+"','"+Cust_dob+"','"+Cust_
gender+"','"+Cust_occupation+"','"+Cust_mailid+"','"+Cust_address+"','"+Cust_nationalit
y+"')");
catch(Exception e)
%>
116
<html>
<head>
</head>
<body>
<div class="main">
<div class="hea">
</div>
<ul>
117
</ul>
<div id="slider">
</div>
<div id="left">
</div>
<div id="centre">
<tr>
color="blue">Customer</font></td>
</tr>
<tr>
<td>Customer Id</td>
<td><input type="text" name="Cust_id" /></td>
</tr>
<tr>
<td><input type="text" name="Cust_firstname" /></td>
</tr>
118
<tr>
<td>First name</td>
</tr>
<tr>
<td>Last name</td>
<td><input type="text" name="Cust_lastname" /></td>
</tr>
<tr>
<td>Date of birth</td>
<td><input type="date" name="Cust_dob" /></td>
</tr>
<tr>
<td>Gender</td>
<td><select name="Cust_gender">
<option>Male</option>
<option>Female</option>
</select></td>
</tr>
<tr>
<td>Occupation</td>
<td><input type="date" name="Cust_occupation" /></td>
119
</tr>
<tr>
<td>Email</td>
</tr>
<tr>
<td>Address</td>
<td><input type="text" name="Cust_address" /></td>
</tr>
<tr>
<td>Nationality</td>
<td><select name="Cust_nationality">
<option>India</option>
<option>Pakistan</option>
<option>Nepal</option>
<option>Other</option>
</select>
</td>
</tr>
<tr>
<td>Address</td>
120
</tr>
<tr>
<td>Phone</td>
<td><input type="text" name="Cust_phone" /></td>
</tr>
<tr>
<td>Mobile</td>
</tr>
<tr>
</tr>
</table>
</form>
</div>
</div>
</body>
</html>
<%--
Document : index
121
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Cust_id=request.getParameter("Cust_id");
String Cust_firstname=request.getParameter("Cust_firstname");
String Cust_lastname=request.getParameter("Cust_lastname");
String Cust_dob=request.getParameter("Cust_dob");
String Cust_gender=request.getParameter("Cust_gender");
String Cust_occupation=request.getParameter("Cust_occupation");
String Cust_mailid=request.getParameter("Cust_mailid");
String Cust_address=request.getParameter("Cust_address");
String Cust_nationality=request.getParameter("Cust_nationality");
try
customer(Cust_id,Cust_firstname,Cust_lastname,Cust_dob,Cust_gender,Cust_occupation
122
,Cust_mailid,Cust_address,Cust_nationality)
values('"+Cust_id+"','"+Cust_firstname+"','"+Cust_lastname+"','"+Cust_dob+"','"+Cust_
gender+"','"+Cust_occupation+"','"+Cust_mailid+"','"+Cust_address+"','"+Cust_nationalit
y+"')");
catch(Exception e)
%>
<html>
<head>
</head>
<body>
123
<div class="main">
<div class="hea">
</div>
<ul>
</ul>
<div id="slider">
</div>
<div id="left">
</div>
<div id="centre">
124
<tr>
color="blue">Customer</font></td>
</tr>
<tr>
<td>Customer Id</td>
<td><input type="text" name="Cust_id" /></td>
</tr>
<tr>
</tr>
<tr>
<td>First name</td>
</tr>
<tr>
<td>Last name</td>
<td><input type="text" name="Cust_lastname" /></td>
</tr>
<tr>
125
<td>Date of birth</td>
<td><input type="date" name="Cust_dob" /></td>
</tr>
<tr>
<td>Gender</td>
<td><select name="Cust_gender">
<option>Male</option>
<option>Female</option>
</select></td>
</tr>
<tr>
<td>Occupation</td>
<td><input type="date" name="Cust_occupation" /></td>
</tr>
<tr>
<td>Email</td>
</tr>
<tr>
<td>Address</td>
</tr>
126
<tr>
<td><select name="Cust_nationality">
<option>India</option>
<option>Pakistan</option>
<option>Nepal</option>
</select>
</td>
</tr>
<tr>
<td>Address</td>
</tr>
<tr>
<td>Phone</td>
<td><input type="text" name="Cust_phone" /></td>
</tr>
<tr>
<td>Mobile</td>
</tr>
127
<tr>
</tr>
</table>
</form>
</div>
</div>
</body>
</html>
Home
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<html>
128
<head>
</head>
<body>
<div class="main">
<div class="hea">
</div>
<ul>
</ul>
<div id="slider">
129
</div>
<div id="left">
</div>
<div id="centre">
</div>
</div>
</body>
</html>
Product
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Pd_id=request.getParameter("Pd_id");
String Pd_name=request.getParameter("Pd_name");
String cat_id=request.getParameter("cat_id");
String Pd_des=request.getParameter("Pd_des");
130
String Pd_price=request.getParameter("Pd_price");
String Pd_qty=request.getParameter("Pd_qty");
String Pd_date=request.getParameter("Pd_date");
String Pd_lastupdate=request.getParameter("Pd_lastupdate");
String Pd_type=request.getParameter("Pd_type");
try
admin(Pd_id,Pd_name,cat_id,Pd_des,Pd_price,Pd_qty,Pd_date,Pd_lastupdate,Pd_type)
values('"+Pd_id+"','"+Pd_name+"','"+cat_id+"','"+Pd_des+"','"+Pd_price+"','"+Pd_qty+"',
'"+Pd_date+"','"+Pd_lastupdate+"','"+Pd_type+"')");
catch(Exception e)
131
}
%>
<html>
<head>
</head>
<body>
<div class="main">
<div class="hea">
</div>
<ul>
132
</ul>
<div id="slider">
</div>
<div id="left">
</div>
<div id="centre">
<tr>
color="blue">Product</font></td>
</tr>
<tr>
<td>Product Id</td>
<td><input type="text" name="Pd_id" /></td>
</tr>
133
<tr>
<td>Categories id</td>
<td><input type="text" name="cat_id" /></td>
</tr>
<tr>
<td><input type="text" name="Pd_des" /></td>
</tr>
<tr>
<td>Price</td>
<td><input type="text" name="Pd_price" /></td>
</tr>
<tr>
<td>Quantity</td>
<td><input type="text" name="Pd_qty" /></td>
</tr>
<tr>
<td>Date</td>
<td><input type="date" name="Pd_date" /></td>
</tr>
<tr>
<td>Email</td>
134
</tr>
<tr>
<td>Last Update</td>
<td><input type="date" name="Pd_lastupdate" /></td>
</tr>
<tr>
<td><select name="Pd_type">
<option>Regular</option>
<option>Special</option>
<option>Sports</option>
</select>
</td>
</tr>
<tr>
</tr>
</table>
</form>
135
</div>
</div>
</body>
</html>
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Pd_id=request.getParameter("Pd_id");
String cat_id=request.getParameter("cat_id");
String Pd_des=request.getParameter("Pd_des");
String Pd_price=request.getParameter("Pd_price");
String Pd_qty=request.getParameter("Pd_qty");
String Pd_date=request.getParameter("Pd_date");
String Pd_lastupdate=request.getParameter("Pd_lastupdate");
String Pd_type=request.getParameter("Pd_type");
136
try
admin(Pd_id,Pd_name,cat_id,Pd_des,Pd_price,Pd_qty,Pd_date,Pd_lastupdate,Pd_type)
values('"+Pd_id+"','"+Pd_name+"','"+cat_id+"','"+Pd_des+"','"+Pd_price+"','"+Pd_qty+"',
'"+Pd_date+"','"+Pd_lastupdate+"','"+Pd_type+"')");
catch(Exception e)
%>
137
<html>
<head>
</head>
<body>
<div class="main">
<div class="hea">
</div>
<ul>
</ul>
138
<div id="slider">
</div>
<div id="left">
</div>
<div id="centre">
<tr>
color="blue">Product</font></td>
</tr>
<tr>
<td>Product Id</td>
<td><input type="text" name="Pd_id" /></td>
</tr>
<tr>
<td>Categories id</td>
<td><input type="text" name="cat_id" /></td>
</tr>
<tr>
139
<td><input type="text" name="Pd_des" /></td>
</tr>
<tr>
<td>Price</td>
<td><input type="text" name="Pd_price" /></td>
</tr>
<tr>
<td>Quantity</td>
<td><input type="text" name="Pd_qty" /></td>
</tr>
<tr>
<td>Date</td>
<td><input type="date" name="Pd_date" /></td>
</tr>
<tr>
<td>Email</td>
</tr>
<tr>
<td>Last Update</td>
<td><input type="date" name="Pd_lastupdate" /></td>
</tr>
<tr>
140
<td><select name="Pd_type">
<option>Regular</option>
<option>Special</option>
<option>Sports</option>
</select>
</td>
</tr>
<tr>
</tr>
</table>
</form>
</div>
</div>
</body>
</html>
141
Query
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Query_usid=request.getParameter("Query_usid");
String Query_id=request.getParameter("Query_id");
String Query_des=request.getParameter("Query_des");
String Query_ans=request.getParameter("Query_ans");
try
int i=st.executeUpdate("insert into query(Query_usid,Query_id,Query_des,Query_ans)
values('"+Query_usid+"','"+Query_id+"','"+Query_des+"','"+Query_ans+"')");
142
}
catch(Exception e)
%>
<html>
<head>
</head>
<body>
<div class="main">
<div class="hea">
</div>
143
<ul>
</ul>
<div id="slider">
</div>
<div id="left">
</div>
<div id="centre">
<tr>
color="blue">Query</font></td>
144
</tr>
<tr>
<td>User Id</td>
<td><input type="text" name="Query_usid" /></td>
</tr>
<tr>
<td>Query id</td>
<td><input type="text" name="Query_id" /></td>
</tr>
<tr>
<td><input type="text" name="Query_des" /></td>
</tr>
<tr>
<td>Query Answer</td>
<td><input type="text" name="Query_ans" /></td>
</tr>
<tr>
</tr>
</table>
</form>
145
</div>
</div>
</body>
</html>
Sopping cart
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Cart_id=request.getParameter("Cart_id");
String Cart_qty=request.getParameter("Cart_qty");
String Cart_date=request.getParameter("Cart_date");
try
146
int i=st.executeUpdate("insert into scart(Cart_id,Cart_qty,Cart_date)
values('"+Cart_id+"','"+Cart_qty+"','"+Cart_date+"')");
catch(Exception e)
%>
<html>
<head>
</head>
147
<body>
<div class="main">
<div class="hea">
</div>
<ul>
</ul>
<div id="slider">
</div>
<div id="left">
</div>
<div id="centre">
148
<tr>
<td colspan="2" align="center"><font size="15px" color="blue">Shopping
cart</font></td>
</tr>
<tr>
<td>Cart Id</td>
<td><input type="text" name="Cart_id" /></td>
</tr>
<tr>
<td>Quantity</td>
<td><input type="text" name="Cart_qty" /></td>
</tr>
<tr>
<td>Date</td>
<td><input type="date" name="Cart_date" /></td>
</tr>
<tr>
149
</tr>
</table>
</form>
</div>
</div>
</body>
</html>
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Cart_id=request.getParameter("Cart_id");
String Cart_qty=request.getParameter("Cart_qty");
String Cart_date=request.getParameter("Cart_date");
150
try
int i=st.executeUpdate("insert into scart(Cart_id,Cart_qty,Cart_date)
values('"+Cart_id+"','"+Cart_qty+"','"+Cart_date+"')");
catch(Exception e)
%>
<html>
<head>
151
</head>
<body>
<div class="main">
<div class="hea">
</div>
<ul>
</ul>
<div id="slider">
</div>
152
<div id="left">
</div>
<div id="centre">
<tr>
<td colspan="2" align="center"><font size="15px" color="blue">Shopping
cart</font></td>
</tr>
<tr>
<td>Cart Id</td>
<td><input type="text" name="Cart_id" /></td>
</tr>
<tr>
<td>Quantity</td>
<td><input type="text" name="Cart_qty" /></td>
</tr>
<tr>
<td>Date</td>
<td><input type="date" name="Cart_date" /></td>
</tr>
153
<tr>
</tr>
</table>
</form>
</div>
</div>
</body>
</html>
Wish
<%--
Document : index
Created on : Mar 19, 2017, 6:49:17 PM
Author : Deepak
--%>
<%
String Cust_name=request.getParameter("Cust_name");
154
try
int i=st.executeUpdate("insert into scart(Cust_name,Pd_name)
values('"+Cust_name+"','"+Pd_name+"')");
catch(Exception e)
%>
155
<html>
<head>
</head>
<body>
<div class="main">
<div class="hea">
</div>
<ul>
</ul>
156
<div id="slider">
</div>
<div id="left">
</div>
<div id="centre">
<tr>
<td colspan="2" align="center"><font size="15px" color="blue">Wish
List</font></td>
</tr>
<tr>
<td>Customer Name</td>
<td><input type="text" name="Cust_name" /></td>
</tr>
<tr>
<td>Product name</td>
<td><input type="text" name="Pd_name" /></td>
</tr>
<tr>
157
</tr>
</table>
</form>
</div>
</div>
</body>
</html>
CSS
.main
width:80%;
height:800px;
margin-left: auto;
margin-right: auto;
background-color: pink;
.hea
158
background-color: windowframe;
text-align: center;
color: blue;
#menu
height:40px;
margin-top: -22px;
ul
list-style-type: none;
margin:0;
padding:0;
background-color:#900C3F;
overflow:hidden;
height:40px;
width:100%;
li
float:left;
159
li a
display:block;
padding:10px 13px;
text-align:center;
color:white;
text-decoration:none;
/* Change the link color to #111 (black) on hover */
li a:hover
background-color:#ff00dc;
#slider
height:300px;
background-color: white;
#left
height: 400px;
width: 25%;
background:bottom;
160
float: left;
#centre
height: 400px;
width: 50%;
background-color: white;
float: left;
#right
height: 400px;
width: 25%;
background: bottom;
float: left;
161
Testing
It should be clear in mind that the philosophy behind testing is to find errors. Test cases
are devised with this purpose in mind. A test case is a set of data that the system will
process as normal input. However, the data are created with the express intent of
determining whether the system will process them correctly. Each test case is designed
with the intent of finding errors in the way the system will process it. There are two
general strategies for testing software: Code testing and Specification testing. In code
testing, the analyst develops that case to execute every instructions and path in a program.
Under specification testing, the analyst examines the program specifications and then
writes test data to determine how the program operates under specific conditions.
Regardless of which strategy the analyst follows, there are preferred practices to ensure
that the testing is useful.
Levels of Testing:
Systems are not designed as entire systems nor are they tested as single systems. The
analyst must perform both unit and system testing.
Unit Testing:
In unit testing the analyst tests the programs making up a system. For this reason, unit
testing is sometimes called program testing. Unit testing gives stress on the modules
independently of one another, to find errors.
The various modules which have been designed for the different type of users i.e. Job-
Seekers, Employers and Consultants. They can be test independently.
This helps the tester in detecting errors in coding and logic that are contained within that
module alone. The errors resulting from the interaction between modules are initially
avoided. For example, My information system Car Furnishing is a system with mainly
three different modules which work independently and can be tested for the operations
specified the specification document. The set of modules can be tested for various sets of
data inputs.
162
Unit testing can be performed from the bottom up, starting with smallest and lowest-level
modules and proceeding one at a time. For each module in bottom-up testing a short
program is used to execute the module and provides the needed data, so that the module
is asked to perform the way it will when embedded within the larger system.
System Testing:
The important and essential part of the system development phase, after designing and
developing the my information system, is system testing. We cannot say that every
program or system design is perfect and because of lack of communication between the
user and the designer, some error is there in the software development. The number and
nature of errors in a newly designed system depend on some usual factors like
communication between the user and the designer; the programmer's ability to generate a
code that reflects exactly the systems specifications and the time frame for the design.
Theoretically, a newly designed system should have all the parts or sub-systems are in
working order, but in reality, each sub-system works independently. This is the time to
gather all the subsystem into one pool and test the whole system to determine whether it
meets the user requirements. This is the last change to detect and correct errors before the
system is installed for user acceptance testing. The purpose of system testing is to
163
consider all the likely variations to which it will be subjected and then push the system to
its limits.
Testing is an important function to the success of the system. System testing makes a
logical assumption that if all the parts of the system are correct, the goal will be
successfully activated. Another reason for system testing is its utility as a user-oriented
vehicle before implementation.
System testing consists of the following five steps:
1) Program testing
2) String testing
3) System testing
4) System documentation
5) User acceptance testing
Program Testing:
A program represents the logical elements of a system. For a program to run
satisfactorily, it must compile and test data correctly and tie in properly with other
programs. It is the responsibility of a programmer to have an error free program. At the
time of testing the system, there exist two types of errors that should be checked. These
errors are syntax and logic. A syntax error is a program statement that violates one or
more rules of the language in which it is written. An improperly defined field dimension
or omitted key words are common syntax errors. These errors are shown through error
messages generated by the computer. A logic error, on the other hand, deals with incorrect
data fields out of range items, and invalid combinations. Since the logical errors are not
detected by compiler, the programmer must examine the output carefully to detect them.
When a program is tested, the actual output is compared with the expected output. When
there is a discrepancy, the sequence of the instructions, must be traced to determine the
problem. The process is facilitated by breaking the program down into self-contained
portions, each of which can be checked at certain key points.
164
String Testing:
Programs are invariably related to one another and interact in a total system. Each
program is tested to see whether it conforms to related programs in the system. Each part
of the system is tested against the entire module with both test and live data before the
whole system is ready to be tested.
System Testing:
System testing is designed to uncover weaknesses that were not found in earlier tests.
This includes forced system failure and validation of total system as it will be
implemented by its user in the operational environment. Under this testing, generally we
take low volumes of transactions based on live data. This volume is increased until the
maximum level for each transaction type is reached. The total system is also tested for
recovery and fallback after various major failures to ensure that no data are lost during
the emergency. All this is done with the old system still in operation. When we see that
the proposed system is successful in the test, the old system is discontinued.
System Documentation:
All design and test documentation should be well prepared and kept in the library for
future reference. The library is the central location for maintenance of the new system.
User Acceptance Testing:

An acceptance test has the objective of selling the user on the validity and reliability of
the system. It verifies that the system's procedures operate to system specifications and
that the integrity of important data is maintained. Performance of an acceptance test is
actually the user's show. User motivation is very important for the successful
performance of the system. After that a comprehensive test report is prepared. This report
shows the system's tolerance, performance range, error rate and accuracy.
Special Systems Tests:
There are other six tests which fall under special category. They are described below:
165
Peak Load Test: It determines whether the system will handle the volume of activities
that occur when the system is at the peak of its processing demand. For example, test the
system by activating all terminals at the same time.
Storage Testing: It determines the capacity of the system to store transaction data on a
disk or in other files. For example, verify documentation statements that the system will
store 10,000 records of 400 bytes length on a single flexible disk.
Performance Time Testing: it determines the length of time system used by the system
to process transaction data. This test is conducted prior to implementation to determine
how long it takes to get a response to an inquiry, make a backup copy of a file, or send a
transmission and get a response.
Recovery Testing: This testing determines the ability of user to recover data or re-start
system after failure. For example, load backup copy of data and resume processing
without data or integrity loss.
Procedure Testing: It determines the clarity of documentation on operation and use of
system by having users do exactly what manuals request. For example, powering down
system at the end of week or responding to paper-out light on printer.
Human Factors Testing: It determines how users will use the system when processing
data or preparing reports.
Testing Strategy used in the project

The tests conducted and the strategy used for the working are:-
1. Unit Testing: In unit testing we checked the code for the errors. The errors are
debugged and removed. After the coding became error free, the next test was
performed.
2. Integration Testing: In this test, all the modules are integrated and links are
formed. The test is conducted to check if all the modules can work with
coordination. And all the different modules named for Job-seeker, Employers and
Consultant and other search modules are working in coordination and with best
results.
166
3. Validation Testing: here we have taken care of user’s INPUT/OUTPUT, means the
user who are entering the data to the system is correct or not, once the User will
put the correct data then the will able to get desire output. The every input field
on the web pages of my project are included with the respective validation
criteria and that have been checked for the number of sets of data input.
4. System Testing: In System testing the quality of system is tested, i.e. overall
working of system.
The Over all information system is running smoothly and all the operation have been
tested for the various set of data and conditions and situations. During testing various
flaws were observed but removed in the next stages. And now the project is giving all
the specified output to the user without any error.
Test case-1
167
Test case-2
Test case-3
168
INPUT OUTPUT SCREEN
169
170
171
172
System Security Measures
In my information System, several security measures have been implemented.

 The information system maintains the data of the number of item, and the
employees. The details of the candidates can be seen by the candidates
himself/herself which are of some personal sort like address and phone no. No
other unauthorized user can enter the others module.
 User can access the specific information only if he is logged in and he must be
having his Login id and Password.
 Valid access rights have been assigned to the various type of users like Job-
Seeker, Employers and of course other consultants who can also access the
database but with some little allowed information.
 There is no direct interaction between database and the user. They do not have
that much of data manipulation rights for the records even of his own.
 Only the user with the administrative power can modify the database of the
update the records of different users.
 The user without the login id and password is treated as guest and is not offered
with that much of right on the database to access. Only the partial part of database
is available for him to see.
 Also, being web application this system gets additional security from various
security measures which are in place to secure data on the net.
 Due to password confirmation, no one other than the valid user can provide
conformations.
173
Report Generation
Report generation is an important parts any system because it provides information to

users which help in decision making. Online shopping website also generates some report
according to its user type. Some of the record are follow below with its user type.
Reports generated for Administrator:
Product detail
 Products availability information with different category.
User or customers
 Number of customers.
Sales Report
 Total sales report of given interval.
 Total COD sales.
 Total online sales.
Manufactures report
 Different manufactures of different products.
174
Cost Estimation
In the early days of the computing, Software costs constituted a small percentage of the
overall computer based cost. Today, software is the most expensive element of virtually
all computer-based system. The software cost and effort estimation will never be an exact
science. Too many variables, human, technical, environmental, political can affect the
ultimate cost of the software and effort applied to develop it. However, software project
estimation can be transformed from a black art to a series of systematic steps that
provides estimates with acceptable risk.
For computing the cost of the project there are a lot of model available. The LOC (Line
of Code) based code estimation model are selected for compute the cost of this project.
LOC – Based Cost Estimation :
On the basis of LOC, the software team estimate total module cost, which are defining
the following table.
FUNCTION ESTIMATED LOC

Total Lines of Code 6000
My organization completed near about 2000 LOC per month and per effort cost is 8,000.
so that cost of one line of code is:-
(8000) / 2000
=4
so, that the cost of software is :-
= 6000 x 4
= 24000
175
Pert and Gantt chart
Pert Chart
A PERT (Program Evaluation and Review Technique) chart is a network of boxes (or
circles) and arrows. There are different variations of PERT charts. The boxes in PERT
Chart can be decorated with starting and ending dates for activities; the arrows help in
computing the earliest possible starting dates for the boxes at their heads. Some boxes
can be designated as milestone.
The Chart below shows that the path through the project that consists of the “design”,
“build code generator”, and “integration and testing” activities is the critical path for the
project. Any delay in any activity in this path will cause a delay in the entire project.
The Diagram of PERT Chart of the Project is given on the following page.
PERT Chart
Input
Input Design
Design
Coding
Coding
Validation
Validation
Preliminary
Preliminary Design
Design Integrity
Integrity Finish
Finish
Start
Start Investigation
Investigation Testing
Testing
Feb 25, 06
Unit
Unit Testing
Testing
Documentation
Documentation
Fig: PERT chart
176
P E RT C h a r t , G a nt t C h a rt
Gantt charts are a project control technique that can be used for several purposes,
including scheduling, budgeting, and resource planning. A Gantt chart is a bar chart, with
each bar representing an activity. The bars are drawn against a time Line. The length of
each bar is proportional to the length of time planned for the activity.
A Gantt chart helps in scheduling the activities of a project, but it does not help in
identifying them. Gantt charts take different forms depending on their intended use. They
are best for resource scheduling.
The Diagram of Gantt Chart for this project is given on the following page.
Gantt Chart
Oct 1, 17 Nov 1, 17 Dec 1, 17 Jan 20, 17 Feb 1, 17 Mar 20, 17
Preliminary
Preliminary Investigation
Investigation
Design
Design (I/O,
(I/O, DFD,
DFD, DATABASE)
DATABASE)
Coding
Coding
Unit
Unit Testing
Testing
Integrity
Integrity Testing
Testing
Documentation
Documentation
Implementation
Implementation
Fig: Gantt chart for PERFECT JOBS

177
LIMITATIONS: -
 This project does not Edit the date of connection or store the date of
transfer in case of connection transfer.
 System date for the project is like as backbone for the human, i.e.
proposed system is depends on system date so it must be correct.
 Cannot be connected to the Internet.

 There are some inherent problems like time, finance etc. to elaborate
further study
178
Future scope and further
enhancement
Today the internet and its boom have created a new economic scenario that not only
stresses on the classical concept of the “product” but also on the modern concept of “service”.
It is this level of service that dictates whether a commercial venture will succeed or not in the market.
To provide a high accessibility of service we will design the online shopping website, so that potential
customers need not go to a physical shop to buy products or services. There are several objective of
this websites are following given bellows.
• This site is gives all the information about the e-shopping to provide better service for the
customer.
•It provides the facility to the customers who want to shop on-line due to lock of time.
•It provides facility to the customer to payment by the cash and cheque and DD also.
•It’s providing the full details about the product and related information about the product like cost, size
etc.
•With the help of it we can save the time and money also.
•It provides the remote shopping by the cash, or DD, or Debit card also
Building a project is just a first step toward its development. By time improvement and
upgrade is necessary According to demand and choice. In future, an android client
application can be develop to make it fast accessible from user mobile handsets. With the
technology development, new features can be added which make it more user friendly
then before.
User feedback is a key source for making any system form better to best. Enhancement
will be carried out according to feedback data from users.
179
Bibliography
1. HTML Complete Reference

BPB Publications
2. Complete Reference of Java
3. Software Engineering 5th Edition.

Roger S. Pressman. Tata McGraw – Hill.
4. An Introduction to Database System.

Bipin C. Desai. Galgotia Publication Pvt. Ltd.
5. Fundamental of Database Systems 3rd Edition

Shamkant B. Navathe, Ramez Elmasri
180

Car FurnishingFInal

Uploaded by

Copyright:

Available Formats

Car FurnishingFInal

Uploaded by

Document Information

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

Car FurnishingFInal

Uploaded by

Copyright:

Available Formats

An Online Shopping

A large percentage of electronic commerce is conducted entirely electronically for virtual

Objective of the application

To provide the complete description of a mobile handset.

 To provide a large range of car furnishing accessories.

 To provide secure mode of payment for purchase of car furnishing accessories.

 To provide free downloading of a large variety of car designing themes,

 To provide communication between staff members with other branches of the

2.1 Present System

A large percentage of electronic commerce is conducted entirely electronically for virtual

Electronic commerce, commonly known as e-commerce,

2.4 Main output Required

To provide the complete description of a Car Furnishing accessories.

6. Support and Maintenance

DATA FLOW DIAGRAMS

The top-level diagram is often called a “Context Diagram”. It contains a

DATA FLOW DIAGRAM OF ADMINISTRATOR MODULE

DATA FLOW DIAGRAM OF CUSTOMER

DATA DLOW DIAGRAM OF FRANCHISE

E-R (Entity-Relationship) Diagram is used to represent the relationship between

The symbols used in E-R diagrams are:

An E-R Diagram allows us to describe the data involved in real-world enterprise

ENTITY: Shopping Cart

Table definitions of Customer:

Table No.: Cust1

Table definitions of Administrator:

Table definitions of Product:

Table No.: Prod1

Table definition of Category:

Table no: Category1

Table Description: This table contains information of shopping cart.

Table No.: Wish list1

1 Cust_name Name varchar

Table description for query list

Table No.: Query1

MODULES AND THEIR DESCRIPTION

In this module, administrator will have an id, name,

This module will provide product name and the customer

In this module, there will be some query which will arise

 Internet Explorer 6.0 or Above

Report generation is an important parts any system because it provides information to

Development Time Security

Security for accessing:

 Cannot be connected to the Internet.

Future scope and further

A large percentage of electronic commerce is conducted entirely electronically for virtual

Objective of the application

To provide the complete description of a mobile handset.

 To provide a large range of car furnishing accessories.

 To provide secure mode of payment for purchase of car furnishing accessories.

 To provide free downloading of a large variety of car designing themes,

 To provide communication between staff members with other branches of the

 Internet Explorer 6.0 or Above

JAVA DATABASE CONNECTIVITY (JDBC)

Java, being robust, secure, easy to understand, and

MIS managers like the combination of Java and JDBC because

WHAT DOES JDBC DO ?

1. Establish a connection with the database

2.Send SQL statements

3.Process the results