PROJECT REPORT

ON
“PROJECT NAME”

Submitted in partial fulfillment of the

Requirement for the award of the degree of
Bachelor of Computer Application

Submitted To Submitted By

(Batch: 2018-2021)

Vivekananda Institute of Professional Studies

(Affiliated to Guru Gobind Singh Indraprastha University)

1
 CERTIFICATE

This is to certify that ……………………….of BCA 5 th Semester from Vivekananda Institute of

Professional Studies, Delhi has presented this project work entitled “PROJECT NAME”, an
online auction website in partial fulfilment of the requirements for the award of the degree of
Bachelor of Computer Applications under our supervision and guidance.

(Faculty Name)

(Designation)

2
 ACKNOWLEDGEMENT

It is our proud privilege to express our profound gratitude to the entire management of
Vivekananda Institute of Professional Studies and teachers of the institute for providing us with
the opportunity to avail the excellent facilities and infrastructure. The knowledge and values
inculcated have proved to be of immense help at the very start of my career. Special thanks to
Hon’ble Founder, Vivekananda Institute of Professional Studies, Delhi for having provided us
an excellent infrastructure at VSIT.

I am grateful to Dr. Supriya Madan (Dean, VSIT), and “project guide” for their astute guidance,
constant encouragement and sincere support for this project work.

Sincere thanks to all my family members, seniors and friends for their support and assistance
throughout the project.

Student Name

3
 Table of Contents Page No.

1 INTRODUCTION 6

1.1 Objective of the System 7

1.2 Justification and need for the system 7
1.3 Advantage of the system 8
1.4 Previous work or related systems, how they are used. 9

2 REQUIREMENT ANALYSIS 10

2.1 Analysis Study 12

2.2 User Requirements 13
2.3 Discussion with IT Experts 14
2.4 Final Requirements 14

3 DESIGN OF THE SYSTEM 15

3.1 Hardware, Software requirements 17

3.2 System requirements 18
3.3 Detailed System Specification (Module Wise) 19
3.4 ER Diagram of the system 20
3.5 DFDs/Algorithms/Flow Charts 20
21
4 IMPLEMENTATION & CODING
22
4.1 Operating System 26
4.2 Languages 30
4.3 S/W Tools 35
4.4 Coding 38

5 TESTING & TEST RESULTS 42

5.1 Software Testing and Objective of Testing 43

5.2 Sample test data/ Output screen printouts etc. 46

6 CONCLUSION
50
6.1 Conclusion
6.2 Future Scope 50
50

Biblography 51

4
 Table of Figures
3 Fig. 3.1 Actor and Use case 17

Fig.3.2 Interaction between user and admin 18

Fig 3.3 ER diagram 19

Fig 3.4 DFD 20

4 Fig 4.1 Member table 21

Fig 4.2 Message Table 22

Fig 4.3 Auction Table 23

Fig 4.4 Home page 28

Fig 4.5 Register Page 34

Fig 4.6 Feedback Page 38

Fig 4.7 Message Page 40

Fig 4.8 Send Messages 41

5 Fig 5.1 Registration Page 46

Fig 5.2 Home page 47

Fig 5.3 Home Page 48

Fig 5.4 Home Page 49

Fig 5.5 Registration Page 50

5
 Chapter 1

INTRODUCTION
Online Auction System specializes in auctioning various products with the interaction of the customers
to each other. It is an online system through which customers can register themselves, add items to sell,
bid on the items to purchase, etc. Online auction service is a major sale and purchase service provided
by our company in many cities all over India. Most of the people use online websites to sell and
purchase the used products. Our company is registered and fulfils all the requirements and security
standards set by the sale and purchase department. The project has 2 different types of logins:-

1. User login
2. Admin login

USER LOGIN

It is the basic login interface for any customer or user of the website. It provides the user with the
information of different items added to be auctioned. Also, the user can add his or her item by using the
add auction option on the member home of the website. He can also bid for the already added items for
auction to purchase them as well as can check the status of auction of every item.

ADMIN LOGIN

This login is meant for the manager of the auction website. It gives an overview of all the auctions
placed, who has placed them, highest bid on the items, etc. It also provides the admin with the advantage
to cancel or finalize any auction. It also has a messages section where the admin can receive the
messages of its users and reply to it appropriately.

1.1 OBJECTIVE OF THE SYSTEM

This project will serve the following objectives:-

1. Provides the user with easy and friendly interface

2. Add and maintain record of available products
3. Add and maintain description of products

6
 4. Provides attractive discounts
5. Accepts Customer Feedback
6. Provides the Tracking Facility
7. Provides a convenient solution for billing pattern

1.2 JUSTIFICATION AND NEED FOR THE SYSTEM

Nowadays when everyone is so busy and occupied, we all want ease of work. And with the lack of time
arises the need of these kinds of applications that would provide all the facilities to the customer (user),
and the manager/admin at one place. Now, the admin can handle all its items added to auction at one
place.

And on the other hand, the user can get/bid his best price to sell/purchase the items from different users
sitting at his home. He also gets to know the status of all the auctions whether added by him or others.

The manager supervises all the auctions which are being made by the users, receive all the feedbacks
and reply to them when he feels necessary. The admin has the right to cancel or finalize any auction
item.

