Classified Adds PDF

5/6/2019 classified_Adds - Google Docs
Development of a feature-rich, Classified Ads Portal Website

A Project Report for Industrial Training
Submitted by
Sk Asif Akram
Sk Ijaj Ahmed
Soumitra Maity
Anwoy Sengupta
Suman Mukherjee
in partial fulfillment for the award of the degree of
Btech
in
Computer Science
Narula Institute Of Technology
At
Ogma TechLab Pvt. Ltd.
https://docs.google.com/document/d/13o84N8HUMBORG3BnHjWI2b5D3biRqM4oxZm899eg6Sg/edit 1/52
Ogma TechLab Pvt. Ltd.

BONAFIDE CERTIFICATE
Certified that this project work was carried out under my supervision
“Development of a feature-rich, Classified Ads Portal Website” is the bonafide work

of
Name of the student:

Sk Asif Akram
Signature:
Name : Saumitra Das
PROJECT MENTOR
SIGNATURE
Ogma TechLab Original Seal
Acknowledgement
I take this opportunity to express my deep gratitude and sincerest thank to my project
mentor, SAUMITRA DAS for giving most valuable suggestion, helpful guidance and
encouragement in the execution of this project work.
I will like to give a special mention to my colleagues. Last but not the least I am grateful
to all the faculty
Table of Contents Page

No
1. Abstract
2. Introduc on and Objec ves of the Project
3. Project Category
(RDBMS/OOPS/Networking/Mul media/Ar ficial
Intelligence/Expert Systems etc.)
4. Tools/Pla orm, Hardware and So ware Requirement
specifica ons
5. Goals of Implementa on
6. SDLC Process Applied
7. Data Model
8. Func onal Requirements (Use Case Diagram)
9. Non-func onal Requirements
10.Feasibility Study
11.Project Planning
12.Project Scheduling
13.So ware Engineering Paradigm applied
Data Flow Diagram (DFD)
14.Database design
15.Tes ng
16.System Security measures (Implementa on of security for the
project developed)
17.Database/Data security
18.Crea on of User profiles and access rights
19.Cost Es ma on of the Project along with Cost Es ma on
Model
20.Coding and screenshots.
21.Future scope and further enhancement of the Project
22.Conclusion
23.Bibliography
1. Abstract:
The main aim of the applica on is to build a Home Shop website. The website has to provide
different kinds of facili es to the users like Car, Real estate, Mobile, Electronics. Now the
people are able to do search without was ng their precious me. This make searching
flexible. As online Car is a popular way for ge ng easily, we are implemen ng it. As
Online rental is a popular way of searching for the apartments and rooms available for
monthly rental. This module gives you brief idea about rooms available and area where
it is located.
2. Introduction and Objectives of the Project

Introduction:
Home Shop is being launched because a need for a des na on where the local community
could come together and help each other is seen. Community members within a city can come
here to find an apartment to live-in, sell their old car, or music system, promote their small
business,get an audience for a local event, trade any item.
This is a website based on classified – OLX and Quikr. In this project we can easily post any type
of ads free by logging in. We also update our classified ads if we register on this website and if
the post has been approved by the admin. In this website we also create an admin panel that
handles our user, create and update categories and manage classified post and much more.
Index page of this classified:
Here are some features of classified php project:
1. User Create Account

2. Login
3. Post Classified A er Login
4. Contact with seller
5. Update Classified
6. Admin Panel
7. Much more
8. An admin login should be present who can read, approve as well as remove any uploads.
Objective:
The summary of the objec ve of this so ware is to completely automate the process of:
• Provide be er understanding between ad posters and its viewers.
• Provide a user friendly environment so that the ad posters can post their ads easily and free
of cost.
• To maintain and store ad details, response details, ad viewer’s details, ad posters details.
• Provide excellent and easy to access means of communica on medium between ad posters
and its viewers.
• Provide value to its contributors by making available to them its vast global audience reach.
• Provide Classifieds as a service to enable its users to connect with one another.
• Provide local commerce site, uniquely integra ng Classifieds and Yellow Pages. The system
offers unmatched values such as Real Estate, Travels, jobs/Training, Movies/Entertainment,
buy/sale and more.
3. Project Category
Web Applica on
4. Tools/Platform, Hardware and Software Requirement specifications.

Tool
● Dreamweaver CS6
● Sublime text 3
● XAMPP server
Platform
Microso Windows 7/8/10
Hardware Requirement Specification:
Client Machine Server Machine
HDD 200 MB HDD 320 GB
Processor Pen um 4 or newer Processor Dual Core or
processor that newer processor
supports SSE2
Memory 512 MB Memory 2 GB
Software Requirement Specification:

Client Machine Server Machine
Browser Any standard Software Apache
browser with
JavaScript
interpreter
Client side mark up / HTML, JavaScript Database MySQL
scripting languages Management
System
Software
Specification MySQL 4.1
5. Goals of Implementation
The implementa on aims at seamless document sharing across the ins tu on.
6. SDLC Process Applied
O en, a customer defines a set of general objec ves for so ware but does not iden fy
detailed input, processing, or output requirements. In other cases, the developer may be
unsure of the efficiency of an algorithm, the adaptability of an opera ng system, or the form
that human/machine interac on should take. In these, and many other situa ons, a
prototyping paradigm may offer the best approach.
The prototyping paradigm begins with requirements gathering. Developer and customer meet
and define the overall objec ves for the so ware, iden fy whatever requirements are known,
and outline areas where further defini on is mandatory. A "quick design" then occurs. The
quick design focuses on a representa on of those aspects of the so ware that will be visible to
the customer/user (e.g., input approaches and output formats). The quick design leads to the
construc on of a prototype. The prototype is evaluated by the customer/user and used to
refine requirements for the so ware to be developed. Itera on occurs as the prototype is
tuned to sa sfy the needs of the customer, while at the same me enabling the developer to
be er understand what needs to be done.
Ideally, the prototype serves as a mechanism for iden fying so ware requirements. If a
working prototype is built, the developer a empts to use exis ng program fragments or
applies tools (e.g., report generators, window managers) that enable working programs to be
generated quickly.
7. Data Model
ER Diagram
8. Functional Requirements
Func onal Requirements are those that refer to the func onality of the system, i.e.,
what services it will provide to the user. Nonfunc onal (supplementary) requirements
pertain to other informa on needed to produce the correct system and are detailed
separately.
Use Case Diagram
Use Case Descriptions (Admin)

