1

CHAPTER 1

INTRODUCTION

1. OBJECTIVE

Digital Placard is a form of advertising which is particularly common in

newspapers, online and other periodicals which may be sold or distributed free of
charge. Advertisements in a newspaper are typically short, as they are charged for by
the line, and one newspaper column wide.

Publications printing news or other information often have sections of classified

advertisements; there are also publications which contain only advertisements. The
advertisements are grouped into categories or classes such as "for sale—telephones",
"wanted—kitchen appliances", and "services—plumbing", hence the term
"classified".

Classified advertisements are much cheaper than larger display advertisements used
by businesses, and are therefore normally used by businesses with smaller
advertising budgets, or by private individuals.

The objective of this application is to design and build a Classifieds website. The
website must provide information to the users about various fields such as
education, rental, real estate, vacancies, cinema, matrimonial etc.
 2

CHAPTER 2

SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

In the present scenario, a user has to browse newspapers or relevant
documents and magazines to get information about various services. Or a user has to
approach some agencies. This requires a user to spend more time and effort. Often the
user may obtain irrelevant information.

Drawbacks
 Performance of the application too slow.
 Less Efficiency and low flexibility.
 Storing the data entries are low performance.

2.2 PROPOSED SYSTEM

In the proposed application, a user can access all services at a single place
and reduce time and effort. The system maintains a centralized repository of all
information. The system allows easy access to relevant data through well defined
interfaces. The system allows one to search and retrieve the desired information.

Advantages
 High performance of the application.
 More Efficiency and high flexibility of the application
 High performance database connection.
 3

CHAPTER 3

SYSTEM SPECIFICATION

3.1 HARDWARE REQUIREMENT

Processor : Intel Pentium®4, 2.3ghz and later.

CPU type : Intel Pentium 4
Ram : 2 GB.
HDD : 50 GB.
Monitor type : 15 Inch color monitor
Clock : 2.10 ghz.
Keyboard : 104Keys Keyboard.
Mouse : TAG Mouse.

3.2 SOFTWARE REQUIREMENT

Operating system : Windows 7 & later, LINIX/UNIX

Software tools : Netbeans IDE 7.0 (win32x86_64)
Front end : JAVA & J2EE
Back end : MySQL Server.
Documentation : Microsoft Word 2007
 4

CHAPTER 4

SOFTWARE DESCRIPTION

4.1 FRONT END

Java has been chosen as the platform because of its feature rich nature. The
Platform provides robust end-to-end solutions for networked applications as well as a
trusted standard for embedded applications. So was a natural choice for development
process.

JAVA

Initially the language was called as “oak” but it was renamed as “java” in
1995.The primary motivation of this language was the need for a platform-
independent(i.e. architecture neutral)language that could be used to create
software to be embedded in various consumer electronic devices.

 Java is a programmer’s language

 Java is cohesive and consistent
 Except for those constraint imposed by the Internet environment. Java
gives the programmer, full control
Finally Java is to Internet Programming where c was to System Programming.

JDBC
The JDBC is a set of the database access classes. The very term JDBC stands
for “Database Connectivity”. It was developed by Soft. JDBC technology is an API
(Application Program Interface) that allows virtual access to any tabular data source
from the programming language by means of some connecting software called
Drivers. It provides cross-DBMS connectivity to a wide range of SQL databases.
JDBC defines a set of interfaces to enable developers to access data independently of
the actual database product used to store the data. JDBC allow applets, Servelet, and
application to access data in famous database management systems.
 5

The JDBC API makes it possible to do three things:

 Establish a connection with a database or access any tabular data source
 Send SQL statements
 Process the results

4.2 BACK END

MYSQL
MySQL is the world's most used open source relational database management
system that runs as a server providing multi-user access to a number of databases.
MySQL is a popular choice of database for use in web applications, and is a central
component of the widely used LAMP open source web application software stack
(and other 'AMP' stacks). LAMP is an acronym for "Linux, Apache, MySQL, and
Perl/PHP/Python." Free-software-open source projects that require a full-featured
database management system often use MySQL.

