Project Post and Sale Report

Post &Sale
Online Classified
Kuldeep Singh
Acknowledgement
I special thanks to the Almighty God who protected me until now and from whom
Wisdom and knowledge comes. . I heartedly give greatly thanks to the College of
Computer Science And Information Technology in Teerthanker Mahaveer
University for their uncountable support during those years. I would also like to
thanks Faculty Mr. Sachin Singh & Mr. Rajeev Kumar
for his guidance and support during my project research.Special thanks also to my
parents, friends that have been so close during our studies.I give special thanks
to my classmates who we have collaborated with since westarted College of
Computer Science And Information Technology in Teerthanker Mahaveer
University.I Say special Thanks to Mr.Afzal Khan
an to Support me develop this software , lastly I kindly express my gratitude to all
my classmates and colleagues for their partnership.
Submitted by:- Kuldeep Singh
Page 2
Certificate
This is to certify that the project work entitled

Post & Sale
is a record of the original work done by
Mr. Kuldeep Singh
Enrollment Number:
TCA 1006010
in partial fulfillment of the requirements for the award of College of
Computer Science and Information Technology in Teerthanker
Mahaveer University, during the academic year 2014-15.
Signature :
Mr. /Miss/
Faculty
Mr. Sachin Singh
MR. Rajeev Kumar
Page 3
Abstract
The aim of this project was to design and create a computer program that
gives easy interaction to the online classifieds portal. This site allows the user to
view different classifieds, send query for particular classified and get response for
it. And it allows advertiser to upload and manage their classifieds, get queries of
user and send them response.
The site is simple, user friendly and secured. The solution is designed to
implement several database management techniques and was primarily evaluated
by its ability to transfer data speedily, maintaining secure transaction and easy
interaction. The final result is a PHP program, which provides facilities at an
instance.
It has many technical elements and the rules are fairly simple. This
simplicity makes it a good choice for learning a new program environment. It
covers a range of areas (data modeling, some coding challenges, user interface, etc)
but none too difficult.
Page 4
Table of Contents
S.no
Topic
Page no.
i
Ii
Cover Page
Acknowledgement
iii
Certificate
Iv
Abstract
Introduction
1.1
Project Profile
1.2
Project Introduction
Feasibility study
10
2.1
Introduction of existing system
12
2.2
Problem of existing system
14
2.3
Feasibility report
16
2.4
Life cycle model
17
2.5
Effort distribution
18
2.6
Work breakdown structure
19
Software requirement system
20
3.1
Requirement specification
21
3.2
Hardware and software requirements
24
3.3
Introduction of Php
25
3.4
Introduction of Mysql
27
3.5
Introduction of HTML
29
3.6
Introduction of css
30
Design
32
4.1
ER diagram
33
4.2
Data flow diagram
35
4.3
Module
40
Page 5
4.4
Database
42
4.5
Screen shot
44
Testing
57
Limitation of future scope
66
6.1
System Limitation
67
6.2
Future scope
68
Conclusion
69
Refrence
71
Page 6
1.1 Project Profile

1.2 Project Introduction
Page 7
1.1 Project Profile
Project Title:
Post & Sale
Front-end tool:
PHP(Net beans 8.0.1)
Back-end tool:
Mysql
Project category:
Internet Based
Project guide:
Mr. Sachin Singh

Mr. Rajeev Kumar
Team Size:
Project Duration:
3 months.
Submitted by:
Kuldeep Singh
Afzal Khan
Submitted to:
Mr. Sachin Singh & Mr. Rajeev Kumar
Page 8
1.2 Project Introduction

In todays modern, sophisticated and fast world, online classifieds have
become a medium of communication among the internet users. On one end it is
informative and on the other end it is convenient and cost effective. Online
classifieds are most effective and proved market winner in current vast
competitive business era. No one can ignore such a powerful medium in totally
changed market environment.
Online Classified Portal is available
marketplace, which gives following benefits:
to
serve
as
your
online
Online Classifieds offer simple solutions to your classified

advertising needs.
Promote your product, company or service to a vast audience
Build consideration, awareness, and buyer response
Customize ads to fit individual or company needs
Convenient and easy to use
Online
classified
portal
site
provides
classifieds/ads. It also allow user to upload their ads.
different
categorized
Online classified portal allows two types of registration:

1. User registration
User can get own account id to interact with advertiser.
2. Advertiser registration
User can register them selves as advertiser who can upload
ads
There are four major section of online classified portal.
Guest section
User section
Advertiser section
Admin section
Page 9
Guest section:
In this section, guest user can view categorized classifieds/ads.
Register themselves as a user or advertiser.
Guest user can search a particular classifieds.
Guest user can view company information, contact detail and can also
give suggestion/feedback about site or classifieds.
User Section:
In this section, user can view categorized classifieds/ads and also able
to save the particular ads.
User can send a query request for particular classified/ad and get
response from advertiser for that query.
User can also search particular classifieds/ads.
User can also update their personal profile and password.
User can also give a feedback for the site or classified.
Advertiser Section:
In this section advertiser can purchase scheme to upload their
classifieds/ads.
Advertiser can upload and manage different classifieds in particular
scheme.
Advertiser can receive query from user and able to give response too.
Advertiser also able to view his/her scheme ledger that contains
information like:
How many schemes are there
How many classifieds/ads are uploaded in particular scheme
Scheme status (i.e. running, expired or inactive) and
sufficient balance, etc.
Admin Section:
Admin can manage different database entries.
Admin can view the information related registered users, advertisers
with their scheme details and their feedback.
Admin can also upload/update ads.
Admin can approve scheme activation and ad activation request of the
advertiser.
Page 10
2.1 Introduction of existing system