1.3 Advantages of the system

1. Easiness in modification of data: The proposed system provides managing of huge data effectively
and efficiently for efficient results, storing the details of the products, users, etc. in such a way that the
database can be modified.

2. User friendly: The proposed system is user friendly because the retrieval and storing of data is fast
and data is maintained efficiently. Moreover the graphical user interface is provided in the proposed
system, which provides user to deal with the system very easily.

3. Customer Feedback: The users of the system are entitled to a feedback about the auctioned item that
they have added.

4. No or very few paperwork: The proposed system either does not require paper work or very few
paper works is required. All the data is feted into the computer immediately and various feedbacks and
reports can be generated through computers. Since all the data is kept in a database no data of the

7
organization can be destroyed. Moreover work becomes very easy because there is no need to keep data
on papers.

5. Support strategic competitive advantage: Proposed system supports strategic competitive

advantages. Since the proposed systems provide easiness in reports generating it will provide strategic
advantages among competitors.

6. Computer operator control: Computer operator control will be there no errors. Moreover storing
and retrieving of information is easy. So work can be done speedily and in time.

1.4 Previous work or related systems; how they are used.

Before we begin a new system it is important to study the system that will be improved or replaced (if
there is one). We need to analyze how this system uses hardware, software, network and the people
resources to convert data resources, such as transaction data, into information products, . Thus we
should document how the information system activities of input, processing, output, storage and control
are accomplished.

Following are the problems associated with the previous project which led to the creation of the
proposed project:-

1.Inability of modification of data: The managing of huge data effectively and efficiently for efficient
results, storing the details of the products etc. in such a way that the database can be modified as not
possible in the current system.

2.Not user friendly: The existing system is not user friendly because the retrieval and storing of data is
slow and data is not maintained efficiently.

3.Difficulty in reports generating: Either no reports generating in a current system or they are
generated with great difficulty reports take time to generate in the current system.

4.Manual operator control: Manual operator control is there and leads to a lot of chaos and errors.

5.Lot of paperwork: Existing system requires lot of paper work and even a small transaction require
many papers fill. Moreover any unnatural cause (such as fire in the organization) can destroy all data of
the organization. Loss of even a single paper led to difficult situation because all the papers are
interrelated.

8
6.Inability of sharing the data: Data cannot be shared in the existing system. This means that no two
persons can use the same data in existing system. Also the two departments in an organization cannot
interact with each other without the actual movement of data.

7. No support in decision-making: Existing system does not support managerial decision-making.

8.No support in strategic competitive advantage: Existing system does not support strategic
competitive advantages.

9
 Chapter 2

REQUIREMENT ANALYSIS
Before we begin a new system it is important to study the system that will be improved or replaced (if
there is one).We need to analyze how this system uses hardware, software, network and the people
resources to convert data resources, such as transaction data, into information products, such as reports
and displays. Thus we should document how the information system activities of input, processing,
output, storage and control are accomplished.

2.1 ANALYSIS STUDY

1. Open Communication Environment:

It provides a good way of communication between the user (customer) and the admin of the system. The
potential customer gets to see a wide variety of products available to him. He may order the products
which he desires to buy and later on give a feedback regarding the selected item and the admin can reply
to that feedback. Which leads to an healthy communication between the user and the manager.
2. Lower Installation Charges:
We neither require any high configuration systems for smooth running of server program, nor do we
require any high configuration systems for smooth running of a client program. This application is
designed with an ease to support any ordinary system having a internet connection. At the server the
charges are only for setting up the LAN connections but not the systems.
3. Secured and Reliable:
The messages that travel across the LAN are enclosed in the form of TCP packets which are a secured
form of data transfer that is most widely used across the globe. So the private sessions would be done in
a secured form without a third party interface.
4. Simple to use and Easy to Understand:
The coding of this application is a tedious job. But the client and server modules are enclosed in servlet
and jsp pages. The user only needs a web browser to start interpreting the coding done in these pages.
5. Platform Independent
Since the project is done completely in java, it also executes main properties of language. The given
application is platform independent. So the client systems may have vista, Linux, Mac or any other
operating system, but they can connect to server easily without any dependencies of OS.

10
2.2 Feasibility Study

All projects are feasible if they have unlimited resources and infinite time. But the development of
software is plagued by the scarcity of resources and difficult delivery rates. It is necessary and prudent to
evaluate the feasibility of a project at the earliest possible time. The three considerations are involved in
the feasibility analysis.

2.3 Technical Feasibility

Technical feasibility centers on the existing mobile system (hardware, software…etc) and to what extent it can
support the proposed addition if the budget is a serious constraint, then the project is judged not feasible. The
technical feasibilities are important role in my project because here I am using Java J2EE. It requires ECLLIPSE
(software) to develop this application. A easily available software and easy to use.

2.4 Economical Feasibility

This procedure is to determine the benefits and savings that are expected from a candidate system and
compare with cost. If benefits outweigh cost then the decision is made to design and implement the
system. Otherwise further justification or alterations in proposed systems that have to be made if it is
having a change of being approved. This is an ongoing effort that improves any feasibility costs spent on
this project because here I am using open source environments.

2.5 Operational Feasibility