MySQL and Microsoft SQL Server are both server frameworks for relational
databases. Although both products are similar, MySQL does not support all of the
features of SQL Server MySQL is, however, a free product, whereas the licensing
costs of Microsoft SQL Server can be significant. Many developers of web-based
applications use MySQL as their preferred technology.
 6

CHAPTER 5

PROJECT DESCRIPTION

5.1 PROBLEM DEFINITION

In earlier days classified advertising are done manually. The data collected
from the customer was gathered manually using hand written forms. After usage of
computers gathering of data from the customer were stored in database using servers

Using visual basic is easier but it needs some more time to complete the
storage of data and retrieving from the database. To make it faster and easier the
same project is developed using java and J2EE frameworks database design.

5.2 OVERVIEW OF THE PROJECT

PRODUCT PERSPECTIVE
The web application falls under the category of classified postings. Only
the Admin is allowed access to add, as well as changing and cancelling of
advertisement according to the customer request.

PRODUCT FEATURES
The web application is used to store the customers classified details like
add university details , add college details , add rental , .. and also viewing and
deleting details from the databases
 7

DESIGN AND IMPLEMENTATION CONSTRAINTS

 Since the application is web based, it should support simultaneous requests
from multiple customers, and should be available 24x7x365.
 Customer authentication is important, since More than 50 customers from
different type of the system have worked at the same time.
 Proper exception and error management facilities should be incorporated
into the system application.
 Since the application is web based, write details gathered for the customers
are to be stored in the database where the system is installed. It can be
retrieving for the same system.

5.3 MODULE DESCRIPTION

 Administrator module
 User module
 Advertisement module.

Administrator module:

This module provides administrator related functionalities. Administrator can

add, delete, edit and view the details of advertisements and classifieds. Administrator
will moderate the system and can allow or ban the users.

User module:

A user must be registered with the system to avail the services. A user can
either purchase or sell a product through the system. A user can view the details of a
specific display item and is allowed to contact the owner of that item.

Advertisement module:

This module maintains all advertisements posted by the users and authorized by
the administrator. The validity and duration of a classified depends on the
administrator. The advertisements and classifieds can belong to categories such as
education, rental, real estate, vacancies, cinema, cars, matrimonial etc.
 8

5.4 DATA FLOW DIAGRAM

A Data flow diagram(DFD) is a graphical representation of the “flow” of data
through an information system.DFD can also be used for the visualization of data
processing(structured design).On a DFD , data items flow from an external data
source or an internal data store or an external data sink, via an internal process.

Figure 5.1 Context Flow Diagram(Level 0)

9
10
11
 12

5.5 ER DIAGRAM
In software engineering, an entity–relationship model (ER model) is a data
model for describing the data or information aspects of a business domain or its
process requirements, in an abstract way that lends itself to ultimately being
implemented in a database such as a relational database. The main components of ER
models are entities (things) and the relationships that can exist among them.
 13

5.6 SEQUENCE DIAGRAM

The sequence diagrams share helpful in detailing the flow of transactions
between the entities such as actor, database, and controller. Hence, for a sequence
diagram to be prepared, It is essential that the “use case diagram” would have been
finalized, else it could mean rework might be required if the use case diagram is
revised.

This sequence diagram is help to customers. Customer is request to the

vehicle to the employee to assign the vehicle to the customer. All the details are
transferring given blow. Show in the following figure.
 14

Figure 5.3 Sequence Diagram

 15

5.7 Use Case diagram

Figure 5.4 Use Case diagram

 16

5.7 DATABASE DESIGN

It is the process of producing a detailed data model of a database. This logical
data model contains all the needed logical and physical design choices and physical
storage parameters needed to generate a design in a Data Definition Language, which
then can be used to create a database. A fully attributed data model contains detailed
attributes for each entity.

Table name : ADMIN

Primary Key : AdminuserId
Description : This table contains information about the Admin details

ADMIN
Column Name Data Type Allow Null

AdminUserId int(20) NO

Password password(15) YES

Status bit YES

Description Varchar(max) YES

 17

Table name : User