se Case Name: uthen ca on
iority sen al
igger enu selec on
econdition dmin is connected to the Internet and on the login page
1. Admin enters username and password.
2. The username and password is matched with the record in the
asic Path database.
3. If the authen ca on parameters are correct the admin is
directed to the admin’s main page, otherwise an error message
is displayed.
ternate Path A
ost Condition he admin is on the Admin Home Page
xception Path there is a connec on failure the server returns to the wait state
-se Case Name: anage category

iority sen al
igger enu selec on
econdition dmin is connected to the Internet and on the category main page
1. Admin selects a category.
asic Path 2. Admin clicks on the add new category bu on.
3. The server side program receives the category details and saves
it in the server system’s file system.
ost Condition he admin uploads the category’s details.
se Case Name: anage sub-category

iority sen al
igger enu selec on

dmin is connected to the Internet and on the Sub-category main
econdition
page
1. Admin selects a sub-category.
asic Path 2. Admin clicks on the add new sub-category bu on.
3. The server side program receives the sub-category details and
saves it in the server system’s file system.
ternate Path A
ost Condition he admin uploads the sub-category’s details.
se Case Name: anage city

iority sen al
igger enu selec on
econdition dmin is connected to the Internet and on the admin’s main page
1. Admin selects a city.
asic Path 2. Admin clicks on the add new city bu on.
3. The server side program receives the city details and saves it in
the server system’s file system.
ternate Path A
ost Condition he admin uploads the city’s details.
Use Case Descriptions (User)

se Case Name: uthen ca on
iority sen al
igger enu selec on
econdition ser is connected to the Internet and on the user’s main page
1. User enters user email and password.
2. User email and password is matched with the record in the
asic Path database.
3. If the authen ca on parameters are correct the User is
directed to the User main page, otherwise an error message is
displayed.
ternate Path A
ost Condition he User is on the User home page.
se Case Name: arch post

iority sen al
igger enu selec on
econdition ser is connected to the Internet and on the User’s main page
User Selects a search post.
asic Path User clicks on the search post details bu on.
The server side program receives the user’s details and saves
it in the server system’s file system.
ternate Path A
ost Condition he users search the post details.
se Case Name: anage post

iority sen al
igger enu selec on
User selects a post add.
asic Path User clicks on the post add details bu on.
The server side program receives the User details and saves it in
ternate Path A
ost Condition he user adds the post.
se Case Name: hange password

iority sen al
igger enu selec on
User selects a my account.
asic Path User clicks on the chance password bu on.
The server side program receives the User details and saves it in
ternate Path A
ost Condition he user can change password.
9. Non Functional Requirements

In addi on to the obvious features and func ons that you will provide in your system, there are
other requirements that don't actually DO anything, but are important characteris cs
nevertheless. These are called "non-func onal requirements" or some mes "Quality
A ributes." For example, a ributes such as performance, security, usability, compa bility. Isn’t
a "feature" of the system, but are a required characteris c. You can't write a specific line of
code to implement them; rather they are "emergent" proper es that arise from the en re
solu on. The specifica on needs to describe any such a ributes the customer requires. You
must decide the kind of requirements that apply to your project and include those that are
appropriate.
Each requirement is simply stated in English. Each requirement must be objec ve and
quan fiable; there must be some measurable way to assess whether the requirement has
been met.
O en deciding on quality a ributes requires making tradeoffs, e.g., between performance and
maintainability. In the APPENDIX you must include an engineering analysis of any significant
decisions regarding tradeoffs between compe ng a ributes.
Here are some examples of non-func onal requirements:
Performance requirements
Requirements about resources required, response me, transac on rates, throughput,
benchmark specifica ons or anything else having to do with performance. For be er
performance the applica on will restrict the document size to 5 MB.
Operating constraints
List any run- me constraints. This could include system resources, people, needed so ware,
The applica on must run without any manual interven on.
Platform constraints
Discuss the target pla orm. Be as specific or general as the user requires. If the user doesn't
care, there are s ll pla orm constraints. Since the applica on will be developed in JEE it is
pla orm independent.
Accuracy and Precision
Requirements about the accuracy and precision of the data. (Do you know the difference?)
Beware of 100% requirements; they o en cost too much.
Modifiability
Requirements about the effort required to make changes in the so ware. O en, the
measurement is personnel effort (person- months).
Portability
The effort required to move the so ware to a different target pla orm. The measurement is
most commonly person-months or % of modules that need changing.
Reliability
Requirements about how o en the so ware fails. The measurement is o en expressed in
MTBF (mean me between failures). The defini on of a failure must be clear. Also, don't
confuse reliability with availability which is quite a different kind of requirement. Be sure to
specify the consequences of so ware failure, how to protect from failure, a strategy for error
detec on, and a strategy for correc on.
Security
One or more requirements about protec on of your system and its data. The measurement
can be expressed in a variety of ways (effort, skill level, and me,) to break into the system. Do
not discuss solu ons (e.g. passwords) in a requirements document.
Only secured users can access the applica on.
No one can go to any independent page without logging in.
Usability
Requirements about how difficult it will be to learn and operate the system. The requirements
are o en expressed in learning me or similar metrics.
Legal
There may be legal issues involving privacy of informa on, intellectual property rights, export
of restricted technologies, etc.
10. Feasibility Study