People are inherently resistant to change and mobiles have been known to facilitate change. There is no
need of technical background is required to work on the application. All the information needed can be
seen on just one click

2.2 USER REQUIREMENTS

The system provides the user with ease of booking bakery items over the internet. The user merely require an web
browser to explore the system and start placing orders. The user might also give the feedback about the product.

11
All this can be done using a internet connection and a web browser installed in user’s system. The system
specifications that a user may want are as follows:

1. It should be easy to understand

2. Must be interactive
3. Should provide a good user interface
4. Security should be maintained
5. Redundancy must be controlled

Inquiry Form/Interviews
Q) What kind of system?

A) A fast and reliable system

Q) User satisfaction from the content?

The content is to be self explanatory and user could easily understand it

Q) Data security?

Data should be in encrypted format so that no third party could access the user credentials.

Q) Using of system

A system that is easy to use and with less complications.

Q) What kind of interface?

A more user oriented interface that is basically designed for the users only

Q) Trustworthiness of the user credentials?

Since the user is providing of its credentials to the application so its rights to use needs to be of the user
i.e. without user permissions it cannot be exchanged or changed

2.3 Discussion with IT experts

Creating an IT project for a beginner can at times become a challenging task. So, the discussion with the
veterans in the field of IT becomes an important task which might lead to some great benefits for the

12
developer. Some IT developers might consider it as an time wasting process but, they would be missing
out on a very important lesson ignoring this step. The people who are in the IT field for a long time
knows the mindset of the user pretty well and might help in giving some important pointers which in
turn would help in improvement of the project. Following were the outcome of the discussion held with
our IT experts:

1. Proper validations were proposed

2. User friendly template was taken
3. Security Checks were performed
4. More functionality was added

So, it was a very eventful and important step taken in the development of the project which leads to
some interesting improvements in the project.

2.4 Final Requirements

User Oriented: A system should be more user friendly not of the technical point of view

Better GUI: All the elements used in the system should be of interactive in nature that is its look and
feel is not so boring that the user could get bored while using it.

Reliability: The system should be reliable and fast in processing

Data security: Access to the organizational data is not to be granted to any unknown person which is
not a part of the transaction

Confidentiality: Whatever the user is providing to the organization ,the user has the full rights to
modify it and it could be not be accessed/modified without users permission

Better Management of information: All the information should be managed that is the flow of the
information is to be in right track

Presentation: The content that is to be presented to the user is to be presented in such a way that is self
explanatory to the user and he/she is satisfied with the data.

13
 Chapter 3

DESIGN OF THE SYSTEM

3. Software requirements

Platform Platform Independent

The Operating System Windows 7
Framework Eclipse, Apache Tomcat Server
Front-End Tool Google Chrome
Back-End Tool Oracle Database
3.1.1 Hardware Requirements

Processor Intel Pentium IV 2.9 GHz Other

RAM Minimum 4 GB

Graphics Integrated graphics card

Hard Disk Minimum 500 GB

3.2 System Requirements

To know the detailed system requirements an SRS has to be prepared .Software requirement
specification abbreviated as SRS is a means of translating the idea of files into a formal document. The
main features of SRS include:
 Establishing the basis for an agreement between the client and the developer.

 Producing a reference for validation of the final product. SRS assist clients in determining if the
software meets the requirements.
Mainly there are six requirements which an SRS must satisfy.

(a) It should specify the external behavior.

(b) It should specify the constraints.

(c) It should be easy to change.

(d) It should be a reference tool.

14
(e) It should record throughout the lifecycle.

(f) It should have the capacity of expectation of an undesired event.

Usually we come across four types of requirement specification

(a) User Interface Requirements

(b) Database Requirements

(c) Functional Requirements

(d) Non-Functional Requirements

3.2.1 User Interface Requirements

The user of the proposed system requires that the developed software should be user friendly, have
security access, and ensure the privacy of the administrator and produce results in timely manner. The
users are not frequently exposed to the reservation system, so the system interface to the user must be
simple and understandable. The web pages must be user-friendly and must be in an easy-to-use style.
The user must be able to easily switch among various I/O screens. The product is well designed so that it
can be used easily by the users who are novices to the system.

3.2.2 Database Requirements

The database should be designed in such a way that it enhances the efficient searching , reservation and
manipulation of all the information associated. For instance all general information regarding an item
attribute should be stored in a particular table.

The database should be organized in such a way that it helps in searching and reserving various essential
summaries needed for users.

3.2.3 Functional Requirements

The various functional requirements of the system can be summarized as:-

(a) A home page that is user friendly and ambiguous.

(b) It is easy to look for the desired information.

15
(c) User can easily do reservation.

3.2.4 Non-Functional Requirements

Non-functional requirements define the system properties and constraints that arise through user needs,
because of the budgeted constraints or organizational policies, or because of the need for interoperability
with other software or due to the external factors such as safety regulations privacy registrations and so
on.

Design Requirements

The main objectives of input design are:

(a) Controlling the amount of input

(b) Keeping the process simple.

(c) The best thing in the input design is to achieve all the objectives mentioned in the simplest manner
possible.

The main objectives of output design are:

(a) Identifying the specific outputs.

(b) Creating reports for displaying and storing information.