2.2 Problem of existing System
2.3 Feasibility Report
2.4 Life cycle Model
2.5 Effort Distribution
2.6 Work breakdown Structure
Page 11
2.1 Introduction of existing system
Heni
refrigeration is the name of service center, which provides free

services for the chilling products due to their warranty period.
Heni
refrigeration center is an authorized center which takes service

contract from different dealers. In this service center they work manually.
Working
Dealer provides list of customers who purchase product on

previous day & also provides the copy of customers bill to
the administrator of service center.
After receiving new customers list, service center is
responsible for installation of product to make it in working
condition.
Service center charges to the dealer for product installation
& the number of service offers during warranty period. Full
payment is received at time of installation from dealer.
Whenever need arise, customer can make a call to the
service center & register their complain.
Management staff
They attend customers call & register their complain & give
them complain number.
On the starting of the day they prepare list of new
complains, pending complains & product installation.
During the day if they receive an emergency call then they
pass it to a particular engineer.
Workload is distributed to different engineers according to
list prepared.
Engineer
After receiving work list, an engineer collects all the repairing

parts that are required for the service.
At the end of the day, engineer has to submit the slip which
contain information about problem arise (e.g. what kind of
problem is arise, which parts are used to solve the problem,
Page 12
status of job i.e. done/pending, sign of customer) for all

given services.
General staff
They keep record of repairing parts. (i.e. who has which

parts & how many)
Maintain stock information. They are responsible for ordering
new parts by checking minimum level & maximum level of
particular parts.
If order receive is not appropriate then they are responsible
for return back & reorder.
Payroll
Management staff & general staff get monthly salary.

Engineer gets salary +(incentive*No. of extra service).
Page 13
2.2 Problem of existing system

Time consuming
In manual system every process like call booking, work
allotment, stock of parts, calculations etc. are done by human entity. So it
would take more time for each process, to do this work daily & also
calculate monthly payroll is difficult & time consuming. So manual system
is not desirable.
Lost of data
In manual system all calls are book on paper means manually &
stock are also maintained by Stock register. If some papers are lost then
it is hard to recollect it. So the documents are more important for service
center.
Tedious
Manual system would take a lot time, concentration & more
paper work. Thus manual system becomes boring.
Expensive
In service center, single person cannot handle all accounts, it
requires more people. So their salary expenses are higher & other
different miscellaneous expenses are also there.
Laborious
In service center many services or call take place. In manual
system whole process is handled by all the staff members & they have a
lot of paper work. Manual system takes a long time & the workload is also
very high.
Manpower used
To do any work manpower is used for e.g. attend the call, work
allotment, stock maintaining. In all case manpower is used & time is also
consumed because man is not as speedier as computer.
Page 14
Less secure
As we know that whole system is based on paper work. So any
unauthorized person may show the important details of the service
center. So it is possible to lack the important information. So manual
system is not secure.
Calculation error
In service centre there is a possibility to arise calculation errors
such as counting of amc-amount (i.e. charged to dealer), salary, repairing
parts quantity, etc.
Lack of instant information
It is very difficult to get information about particular things on a
particular day.
Difficult to generate different types of report
Report generation is the major problem of the service center.
Because it is very difficult to generate timely report. (Means one cannot
able to see any report with minimal efforts, on particular time)
Page 15
2.3 Feasibility Study

Feasibility study plays very important role in the development of any
system, but when it is the case of development of any software then its
importance increases much more because in the case one should be very clear
about availability of the time and resources. Before starting the development of
the software one should give considerable amount of time for feasibility study
because the successful completion of project depends upon feasibility.
The feasibility of our project has been judged on the basis of time,
technology, resources available and project length.
Time:
This project takes at least 2 month to be completed if we take help of
reused components otherwise it will take 3 months to be completed.
We will not make use of components and therefore will be able to
complete the project in 3 months. Thus according to time the feasibility is not
that right.
Technology:
The necessary technology, viz., front-end development tool, back-end
database technology and various other tools namely installation tools, etc.
for developing the system, are already available within the organization. So
this problem is feasible.
Resources:
We need good knowledge software engineers and practitioners. We
need Net connection.
We have all the resources in the desired amount.
Project Size:
The Project size might be above 15000 LOC. This is just the rough
assumption because we dont have any basis of the past projects.
Thus the project overall feasibility is normal and therefore we have
undertaken this project.
Page 16
2.4 Life Cycle Model
The Online Classified Portal project requires frequent user interaction.