You should provide a feasibility report in the following format:
● Product: A general statement of the product; give a brief descrip on of what the
proposed system will do, highligh ng where the proposed system meets the specified
business requirements of the organiza on.
● Technical Feasibility: Will the proposed system perform to the required specifica on?
Outline technical systems op ons you propose to use, which will give a technical
solu on sa sfying the requirements and constraints of the system, as outlined in the
terms of reference.
● Social Feasibility: Considera on of whether the proposed system would prove
acceptable to the people who would be affected by its introduc on. Describe the effect
on users from the introduc on of the new system; consider whether there will be a need
for retraining the workforce. Will there be a need for reloca on of some of the
workforce? Will some jobs become deskilled? Will the current workforce be able to
perform effec vely any new tasks introduced by the proposed system? Describe how
you propose to ensure user co-opera on before changes are introduced.
● Economic Feasibility: Consider the cost/benefits of the proposed system. Detail the
costs that will be incurred by the organiza on adop ng the new system; consider
development costs and running costs. Detail benefits that the new system will bring,
direct economic benefits such as reduced costs, and indirect benefits, such as improved
management informa on and be er customer service. Illustrate the cost/benefit of the
new system by applying a suitable cost/benefit analysis method such as the payback
method.
● Market Research: A comprehensive market research iden fying a need for the
product. Detail all market research you carried out, lis ng sources of informa on. Jus fy
any conclusions you have drawn from your research. Iden fy the poten al customer
base for your product, together with evidence of customer need for the product.
Describe how you propose to compete with similar products on the market.
● Alternative Solution: Considera on of alterna ve solu ons should be documented.
At least two alterna ve business or technical systems op ons should be considered.
Detail the differences between these op ons and the proposed system. Jus fy your
choice of the proposed system and the reasons for rejec ng the alterna ve op ons.
At this point, all of the planning for the project has been done and if the feasibility study has
shown that the project is likely to succeed within its constraints, then it only remains for us to
start the requirements analysis and thus proceed with the project.
Feasibility Study
System: HOMESHOP Date:
Author: Rathindranath Sahoo Page: 1
Product
The project requires a web applica on to be developed that will allow online
treading/document/paper sharing.
Technical Feasibility
The web applica on will be developed using PHP and MySQL. The team is
competent in that.
Social Feasibility
Some training for the users/admin is required but all users are IT literate.
Market Research
Market research says that this applica on would be useful for the users as it
could seamlessly help them to share documents.
Economic Feasibility
The applica on can be developed within budget.
Alternate Solution
Could be a desktop system but that would not allow documents to be shared
online.
11. Project Planning

Project planning is concerned with iden fying the following for every project:
● Ac vi es
● Milestones
● Deliverables.
A plan must be drawn up to guide the development towards the project goal. A plan is drawn
up at the start of a project. This plan should be used as the driver for the project. The ini al
plan is not sta c, and must be modified as the project progresses.
Planning is required for development ac vi es from specifica on through to delivery of the

system.
12. Project Scheduling:
Grant Chart
Task Person(s) Week Week Week Week Week Week
Responsible 1 2 3 4 5 6
Communication
Quick Plan
Modeling Quick
Design
Construction of
Prototype
Deployment,
Delivery and
Feedback
13. Software Engineering Paradigm Applied

Data Flow Diagrams (DFD)
Level 0
‘1’ LEVEL DIAGRAM (FOR ADMIN)
DFD Level 2 for Admin Category:
DFD Level 2 for Admin Subcategory:
DFD Level 2 for Admin City:
‘1’LEVEL DIAGRAM (FOR USER)
DFD LEVEL 2 FOR USER
DFD LEVEL 2 FOR USER
14. Schema/Database Design

Table name:- users
Name of type Data types Key Description

attributes
id Int(11) Primary key User id

name Varchar(250) User Name
email Varchar(250) User Email
password Varchar(250) User password
dp Varchar(250) Display Picture url
admin Tinyint(1) Check Admin or Not
Table name:- category

attributes
id Int(11) Primary key Category id

name Varchar(250) Category name
icon Varchar(250) Path of the icon
Table name:- ads

attributes
id Int(11) Primary key Ads id