The primary goal of the system analysis is to improve the efficiency of the existing system. For that the
study of specification of the requirements is very essential. For the development of the new system, a
preliminary survey of the existing system will be conducted. Investigation done whether the upgradation
of the system into an application program could solve the problems and eradicate the inefficiency of the
existing system

3.3 Detailed System Specification (Module Wise)

The proposed system consists of mainly 6 important modules and various other sub modules. The main
6 modules of the system are as follows

16
1 Create Account-this module is used by the customer to get himself/herself registered to the website.
The customer has to provide some basic information regarding him to get registered to the website. The
information to be provided by the customer for getting himself registered is: name, contact, address,
password and email. Once the user is registered he is ready to use the functionalities present in the
website.

2 Login-Once a user has been registered to the website, he is free to use the services offered to him by
logging into his account using appropriate details. The proposed website accepts two kinds of logins
which are as follows:

User Login: it is the basic normal login for any customer of the website. The user enters his username
and password to login.

Admin Login: this is the login portal made especially for admin(s) of the website. It allows the admin to
gain access to privileged root user powers.

3 Feedback: user can give his/her feedback or suggestions which could help in overall quality of the
product.

4 Messages: user can send or/and receive messages to and from other users that can be thought of as a
chat messenger, as well as to the admin.

3.3 THE USE CASE APPROACH

A use case is a set of scenarios that describe an interaction between a user and a system.

A use case diagram displays the relationship among actors and use cases. The two main components of a
use case diagram are use cases and actors.

USE CASE

Fig. 3.1 Actor and Usecase

17
An actor is represents a user or another system that will interact with the system you are modelling.

A use case is an external view of the system that represents some action the user might perform in order
to complete a task.

LOGIN
LOG IN

LOG OUT
LOG OUT

AUCTIO MANAGES
N
AUCTIONS

ADMIN
User BIDS
MANAGES
MESSAGES

MESSAGES

Fig.3.2 Interaction between user and admin

In The above diagram there are 2 actors or users who use the system. These two users are as follows:

1. User-The customer is allowed to login to the system, logout of it, add items to auction, bid for
the items added to the website to purchase and view the status of his bookings.

2. Admin-The admin can also login and logout of the system. Other than that the admin of the
system manages all the auctions and can cancel/finalize the item for the auction.

18
 3.4 ER DIAGRAM
Entity – Relationship model (ER model) in software engineering is an abstract way to describe
a database. This article refers to the techniques proposed in Peter
ITEMChen's 1976 paper. However, variants
of the idea existed previously, and have been devised subsequently such as super type and subtype data
entities and commonality relationships.
CONTACT AUCID NAME
NAME

ADDS
EMAIL USER BUYNO
ITEM
W

BALANC

BID
ADD
SENDS
&

SEND

AUCTION

FEEDBACK MESSAGES

RECIEVE ADMINSENDS & MANA

NAME
RECEIVE

PASSWOR CANCEL
D /

Fig 3.3 ER diagram

In The above diagram shows the entity relationship. An Entity Relationship Diagram (ERD) is a visual
representation of different data using conventions that describe how these data are related to each other.
For example, the elements writer, novel, and consumer may be described using ER diagram. In the
diagram, the elements inside rectangles are called entities while the items inside diamonds denote the

19
relationships between entities. This ER diagram tutorial for beginners covers most things related to ER
diagram

3.5 DATA FLOW DIAGRAM (DFD)

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information
system, modelling its process aspects. Often they are a preliminary step used to create an overview of
the system which can later be elaborated. DFDs can also be used for the visualization of data
processing (structured design).

NEW USER BOOK

USER LOGIN CANCEL

EXISTING USER VIEW

UPDATES INFO
ADMIN LOG IN TRAINS
MANAGES
CHEF LOG IN INVENTORY

Fig 3.4 DFD

A DFD shows what kinds of information will be input to and output from the system, where the data
will come from and go to, and where the data will be stored. It does not show information about the
timing of processes, or information about whether processes will operate in sequence or in parallel
(which is shown on a flowchart).

Chapter 4

IMPLEMENTATION AND CODING

MEMBER TABLE

20
 Fig. 4.1 member table

This fig shows the table which is said to be a member table. It contains the data about the members who
are user in the auction website. It contains eleven fields name ,address ,country ,phone ,email
,password ,securityques ,status ,balance. This table is the part of our auction’s database.

MESSAGES TABLE

21
 Fig 4.2 Message Table

This fig shows the table which is said to be a message table. It contains the data about all the messages
who are user in the auction website. It contains eleven fields msdid, sender, receiver, subject, message..
This table is the part of our auction’s database. This table also contains feedback those are send by the
user and it is send to admin.

AUCTION TABLE

22
 Fig. 4.3

This fig shows the table which is said to be a auction table. It contains the data about the members who
are user in the auction website and who auctioned on the website their product . It contains eight fields
ownerid, item, currentbid, buynow, sender, description, aucid. This table is the part of our auction’s
database.

4.1 OPERATING SYSTEM

Platform Independent: Since the project is done completely in java, it also executes main properties of
language. The chat application is platform independent. So the client systems may have vista, Linux,
Mac or any other operating system, but they can connect to server easily without any dependencies of
OS.

