7.1.3 password

Transcription

7.1.3 password

BookBa
r
t
e
r
Gr
oup:
-1
1
3015Bha
vi
nV.Ga
j
j
a
r
3077Di
pe
s
hV.Sukhi
a
Re
c
y
c
l
e
Yo
u
r
Re
d
i
n
g
BooksAr
eMe
n’
s
Be
s
tFr
i
e
nds
!
BOOK BARTER
6TH SEM OF 3 RD YEAR. MSC (CA&IT) (2014-2015)
STUDENT NAME
ROLL NO
Bhavin V. Gajjar
3015
Dipesh V. Sukhia
3077
NAME OF COMPANY
REPORT SUBMITTED TO
K.S. School of Business Management and Research
Date of Submission: 28
TH
APRIL, 2015.
Project Coordinator
Mrs. Nandita Goswami
Book Barter http://bookbarter.creartian.com
ACKNOWLEDGEMENT
It was a great experience working on the project of “Book Barter”.
We express our gratitude towards those who were constantly involved
with us during our project. CreArt Solutions, will always occupies a
special place in our heart, throughout our career, for both personal and
professional reasons.
The phenomenon remains same that no project ever can be executed
proficiently and efficiently without sharing the meticulous ideas,
technical expertise and innovative thoughts put forwarded by technical
and non-technical veterans.
Whenever a technical project is developed, eventually it requires
conductive technical environment and technical guidance to get
involved in the assigned project enthusiastically. We also grateful to
“CreArt Solutions” for being extremely friendly and co-operative
during entire course of our project. Their continuous help and support
made the project much easy.
There is no exact word to express our regards and legitimate gratitude
to one of our esteemed techno personality, without him this project
could not get an entrance towards the execution. Our project manager is
the pioneer who availed this magnificent option to us to move ahead.
He is always inspired and guided us for the right track to be followed
for all the system analysis section of this project.
From,
Bhavin V. Gajjar
Dipesh V. Sukhia
1
INDEX
No
Table Of Contents
Page No
1
Company Profile
3
2
Introduction
5
3
2.1
Purpose
5
2.2
Document Conventions
5
2.3
Intended Audience and Reading Suggestions
5
2.4
Product Scope
6
Project Profile and Technology used
Product Perspective
7
3.1.1 Existing System
7
3.1.2 Proposed System
7
3.2
Technology used
7
3.3
Operating Environment
13
3.1
4
7
UML Diagrams:
15
4.1
Use Case Diagram
15
4.2
Activity Diagram
17
4.3
Class Diagram
21
4.4
Sequence Diagram
23
5
Data Dictionary
25
6
Input-Output Design
31
7
Validation
51
8
Future Scope
56
9
Bibliography
57
10
Conclusion
58
2
1. COMPANY PROFILE
CREART SOLUTIONS
CreArt Solutions started with the goal to march forward in various
faces with novel ideas. We strongly believe that every creation follows
the strategically strong principles and the innovative judgments. Our
great asset – skilled professionals, make us ever growing organization.
By maintain long lasting relations with people and technology, we have
gained the place of global admirer and a fair business entity. Timely
achievement of targets and professionally qualitative results is our true
identity. We deliver admirable results by incorporating the lessons from
the past projects and adventures.
We have the key capabilities in the fields of:
 Web Development
 Mobile Development
 Research & Market Analysis
 Offshore Development
 QA outsourcing
 Networking
We have dedicated professionals in following areas,
 JQuery Mobile
 Android
 PHP
 .NET
3
We have enthusiastic team with long term steadiness which makes it
possible to commit the timely results. Our team follows time tested
procedures and structures for development. Our customers are
completely involved in all the phases of product development and
hence we are able to maintain the lucidity in our developments. With
our dynamic thinking we provide customized and easy adaptable
solutions. For project development we follow responsive development
strategies from the very beginning stage of planning to deployment and
hosting.
Address
8,3rd Floor,
Agrawal Avenue Opp, Telephone Exchange,
C.G. Road, Ahmadabad.
Mobile :( +91) 982496 9300
Email: solutions.creart@gmail.com
Web: solutions.creart.in
4
2. INTRODUCTION
2.1 PURPOSE
The purpose of this document is to give a detailed description of the requirements
for the “Book Barter”. It will illustrate the purpose and complete declaration for
the development of “Book Barter”. Book Barter`s main purpose is selling,
exchange, donate and give book on rent as per user`s requirement. Which give
user more flexibility to get knowledge from books. This document is primarily
intended to be proposed to a user for its approval and a reference for developing
the first version of the system for the development team.
2.2 DOCUMENT CONVENTIONS
The document has used underlined words to high light the user requirements. It
also uses capital lettered words to highlight key words. The document has tried to
maintain a priority of requirements .The priority has been determined by the
judgment of the author and may subject to change. Priority of higher-level
requirements is inherited by detailed requirements. The document has used short
forms for some commonly abbreviated terms.
2.3 INTENDED AUDIENCE AND READING
SUGGESTIONS
The document is intended to be a guide for developers, users and testers. The goal
of this document is to identify the requirements of application “Book Barter”. A
developer may directly want to know the requirements by reading the section of
USER REQUIREMENTS and skipping other sections if required.
5
2.4 PRODUCT SCOPE
PURPOSE