For that reason, our first choice included the Prototype model. However, we had
doubts about the prototype model, and therefore we concluded to use the Spiral
Model. The risk-based approach of the Spiral Model is significant to the
development of this prototype, and it would also help select an established
lifecycle model or determine a different model constructed from various phases
of other lifecycle models. After regular reviews, we decided that the best
approach was to use a hybrid model that would implement the risk management
of the spiral model along with the incremental model, which is a mixture of the
prototype model and the linear sequential model. Currently, the project revolves
around two established stages: Requirement Analysis and Prototype
Development. Above figure shows the life cycle for the development process as
well as entry and exit criteria for the different phases of the project.
Page 17
2.5 Effort Distribution
Project Planning:
2 to 3 %
Requirement Analysis:
10 to 25 %
Design:
20 to 25 %
Coding:
15 to 20 %
Testing / Debugging:
30 to 40 %
Page 18
2.6 Work Breakdown Structure
It is divided in to five main parts:
1. Scope & Planning:

In this particular phase of the project we have explained the problem definition
along with its requirements in detail. All the research work and background study prior the
project initialization has been conducted in this phase. The work breakdown structure and
scheduling chart is prepared after conducting the feasibility study and risk analysis.
2. Requirement Analysis:
Here we have tried to gather all the requirements pertaining program code, user
interface and database design. The detailed flow of data in the system is depicted. We have
shown the relationships between the entities of data through entities relationship diagrams.
This particular phase leads milestone SOFTWARE REQUIREMENT SPECIFICATION.
3. User Interface Designing:

Depending on the inputs and outputs of the system i.e. the interaction between the
user and the system we have designed the interface. We have made it simple and attractive
which makes it more users friendly.
4. Implementation and Testing:

Depending upon the requirement specified in scope, we have implemented the
system using latest ASP.Net technology.
5. Other Peripheral Activities For Quality Assurance:
Continuously meetings were held for project tracking and analyzing the higher
risks. Their degree of rigor was always tested and properly documented. These activities
were conducted considering our budget constraints and required accuracy. It helped us to be
focused and built a quality product.
Page 19
3.1 Requirements specification

3.2 Hardware And software Requirements
3.3 Introduction of PHP
3.4 Introduction of Mysql
3.5 Introduction of HTML
3.6 Introduction of CSS
Page 20
3.1 Software specification

Requirement analysis is a software engineering task that bridges the gap between
system level software analysis and software design.
Requirement analysis enables the system engineer to specify software function and
performance indicate s/w interface with other system elements and establish
constraints that software must meet. Requirements analysis allows the software
engineer to refine the software allocation and build modules of the data, function
and behavior domain that will be treated by software.
Requirement specification provides the description to the developer and the
customer with the mean to access quality rule.
There are four basic elements in system requirements analysis:
Output
The main requirement of my customer was a user friendly online cloth products
advertisement portal where he can put his products at one place along with
each product description. So that customer can view his added products and
buy online. He also wanted that timely notifications should be sent to him when
a particular customer purchases his added products
Input
Once we know the output, we can easily determine when the inputs should be
sometimes, it may happen that the required information may not be readily
available in the proper form. This may be because of the existing terms we are not
properly designed. Input to the project is product description so that necessary
output in required format is achieved. In product description product price,
quantity, images etc needs to be added.
Accuracy
If the data is not accurate the output will be also not be correct. If product quantity
is not accurate then user may not able to buy the product.
Timeliness
Page 21
If data is not obtained in time, the entire system is considered to be a bad system.
SYSTEM ANALYSIS
1. All user requirements were found feasible instead message alerts on owners
cell phone requirement because product was needed within 10 days so this
requirement cant be met in required time frame. It will be added in future.
2. Searching of Product according to price and color will be added in future.
3. Product listing will be done
4. Necessary email notifications will be sent on owners email id when user wants
to see latest design of products.
SYSTEM DESIGN
The design phase focuses on the detailed implementation for the system
recommendation in the feasibility study. The design phase is a translation from a
program-oriented-document to user-oriented-document. The design activity begins
when the required document for the software to be developed is available. This may
be SRS for the complete system, in case of waterfall model is being followed or the
requirement for the next iteration, if the iterative enhancement is being followed or
the requirement for the prototype if the prototyping is being followed. Design is
essentially the bridge between requirement specification and the final solution for
satisfying the requirements. The term design is used in two ways, when used as a
verb it represents the process the designing while it represents the result of design
process. The goal of design process is to produce some order, which can be later
used to build that system. The produced model is called the design of the system.
The design of the system is essentially a blueprint or a plan for solution for the
system. Here we consider a system to be asset of components which clearly defines
the behavior that interacts with each other in a fixed define manner. A component
of a system can be considered as a system with its own components. In a software
system a component is a software module.
Page 22
The design process for software system has two levels, Top level and logical design.
In top level, it is indicated that how the modules should be integrated. Logical
design expands the system design to contain more detailed description of
processing logic and data structures.
Design is essentially the bridge between requirement specification and the final
solution for satisfying the requirements. The term design is used in two ways,
when used as a verb it represents the process the designing while it represents the
result of design process.
The goal of design process is to produce some order, which can be later used to
build that system. The produced model is called the design of the system. The
design of the system is essentially a blueprint or a plan for solution for the system.
Here we consider a system to be asset of components which clearly defines the
behavior that interacts with each other in a fixed define manner. A component of a
system can be considered as a system with its own components. In a software
system a component is a software module.
MODULAR DESCRIPTION
Administrator: The administrator is most powerful part. All rights are in hand of
administrator.
Administrator
can
add
different
categories,
subcategories,
Subcategories type, Add Products, Purchasing, Issuing. He is the only one who can
adding entries to the database. Without admin permission, nothing can be changed.
Categories: The whole picture revolves around the categories. The categories
includes the Ladies, Gents, Others and party wear. Further the categories are
divided into sub categories like different locations from where products are
purchased all such are the sub categories. To start with anything on the site, the
user has to first select some category and the selection of the category is controlled
by the session. User have to login to purchase the products.
User: Users can view the products, If he/she is interested to purchase the product
firstly he/she need to login in if he/she already registered then start shopping
otherwise he/she have to create account.
Page 23
3.2 Hardware and Software Requirements
Hardware specification of machine used
Intel Pentium 4 2.4GHZ