23
4.2 Languages used

Java Enterprise Edition (J2EE)

Java Platform, Enterprise Edition or Java EE is Oracle's enterprise Java computing platform. The
platform provides an API and runtime environment for developing and running enterprise software,
including network and web services, and other large-scale, multi-tiered, scalable, reliable, and secure
network applications. Java EE extends the Java Platform, Standard Edition(Java SE),[1] providing an API
for object-relational mapping, distributed and multi-tier architectures, and web services. The platform
incorporates a design based largely on modular components running on an application server. Software
for Java EE is primarily developed in the Java programming language. The platform
emphasizes convention over configuration  and annotations for configuration. Optionally XML can be
used to override annotations or to deviate from the platform defaults.

4.3 S/W Tools

4.3.1 APACHE

The Apache HTTP Server, commonly is a web server software notable for playing a key role in the
initial growth of the World Wide Web. In 2009 it became the first web server software to surpass the
100 million website milestone.
Apache was the first viable alternative to the Netscape Communications Corporation web server
(currently named Oracle iPlanet Web Server), and since has evolved to dominate other web servers in
terms of functionality and performance. Typically Apache is run on a Unix-like operating system, and
was developed for use on Linux.

4.4 CODING
4.4.1 Login.jsp
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>
<%@include file="HEADER1.jsp" %>
<!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=ISO-8859-1">
<title>lOGIN </title>

24
</head>
<body>
<table>
<br><br><br><br>
<form action="loginservlet" method="get">
<tr><td><b>E-mail :</b></td><td><input type="text" name="email" max length="40"
required></td></tr>
<tr><td><b>Password :</b></td><td><input type="password" name="password" max length="30"
required></td></tr>
<tr><td></td><td><input type="submit"></td></tr>
<tr><td>not registered?<a class="cust1" href="register.jsp">register now</a></td>
<tr><td><a class="cust1" href="forgot.jsp">forgot password?</a></td></tr>
</form>
</table>
</body>
</html>

4.4.2 Loginservlet.java
package Controller;

import java.io.IOException;
import java.io.PrintWriter;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;

import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