Primary Key : userId
Description : This table contains information about the User details

USER
Column Name Data Type Allow Null

UserId int(20) NO

Password password(15) YES

Feedback Varchar(1000) YES

Description Varchar(max) YES

UserDetails Varchar(max) YES

UserContactNo Int(10) YES

Table name : College

Primary Key : CollegeId
Description : This table contains information about the College details

COLLEGE
Column Name Data Type Allow Null

CollegeId int(20) NO

CollegeName password(15) YES

CollageLocation Varchar(1000) YES

Date Date(8) YES

 18

Table name : Advertisement

Primary Key : AdvertisementNo
Description : This table contains information about the Advertisement details

Advertisement
Column Name Data Type Allow Null

AdvertisementNo int(8) NO

AdDetails Varchar(200) YES

AdDesc Varchar(1000) YES

Table name : JobDetails

Primary Key : JobCode
Description : This table contains information about the Job details

JOBDETAILS
Column Name Data Type Allow Null

JobCode int(5) NO

JobName Varchar(30) YES

Skills Varchar(1000) YES

LastDate Date(8) YES

Status bit YES

 19

Table name : Education

Primary Key : CourseNo
Description : This table contains information about the Education details

EDUCATION
Column Name Data Type Allow Null

CourseNo int(8) NO

DepartmentCode int(6) NO

StudentDetails Varchar(1000) YES

Table name : RealEstate

Primary Key : FlatNo
Description : This table contains information about the RealEstate details

REALESTATE
Column Name Data Type Allow Null

FlatNo int(5) NO

OwnersName Varchar(30) YES

ADDRESS Varchar(1000) NO
20
 21

5.9 INPUT DESIGN

Login
Login form will allow the user name and password values such as
Authentication process of the Customers (shown in the Figure 9.1)

University details
registration form will allow the user to give input values such as registration
no, permit no, insurance policy no, chassis no, of the new and existing vehicle for
further verification (shown in the figure 9.12)

Customer details
This maintenance form will allow the user to enter the Customer details such
as Customer name, pickup address, drop address and mobile number (Refer
figure 9.4)

Driver details
This maintenance form will allow the employee to enter the Driver details
such as Driver name, Driver id, address and mobile number (Refer figure 9.11)

Landmark details
This maintenance form will allow the employee to enter the Landmark details
such as Zone id, Zone Name and Landmark Name (Refer figure 9.5)

Taxi Master details

This maintenance form will allow the employee to enter the taxi Master
details such as taxi details, driver details and owner details (Refer figure 9.9)

Vehicle In details
This maintenance form will allow the Employee to enter the vehicle in details
such as Trip sheet no, registration id, driver name, vehicle in time and Landmark
(Refer figure 9.12)
 22

Vehicle Out details

This maintenance form will allow the Employee to enter the vehicle out
details such as Trip sheet no, registration id, driver name, vehicle out time and
Landmark (Refer figure 9.13)

5.9 OUTPUT DESIGN

Login
All the employee user name and password to be stored in a database (shown
in the figure 9.1)

Vehicle details
All the vehicle details will be stored to the database(shown in the figure 9.12)

Customer details
All the customer details will be stored the database (Refer figure 9.4)

Driver detail
All the deriver details will be stored the database (Refer figure 9.11)

Landmark detail
All the landmark details will be stored the database (Refer figure 9.5)

Taxi Master detail

All the Taxi master details will be stored the database (Refer figure 9.9)

Vehicle In detail
All the vehicle in details will be stored the database (Refer figure 9.12)

Vehicle Out detail

All the vehicle details will be stored the database (Refer figure 9.13)
 23

CHAPTER 6

SYSTEM TESTING

TESTING
Testing is vital to the success of the system. System testing makes a logical
assumption that if all the part of the system is correct, the goal will be successfully
achieved. It is the major quality measure used to determine the status and usefulness
of the system. Its basic function is to find the error in the software by examining all
possible loopholes.

The goal of testing is to print out uncovered requirements, design or coding