20 GB HDD
128 MB RAM
Software used along with the versions
Operating System: Windows XP

Front-end tool: NetBeans
(HTML,CSS,VBSCRIPT,JAVASCRIPT)
Back-end tool: Mysql

Server:Apache
Others tools: Photoshop, macromedia Dreamweaver ,Paint
Page 24
3.3 Introduction of PHP
PHP is a powerful language and the interpreter, whether included in a web server as
a module or executed as a separate CGI binary, is able to access files, execute
commands and open network connections on the server. These properties make
anything run on a web server insecure by default. PHP is designed specifically to be
a more secure language for writing CGI programs than Perl or C, and with correct
selection of compile-time and runtime configuration options, and proper coding
practices, it can give you exactly the combination of freedom and security you
need.
As there are many different ways of utilizing PHP, there are many configuration
options controlling its behavior. A large selection of options guarantees you can use
PHP for a lot of purposes, but it also means there are combinations of these options
and server configurations that result in an insecure setup.
The configuration flexibility of PHP is equally rivaled by the code flexibility. PHP can
be used to build complete server applications, with all the power of a shell user, or
it can be used for simple server-side includes with little risk in a tightly controlled
environment. How you build that environment, and how secure it is, is largely up to
the PHP developer.
This chapter starts with some general security advice, explains the different
configuration option combinations and the situations they can be safely used, and
describes different considerations in coding for different levels of security.
Page 25
Common uses of PHP:

PHP performs system functions, i.e. from files on a system it can create,
open, read, write, and close them.
PHP can handle forms, i.e. gather data from files, save data to a file, thru
email you can send data, return data to the user.
You add, delete, and modify elements within your database through PHP.
Access cookies variables and set cookies.
Using PHP, you can restrict users to access some pages of your website.
Page 26
3.4 Introduction of Mysql

Microsoft SQL Server is a full-featured relational database management system
(RDBMS) that offers a variety of administrative tools to ease the burdens of database
development, maintenance and administration. In this article, we'll cover six of the
more frequently used tools: Enterprise Manager, Query Analyzer, SQL Profiler, Service
Manager, Data Transformation Services and Books Online.
Enterprise Manager: It is the main administrative console for SQL Server
installations. It provides you with a graphical "birds-eye" view of all of the SQL
Server installations on your network. You can perform high-level administrative
functions that affect one or more servers, schedule common maintenance tasks or
create and modify the structure of individual databases.
Query Analyzer: It offers a quick and dirty method for performing queries against
any of your SQL Server databases. It's a great way to quickly pull information out
of a database in response to a user request, test queries before implementing them
in other applications, create/modify stored procedures and execute administrative
tasks.
SQL Profiler: It provides a window into the inner workings of your database. You
can monitor many different event types and observe database performance in real
time. SQL Profiler allows you to capture and replay system "traces" that log various
activities. It's a great tool for optimizing databases with performance issues or
troubleshooting particular problems.
Service Manager: It is used to control the MSSQLServer (the main SQL Server
process),
MSDTC
(Microsoft
Distributed
Transaction
Coordinator)
and
SQLServerAgent processes. An icon for this service normally resides in the system
tray of machines running SQL Server. You can use Service Manager to start, stop or
pause any one of these services.
Page 27
Data Transformation Services (DTS): provide an extremely flexible method for

importing and exporting data between a Microsoft SQL Server installation and a
large variety of other formats. The most commonly used DTS application is the
"Import and Export Data" wizard found in the SQL Server program group.
Books Online: is an often overlooked resource provided with SQL Server that
contains answers to a variety of administrative, development and installation
issues. It's a great resource to consult before turning to the Internet or technical
support.
Page 28
3.5 Introduction of HTML
HTML stands for Hyper Text Markup Language
HTML is not a programming language, it is a markup language
A markup language is a set of markup tags
HTML uses markup tags to describe web pages
HTML markup tags are usually called HTML tags
HTML tags are keywords surrounded by angle brackets like <html>
HTML tags normally come in pairs like <b> and </b>
The first tag in a pair is the start tag, the second tag is the end tag
Start and end tags are also called opening tags and closing tags.
HTML Documents
a) HTML documents describe web pages
b) HTML documents contain HTML tags and plain text
c) HTML documents are also called web pages
The purpose of a web browser (like Internet Explorer or Firefox) is to read HTML
documents and display them as web pages. The browser does not display the HTML
tags, but uses the tags to interpret the content of the page.
Page 29
3.6 Introduction of CSS