@WebServlet("/loginservlet")
public class loginservlet extends HttpServlet {

25
 private static final long serialVersionUID = 1L;

public loginservlet() {
super();

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws

ServletException, IOException {
PrintWriter out=response.getWriter();
int flag=0;
String email=(String)request.getParameter("email");
String pass=(String)request.getParameter("password");
try{

Class.forName("oracle.jdbc.driver.OracleDriver");
Connection
con=DriverManager.getConnection("jdbc:oracle:thin:system/pass@localhost:1521:XE","Auction","995
3330821");
Statement st=con.createStatement();
ResultSet rs=st.executeQuery("select email,password,status from member where
email='"+email+"' and password='"+pass+"'");
while(rs.next())
{
flag=1;
String status=(String)rs.getString(3).trim();
String mail=(String)rs.getString(1).trim();
if(status.equals("member"))
{
HttpSession sess=request.getSession(true);

26
 sess.setAttribute("s3cret", "secret");
sess.setAttribute("email",mail);
sess.setAttribute("status",status);

request.getRequestDispatcher("memberhome.jsp").forward(request, response);
break;
}
else if(status.equals("admin"))
{
HttpSession sess=request.getSession(true);
sess.setAttribute("s3cret", "secret");
sess.setAttribute("email",mail);
sess.setAttribute("status",status);

request.getRequestDispatcher("adminhome.jsp").forward(request, response);
break;
}

break;
}

if(flag==0)
{
request.setAttribute("error", "Enter a Valid Id and Password");
request.getRequestDispatcher("error.jsp").forward(request, response);
}

27
 catch(Exception e)
{
out.println(e);

}
}

protected void doPost(HttpServletRequest request, HttpServletResponse response) throws

ServletException, IOException {

28
 Fig. 4.4 home page
This fig show the home page of this auction website. Which contains the images related to this site and
the various modules.

4.4.3 Register.jsp
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@include file="HEADER1.jsp" %>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
</head>
<body>
<br><br><br><br>
<table>
<form action="registerservlet" method ="get">
<tr><td><b>Name:</b></td><td><input type="text" name="rname" required
maxlength="50" ></td></tr>
<tr><td><b>Address:</b></td><td><input type="text" name="radd" required
maxlength="50"></td></tr>
<tr><td><b>Country:</b></td><td><input type="text" name="rcountry" required
maxlength="20"></td></tr>
<tr><td><b>Email ID:</b></td><td><input type="email" name="rid" required
maxlength="30"></td></tr>
<tr><td><b>Phone No:</b></td><td><input type="text" name="rpno" required
maxlength="10"></td></tr>
<tr><td><b>Password:</b></td><td><input type="password" name="rpass"
required maxlength="20"></td></tr>
<tr><td><b>Confirm Password:</b></td><td><input type="password"
name="rcpass" required maxlength="20"></td></tr>
<tr><td><b>Select Security question :</b></td><td><select name="sq">
<option value=1>whats your favorite color? </option>
<option value=2>whats the name of your 1st pet? </option>
<option value=3>whats your favorite cartoon? </option>
</select></td></tr>
<tr><td><b>Answer</b></td><td><input type="text" name="rans" required
maxlength="25"></td></tr>
<tr><td><input type="submit"></td></tr>
</form>
</body>
</html>

29
4.4.4 Registerservlet.java
package Controller;
import java.io.IOException;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.io.IOException;
import java.io.PrintWriter;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
@WebServlet("/registerservlet")
public class registerservlet extends HttpServlet {
private static final long serialVersionUID = 1L;
public registerservlet() {
super();
// TODO Auto-generated constructor stub
}
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws
ServletException, IOException {
PrintWriter out=response.getWriter();
String usename=(String)request.getParameter("rname");
String useadd=(String)request.getParameter("radd");
String usecountry=(String)request.getParameter("rcountry");
String useno=(String)request.getParameter("rpno");
String usepass=(String)request.getParameter("rpass");
String usecpass=(String)request.getParameter("rcpass");
String usemail=(String)request.getParameter("rid");

30
 String usesq=(String)request.getParameter("sq");
String useans=(String)request.getParameter("rans");

if(usepass.equalsIgnoreCase(usecpass) && (useno.length()==10))

{

try{
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection
con=DriverManager.getConnection("jdbc:oracle:thin:Auction/9953330821@localhost:1521:XE");
Statement st=con.createStatement();
ResultSet rs=st.executeQuery("select name,phone from member");

while(rs.next())
{
String check1=(String)rs.getString(1);
String check2= (String)rs.getString(2);

if(check1.equalsIgnoreCase(usename) ||
check2.equalsIgnoreCase(useno))
{

request.getRequestDispatcher("register.jsp").forward(request, response);
}
else
{
int q=Integer.parseInt(usesq);
switch(q)
{
case 1:
{

31
 int r=st.executeUpdate("insert into member
values('"+usename+"','"+useadd+"','"+usecountry+"','"+useno+"','"+usemail+"','"+usepass+"','whats you
faviorite color?','"+useans+"','member',10000)");
if(r>0)
{

request.getRequestDispatcher("sucessreg.jsp").forward(request, response);
break;
}
break;
}

case 2:
{
int r=st.executeUpdate("insert into member
values('"+usename+"','"+useadd+"','"+usecountry+"','"+useno+"','"+usemail+"','"+usepass+"','whats the
name of your 1st pet?','"+useans+"','member',10000)");
if(r>0)
{

request.getRequestDispatcher("sucessreg.jsp").forward(request, response);
break;
}
break;
}

case 3:
{

32
 int r=st.executeUpdate("insert into member
values('"+usename+"','"+useadd+"','"+usecountry+"','"+useno+"','"+usemail+"','"+usepass+"','whats you
faviorite cartoon?','"+useans+"','member',10000)");
if(r>0)
{

request.getRequestDispatcher("sucessreg.jsp").forward(request, response);
break;
}
break;
}

default:
out.println("Not a valid choice");
}

}
}

catch(Exception e)
{
out.println("error"+e.getMessage());
}

}
else{
request.setAttribute("error", "the passwords do not match");
request.getRequestDispatcher("error.jsp").forward(request, response);

33
 }

}
protected void doPost(HttpServletRequest request, HttpServletResponse response) throws
ServletException, IOException {
// TODO Auto-generated method stub
}

Fig.4.5 Register Page

This fig. show the registration page. This page contains all the mandatory fields which is to be filled by
the new user to register himself on this particularly website. To be the member of this website a paerson
should register himself first.

4.4.5 Feedback.jsp

<%@ page language="java" contentType="text/html; charset=ISO-8859-1"

pageEncoding="ISO-8859-1"%>

34
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@include file="mheader.jsp" %>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
</head>
<body>
<table >
<form action="feedback" method="get">
<%

if(sess.getAttribute("s3cret")!=null)
{
%>
<h2>Feedback</h2>
<tr><td><b>Subject : </b><input type="text" name="subject" max length="20"
required></td></tr>
<tr><td><b>Feedback</b></td></tr>
<tr><td><TEXTAREA NAME="message" ROWS="5" max length="120"
required></TEXTAREA></td></tr>
<tr><td><input type="submit" value="send"></td></form><form
action="gateway"><td><input type="submit" value="back"></td></tr></form>

<%
}
else
request.getRequestDispatcher("login.jsp").forward(request,response);
%>

</table>
</body>
</html>
4.4.6Feedbackservlet.java
package Controller;

import java.io.IOException;
import java.io.PrintWriter;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;

35
import java.sql.Statement;

import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

@WebServlet("/feedback")
public class feedback extends HttpServlet {
private static final long serialVersionUID = 1L;

public feedback() {
super();
// TODO Auto-generated constructor stub
}

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws

ServletException, IOException {
PrintWriter out=response.getWriter();
HttpSession sess=request.getSession(false);
int count=0;
if(sess.getAttribute("s3cret")!=null)
{
String email=(String)sess.getAttribute("email");
String subject=(String)request.getParameter("subject");
String message=(String)request.getParameter("message");

try{

36
 Class.forName("oracle.jdbc.driver.OracleDriver");
Connection
con=DriverManager.getConnection("jdbc:oracle:thin:Auction/9953330821@localhost:1521:XE");
Statement st=con.createStatement();
ResultSet rs=st.executeQuery("select * from messages");
while(rs.next())
{
count++;
}
st.executeUpdate("insert into messages
values("+count+",'"+email+"','admin','"+subject+"','"+message+"')");
request.setAttribute("success","Thank you for your valuable feedback");
request.getRequestDispatcher("success.jsp").forward(request, response);
}
catch(Exception e)
{
out.println(e);
}
}
else
request.getRequestDispatcher("login.jsp").forward(request,response);

protected void doPost(HttpServletRequest request, HttpServletResponse response) throws

ServletException, IOException {
}

37
 Fig. 4.6 Feedback Page
This fig. show the feedback page. This page contains all the mandatory fields which is to be filled by
the existing user to give the feedback to the admin about his/her experience for using this website. To
be the member of this website a person should give a feedback to the admin .
4.4.7 Mymessages.jsp
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@page import="java.sql.*" %>
<%@include file="mheader.jsp" %>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
</head>
<body>
<table border="2">

<tr>
<th>S.no</th><th>Sender</th><th>Subject</th><th>Message</th>
</tr>
<%

38
if(sess.getAttribute("s3cret")!=null)
{

try{

Class.forName("oracle.jdbc.driver.OracleDriver");
Connection
con=DriverManager.getConnection("jdbc:oracle:thin:Auction/9953330821@localhost:1521:XE");
Statement st=con.createStatement();
ResultSet rs=st.executeQuery("select * from messages where reciever='"+email+"'");
while(rs.next())
{ count++;
int msgid=(int)rs.getInt(1);
String sender=(String)rs.getString(2);
String subject=(String)rs.getString(4);
String message=(String)rs.getString(5);

%>

<tr>
<td><%=count %></td>
<td><%=sender%></td>
<td><%=subject%></td>
<td><%=message%></td>

<td> <a class="cust1" href ="deletemessage?deleteid=<%=msgid%>">Delete</a></td>

</tr>
<%
}
}
catch(Exception e)
{
out.println(e);
}
%>
<tr></tr><tr></tr><tr><td></td><td>
</table><br><br><br>
<form
action="gateway">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<input type="submit" value="back"></form>
</body>
</html>

<%
}
else

39
 request.getRequestDispatcher("login.jsp").forward(request,response);
%>

Fig. 4.7 Message Page

This fig. show the message page. This page contains all the messages. These messages are sent by the
users to the user and the user to the admin and the admin to the user. This page also have one more
functionality to delete the messages. It also inform and give the info about the sender, that who is the
sender for the particular message.

4.4.8 Sendmessage.jsp

<%@ page language="java" contentType="text/html; charset=ISO-8859-1"

pageEncoding="ISO-8859-1"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@page import="java.sql.*" %>
<%@include file="mheader.jsp" %>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
</head>
<body>
<table >
<form action="sendmessage" method="get">

40
<%

if(sess.getAttribute("s3cret")!=null)
{
%>
<h2>Send a Message</h2>
<tr><td><b>Recipient</b><input type="text" name="reciever" max length="30" required></td></tr>
<tr><td><b>Subject</b><input type="text" name="subject" max length="30" required></td></tr>
<tr><td><b>Message</b></td></tr>
<tr><td><TEXTAREA NAME="message" ROWS="5" max length="120"
required></TEXTAREA></td></tr>
<tr><td><input type="submit" value="send"></td></form><form action="gateway"><td><input
type="submit" value="back"></td></tr></form>

<%
}
else
request.getRequestDispatcher("login.jsp").forward(request,response);
%>

</table>
</body>
</html>

41
 Chapter 5

TESTING & TEST RESULTS

5.1 SOFTWARE TESTING

Software testing is a critical element of software quality assurance and represents the ultimate review of
specification design and coding. Testing is an exposure of a system to trial input to see whether software
meets correct output. Testing cannot be determined whether software meets user’s needs, only whether it
appears to confirm to requirements. Testing can show that a system is free of errors, only that it contains
error. Testing finds errors, it does not correct errors. Software success is a quality product, on time and
within cost. Through testing can reveal critical mistakes. Testing should therefore,

Validate Performance

Detects Errors

Identify Inconsistencies

5.2 Test Objective

 There is strong evidence that effective requirement management leads to overall project cost
savings. The three primary reasons for this are,
 Requirement errors typically cost well over 10 times more to repair than other errors.
 Requirement errors typically comprise over 40% of all errors in a software project.
 Small reduction in the number of requirement errors pays big dividend in avoided rework costs
and schedule delays.
 System are not designed as entire systems nor are they tested as single systems the analyst must
perform both unit and system testing. For this different level testing are use:

5.2.1 Unit Testing

In unit testing Module is tested separately and the programmer simultaneously along with the coding of
the module performs it.

42
In unit testing the analyst tests the programs making up a system. For this reason, unit testing is
sometime called program testing. Unit testing gives stress on modules independently of one another, to
find errors. 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.

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.

5.2.2 System Testing

This is performed after the system is put together. The system is tested against the system requirement to
check if all the requirements are met and if the system performs of specify by the requirements.

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.

The function of testing is to detect the defects in the Software. The main goal testing is to uncover
requirement, design and coding errors in the programs. The types of testing are discussed below:

5.2.3 MODULE TESTING

Module tests are typically dynamic white-box tests. This requires the execution of the software or parts
of the software. The software can be executed in the target system, an emulator, simulator or any other
suitable test environment.
The focus of the tests is:
 Set up of regression tests. This means the test environment once set up for a function can be re-
used to check its performance e.g. after maintenance.
 Coverage of the relevant state of the art test methods like equivalence class building, boundary
value analysis and condition coverage are used.

5.2.3 INTEGRATION TESTING

“If they all work individually, they should work when we put them together.” The problem of course is
“putting them together “. This can be done in two ways:

43
 1. Top down integration: Modules are integrated by moving downwards through the control
hierarchy, beginning with main control module are incorporated into the structure in either a
depth first or breadth first manner.
2. Bottom up integration: It begins with construction and testing with atomic modules i.e. modules
at the lowest level of the program structure. Because modules are integrated from the bottom up,
processing required for the modules subordinate to a given level is always available and the need
of stubs is eliminated.

5.2.4 BLACK-BOX TESTING

Black-box testing is a method of software testing that tests the functionality of an application as opposed
to its internal structures or workings.
The system is tested just to assure whether it is meeting all the expectations or requirements from it,
tester is not concerned with the internal logic of the module or system to be tested. Some inputs are
given to system and it is observed whether the system is working as per the client’s requirements or not
or according to the requirements specified in SRS document. Specific knowledge of the application's
code/internal structure and programming knowledge in general is not required.
Test cases are built around specifications and requirements, i.e., what the application is supposed to do.
It uses external descriptions of the software, including specifications, requirements, and designs to
derive test cases. These tests can be functional or non-functional, though usually functional. The test
designer selects valid and invalid inputs and determines the correct output. There is no knowledge of the
test object's internal structure. This method of test can be applied to all levels of software
testing: unit, integration, functional, system and acceptance. It typically comprises most if not all testing
at higher levels, but can also dominate unit testing as well. Black box testing or functional testing is used
to check that the outputs of a program, given certain inputs, conform to the functional specification of
the program. The term black box indicates that the tester does not examine the internal implementation
of the program being executed

5.2.5 WHITE-BOX TESTING

A software testing technique where by explicit knowledge of the internal workings of the item being
tested are used to select the test data. Unlike black box testing, white box testing uses specific
knowledge of programming code to examine outputs. The test is accurate only if the tester knows what
the program is supposed to do. He or she can then see if the program diverges from its intended goal.

44
White box testing does not account for errors caused by omission, and all visible code must also be
readable.
Contrary to black-box testing, software is viewed as a white-box, or glass-box in white-box testing, as
the structure and flow of the software under test are visible to the tester. Testing plans are made
according to the details of the software implementation, such as programming language, logic, and
styles. Test cases are derived from the program structure. White-box testing is also called glass-box
testing, logic-driven testing or design-based testing. There are many techniques available in white-box
testing, because the problem of intractability is eased by specific knowledge and attention on the
structure of the software under test.

5.2.6 VALIDATION TESTING

TEST CASES
Field Value Valid/Invalid Result
Contact Null Invalid Fill all the fields
Confirm Wrong Invalid Passwords do not match
password
Password Wrong Invalid Please enter a valid id and
password
Name Null Invalid Fill all the fields
OUTPUTS
Contact=Null

45
 Fig. 5.1 Registration Page

This fig. shows the validation of the mandatory fields. All the fields are mandatory to be filled, this the
validation for the fields when a user is registering himself on this particular website.

Password=Do not match

46
 Fig. 5.2 Home page
This fig. shows the validation of password do not match. This means if the password is not matched with
the previous one then it will produce this error. A user must match ot fulfilled this validation to login
himself successfully.
Username/Password=wrong

47
 Fig. 5.3 Home Page

This fig. shows the validation of not fulfilling the right id and password. A user must entered the right id
and password.

48
 Name=Null

Fig. 4.5 Registration page

This fig. shows the validation of the mandatory fields. All the fields are mandatory to be filled, this the
validation for the fields when a user is registering himself on this particular website.

49
 Chapter 6

CONCLUSION

6.1CONCLUSION
Now a day’s there is a big demand of different types of applications, which is because IT has become
the main part of our New World. There is a big need of different applications. People want application
for every specific task from work to entertainment. We have developed the Java application “GO Grab
it” which works easy on any given web browser.

The application has been tested on platform of java and found to be working as per the given criteria. It
can be safely concluded that the application possesses a highly efficient UI system and is working
properly and meeting to all the requirements of the user. The application gives the user maximum
flexibility in the types of touch and other device movements.

6.2 FUTURE SCOPE

Every project whether large or small has some limitations no matter however  diligently
developed. In some cases limitations is small while in other cases they may be broad also. The new
system has got some limitations. Major areas where modifications can be done are as follows:

 Our system is not online so further it can be improved.

 The security is limited so some additional arrangement could be made to provide more security
to the system.
 There is no provision of complain handling so further it can be added.

50
 BIBLOGRAPHY

 http://www.w3schools.com
 http:// www .stackoverflow.com
 http://wikipedia.com
 Java The Complete Reference, by Herbert Schildt

51