errors or invalid acceptance or storage of data. During system testing , the system is
used to experimentally ensure that the software runs according to its specification
and in the way users except. Special test data is the input for processing, and results
are examined. The process of testing is divided into three distinctive stages. Different
tests are performed at different levels.

6.1 MODULE TESTING

Tested the small piece of software for separate specification exists. The
software was executed in an emulator for the module test. The fetching of data will
be done successfully as given below. Reference to figure 9.3 and 9.4

6.2 INTEGRATION TESTING

If the user accepts the condition and terms then must load the next form and
the user wants to view and edit the details must load the Enter Address Detail form.
Refers to figures 9.3, 9.4
 24

6.3 VALIDATION TESTING

The user can read the file by clicking on the file. If the date, time and mobile
number field should be validated for each and every forms. Refer figures 9.1 to 9.13.

6.4 UNIT TESTING

Unit testing is usually conducted as part of a combined code and unit test
phase of the software lifecycle, although it is not uncommon for coding and unit
testing to be conducted as two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written
in detail.

Test objectives
 All field entries must work properly.
 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested
 Verify that the entries are of the correct format
 No duplicate entries should be allowed
 All links should take the user to the correct page.
Refer to Figures 9.5 and 9.7
 25

6.4 TEST CASES

Table 6.1 Test Cases

 26

CHAPTER 7

SYSTEM IMPLEMENTATION

7.1 IMPLEMENTATION
System Implementation is the stage in the project where the theoretical design
is turned into a working system. The most critical stage is achieving a successful
system and in giving confidence on the new system for the user that it will work
efficiently and effectively. The existing system was long time process. The proposed
system was developed using. The existing system caused long time transmission
process but the system developed now has a very good user-friendly tool, which has
a menu-based interface, graphical interface for the end user. After coding and testing,
the project is to be uploaded to the necessary server. The Web Application is to be
created and loaded in the system. Again the code is tested in the installed server.
Installing the developed code in system in the form of Server file is implementation.

MAINTENANCE
The term “software maintenance” is used to describe the software
engineering activities that occur following delivery of a software product to the
customer. The maintenance phase of the software life cycle is the time period in
which a software product performs useful work. Maintenance activities involve
making enhancement to software products, adapting products to new environments
and correcting problems. Software product enhancement may involve providing new
functional capabilities, improving user display and modes of interaction, and
upgrading external documents. Adaptation of software to a new environment may
involve moving the software to a different machine. Problem correction involves
modification and revalidation of software to correct errors. Adaptation of this
project to a new environment is also performed easily.
 27

CORRECTIVE MAINTENANCE
Even with the best quality assurance activities, it is likely that they customer
will uncover defects in the software. Corrective maintenance changes the software to
correct defects.

ADAPTIVE MAINTENANCE
An activity are modifies the software to a proper interface with a changing
environment. The system has been modified so that various change include to the
new system.

In case of Fund Transfer, adoptive maintenance has been performed, that is

in earlier system (character based UNIX system) changes are fixed and if any new
changes are to be included, was a difficult task. Now provisions are given so that the
user can define various changes. Such as, it is designed to accommodate the new
change in future.

ENHANCEMENT MAINTENANCE
As software is used, the customer/user will recognize additional functions
that will provide benefit. Perceptive maintenance extends the software beyond its
original functional requirements.
 28

CHAPTER 8

CONCLUSION AND FUTURE ENHANCEMENT

8.1 CONCLUSION
An exploratory investigation on utilizing (”Digital Placard”) Web application
is presented. It is different from existing works, so take interference and based on
RCP plug-in project. This project is mainly succeed the existing project with new
requirement. It helps the customer to gain the needed advertisements when and
where the customer wants. The application does the operations automatically and
manual work has been reduced. According to the results, the global performance is
improved considerably by database transmissions in terms of both throughput and
job completion time; in addition, the Scheduling algorithms are effective and
efficient in tackling the Classified Posting System.

8.2 FUTURE ENHANCEMENT