tle Varchar(250) Ad tle
cat_id Varchar(250) Foreign Key Category Id
user_id Varchar(250) Foreign Key User id
loca on Varchar(250) City name
price Decimal(20,2) Price
specifica on Text Specifica on
feature Text Feature
images Text Image path
descrip on Text Descrip on
mobile Varchar(250) Mobile No
address Varchar(250) Address
views Int(11) No of views
status Tinyint(1) Status of ad
dt Date Date
15. Testing
Team Interaction
The following describes the level of team interac on necessary to have a successful product.
● The Test Team will work closely with the Development Team to achieve a high quality design
and user interface specifica ons based on customer requirements. The Test Team is
responsible for visualizing test cases and raising quality issues and concerns during
mee ngs to address issues early enough in the development cycle.
● The Test Team will work closely with Development Team to determine whether or not the
applica on meets standards for completeness. If an area is not acceptable for tes ng, the
code complete date will be pushed out, giving the developers addi onal me to stabilize
the area.
● Since the applica on interacts with a back-end system component, the Test Team will need
to include a plan for integra on tes ng. Integra on tes ng must be executed successfully
prior to system tes ng.
Test Objective
The objec ve our test plan is to find and report as many bugs as possible to improve the
integrity of our program. Although exhaus ve tes ng is not possible, we will exercise a broad
range of tests to achieve our goal. We will be tes ng a Binary Search Tree Applica on u lizing
a pre-order traversal format. There will be eight key func ons used to manage our applica on:
load, store, clear, search, insert, delete, list in ascending order, and list in descending order.
Our user interface to u lize these func ons is designed to be user-friendly and provide easy
manipula on of the tree. The applica on will only be used as a demonstra on tool, but we
would like to ensure that it could be run from a variety of pla orms with li le impact on
performance or usability.
Process Overview
The following represents the overall flow of the testing process:
1. Iden fy the requirements to be tested. All test cases shall be derived using the current
Program Specifica on.
2. Iden fy which par cular test(s) will be used to test each module.
3. Review the test data and test cases to ensure that the unit has been thoroughly verified
and that the test data and test cases are adequate to verify proper opera on of the unit.
4. Iden fy the expected results for each test.
5. Document the test case configura on, test data, and expected results.
6. Perform the test(s).
7. Document the test data, test cases, and test configura on used during the tes ng
process. This informa on shall be submi ed via the Unit/System Test Report (STR).
8. Successful unit tes ng is required before the unit is eligible for component
integra on/system tes ng.
9. Unsuccessful tes ng requires a Bug Report Form to be generated. This document shall
describe the test case, the problem encountered, it’s possible cause, and the sequence
of events that led to the problem. It shall be used as a basis for later technical analysis.
10.Test documents and reports shall be submi ed. Any specifica ons to be reviewed,
revised, or updated shall be handled immediately.
Testing Process
The diagram above outlines the Test Process approach that will be followed.
a. Organize Project involves crea ng a System Test Plan, Schedule & Test Approach, and
assigning responsibili es.
b. Design/Build System Test involves iden fying Test Cycles, Test Cases, Entrance & Exit
Criteria, Expected Results, etc. In general, test condi ons/expected results will be iden fied
by the Test Team in conjunc on with the Development Team. The Test Team will then
iden fy Test Cases and the Data required. The Test condi ons are derived from the Program
Specifica ons Document.
c. Design/Build Test Procedures includes se ng up procedures such as Error Management
systems and Status repor ng.
d. Build Test Environment includes reques ng/building hardware, so ware and data set-ups.
e. Execute System Tests – The tests iden fied in the Design/Build Test Procedures will be
executed. All results will be documented and Bug Report Forms filled out and given to the
Development Team as necessary.
f. Signoff - Signoff happens when all pre-defined exit criteria have been achieved.
Testing Strategy
The following outlines the types of tes ng that will be done for unit, integra on, and system
tes ng. While it includes what will be tested, the specific use cases that determine how the
tes ng is done will be detailed in the Test Design Document. The test cases that will be used
for designing use cases is shown in Figure 2.1 and onwards.
Test Cases
Tested By: Rathindranath Sahoo
Test Type Unit Tes ng
Test Case Number 1
Test Case Name User Iden fica on
Test Case Description The user should enter his/ her accurate userid and
password so that he/she can able to go for the
further op ons. The test case will check the
applica on for the same since a user can only login
with the correct userid, password.
Item(s) to be tested
Verifica on of the userid and password with the record in the
1
database.
Specifications
Expected
Input Output/Result
1) Correct User id and password 1) Successful login
2) Incorrect Id or Password 2) Failure Message
Tested By: Rathindranath Sahoo

Test Type Unit Tes ng
Test Case Number 2
Test Case Name Submit Document
Test Case Description

The User submit document. For document
submission the must login.
Item(s) to be tested
1 Check whether the user id logged in.
Check if the user has selected a document and the size of that is <
2
5 MB.
Specifications
Expected
Input Output/Result
1) Trying to submit document 1) The user is redirected to the login
without logging in. page.
2) Check whether document is 2) A message asks the user to select a
selected. document.
3) Check whether the size of the 3) Return an error message.
document is < 5 MB.
Unit Testing
Unit Tes ng is done at the source or code level for language-specific programming errors such
as bad syntax, logic errors, or to test par cular func ons or code modules. The unit test cases
shall be designed to test the validity of the programs correctness.
White Box Testing

In white box tes ng, the UI is bypassed. Inputs and outputs are tested directly at the code
level and the results are compared against specifica ons. This form of tes ng ignores the
func on of the program under test and will focus only on its code and the structure of that
code. Test case designers shall generate cases that not only cause each condi on to take on all
possible values at least once, but that cause each such condi on to be executed at least once.
To ensure this happens, we will be applying Branch Tes ng. Because the func onality of the
program is rela vely simple, this method will be feasible to apply.
Each func on of the binary tree repository is executed independently; therefore, a program
flow for each func on has been derived from the code.
Black Box Testing

Black box tes ng typically involves running through every possible input to verify that it results
in the right outputs using the so ware as an end-user would. We have decided to perform
Equivalence Par oning and Boundary Value Analysis tes ng on our applica on.
System Testing
The goals of system tes ng are to detect faults that can only be exposed by tes ng the en re
integrated system or some major part of it. Generally, system tes ng is mainly concerned with
areas such as performance, security, valida on, load/stress, and configura on sensi vity. But in
our case well focus only on func on valida on and performance. And in both cases we will use
the black-box method of tes ng
16. System Security measures (Implementation of security for the

project developed)
● Only authorized users are allowed.

