Table of Contents

Table of Contents................................................................................................................................................ii
Table of Figures.................................................................................................................................................iii
1.0. Purpose..........................................................................................................................................................1
1.1. Introduction...................................................................................................................................................1
1.2. Scope.............................................................................................................................................................1
1.3. References.....................................................................................................................................................2
1.4. Document overview......................................................................................................................................2
2.0. Overall description.....................................................................................................................................4
2.1. System environment.....................................................................................................................................4
2.2. Functional requirements definitions.............................................................................................................4
2.3. Use cases.......................................................................................................................................................5
2.3.1. Use Case: Access Home Page................................................................................................................6
2.3.2. Use Case: Select Product.......................................................................................................................7
2.3.3. Use Case: Create New Entry in Data Base............................................................................................8
2.3.4. Use Case: Update Data Base.................................................................................................................9
2.4. Non-functional requirements..........................................................................................................................11
3.0. Requirement specifications...................................................................................................................12
3.1. External interface specifications.................................................................................................................12
3.2. Functional Requirements............................................................................................................................12
3.2.1. Access Home Page...................................................................................................................................
3.2.3. Create New Entry in Data Base...........................................................................................................13
3.2.4 Update Data Base.....................................................................................................................................
3.3. Detailed non-functional requirements........................................................................................................17
3.4. System Evolution............................................................................................................................................

1.0. Purpose
A proxy server is a computer that offers a computer network service to allow clients to make indirect network
connections to other network services.
As the name proxy, it means a server which fills up or acts and provides functionalities of some other Server Our
project is a proxy server which acts as
an intermediate between Web Server and its clients.
An HTTP proxy server is a server that handles HTTP requests from clients. If the client are of a common
organization or domain, or exhibit a similarity in browsing behavior, the proxy can effectively cache requested
documents.
Caching, which migrates documents across the network closer to the users, reduces network traffic, reduces the load
on popular Web servers and reduces the time that end users wait for documents to load.

1.1 Introduction (Module)

A proxy server is a computer that offers a computer network service to allow clients to make indirect network
connections to other network services. A client connects to the proxy server, and then requests a connection, file, or
other resource available on a different server. The proxy provides the resource either by connecting to the specified
server or by serving it from a cache. In some cases, the proxy may alter the client's request or the server's response
for various purposes, usually to view websites that are normally not allowed, such as game sites in school or work
place.

1.2. Scope (Module)

Caching proxies keep local copies of frequently requested resources, allowing large organizations to significantly
reduce their upstream bandwidth usage and cost while significantly increasing performance.
A caching proxy server accelerates service requests by retrieving content saved from a previous request made by the
same client or even other clients

1.3. References
Java 2 The Complete Reference 5th Edition,
Herbert Schildt, Tata Mc Graw Hill.
Sun Java Volume 1 & 2.
Professional Java Server Programming, Wrox
Press Ltd.
Roger S. Pressman, Software Engineering: A
Practitioners Approach
www.java.sun.com
www.jakarta.apache.org

1.4. Overview (Document/ Module)

Proxy User Interface
Proxy Server Listener
Connection Manager
Cache Manager
Log Manager
Configuration

2.0. Overall description

The proxy server-encompasses numerous files and information from the -oracle--Database, as well as files
on the department server system. This system will be completely web-based, linking to JDBC-ODBC-and the
remote web server from a standard web browser. An Internet connection is necessary to access the system.

Security:
By caching pages that have been previously requested, the proxy server speeds up performance by responding to
future requests for the same page using the cached information rather than going to the web site again.

When using a proxy server external systems only see the IP address of the proxy server so the true identity of
internal computers is hidden. The proxy server can also be configured with basic rules of what ports or IP addresses
are or are not allowed to pass through which makes it a type of basic firewall.

Quality:
A horizontal and vertical involvement of all concerned in project management processes and procedures becomes
very important. These concerned persons may also be termed as stakeholders and may vary with their existence at
various levels inside and outside the organization. All stakeholders must be well aware of the existence of standard
procedures and processes related to any project.
Well defined processes and procedures documented and distributed to all must be harnessed for strategic long term
benefits. This is important to achieve and is possible only by way of adherence to what is documented. A continuous
adoption of such well defined processes and procedures will definitely help in understanding and optimization .

2.1. System environment

Technologies Used:

Net beans IDE 6.5 for java programming.

JDK 1.6 .
Socket programming.

Hardware Requirement For User:

* Intel 486 or higher. RISC support should be available

* 24 MB Ram for Intel chips and 32 MB Ram for RISC
* 10 MB for installation.100 MB + .5 MB per client for Cache space.
* 2 Network interfaces (Adapters, Dial-Up, etc)

Software Requirement For User:

* Windows NT server 4.0
* Internet Information Server 2.0
* Service Pack 3
*TCP/IP

2.2. Functional requirements definitions

Caching

Reduces Latency

Reduces traffic on the web

Bandwidth Conservation

Increases accessibility

Firewalling and filtering

Connection sharing.

2.3. Non-functional requirements

INTRODUCTION:
Gives a brief introduction about the project. It consists of Objective, Scope,Motivation, Problem Definition and
Technology Used as the sub headings which completely summarizes about the whole project.
BACKGROUND: Gives a few details about the various technologies used in this project and also explains in brief
about the functioning of the various technologies.
PROJECT DESCRIPTION: Includes the software requirement specification (SRS) document of the project and
describes about the various features of the project. It also includes the disadvantages of the previous system
and advantages of the proposed system.
PROJECT DESIGN & IMPLEMENTATION: Describes about the various designing phases that the project
undergoes such as Gantt chart and data flow diagram. Also includes the documentation of them and the testing
of the various modules incorporated within the project.
PROJECT OUTPUT: Includes the snapshots of the various screens that the project shows while running in the real
time.
FUTURE SCOPE & CONCLUSION: Gives the direction about the enhancement of the project in various
dimensions and also concludes the project report

3.0. Requirement Specifications

1. Product Perspective:
Product is designed to solve the problems regarding use of internet services and speed related with bandwidth and to
enhance surfing facility and minimize load from server.

2. User Interfaces:

User interface of the product is interactive and easily understandable by the user.

3. Hardware Requirement For User:

* Intel 486 or higher. RISC support should be available.
* 24 MB Ram for Intel chips and 32 MB Ram for RISC.
* 10 MB for installation.100 MB + .5 MB per client for Cache space.
* 2 Network interfaces (Adapters, Dial-Up, etc)

4. Software Requirement For User:

* Windows NT server 4.0
* Internet Information Server 2.0
* Service Pack 3
* TCP/IP

5. Operations:
A cache/proxy server network conserves bandwidth, decreases network-imposed latency, and offsets the load on the
origin server from which the content is published.

3.4. System Evolution

The caching proxy server as stand-alone product is an endangered species In its place. Well continue to see
software firewalls expand their breadth to include the kind of content filtering, caching, and authentication that was
traditionally the role of the proxy server. However, the testing process downloads web pages which consume
network bandwidth, so it is suggested that in the future, it can re-use the statistical information from some existing
measurement system like perfsonar so that it need not download web pages frequently.