A few words about CSS:
CSS stands for Cascading Style Sheets
Styles define how to display HTML elements
Styles are normally stored in Style Sheets
Styles were added to HTML 4.0 to solve a problem
External Style Sheets can save you a lot of work
External Style Sheets are stored in CSS files
Multiple style definitions will cascade into one
CSS provides means to customize inbuilt HTML tags

HTML tags were originally designed to define the content of a document. They were
supposed to say "This is a header", "This is a paragraph", "This is a table", by using
tags like <h1>, <p>, <table>, and so on. The layout of the document was
supposed to be taken care of by the browser, without using any formatting tags.
As the two major browsers - Netscape and Internet Explorer - continued to add new
HTML tags and attributes (like the <font> tag and the color attribute) to the
original HTML specification, it became more and more difficult to create Web sites
where the content of HTML documents was clearly separated from the document's
presentation layout.
To solve this problem, the World Wide Web Consortium (W3C) - the nonprofit,
standard setting consortium, responsible for standardizing HTML - created STYLES
in addition to HTML 4.0.
Multiple Styles Will Cascade into One
Style sheets allow style information to be specified in many ways. Styles can be
specified inside a single HTML element, inside the <head> element of an HTML
page, or in an external CSS file. Even multiple external style sheets can be
referenced inside a single HTML document.
Page 30
Generally speaking we can say that all the styles will "cascade" into a new "virtual"
style sheet by the following rules, where number four has the highest priority:
Browser default
External style sheet
Internal style sheet (inside the <head> tag)
Inline style (inside an HTML element)
So, an inline style (inside an HTML element) has the highest priority, which means
that it will override a style declared inside the <head> tag, in an external style
sheet, or in a browser (a default value).
Page 31
4.1 ER Diagram
4.2 Data flow Diagram
4.3 Module
4.4 Database
4.5 Screen Shot
Page 32
4.1 ER Diagram
Data Flow Diagramming is a means of representing a system at any level of
detail with a graphic network of symbols showing data flows, data stores, data
processes, and data sources/destination.
The data flow diagram is analogous to a road map. It is a network model
of all possibilities with different detail shown on different hierarchical levels. This
processes of representing different details level is called leveling or partitioning
by some data flow diagram advocates. Like a road map, there is no starting point or
stop point, no time or timing, or steps to get somewhere. We just know that the
data path must exist because at some point it will be needed. A road map shows all
existing or planned roads because the road is needed.
Details that is not shown on the different levels of the data flow diagram
such as volumes, timing, frequency, etc. is shown on supplementary diagrams or in
the data dictionary. For example, data store contents may be shown in the data
dictionary.
Data Flow Diagram (DFD) uses a number of symbols to represent the
systems. Data Flow Diagram also known as Bubble Chart is used to clarify system
requirements and identifying the major transformations that will become programs
in system design. So it is the starting point of the design phase that functionally
decomposes the requirements specifications down to the level of details.
Page 33
Page 34
4.2 Data flow Diagram

Data Flow Diagramming is a means of representing a system at any level of detail
with a graphic network of symbols showing data flows, data stores, data processes,
and data sources/destination.
The data flow diagram is analogous to a road map. It is a network model
of all possibilities with different detail shown on different hierarchical levels. This
processes of representing different details level is called leveling or partitioning
by some data flow diagram advocates. Like a road map, there is no starting point or
stop point, no time or timing, or steps to get somewhere. We just know that the
data path must exist because at some point it will be needed. A road map shows all
existing or planned roads because the road is needed.
Details that is not shown on the different levels of the data flow diagram
such as volumes, timing, frequency, etc. is shown on supplementary diagrams or in
the data dictionary. For example, data store contents may be shown in the data
dictionary.
Data Flow Diagram (DFD) uses a number of symbols to represent the
systems. Data Flow Diagram also known as Bubble Chart is used to clarify system
requirements and identifying the major transformations that will become programs
in system design. So it is the starting point of the design phase that functionally
decomposes the requirements specifications down to the level of details.
Page 35
Terms used in DFD
Process
A process transforms data values. The lowest level processes are pure
functions without side effects. An entire data flow graphics high level process.
Graphical representation:
Graphical Representation:
Data flows
A data flow connects the output of an object or process to input of another
object or process. It represents the intermediate data value within a computation.

It is represented by an arrow and labeled with a description of data, usually its
name or type.
Actors
An actor is active object that drives the data flow graph by producing or
consuming values.
Page 36
Data store
A data store is a passive object with in a data flow diagram that stores data
for later access.

External Entity
A rectangle represents an external entity such as a librarian ,a library
member.
OutPut Symbol
This box represented data production during human computer interaction
Page 37
Context Level DFD for
ClassifiedsOnline
Page 38
LEVEL1 DFD for
ClassifiedsOnline
Page 39
4.3 Module
1. Search Ads:
Through this module Viewer can view ads, can also send
response to particular poster.
2. Yellow Pages:
3. Login :
Through this module works as yellow pages. Provide