From selling items you no longer need, a car, real estate, job opportunities to
virtually anything you can think of, the online classifieds market can do it. And
because it is a cheaper form of advertising than the conventional media, the
industry’s growth will continue booming for years to come. The online classifieds
industry continues to be a major boom in, thanks to the internet penetration that has
allowed the posting of classifieds on the web to reach a wide client base.
 29

CHAPTER 9

APPENDICES

9.1 SOURCE CODE

Coursedet.jsp.
<%@ include file="makecon.jsp" %>
<%@page import="java.sql.*" %>
<%! ResultSet rs1 = null;
%>
<html>
<body background="images/17.jpg">
<form action="coursedet.jsp" method=post>

<%
String univerid=(String)session.getAttribute("uniid");
//out.println("Session id"+univerid);
try{
String selectedname=request.getParameter("collageinfo");
//out.println("Selected name"+selectedname);
String uniid="";
String collageid="";
String colname="";
PreparedStatement pst=null;
//ResultSet rs1=null;

//Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
//Connection
con=DriverManager.getConnection("jdbc:odbc:eclassifieds","advt","advt");
%>

<P style="FONT-SIZE: medium" align="center">Select The College:-

 30

<select id=select2 style="LEFT: 182px; WIDTH: 161px; TOP: 136px" name

="collagename">
<%

if(selectedname.equals("Collage Addmission"))
{
pst=con.prepareStatement("select * from collage_det where univid='"+univerid+"'");
rs1=pst.executeQuery();
while(rs1.next())
{
collageid=rs1.getString(1);
//colname=rs1.getString(3);
out.println("oooo"+colname);
//request.setAttribute("collagename",new String(colname));
//session.setAttribute("cid",new String(collageid));
System.out.println("Collage Id"+collageid);
//System.out.println("CollageName"+rs1.getString(2));
%>
<option><%=rs1.getString(3)%></option>
<!--<option selected><%= colname %></option>-->
<%
//request.setAttribute("collagename",new String(colname));
//session.setAttribute("cid",new String(collageid));
}

}
else
{
response.sendRedirect("results.html");
}
rs1.close();
pst.close();
con.close();
 31

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

%>
</select>
<p
align="center">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;<input type="submit" name="Submit" value="Submit"
tabindex="9">

</form>
</body>
</html>
 32

9.2 SCREEN SHOTS

This form used to shows Home page.

Figure 9.1 Home page

 33

This form used to enters admin login details

Figure 9.2 Admin Login Page

 34

This form used to Shows admin home page

Figure 9.3 admin home page

 35

This form is used to show menu items

Figure 9.4 Menu Items

 36

This form is used to enter all the details about university

Figure 9.5 University Details

 37

This form used to enter college details

Figure 9.6 College Details Form

 38

This form used to enter course details

Figure 9.7 Course Details form

 39

This form used to enter the data into Rental table

Figure 9.8 Retail form

 40

This form used to delete house details.

Figure 9.9 House details Deleting Form

 41

This form used to enter the Real Estate Information.

Figure 9.10 Real Estate form

 42

This form used to delete real estate details.

Figure 9.11 Deleting Real Estate form

 43

This form used to enter the jobs details.

Figure 9.12 Job Details Form

 44

This form used to show job details.

Figure 9.13 View Job Details

 45

CHAPTER 10

REFERENCES

Reference Books
1. Deitel and Nieto ,Internet and World Wide Web – how to program.
2. Ian Somerville, Principles of Software Engineering, 4 Edition .
3. Roger S. Pressman, Software Engineering – A Practitioner’s Approach.
4. IEEE, IEEE Software Standards, IEEE Press, 1999.
5. Patrick Naughton and Herbert Schildt , Complete Reference –Java 2 ,
3 Edition,Tata McGraw – Hill ,1999.
6. Er. V.K.Jain , Programming Java Server Pages & Servlets.

Online References
1. http://www.ebook3000.com/Java-2--The-Complete-Reference--Fifth-
Edition_21908.html.
2. http://www.ebook3000.com/Java-The-Complete-Reference--Seventh-
Edition_124995.html.
3. http://books.google.co.in/books/about/Java_The_Complete_Reference_Seven
th_Edit.html.