● Without signing in users are not allowed to go an intermediate page by typing an URL.
For all such efforts, users will be redirected to the home page.
17. Database/Data security
● Database is present in remote machine.

● Oracle’s default securi es are applied.
18. Creation of User profiles and access rights
● The admin must create users manually.

● The admin can create more admin’s.
19. Cost Estimation of the Project along with Cost Estimation Model
Analogous estimate of effort or cost

Used for Early Es mate or Individual Ac vity Es mate
Sample example shown below is for two major deliverables of a so ware project. You use a
previous project as a benchmark for analogous es ma on. Using your experience you will
es mate a mul plier.
Mul pliers:
1. Prototyping: 0.75.
2. Tes ng: 0.5
3. Deployment: 0.5
Finally, if you want to convert to cost, you would use current rates for the resource.
Previous Effort
Current Cost
WBS Similar Previous Multiplie (Previou
Project (Rs.
ID Project Effort r s Effort *
Estimate 500/hr.)
Activity 0.75)
40 30
Prototypin Rs.
1 Prototyping Work-Ho 0.75 Work-ho
g 15000/-
urs urs
20 10
Rs.
2 Tes ng Work-Ho Tes ng 0.50 Work-Ho
5000/-
urs urs
40 Work- Rs.
Total
Hours 20000/-
20. Coding and screenshots

20.1 Home page
Coding Home page:php,Html,Css,Java script:

<!DOCTYPE html>
<html>
<head>
< tle>
<?php echo $ob->sitename; ?>
</ tle>
<link rel="stylesheet" type="text/css" href="/assets/preloader.css" />
<link rel="stylesheet" type="text/css" href="/assets/theme.css" />
<script src="/assets/jquery.js"></script>
</head>
<body>
<div class="preloader">
<div class="dot-container">
<div class="dot"></div>
</div>
</div>

<?php require 'naviga on.php'; ?>
<div class="landing-page"></div>
<div id="container" style="margin-top:150px">
<div class="table">
<div class="table-cell w-50 v-align-t">
<div class="slogans">
<h1>World's Largest Marketplace</h1>
<h2>You Can Buy, Sell Anything You Can Think Of.</h2>
<div class="slogan3">NEW STUFF - OLD STUFF - SERVICES - LOOKING FOR
- BUY - SELL</div>
<a href="/dashboard/?ad-edit=0"><div
class="postAds"><span>Post</span> Your Ad</div></a>
</div>
</div>
<div class="table-cell w-50 v-align-m">
<div class="top-form-wrapper">
<div class="heading">You Are Looking For ??</div>
<form ac on="/search/1" method="POST">
<input class="input" type="text" name="query" value=""
placeholder="Looking for ?">
<select name="category">
<?php
$cate = $ob->getCategories();
while($category = $cate->fetch_assoc()){
echo '<op on
value="'.$category['id'].'">'.$category['name'].'</op on>';
}
?>
</select>
<select name="loca on">
<?php
$ob->loadCi es();
?>
</select>
<bu on type="submit"> SEARCH </bu on>
</form>
</div>
</div>
</div>
</div>
<div class="content">
<div class="category">
<div class="box-container">
<?php
$cat = $ob->getCategories();
if(!empty($cat)){
while($c = $cat->fetch_assoc()){
echo '
<a href="/list/'.$c['id'].'">
<div class="box">
<div class="text-panel">
<img src="'.$c['icon'].'">
'.$c['name'].'
<div
class="ads">['.$ob->getAdCount($c['id']).']</div>
</div>
</div>
</a>
';
}
}
?>
</div>
</div>
<div id="container" style="padding-top: 100px;">

<div class="head- tle">LATEST ADS</div>
<div class="ads-wrapper-container">
<div class="ads-wrapper">
<?php
if(!empty($ob->latestAd())){
$query = $ob->latestAd();
while($ads = $query->fetch_assoc()){
$thumb = json_decode($ads['images'])[0];
echo '
<div class="ad-container ad-hidden">
<div class="thumb">
<div class="img">
<a
href="/view/'.$ads['id'].'/'.urlencode($ads[' tle']).'"><img src="'.$thumb.'"></a>
</div>
<a
href="/all-ads/'.$ads['user_id'].'"><img src="'.$ob->user2dp($ads['user_id']).'" class="seller-dp"></a>
</div>
<div class="type"> <a
href="/list/'.$ads['cat_id'].'">'.$ob->cat_id2name($ads['cat_id']).'</a></div>
<a
href="/view/'.$ads['id'].'/'.urlencode($ads[' tle']).'"><div class=" tle">'.$ads[' tle'].'</div></a>
<div class="address"><img
src="/assets/icons/loca on.svg" class="icon-small"> '.$ads['address'].' </div>
<div class="price">₹ '.

number_format($ads['price'],2,'.',',') .' /-</div>
</div>
';
}
}
?>
</div>
</div>
</div>
</div>
<div class="footer">
<a href="">Privacy Policy</a>  |  <a href="">Terms of
use</a>  |  <a href="">Faqs</a>
</div>
<div class="reserve">All Copyrights reserved @ <?php echo date('Y'); ?> </div>
</body>
</html>
<script type="text/javascript">
$(document).ready(func on(){
//naviga on scroll func on
$(window).scroll(func on(){
if($(this).scrollTop()>=50){
$("nav").css({"background-color":"#FFF"});
}
else{
$("nav").css({"background-color":"rgba(255, 255, 255, 0.1)"});
}
});
//ads loading anima on on scroll
func on apperance(_this,i) {
setTimeout(func on() {
$(_this).removeClass("ad-hidden");
}, 100 + i * 300);
}
var scrTop = $(this).scrollTop()+$(this).height();
$(".ad-hidden").each(func on(index){
if(scrTop > $(this).offset().top){
apperance(this,index);
}
});
});
});
$(window).on("load", func on(){
//$(".preloader").fadeOut("slow");
setTimeout(func on(){
$(".preloader").fadeOut("slow");
$(".landing-page").addClass("bg-anima on");
$(".top-form-wrapper").addClass("form-anima on");
$(".slogans h1").addClass("slogan-h1-anima on");
}, 1000);
});
</script>
20.2. All Item/Search Page:
Coding All Category Page:php,Html,Css,Java script:

<?php require 'header.php'; ?>
<div class="content" style="padding:0;margin:0;">

<div id="container" style="padding-top: 100px;">
<div class="head- tle"><?php echo $ob->setTitle();?></div>
<div class="list-type-holder">
<ul>
<li><span>SORT BY :</span></li>
<li><a href="?orderby=date" <?php echo (!isset($_GET['orderby']) ||
$_GET['orderby']=='date') ? 'class="ac ve"' : '' ;?>>DATE</a></li>
<li><a href="?orderby= tle" <?php echo (isset($_GET['orderby']) &&
$_GET['orderby']==' tle') ? 'class="ac ve"' : '' ;?>>TITLE</a></li>
<li><a href="?orderby=price" <?php echo (isset($_GET['orderby']) &&
$_GET['orderby']=='price') ? 'class="ac ve"' : '' ;?>>PRICE</a></li>
</ul>
</div>
<div class="ads-wrapper-container">
<div class="ads-wrapper">
<?php
if(!empty($ob->display())){
$query = $ob->display();
while($ads = $query->fetch_assoc()){
$thumb = json_decode($ads['images'])[0];
echo '
<div class="ad-container ad-hidden">
<div class="thumb">
<div class="img">
<a
href="/view/'.$ads['id'].'/'.urlencode($ads[' tle']).'"><img src="'.$thumb.'"></a>
</div>
<a
href="/all-ads/'.$ads['user_id'].'"><img src="'.$ob->user2dp($ads['user_id']).'" class="seller-dp"></a>
</div>
<div class="type"> <a
href="/list/'.$ads['cat_id'].'">'.$ob->cat_id2name($ads['cat_id']).'</a></div>
<a
href="/view/'.$ads['id'].'/'.urlencode($ads[' tle']).'"><div class=" tle">'.$ads[' tle'].'</div></a>
<div class="address"><img
src="/assets/icons/loca on.svg" class="icon-small"> '.$ads['address'].' </div>
<div class="price">₹ '.
number_format($ads['price'],2,'.',',') .' /-</div>
</div>
';
}
}
else{
echo '<h3 style="color:#66a80f;">No Data Found !</h3>';
}
?>
</div>
</div>
</div>
</div>
<?php require 'footer.php'; ?>
}
else{
}
});
//ads loading anima on on scroll
func on apperance(_this,i) {
setTimeout(func on() {
$(_this).removeClass("ad-hidden");
}, 100 + i * 300);
}
func on checkLoad(){
var scrTop = $(this).scrollTop()+$(this).height();
$(".ad-hidden").each(func on(index){
if(scrTop > $(this).offset().top){
apperance(this,index);
}
});
}
checkLoad();
checkLoad();
});
});
$(window).on("load", func on(){
//$(".preloader").fadeOut("slow");
setTimeout(func on(){
$(".preloader").fadeOut("slow");
$(".landing-page").addClass("bg-anima on");
$(".top-form-wrapper").addClass("form-anima on");
}, 1000);
});
</script>
20.3. User Dashboard:
Coding User/Admin Dashboard Page:php,Html,Css,Java script:

<?php require 'header.php'; ?>
<div class="adViewer">
<div id="container">
<table>
<tr>
<td class="v-align-t" style="width:70%;color:#000;">
<div class="ad-content">
<?php
if(isset($_GET['edit-profile'])){
?>
<form ac on="" method="POST"
enctype="mul part/form-data" class="dash-form">
<div class="group">
<div class="label">Email </div>
<input type="email" name="email"

placeholder="Email" value="<?php echo $ob->data['user']['email'];?>" class="input">
</div>
<div class="group">
<div class="label">Name </div>
<input type="text" name="name"
placeholder="Name" value="<?php echo $ob->data['user']['name'];?>" class="input">
</div>
Leave the fields blank to keep unchanged.
<div class="group">
<span class="label">Profile
Picture</span>
<input type="file" name="picture"
accept="image/*" placeholder="Picture" class="input" style="font-size:11px;border-bo om:0px;">
</div>
<div class="group">
<div class="label">Old Password
</div>
<input type="password"
name="opassword" placeholder="Old Password" class="input">
</div>
<div class="group">
<div class="label">New Password
</div>
name="npassword" placeholder="New Password" class="input">
</div>
<div class="group">
<div class="label">Confirm Password
</div>
name="cpassword" placeholder="Confirm Password" class="input">
</div>
<bu on type="submit">Update</bu on>
</form>
<?php
}
else if(isset($_GET['ad-edit'])){
$spec = $ob->loadSpecifica on();
$feature = $ob->loadFeature();
?>
<form ac on="" method="POST" class="dash-form"
enctype="mul part/form-data">
<?php
if(isset($ob->data['error']) &&
!empty($ob->data['error'])){
foreach ($ob->data['error'] as
$error) {
echo '<div
style="color:#00FF00;padding:5px">'.$error.'</div>';
}
}
?>
<strong>Ad Details : </strong><br>

<div class="group">
<div class="label">Title </div>
<input type="text" name=" tle"
placeholder="Title" value="<?php echo (isset($ob->data['ad'][' tle']))?$ob->data['ad'][' tle']:'';?>"
class="input" required>
</div>
<div class="group">
<div class="label">Category </div>
<select id="category"
name="category" class="input" style="font-size:14.1px;">
<?php
$cate =
$ob->getCategories();
while($category =
$cate->fetch_assoc()){
if(isset($ob->data['ad']['cat_id']) && $category['id']==$ob->data['ad']['cat_id'])

echo
'<op on value="'.$category['id'].'" selected>'.$category['name'].'</op on>';
else
echo
'<op on value="'.$category['id'].'">'.$category['name'].'</op on>';
}
?>
</select>
</div>
<div>
Specifica ons : <br>
<div id="specifica on"></div>
</div>
<div style="padding:10px;">
Features : <br>
<div id="features"></div>
</div>
<div class="group">
<div class="label">Price </div>
<input type="number"
name="price" placeholder="Price" value="<?php echo
(isset($ob->data['ad']['price']))?$ob->data['ad']['price']:'';?>" step="10" class="input" required>
</div>
<div class="group">
<span class="label">Images</span>
<input type="file" name="images[]"
placeholder="Images" class="input" style="font-size:11px;border-bo om:0px;" mul ple="mul ple">
</div>
<textarea name="descrip on"
placeholder="Descrip on" class="input"><?php echo
(isset($ob->data['ad']['descrip on']))?$ob->data['ad']['descrip on']:'';?></textarea>
<strong>Seller Details : </strong><br>
<div class="group">
<div class="label">Mobile </div>
<input type="text" name="mobile"
value="<?php echo (isset($ob->data['ad']['mobile']))?$ob->data['ad']['mobile']:'';?>" placeholder="Mobile"
</div>
<div class="group">
<div class="label">Address </div>
<input type="text" name="address"
value="<?php echo (isset($ob->data['ad']['address']))?$ob->data['ad']['address']:'';?>"" placeholder="Address"
</div>
<div class="group">
<div class="label">Loca on </div>
<select name="loca on"
class="input" style="font-size:14.1px;">
<?php
$ob->loadCi es();
?>
</select>
</div>
<bu on type="submit"><?php echo
($_GET['ad-edit']==0)? 'Post' : 'Update';?> AD</bu on>
</form>
var specifica on = '<?php echo (!empty($spec))?json_encode($spec):'';?>';

var feature = '<?php echo (!empty($spec))?json_encode($feature):'';?>';
feature = $.parseJSON(feature);
specifica on = $.parseJSON(specifica on);
$('#category').on('change',func on(){
loadfeature();
loadspec();
});
<?php
if($_GET['ad-edit']!='0'){
?>
var edit = 1;
var tempfeature = $.parseJSON('<?php echo

(isset($ob->data['ad']['feature']))?$ob->data['ad']['feature']:'';?>');
var temp = $.parseJSON('<?php echo
(isset($ob->data['ad']['specifica on']))?$ob->data['ad']['specifica on']:'';?>');
<?php
}
else{
?>
var edit = 0;
<?php
}
?>
loadspec();
loadfeature();
func on loadfeature(){
//console.log(tempfeature);
if(feature!=''){
category = $('#category op on:selected').html();
$('#features').html('');
$.each(feature[category], func on (key,val) {
if(edit==1 && jQuery.inArray(val, tempfeature) !== -1)
$('#features').append('<input type="checkbox" name="features[]"
value="'+val+'" checked> '+val+'  ');
else
$('#features').append('<input type="checkbox" name="features[]"
value="'+val+'"> '+val+'  ');
});
}
}
func on loadspec(){
//console.log(tempfeature);
if(specifica on!=''){
category = $('#category op on:selected').html();
$('#specifica on').html('');
$.each(specifica on[category], func on (key,val) {
if(edit==1 && temp[val])
$('#specifica on').append('<div class="group"><div
class="label">'+val+' </div><input type="text" name="spec['+val+']" value="'+temp[val]+'"
class="input"></div>');
else
$('#specifica on').append('<div class="group"><div
class="label">'+val+' </div><input type="text" name="spec['+val+']" class="input"></div>');
});
}
}
});
</script>
<?php
}
else{
if($ob->data['user']['admin']==1){
?>
<center>
<a href="?dashboard=1&list=pending"><div
class="dashbox">Pending [<?php echo $ob->getCount('0');?>]</div></a>
<a href="?dashboard=1&list=approved"><div
class="dashbox">Approved [<?php echo $ob->getCount();?>]</div></a>
<a href="?dashboard"><div
class="dashbox">Owned</div></a>
</center>
<?php
}
?>
<table class="ad-list" cellspacing="0">
<tr>
<th>Id</th>
<th>Title</th>
<th>Status</th>
<th>Ac on</th>
</tr>
<?php
if($ob->data['list']!=''){
while($ads =
$ob->data['list']->fetch_assoc()){
$status =
($ads['status']==0)?'Pending':'Ac ve';
echo '
<tr>
<td
style="width:5%">'.$ads['id'].'</td>
<td
style="width:50%">'.$ads[' tle'].'</td>
<td
style="width:5%">'.$status.'</td>
<td style="width:40%"> ';
if($ob->data['user']['admin']==1 &&
$_GET['list']=='pending')
echo '<a
href="/view/'.$ads['id'].'/'.urlencode($ads[' tle']).'">View ad</a> <a
href="?ad-approve='.$ads['id'].'">Approve</a> <a href="?delete-ad='.$ads['id'].'">Decline</a>';
else
echo '<a
href="/view/'.$ads['id'].'/'.urlencode($ads[' tle']).'">View ad</a> <a href="?ad-edit='.$ads['id'].'">Edit ad</a>
<a href="?delete-ad='.$ads['id'].'">Delete</a>';
echo '
</td>
</tr>
';
}
}
else{
echo '
<tr>
<td colspan="4" style="width:100%">No
data found! Post a ad first.</td>
</tr>';
}
?>
</table>
<?php
}
?>
</div>
</td>
<td class="v-align-t">
<div class="ad-content">
<div class="dp"><img src="<?php echo
$ob->data['user']['dp'];?>"></div>
<div class="seller-name"><?php echo
$ob->data['user']['name'];?></div>
<ul class="menu">
<li><a href="?dashboard">Dashboard</a></li>
<li><a href="?ad-edit=0">Post New Ad</a></li>
<li><a href="?edit-profile=1">Edit Profile</a></li>
</ul>
</div>
</td>
</tr>
</table>
</div>
</div>
<?php require 'footer.php'; ?>
}
else{
}
});
});
</script>
21. Future scope and further enhancement of the Project