contact details about various companies, institutes, banks
etc.
In this module Poster enter the User id and password is

checked and only valid user id and password will get
entry into members zone. This is a security feature to
avoid entry of unauthorized users.
4. Registration Process:
Through this module new posters can registered them.
After giving their details, they will get a user id and
password. Then to get entry into poster section they need
to provide this id and password and only poster with valid
id and password will get entry into poster zone. This is
also a security feature to avoid entry of unauthorized
user.
5. Poster
:
Through this module a poster can post a new ad, update
ad details. He can update including user name and
password and search and shortlist the Viewers, check the
status of advertisements response. He can reply to the
viewers In short this module deals with the whole
advertisement process.
6. Administrator:
This is the Administrators module by which he keep the
eye on whole site and maintain and upgrade the sites
Page 40
service for sake of users. Administrator can show banner

ads of others, which help the site in revenue.
7. Log Out:
To provide functionality to logout your id and return to
home page.
8. Write Mail:
You can write any mail and also attach any
image and send to your destinations.
document or
9. Mail Inbox:
You can check your mail also and attach the important
files with your mail box.
10. Help:
Provide the functionality to get help about the online
reminder.
Page 41
4.4 Database
Freead:
S.No.
1.
Field Name
Id
Data Type
Integer
Description
Unique ID
2.
Cat_id
Integer
Category ID
3.
Ad_title
Varchar
Title of adv.
4.
Photo_name
Varchar
Name of photo
5.
Description
Text
Description of adv.
6.
Price
Integer
Expected Price
7.
Contact_name
Varchar
Name of contact
8.
Email
Varchar
Email of contact
9.
m_number
Integer
Mobile no. of contact
10.
Address
Text
Address of contact
Field Name
Id
Title
Visible
Extension
Data Type
Integer
Verchar
Tinyint
varchar
Description
Unique id
Title of heading
Visible of heading
Extension of heading
Data Type
Int
Int
Varchar
Int
Description
Unique id
Id of sub heading
Title of sub heading
Position of sub heading
Heading:
S.No.
1.
2.
3.
4.
Sub_heading:
S.No.
1.
2.
3.
4.
Field Name
Id
Sub_id
Sub_title
Position
Page 42
User:
S.No.
1.
2.
3.
4.
5.
6.
Field Name
Id
F_Name
L_Name
U_email
U_hash
Username
Data Type
Integer
Varchar
Varchar
Varchar
Varchar
Varchar
Description
Unique id
First name of user
Second name of user
Email of user
Encrypted password of user
Username of user
Data Type
Integer
Integer
Varchar
Varchar
Text
Integaer
Varchar
Varchar
Varchar
Varchar
Varchar
Description
Unique id of user adv.
Category id of user adv.
Title of user adv.
Photo name of adv.
Description of adv.
Expected price
Contact name of user
Email of user
Mobile number of user
Address of user
User name of user
userad:
S.No.
1.
2.
3.
4.
5.
7.
8.
9.
10.
11.
12.
Field Name
Id
Cat_id
Ad_title
Photo_name
Description
Price
Contact_name
Email
M_number
Address
U_name
Page 43
4.5 Screen Shot

HOMEPAGE
Page 44
lOGIN
Page 45
Signup
Page 46
Registration Success full
Page 47
User Login
Page 48
User edit post
Page 49
Ad of your choice
Page 50
Post an add
Page 51
Contact us
Page 52
Site Map
Page 53
Page 54
SYSTEM TESTING
Here the System testing involved is the most widely used testing process
consisting of five stages as shown in the figure. In general, the sequence of testing
activities is component testing, integration testing, and then user testing.
However, as defects are discovered at any one stage, they require program
modifications to correct them and this may require other stages in the testing
process to be repeated.
Testing is the process of detecting errors. Testing performs a very critical role
for quality assurance and for ensuring the reliability of the software. The results of
testing are used later on during maintenance also.
Page 55
Testing is vital to the success of the system. System testing makes a logical
assumption that if the parts of the system are correct, the goal will be successfully
achieved. In adequate testing or non-testing leads to errors that may not appear
until months or even years later (Remember the New York three day power failure
due to a misplaced Break statement).
This creates two problems:

1.
The time lag between the cause and the appearance of the problem.
2.
The time interval effect of the system errors on files and the records on the
system.
A small error can conceivably explode into a much larger problem. Effective testing
early in the process translates directly into long term cost savings from a reduced
number of errors.
Another reason for system testing is its utility as a user oriented vehicle before
implementation. The best program is worthless if it does not meet the user
requirements. Unfortunately, the users demands are often compromised by efforts
to facilitate program or design efficiency in terms of processing time or design
efficiency.
Thus in this phase we went to test the code we wrote. We needed to know if the
code compiled with the design or not? Whether the code gave the desired outputs
on given inputs? Whether it was ready to be installed on the users computer or
some more modifications were needed?
Page 56
Through the web applications are characteristically different from there software
counterparts but the basic approach for testing these web applications is quite
similar. These basic steps of testing have been picked from software engineering
practices. The following are the steps, we undertook:
1. The content of the Intranet site is reviewed to uncover Content