In today’s world, This type of Book Barter system is not exists. Book
Barter`s main purpose is selling, exchange, donate and give book on
rent as per user`s requirement. Which give user more flexibility to get
knowledge from books.
BENEFITS
It will give facility to selling, exchange, donate and give book on rent
as per user`s requirement. Here User can also put any type of
condition`s book like good, fair, poor. Which give user more
flexibility to get knowledge from books.

OBJECTIVES
Book Barter`s main objective is give user more flexibility to get
knowledge from books.
6
3. PROJECT PROFILE
NTRODUCTION
3.1 PRODUCT PERSPECTIVE
Book Barter is an exclusive system which provides more flexibility to get
knowledge from books. "Book Barter" is place where anyone can enter in system
without sign in and order for book as per requirement. And User can also put any
type of condition`s book like good, fair, poor.
3.1.1 EXISTING SYSTEM:
In current System user when need for any type of book he/she have to
purchase book. It is so costly. Users have to pay more money for the
book. After reading the book user want sell the book but he/she not
get money as per he/she purchase.
3.1.2 PROPOSED SYSTEM:
In Book Barter we will give facility to selling, exchange, donate and
give book on rent as per user`s requirement. Here User can also put
any type of condition`s book like good, fair, poor. Which give user
more flexibility to get knowledge from books.
3.2 TECHNOLOGY USED:
The technology used to develop the project is PHP which provides
excellent integrated development of project and has convenience in
understanding and operating the System.It provides facility to connect
to various resources like database required. It supports many
languages for developing the project like HTML, CSS, and JQUERY
etc.
7
FRONTEND TECHNOLOGY
HTML 5:
The website is growing up quickly, and tons of great HTML5 features
are already supported on modern browsers. Web developers can use
the same set of technologies they know and love to build rich web
applications that work across different device types.
CSS 3:
Cascading Style Sheets (CSS) is a style sheet language used for
describing the presentation semantics (the look and formatting) of a
document written in a mark-up language. It’s most common
application is to style web pages written in HTML and XHTML, but
the language can also be applied to any kind of XML document,
including plain XML, SVG and XUL.
JQUERY 2.0.3:
JQuery is free, open source software, licensed under the MIT License.
Query’s syntax is designed to make it easier to navigate a document,
select DOM elements, create animations, handle events, and develop
Ajax applications. JQuery also provides capabilities for developers to
create plug-ins on top of the JavaScript library.
This enables developers to create abstractions for low-level interaction
and animation, advanced effects and high-level, theme-able widgets.
The modular approach to the JQuery library allows the creation of
powerful dynamic web pages and web applications.
8
AJAX:
AJAX = Asynchronous JavaScript and XML.
AJAX is a technique for creating fast and dynamic web pages. AJAX
allows web pages to be updated asynchronously by exchanging small
amounts of data with the server behind the scenes. This means that it
is possible to update parts of a web page, without reloading the whole
page. Classic web pages, (which do not use AJAX) must reload the
entire page if the content should change. Examples of applications
using AJAX: Google Maps, Gmail, Youtube, and Facebook tabs.
BOOTSTRAP 3.3.1:
Bootstrap is the most popular HTML, CSS, and JS framework for
developing responsive, mobile first projects on the web.
Bootstrap is a free collection of tools for creating website and web
applications. It contains HTML and CSS based design templates for
typography,
forms,
buttons,
navigation
and
other
interface
components, as well as optional JavaScript extensions.
MORRIS CHART 0.5.1:
It is possible to display only the code in the x-axis and to display the
whole description in the hover legend.
DATA TABLES:
DataTables is a plug-in for the jQuery Javascript library. It is a highly
flexible tool, based upon the foundations of progressive enhancement,
and will add advanced interaction controls to any HTML table.
9
CAPTCHA:
A CAPTCHA (an acronym for "Completely Automated Public Turing
test to tell Computers and Humans Apart") is a type of challengeresponse test used in computing to determine whether or not the user
is human.
JSON:
JSON (JavaScript Object Notation) is a lightweight data-interchange
format. It is easy for humans to read and write. It is easy for machines
to parse and generate.
FRONTEND TOOLS:
 Adobe Dreamweaver CC
 Adobe Photoshop CC
 Adobe Premiere Pro CC
 PHP Storm 8.0.3
 Brackets 1.2
 Sublime Text 2.0.2
SERVER:
 Apache 2.4.9
 Wamp 2.5
Book Barter http://bookbarter.creartian.com 10
BACKEND TECHNOLOGY
PHP 5.5.12:
PHP is probably the most popular scripting language on the web. It is
used to enhance web pages. With PHP, you can do things like create
username and password login pages, check details from a form, create
forums, picture galleries, surveys, and a whole lot more. If you've
come across a web page that ends in PHP, then the author has written
some programming code to liven up the plain, old HTML.PHP is
known as a server-sided language. That's because the PHP doesn't get
executed on your computer, but on the computer you requested the
page from. The results are then handed over to you, and displayed in
your browser.
MYSQL 5.6.17:
MySQL is a database system used on the web. MySQL is a database
system that runs on a server. MySQL is ideal for both small and large
applications. MySQL is very fast, reliable, and easy to use. MySQL
supports standard SQL. MySQL compiles on a number of platforms.
MySQL is free to download and use. MySQL is developed,
distributed, and supported by Oracle Corporation. MySQL is named
after co-founder Monty Widenius`s daughter: My. The data in
MySQL is stored in tables. A table is a collection of related data, and
it consists of columns and rows.
COOKIE:
A cookie is often used to identify a user. A cookie is a small file that
the server embeds on the user's computer. Each time the same
computer requests a page with a browser, it will send the cookie too.
With PHP, you can both create and retrieve cookie values.
GUZZLE:
Guzzle is a PHP HTTP client that makes it easy to send HTTP
requests and trivial to integrate with web services.
MESSAGE API:
This API enables you to send messages via Plivo SMS service. The
API supports Unicode UTF-8 encoded texts, so you can send
messages in any language. The API also handles long SMS
automatically by splitting it into standard SMS sized chunks and
sending them. Delivery reports are automatically supported in
networks where they are provided by the operator.
FACEBOOK SDK 4:
The Facebook SDK for PHP provides developers with a modern,
native library for accessing the Graph API and taking advantage of
Facebook Login. Usually this means you're developing with PHP for a
Facebook Canvas app, building your own website, or adding serverside functionality to an app that already uses the Facebook SDK for
JavaScript.
PSR 4:
This PSR describes a specification for auto loading classes from file
paths. It is fully interoperable, and can be used in addition to any other
autoloading specification, including PSR-0. This PSR also describes
where to place files that will be auto loaded according to the
specification.
COMPOSER:
When Composer showed up and took the PHP package management
world by storm, things changed. Due to some of its rules, folders often
duplicated and became too deep.
TESTING TOOLS:
BROWSER:
 Google Chrome Version : 41.0.2272.118 m
 Firefox 39.0a2
 Internet Explorer 11
OPERATING SYSTEM:
 Windows 7/8/8.1
 Linux
 Mac OS
 Android
 Jelly bean 4.3, Kitkat 4.4, Lollipop 5.0.2
3.3 OPERATING ENVIRONMENT
CLIENT SIDE TOOLS

Processor
PC with a Dual core processor or above
Recommended: 2.20 GHz processor.

RAM
512 MB or onwards Recommended.

Hard Disk
45 MB of available space required on system
drive of available or more.

Operating
System
Windows or open source 32 bit operating
system, or later versions.

Browser
Mozilla Firefox 2.0 /Internet Explorer 8.0
Onwards with Player Plug-in 9.0 or onwards /
Google Chrome.
SERVER SIDE TOOLS

Processor
PC with a Dual core processor or above
Recommended: 2.50 GHz processor.

RAM
4 GB or onwards Recommended.

Hard Disk
25 GB.

Operating
System
Windows Service Pack 2, Windows Server
2003 Service Pack 1, or later versions.

Software
Mysql, PHP, Apache server or Wamp server.

Browser
Mozilla Firefox 2.0 /Internet Explorer 7.0
Onwards with Player Plug-in 9.0 or onwards.
4. UML DIAGRAMS
4.1 USE CASE DIAGRAM:
A Use case diagram determines the functionality and features of
the system from user’s perspective. In the use case diagram the use
cases are displayed as ovals. The actors are connected by the lines
to the use cases that they carry out. Use cases are placed in a
Rectangle but actors are not. This rectangle is the visual reminder
of the system boundaries and that the actors are outside the system.
Boundary for Use cases
For Actor
For use cases ( Known as oval)
FOR CONNECTION BETWEEN
ACTORS AND OVALS
Book Barter
State
Extends
City
User
Registration
Admin
Register Book
Extends
Category Type
Book Type
Visitor
Condition Detail
View Book
Feedback
4.2 ACTIVITY DIAGRAM:
An UML Activity Diagram depicts the dynamic behavior of a
system or part of a system through the flow of control between
actions that the system performs. It is similar to a flowchart except
that an activity diagram can show current flows.
Starting point of Activity Diagram
Action Node
(Represented task performed by system)
Join
(synchronize concurrent flows of a system )
Decision Node
(condition based control flow)
Exit point of Activity Diagram
A
Manage City
And
State
Manage User
Manage
FeedBack
Manage Post
View
View
View
Add
Update
Active/
Deactive
Delete
Block/
Unblock
View
Block/
Unblock
Stop
Edit Profile
Delete
Start
Home Page
Existing User
New User
FeedBack
Registration
Forgot
Password
Login
Enter
Details
Enter
Security
Answer
Enter
UserName
Password
NO
Validation
NO
Validation
NO
YES
Validation
YES
Register User
YES
Display Answer
Check User
Type
Admin
User
A
B
B
Search Book
View
Manage Post
Add
Update
Delete
Give FeedBack
Message
NO
Available
YES
Show Result
Stop
Edit Profile
4.3 CLASS DIAGRAM:
Class Diagram provides static view of a system .It does not show
the dynamic nature of the communications between the objects of
the classes in the diagram. The main elements of a class diagram
are boxes which are the icons used to represent classes each box is
divided into three horizontal parts.

The top part contain the name of the class.

The middle section contains the attributes of class. Attributes
are usually implemented as fields of the class.

The third section contains the operation or behavior of a
class an operation refers to what objects of the class can do.
It is usually implemented as a method of the class.
For representing class
Class Name
Attributes
Operations
For connecting one class with
another class
User
UserId : Int
UserName: String
Password: String
Super Class
checkValidation()
Derived
Class
FeedBack
Post
Serch
FeedBack: String
BookName: String
BookType: String
BookName: String
BookType: String
addBook()
Close()
serchBook()
Close()
addFeedBack()
Close()
SubClass
Admin
UserId : Int
UserName: String
Password: String
Super Class
checkValidation()
Derived
Class
Add
View
Manage
City: String State:
String
City: String
State: String
User: String
Post: String
FeedBack:
String
User: String
FeedBack: String
add()
Close()
manage()
Close()
view()
Close()
SubClass
4.4 SEQUENCE DIAGRAM:
A Sequence Diagram is used to show the dynamic communications
between objects during execution of task. It shows the temporal
order in which messages are sent between the objects to accomplish
the task.
In contrast to class diagram which shows the static structure of a
software component.
Arrow Represents an Event occur between
objects
Rectangle Represents Object in Diagram
Represents the Time occur between request and
response of the object.
Represents synchronous message
Back Arrow Represents Response of the Event to
the object.
5. DATA DICTIONARY
A Data Dictionary, or metadata repository, as defined in the IBM Dictionary of
Computing, is a "centralized repository of information about data such as
meaning, relationships to other data, origin, usage, and format. “The term can
have
one
of
several
closely
related
meanings
pertaining
databases and database management systems (DBMS):

A document describing a database or collection of databases

An integral component of a DBMS that is required to determine its
structure

A piece of middleware that extends or supplants the native data
dictionary of a DBMS
CITY:
Column
Type
Constraints
Comments
City Id
Int (3)
Primary Key
Store The City Id
State Id
Int (2)
Foreign Key
Store The State Id
City Name
Varchar (20)
Not Null
Store The City Name
Date Created
Timestamp
00-00-0000 00:00:00
Store The Time When City Is Created
Date Modified
Timestamp
00-00-0000 00:00:00
Store The Time When City Is Modified
to
BOOK DETAIL:
Column
Type
Constraints
Comments
Book Detail Id
Int (4)
Primary Key
Store The Book Id
Book Type Id
Int (2)
Foreign Key
Store The Book Type Id
Condition Detail Id
Int (2)
Foreign Key
Store The Condition Details Id
Registration Id
Int (6)
Foreign Key
Store The Registration Id
Title
Varchar (30)
Not Null
Store The Book Title
Book Image
Varchar (200)
Not Null
Store The Book Image
Author
Varchar (32)
Null
Store The Author Information
Publisher
Varchar (32)
Null
Store The Publisher Information
Description
Varchar (500)
Not Null
Store The Detail Of Book
Post On Type Id
Int (2)
Foreign Key
Store The Post On Type Id
Category Type Id
Int (2)
Foreign Key
Store The Category Type Id
Market Price
Int (4)
Null
Store The Market Price
User Price
Int (4)
Null
Store The User Price Of Book
Not Null
Store The Id Of Book Status
Is Book Detail Active Boolean (1)
Date Created
Timestamp
00-00-0000 00:00:00
Store The Time When Book Is Registered
Date Modified
Timestamp
00-00-0000 00:00:00
Store The Time When Book Detail Is Modified
BOOK TYPE:
Column
Type
Constraints
Comments
Book Type Id
Int (2)
Primary Key
Store The Book Type Id
Book Type Name
Varchar (20)
Not Null
Store The Book Type Name
Date Created
Timestamp
00-00-0000 00:00:00 Store The Book Type Date Created
Date Modified
Timestamp
00-00-0000 00:00:00 Store The Book Type Modified Date
MESSAGE:
Column
Type
Constraints
Comments
Message Id
Int (2)
Primary Key
Store The State Id
To Registration Id
Int (2)
Foreign Key
Store The To Registration Id
From Registration Id
Int (2)
Foreign Key
Store The From Registration Id
Name
Varchar (20)
Not Null
Store The Name Of A Person
Email Id
Varchar (32)
Not Null
Store The Email Id Of A Person
Mobile Number
Int (10)
Null
Store Mobile Number Id Of A Person
Message
Varchar (500)
Not Null
Store The User Message
Date Created
Timestamp
00-00-0000 00:00:00
Store Time When Message Is Registered
Date Modified
Timestamp
00-00-0000 00:00:00
Store Time When Message Is Modified
CATEGORY TYPE:
Column
Type
Constraints
Comments
Category Type Id
Int (2)
Primary Key
Store The Category Type Id
Category Type Name
Varchar (20)
Not Null
Store The Category Type Name
Date Created
Timestamp
00-00-0000 00:00:00
Store The Time When Category Created
Date Modified
Timestamp
00-00-0000 00:00:00
Store The Time When Category Modified
CONDITION DETAIL:
Column
Type
Constraints
Comments
Condition Detail Id
Int (2)
Primary Key
Store The Condition Type Id
Condition Detail Name
Varchar (20)
Not Null
Store The Condition Type Name
Date Created
Timestamp
00-00-0000 00:00:00
Store Time When Condition Created
Date Modified
Timestamp
00-00-0000 00:00:00
Store Time When Condition Modified
POST ON TYPE:
Column
Type
Constraints
Comments
Post On Type Id
Int (2)
Primary Key
Store The Post On Type Type Id
Post On Type Name
Varchar (20) Not Null
Date Created
Timestamp
Store The Post On Type Type Name
00-00-0000 00:00:00 Store The Time When Condition Created
Timestamp
Date Modified
00-00-0000 00:00:00 Store The Time When Condition Modified
STATE:
Column
Type
Constraints
Comments
State Id
Int (2)
Primary Key
Store The State Id
State Name
Varchar (20)
Not Null
Store The State Name
Date Created
Timestamp
00-00-0000 00:00:00
Store The Time When State Created
Date Modified
Timestamp
00-00-0000 00:00:00
Store The Time When State Modified
FEEDBACK:
Type
Constraints
Comments
Int (2)
Primary Key
Store The State Id
Registration Id
Int (2)
Foreign Key
Name
Varchar (20)
Not Null
Store The Name Of A Person
Email Id
Varchar (32)
Not Null
Store The Email Id Of A Person
Feedback
Varchar (500)
Not Null
Store The FeedBack
Is Feedback Active
Boolean (1)
Not Null
Store The FeedBack Status Active OR Not
Date Created
Timestamp
00-00-0000 00:00:00 Store The Time When Feedback Created
Date Modified
Timestamp
00-00-0000 00:00:00 Store The Time When Feedback Modified
Column
Feedback
Id
REGISTRATION:
Type
Constraints
Comments
Int (2)
Primary Key
First Name
Varchar (20)
Not Null
Store The User First Name
Last Name
Varchar (20)
Not Null
Store The User Last Name
Email Id
Varchar (32)
Not Null
Store The User Email Id
Password
Varchar (64)
Not Null
Store The User Password
Gender
Varchar (6)
Not Null
Store The User Gender
Address
Varchar (200)
Not Null
Store The User Address
City Id
Int (3)
Foreign Key
Store The User City
Occupation
Varchar (20)
Not Null
Store The User Occupation
Mobile Number
Int (10)
Not Null
Store The User Mobile Number
User Image
Varchar (200)
Not Null
Store The User Image
Is User Active
Boolean (1)
Not Null
Store The User Status Active OR Not
User Type
Int (2)
Not Null
Store The User Type
Date Created
Timestamp
00-00-0000 00:00:00
Store The Time When Registration Created
Date Modified
Timestamp
00-00-0000 00:00:00
Store The Time When Registration Modified
Column
Registration
Id
6. INPUT-OUTPUT DESIGN
6.1 RESPONSIVE WEB APP:
6.1.1 USER:
6.1.2 ADMIN:
6.2 ANDROID APP:
http://bookbarter.creartian.com/android.html
6.3 VISITOR:
6.3.1 HOME:
6.3.2 BOOKS:
6.3.2.1 BOOK INFORMATION:
6.3.2.2 FB SHARE:
6.3.2.3 SEND MASSAGE:
6.3.3 ABOUT:
6.3.4 CONTACT:
6.3.5 REGISTER:
6.3.6 LOGIN:
6.3.7 LOST YOUR PASSWORD:
6.4 USER:
6.4.1 REGISTERED BOOK:
6.4.2 POST BOOK:
6.4.3 MY ACCOUNT:
6.4.3.1 PROFILE DETAILS:
6.4.3.1.1 EDIT PROFILE:
6.4.3.2 SETTING:
6.4.3.3 MASSAGES:
6.5 ADMIN:
6.5.1 DASHBOARD:
6.5.2 USER:
6.5.2 CITY:
6.5.3 FEEDBACK:
7. VALIDATION
7.1 JQUERY:
7.1.1 FIRST, LAST NAME AND OCCUPATION:
7.1.2 EMAIL:
7.1.3 PASSWORD:
7.1.4 COFIRM PASSWORD:
7.1.5 MOBILE NUMBAR:
7.1.6 ADDRESS:
7.1.7 CPTCHA:
7.1.8 AGREE CONDITION:
7.1.9 IMAGE:
7.2 AJAX:
7.2.1 EMAIL:
7.2.2 MOBILE NUMBER:
7.2.3 LOST PASSWORD:
7.3 PHP:
7.3.1 EMAIL CONFIRMATION:
7.3.2 USERID PASSWORD NOT MATCH:
7.3.3 UPLOAD IMAGE:
7.3.3.1 SIZE:
7.3.3.2 TYPE:
7.4 .HTACCESS:
7.5 SEO:
7.5.1 RANK:
7.5.2 SPEED TEST:
http://seositecheckup.com/checkup/result/0ab9e65c4eae099bf6c
c6f6e23022355?url=http://bookbarter.creartian.com/
8. FUTURE SCOPE
 We will provide the facility of show offers with dynamic slider.
 We will provide the facility of allow Visitor to Online Conversation
with User.
 We will provide the facility of online payment for Buy Books.
9. BIBLIOGRAPHY
http://www.w3schools.com/
http://php.net/
http://jquery.com/
http://getbootstrap.com/
http://stackoverflow.com/
http://en.wikipedia.org/wiki/Main_Page
http://seositecheckup.com/
http://mattkersley.com/responsive/
10. CONCLUSION
ANY WORK MAY NOT ALWAYS BE
PERFECT:
There may be some defects or errors. We have taken enough care
to make the project User friendly and more interactive.
ANY SUGGESTION TO MAKE THIS
PROJECT MORE USEFUL IS ALWAYS
MOST
WELCOME.
BOOK BARTER
THANK
YOU

7.1.3 password

Transcription

Similar documents

A better bartering system

Antigone - Barter Theatre

here - Guild of Independent Currencies

read more - Tradebank International

DEVELOPMENT OF CREATIVE THINKING IN

Delivering Delivering - Tradebank International

Page 22 - Previews: Regional Theatre

TCPDF Example 021

BARTER NETWORK

& VI Economics