HOMESHOP has lot of enhancement op ons. In future documents may be classified
category-wise. It may try to analyze the user behavior and preferences and accordingly suggest
document categories. AIl concepts can be applied to make HOMESHOP intelligent.
We had performed the ini al stages of the project like determining the pla orm to execute
project codes, database concerning figures (ER diagram, Schema diagram).
22. CONCLUSION
Through the Homeshop, the user can easily get the category a er logging in. The admin
approves it. But through this portal they can also easily search user. It never contains any cost it
just contains the charges which is requiring to surfing the internet.
In an era of applying for users in future there will be some more new technologies will be
developed rather than this which can make human life easier because day by day technology is
increasing and it also saves me.
23. Bibliography
1. Roger S. Pressman. So ware Engineering: A Prac oner's Approach (Sixth Edi on,
Interna onal Edi on). McGraw-Hill, 2005.
2. Ian Somerville. So ware Engineering (Seventh Edi on). Addison-Wesley, 2004.
3. Frederick P. Brooks. The Mythical Man-Month: Essays on So ware Engineering,

Anniversary Edi on. Addison-Wesley Pub Co; 1st edi on (August 2, 1995).
4. Introducing HTML5 by Bruce Lawson, Remy Sharp.
5. HTML5 for Web Designer by Jeremy Keith.
6. HTML for World Wide Web (Visual Quick Start Guide) by Elizabeth Castro.
7. HTML5 Up and Running by Mark Pilgrim.
8. The Defini ve Guide To HTML5 by Adam Freeman.
9. Pro HTML5 Programming: Powerful APIs for RcherInternet Applica on Development by
Peter Lubbers.
10.Dynamic HTML: The Defini ve Reference by Danny God man.
11.CSS: Defini ve Guide by Eric.A.Mayer.
12.CSS Cook Book by Christopher Schmi .
13.CSS: Missing Manual by David Sawyer McFarland.
14.CSS Mastery: Advance Web Standard Solu on by Andy Budd, Cameron Moll, Simon
Collision.
15. CSS Anthology by Rachel Andrew.
16. Han cra ed CSS: More Bulletproof Web Design/Bulletproof Essen als by Dan Aderholt,
EthanMarco e.

Classified Adds PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Classified Adds PDF

Transféré par

Droits d'auteur :

Formats disponibles

5/6/2019 classified_Adds - Google Docs

Development of a feature-rich, Classified Ads Portal Website

in partial fulfillment for the award of the degree of

Ogma TechLab Pvt. Ltd.

Ogma TechLab Pvt. Ltd.

“Development of a feature-rich, Classified Ads Portal Website” is the bonafide work

Name of the student:

Name : Saumitra Das

Ogma TechLab Original Seal

Table of Contents Page

2. Introduction and Objectives of the Project

Here are some features of classiﬁed php project:

1. User Create Account

4. Tools/Platform, Hardware and Software Requirement specifications.

Software Requirement Specification:

6. SDLC Process Applied

Use Case Descriptions (Admin)

-se Case Name: anage category

se Case Name: anage sub-category

igger enu selec on

se Case Name: anage city

Use Case Descriptions (User)

se Case Name: arch post

se Case Name: anage post

se Case Name: hange password

9. Non Functional Requirements

10. Feasibility Study

System: HOMESHOP Date:

Author: Rathindranath Sahoo Page: 1

The applica on can be developed within budget.

11. Project Planning

Planning is required for development ac vi es from speciﬁca on through to delivery of the

12. Project Scheduling:

13. Software Engineering Paradigm Applied

‘1’ LEVEL DIAGRAM (FOR ADMIN)

DFD Level 2 for Admin Category:

DFD Level 2 for Admin Subcategory:

DFD Level 2 for Admin City:

‘1’LEVEL DIAGRAM (FOR USER)

DFD LEVEL 2 FOR USER

DFD LEVEL 2 FOR USER

14. Schema/Database Design

Name of type Data types Key Description

id Int(11) Primary key User id

email Varchar(250) User Email

password Varchar(250) User password

dp Varchar(250) Display Picture url

admin Tinyint(1) Check Admin or Not

Table name:- category

Name of type Data types Key Description

id Int(11) Primary key Category id

Table name:- ads

Name of type Data types Key Description

id Int(11) Primary key Ads id

2) Incorrect Id or Password 2) Failure Message

Tested By: Rathindranath Sahoo

Test Case Description

White Box Testing

Black Box Testing

16. System Security measures (Implementation of security for the

● Only authorized users are allowed.

17. Database/Data security

● Database is present in remote machine.