Errors. Content Errors covers the typographical errors, grammatical errors,
errors in content consistency, graphical representation and cross referencing
errors
2. The design model of the web application is reviewed to uncover the

navigation errors. Use cases, derived as a part of the analysis activity allows
a web designer to exercise each usage scenario against the architectural and
navigational design. In essence these non-executable tests help to uncover
the errors in navigation.
3. When web applications are considered the concept of unit changes. Each web
page
encapsulate
content
navigation
links,
content
and
processing
elements(Forms, Scripts, JSPs as in our case). It is not always possible to

test each of these individually. Thus is the base of the web applications the
unit to be considered is the web page. Unlike the testing of the algorithmic
details of a module the data that flows across the module interface, page
level testing for web applications is driven by content, processing and links
encapsulating the web page.
Page 57
4. The Assembled web application
is tested for overall functionality and
content delivery. the various user cases are used that test the system for
errors and mistakes.
5. The Web application is tested for a variety of environmental settings and is

tested for various configurations and upon various platforms.
The modules are integrated and integration test are conducted.
6. Thread based testing is done to monitor the regression tests so that the site
does not become very slow is a lot of users are simultaneously logged on.
7. A controlled and monitored population of end users tests Intranet application

, this all comprises of the User Acceptance Testing .
Because web application evolve continuously , the testing process is an

ongoing activity, conducted by web support staff in our case the Organizations
IS people who will finally update and manage the application.
PSYCHOLOGY OF TESTING
The aim of testing is often to demonstrate that a program works by showing

that it has no errors. The basic purpose of testing phase is to detect the errors that
may be present in the program. Hence one should not start testing with the intent
of showing that a program works, but the intent should be to show that a program
doesnt work. Testing is the process of executing a program with the intent of
finding errors.
Page 58
TESTING OBJECTIVES:
The main objective of testing is to uncover a host of errors, systematically

and with minimum effort and time. Stating formally, we can say,
Testing is a process of executing a program with the intent of finding an

error.
A successful test is one that uncovers an as yet undiscovered error.
A good test case is one that has a high probability of finding error, if it
exists.
The tests are inadequate to detect possibly present errors.
The software more or less confirms to the quality and reliable standards.
LEVELS OF TESTING
In order to uncover the errors present in different phases, we have the

concept of levels of testing. The basic levels of testing are
Page 59
Unit testing
Unit testing focuses verification effort on the smallest unit of software i.e. the
module. Using the detailed design and the process specifications, testing is done to
uncover errors within the boundary of the module. All modules must be successful
in the unit test before the start of the integration testing begins.
In this project each service can be thought of a module. There are so many
modules like Login, HR Department, Interviewer Section, etc. Each module has
been tested by giving different sets of inputs. When developing the module as well
as finishing the development, the module works without any error. The inputs are
validated when accepting them from the user.
Integration Testing
After unit testing, we have to perform integration testing. The goal here is to
see if modules can be integrated properly, the emphasis being on testing interfaces
Page 60
between modules. This testing activity can be considered as testing the design and
hence the emphasis on testing module interactions.
In this project the main system is formed by integrating all the modules.
When integrating all the modules I have checked whether the integration effects
working of any of the services by giving different combinations of inputs with which
the two services run perfectly before Integration.
SYSTEM TESTING
Here the entire software system is tested. The reference document for this
process is the requirements document, and the goal is to see if software meets its
requirements.
Here entire HRRP has been tested against requirements of project and it is
checked whether all requirements of project have been satisfied or not.
ACCEPTANCE TESTING
Acceptance Testing is performed with realistic data of the client to

demonstrate that the software is working satisfactorily. Testing here is focused on
external behavior of the system; the internal logic of program is not emphasized.
Test cases should be selected so that the largest number of attributes of an

equivalence class is exercised at once. The testing phase is an important part of
software development. It is the process of finding errors and missing operations
Page 61
and also a complete verification to determine whether the objectives are met and
the user requirements are satisfied.
WHITE BOX TESTING
This is a unit testing method, where a unit will be taken at a time and tested
thoroughly at a statement level to find the maximum possible errors.
I tested step wise every piece of code, taking care that every statement in
the code is executed at least once. The white box testing is also called Glass Box
Testing.
I have generated a list of test cases, sample data, which is used to check all
possible combinations of execution paths through the code at every module level.
White-box test focuses on the program control structure. Test cases are
derived to ensure that all statement in the program control structure. Test cases
are derived to ensure that all statement in the program control structure. Test
cases are derived to ensure that all statement in the program has been executed at
least once during testing and that all logical conditions have been exercised. Basis
path testing, a white box technique, makes use of program graphs (or graph
matrices) to derive the set of linearly independent test that will ensure coverage.
Condition and data flow testing further exercising degrees of complexity.
Page 62
BLACK BOX TESTING

This testing method considers a module as a single unit and checks the unit
at interface and communication with other modules rather getting into details at
statement level. Here the module will be treated as a block that will take some
input and generate output. Output for a given set of input combinations are
forwarded to other modules.
Black-box test are designed to uncover errors functional requirement without
regard to the internal workings of a program. Black-box testing techniques focus on
the information domain of the software, deriving test cases by partitioning the input
and output domain of a program in manner that provides through test coverage.
The black-box test is used to demonstrate that software functions are operational,
that input is properly produced, and that the integrity of external information are
maintained. A black-box test examines some fundamental aspect of a system with
little or no regard for the integral logical structure of the software.
Graph based testing methods explore the relationship between and behavior
of program objects. Equivalence partitioning divides the input classes of data are
likely to exercise specific software function. Boundary values analysis probes the
programs ability to handle data at the limits of acceptability.
TEST INFORMATION FLOW

A strategy for software testing may also be viewed in the context of the spiral. Unit
testing begins at the vortex of the spiral and, concentrates on each unit, component
of the software as implemented in source code. Testing progresses moving outward
along the spiral to integration testing, where the focus is on designed the
construction of the software architecture. Taking another turn outward on spiral, we
Page 63
encounter validation testing, where requirements established as part of software

requirements analysis are validated against the software that has been constructed.
Finally, we arrive at system testing, where the software and other system elements
are tested as a whole. To test computer software, we spiral out along stream lines
that broaden the scope of testing with each turn.
Considering the process from a procedural point of view, testing within the
context of software engineering is actually a series of four steps that are
implemented sequentially. The steps are shown in Figure. Initially, tests focus on
each component individually, ensuring that it functions properly as unit. Hence, the
name unit testing. Unit testing makes heavy use of white-box testing techniques,
exercising specific paths in modules control structure to ensure complete coverage
and maximum error detection.
Page 64
INFORMATION FLOW OF DATA FOR TESTING
Page 65
Page 66
6.1 System Limitations

Very hard to find out the legal information about the surfer.
Backup and recovery of data along with time is large and lengthy
process and hard to maintain.
Redundancy of data may occur in system when one or more surfers
are going to perform same task at same time.
It is very hard to keep track of every users information and verify the
personal information.
Page 67
6.2 Future scope

The system is highly flexible and any modules will be added in future as per
customer requirements.
Mobile version will be developed for the website so that it can be accessible
on cell phones also.
SMS alerts will be sent to owner when a user wants a product in future.
Page 68
Page 69
7.1 Conclusion
All feasible requirements of project are met.
Things that have been achieved are:
o Customer can view all the product details
o A customer can login if he already have registered and can buy
the product online.
o Customer can view the products and see the product details like
images and price.
o Only those products will be displayed on website that are allowed
by admin.
o Only admin can edit products details
o Customer can contact admin about product related problems.
Page 70
8.1 Bibliography
8.2 Webography
Page 71
8.1 Bibliography
Php Tutorial
Complete Refrence
Php and Mysql Development
Programming PHP(paperback)
Learning PHP,Mysql And Java script
Sql for Mysql Developers
The Web book
8.2 Webography
www.google.com
www.phptpoint.com
www.w3school.com
www.wix.com
www.htmldrive.net
Page 72

Project Post and Sale Report

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Project Post and Sale Report

Загружено:

Авторское право:

Доступные форматы

Post &Sale

Submitted by:- Kuldeep Singh

This is to certify that the project work entitled

Submitted by:- Kuldeep Singh

Submitted by:- Kuldeep Singh

Introduction of existing system

Problem of existing system

Life cycle model

Work breakdown structure

Software requirement system

Hardware and software requirements

Data flow diagram

Submitted by:- Kuldeep Singh

Limitation of future scope

Submitted by:- Kuldeep Singh

1.1 Project Profile

Submitted by:- Kuldeep Singh

1.1 Project Profile

Post & Sale

PHP(Net beans 8.0.1)

Mr. Sachin Singh

Submitted by:- Kuldeep Singh

Mr. Sachin Singh & Mr. Rajeev Kumar

1.2 Project Introduction

Online Classifieds offer simple solutions to your classified

Promote your product, company or service to a vast audience

Build consideration, awareness, and buyer response

Customize ads to fit individual or company needs

Convenient and easy to use

Online classified portal allows two types of registration:

Submitted by:- Kuldeep Singh

Submitted by:- Kuldeep Singh

2.1 Introduction of existing system

Submitted by:- Kuldeep Singh

2.1 Introduction of existing system

refrigeration is the name of service center, which provides free

refrigeration center is an authorized center which takes service

Dealer provides list of customers who purchase product on

After receiving work list, an engineer collects all the repairing

Submitted by:- Kuldeep Singh

status of job i.e. done/pending, sign of customer) for all

They keep record of repairing parts. (i.e. who has which

Management staff & general staff get monthly salary.

Submitted by:- Kuldeep Singh

2.2 Problem of existing system

Submitted by:- Kuldeep Singh

Submitted by:- Kuldeep Singh

2.3 Feasibility Study

Submitted by:- Kuldeep Singh

2.4 Life Cycle Model

The Online Classified Portal project requires frequent user interaction.

Submitted by:- Kuldeep Singh

2.5 Effort Distribution

Submitted by:- Kuldeep Singh

2.6 Work Breakdown Structure

It is divided in to five main parts:

1. Scope & Planning:

3. User Interface Designing:

4. Implementation and Testing:

Submitted by:- Kuldeep Singh

3.1 Requirements specification

Submitted by:- Kuldeep Singh