Ravi Furniture Project Blackbook

SYNOPSIS
Made By Ravishankar Pathak Page 1

INTRODUCTION
The project is for setting up a shop for sale of furniture. Depending upon the taste and purchasing
power of the local people, the unit will select the type and quality of furniture to be sold from the sales
unit. Attempt should be made to locate the unit in the market place, so that it attracts maximum number
of people. The proposed unit will sell furniture of moderate quality at affordable price for middle class
people. The unit will keep, on an average, one item each on display in the showroom and shall prepare
comprehensive catalogues with specifications, price lists etc. so that buyers can take on the spot
decisions. The unit will have necessary tie-up with nearby reliable SSI manufactures of furniture. The
unit will supply the products to the customers from the showroom. The unit has to take the shop
premises in a commercial area and get license from local Municipality Corporation to run the shop.
Provision for electricity, infrastructure arrangements etc. may take about two months before regular sales
of furniture from the shop start.
OBJECTIVE OF THE PROJECT

An online furniture shop that allows users to check for various furniture available at the online
store and can purchase furniture online. The project consists of list of furniture products displayed in
various models and designs. The user may browse through these products as per categories. If the user
likes a product he may add it to his shopping cart. Once user wishes to checkout he must register on the
site first. He can then login using same id password next time. Payment can be made through a credit
card or cash on delivery. Once the user makes a successful transaction he gets a copy of the shopping
receipt on his email id. Here we use php to make the entire frontend. The middle tier or code behind
model is designed in php. And SQL serves as a backend to store furniture lists and inventory data. Thus
the online furniture shopping project brings an entire furniture shop online and makes it easy for both
buyer and seller to make furniture deals.
THE OBJECTIVE OF THE SYSTEM ARE-
 Helps furniture shops to automate furniture selling online.

 Helps furniture shops to take credit cards payments.
 Customer easily purchase any product in cash payment.

PROBLEM WITH EXISTING SYSTEM
 Presently there are only few sites offering online furniture shopping.
 Online furniture shopping is not much popular and all types of product are not available on online
furniture shopping system.
 Time consumed in accessing customer records.
SOLUTION FOR EXISTING SYSTEM

The system is to make an online web portal for Furniture Shop, So that everyone can get information
about the Product, Customers can easily communicate with Sellers from anywhere. Sellers can easily
communicate with the Customers, and can keep records of every Customer easily and efficiently.
THE NEW SYSTEM HAS:-
 Simple GUI.
 Online registration.
THE ADVANTAGES OF THE SYSTEM ARE-
 Helps furniture shops to automate furniture selling online.
 Helps furniture shops to take credit cards payments.
TOOLS AND TECHNOLOGY USED
 TOOLS:-PHP: Hypertext Preprocessor (PHP) is a technology that allows software developers to

create dynamically generated web pages, in HTML, XML, or other document types, as per client
request. PHP is open source software.
 MySQL: MySql is a database, widely used for accessing querying, updating, and managing data
in databases.

 TECHNOLOGY:-HTML: – It is used for giving eye catching look to the website. And also
providing easy to use GUI.
 CSS: – CSS is cascading style sheet which is used to give designer look to HTML using the
external file.
 Java script: – Java script is used for client side scripting which can help in using validation on the
website and many more other functions

REQUIREMENT
ANALYSIS

Requirement Gathering
ANALYSIS PHASE
REQUIREMENT GATHERING
PROBLEM STATEMENT:-
Prently there are only few sites offering online furniture shopping.
Online furniture shopping is not much popular and all types of product are not available on online
furniture shopping system.
Time consumed in accessing customer records.
Which you are creating web site what is the reason behind it?What problem customer facing during
online shopping.If there is money problem or product (customer satisfaction) problem during online
shopping. Like customers have to visit many web site for different product.
FACT FINDING TECHNIQUES:-

Fact-finding is one of the important steps toward any system development. It is essential to
gather all the information and facts about an existing system to ensure that all strengths
and weakness are discovered. Thus when a new system is designed as many of the
weaknesses as possible are eliminated, whilst retaining the strengths. There are three
general techniques available; those used depend upon the particular circumstances!
USED FACT FINDING TECHNIQUES
A database developer normally uses several fact-finding techniques during a single database project
including:
observation
interview

OBSERVATION
Observation could be Formal or Informal. This is most effective when and analyst wants to obtain an
understanding of a system. This technique used when analyst wants either participates in or watches a
person perform activities to learn about the system.
As I visited many shops for getting their invoice, I’ve observe their work style, activity well. I see most of
their client system. But again for confidentially and software license they didn’t agree to show me their
server system.
By observing shops I greatly understand the system of Point of Sales and all of my lacking knowledge
about a POS become clear.
I watch their product cost in a sticker labeled in the products body, date validation in that label for date
oriented product and non-date oriented products. By observing one shop I got the idea for fixing product
rate in every product purchase invoice.

INTERVIEW
This technique of fact-finding is most popular, productive for good analysts and most probably
widely used. Interviews are a fact-finding technique where by the systems analysts collects information
from Individual fact to face. Interviewing can be used to find-facts; verify facts; clarify facts; general
enthusiasm etc.
1.Would you be interested in buying a restored piece of furniture for example a hand-
painted vintage table/storage unit, re-upholstered old chair or decorative objects for the
house or garden?
ANS: Yes or no.
2.How would you describe the interior of your home?
ANS: eco-friendly……
3.Where to you mostly buy your furniture and home furnishing?
ANS: next at home,marks and spencer…..
4.How do you shop for your furniture and home furnishing?
ANS: online,in store…..
5. Do you own a piece off old furniture that you would pay to have re-stored or painted?
ANS: no…..

HARDWARE AND SOFTWARE REQUIREMENTS TO RUN THE PROJECT.
HARDWARE REQUIREMENTS:-
1. Operating System:- Windows 7 and above
2. Processor:- i3
3. Installed Memory(RAM):- Minimum 1 GB
4. System Type:- 32-bit or 64-bit Operating System
SOFTWARE REQUIREMENTS:-
1. Front End: - HTML,CSS,JavaScripts.

2. Back End: - PHP, MySQL Server.
USER REQUIREMENTS:-
Each part of the user requirement intends to be as user friendly as possible. The fonts and buttons used
will be intended to be very fast and easy to load on web pages. The pages will be kept light in space so
that it won’t take a long time for the page to load.

PROJECT SCHEDULE

GANTT CHART
A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts illustrate the start and finish
dates of the terminal elements and summary elements of a project. Terminal elements and summary elements
comprise the work breakdown structure of the project.
Gantt Charts (Gantt Charts) are useful tools for analyzing and planning more complex projects. They:
 Help you to plan out the tasks that need to be completed.

 Give you a basis for scheduling when these tasks will be carried out.
 Help you to work out critical path for a project where you must complete it by a particular date.
When a project is under way. Gantt Charts help you to monitor whether the project is on schedule. If it is
not, it allows you to pinpoint the remedial action necessary to put it back on schedule. This chart is also used
in Information Technology to represent data that has been collected.
Pie Chart

Gantt Chart:

SOFTWARE
DEVELOPMENT
LIFECYCLE

Software Development Life Cycle (SDLC)
Software Development Life Cycle (SDLC) suggests a systematic approach to develop the
software application. The primary objective of implementing a standardized SDLC policy is to provide
coordinated excellent service, at reduced costs, to support the activity of customers and users of this
system. SDLC consist of fivephases as the following diagram:
a) Analysis: The Requirement gathering processes focused specifically on software. To understand the
nature of programs to be build, the software engineer must understand the information domain for the
software, as well as required function interface representation, behavior and performance.
b) Design: The Design translates the requirements in to the representation of the software that can be
assessed for quality before coding begins. Design is actually multistep process that focuses on four
distinct attributes of a program. Data Structure, software Architecture, interface representation and
procedural details.

c) Coding: The Design must be translated into a machine readable form and this transformation is called
Coding. If design is performed in a detailed manner, coding can be done very easily.
d) Testing: Once code has been generated, program, testing begins, this testing process focus on logical
internals of the software ensuring that all statements have been tested to uncover errors and ensure
that defined input will produce actual results that agree with the required result that agree with the
required result as stated in SRS.
e) Support: Software will undergo changes after it is delivered to the customer. Change will occur
because errors have been raised. Software must be adapted to accommodate changes in the external
environment.
The Unified Modeling Language (UML)
It is used to communicate the Business System’s processes to the various stakeholders, it is a
means of expression and does not contribute to the way a business system or process works. In a major
and positive development, various competitors joined hands and started working together. This language
became the basis of Business Modeling. Business modeling techniques can be used to capture users’
requirements, going through analysis, design and development. When designing a system, models are
required to view the As Is processes and to convert them into the To Be processes. The design method in
use for the particular system will require a language to express all interim documents and diagrams.

FEASIBILITY

FEASIBILITY STUDY
The main purpose of feasibility analysis is to check the economic viability of the proposed system.
The result of the feasibility study will indicate whether to proceed with the proposed system or not. If the
results of the feasibility study are positive, then we can proceed to develop a system otherwise project
should not be pursued. Preliminary investigation examine project feasibility, the likelihood the system
will be useful to the organization. The main objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules and debugging old running system. All
system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility
study portion of the preliminary investigation:
 Operational Feasibility
 Technical Feasibility
 Economical Feasibility
 Shedule Feasibility
OPERATIONAL FEASIBILITY:
Operational feasibility study tests the operational scope of the system to be developed.
The proposed system must have high operational feasibility. It refers to the feasibility of the product to
be operational. Some products may work very well at the design a implementation but many fail in the
real time environment. It introduces the study of human resources required and their technical expertise.
This product is operationally feasible as it is designed specifically for EGovernance, This

provides consistent and integrated data management. It also provides information at all levels of people.
 In case of any mistakes while registering, the user is made aware about the error messages.
 The usability will be high.
 Response time of the website is fast.
 The website is developed with clear and easy to understand navigation that enables users to find
information quickly.

 The website itself does major task of the user, the only work for the user is to click on the
controls .
 Thus, the proposed system is operationally feasible.
TECHNICAL FEASIBILITY:
The technical feasibility assessment is focused on gaining an understanding of the present

technical resources and their applicability to the expected needs of the proposed system. It is an
evaluation of the hardware and software and how it meets the need of the proposed system.
This system will be developed using html,css,javascripts technology. As we require some time to
learn these technologies, all these are easy to learn and can develop system very rapidly.
After developing and deploying the system, any user can view this site on the Internet.It is a web
based user interface thus it provides an easy access to the users.Permission to the users would be granted
based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and
security.Thus, the proposed system is technically feasible. A system has been built by concentratir on the
graphical uses interface concepts.the application can also be handled very easily with a novice uses. The
overall time that a user needs to get trained is less than 15 minutes.The system has been added with
features of menu device and button interaction methods,which makes him the master as he starts working
through the environment.
ECONOMICAL FEASIBILITY:
Higher level of automation most often requires more funds. Hence based on the hardware and
software specification a desirable alternative costs and benefits to see if the investment made in
creating/developing a new system is costlier or more beneficial. Financial benefits must equal or exceed
the costs.Economical feasibility determines whether there are sufficient benefits in creating to make the
cost acceptable,or is the cost of the system too high. As this signifies cost-benefit analysis and savings.
On the behalf of the cost-benefit analysis, the proposed system is feasible and is economical regarding its
pre-assumed cost for making a system.We classified the costs of online shop according to the phase in

which they occur. As we know that the system development costs are usually one-time costs that will not
recur after the project has been completed. To assure this one must estimate the following:-
1. Personal costs
2. Computer usage
3. Supply and equipments costs
4. Cost of any new computer equipments and software
5. The cost of hardware and software is affordable.
6. High increase in the amount of profit earned by going global.
7. Easy and cheap maintenance of the system possible.
8. Very cheap price for going global.
So Economic Feasibility in this project can be calculated as

Items Cost
Cost for electricity and cooling 2,000
Supply and equipments costs 10,000
Rent for workspace 10,000
Internet connection charges 5,000
Travelling Charges 3,000
Design and coding 10,000
Miscellaneous Charges 20,000
Total Charges 60,000
Benefit= No of Years the project will work * Cost saved on

employees ,books and maintenance
= 2 * 60,000
=1,20,000
Where cost of one employee per month Rs 2,000 will be reduced due to automation.
Cost Benefit=Benefit / Cost

=1,20,000/60,000
=2
Therefore, the cost benefit is 2 which is more than 1.2.So this project is economically feasible.
Schedule Feasibility
Schedule Feasibility is defined as the probability of a project to be completed within its scheduled
time limits, by a planned due date. If a project has a high probability to be completed on-time, then its
schedule feasibility is appraised as high. In many cases a project will be unsuccessful if it takes longer
than it was estimated: some external environmental conditions may change, hence a project can lose its
benefits, expediency and profitability. If a work to be accomplished at a project does not fit the
timeframes demanded by its customers, then a schedule is unfeasible (amount of work should be reduced
or other schedule compression methods applied).
If the project managers want to see their projects completed before they can lose their utility, they
(project managers) need to give proper attention to controlling their schedule feasibility: to calculate and
continually reexamine whether it is possible to complete all amount and scope of work lying ahead,
utilizing the given amount of resources, within required period of time.
The below table will show how the schedule of project will go
Work Type Days

Requirements gathering 1 week
Planning 1 week
Resource Gathering 1 week
Coding and Design 4 week
Deployment Over Play Store & 2 Week
website
Testing & Delivery 1 Week
Total Schedule Time 10 Weeks

This project is based on incremental model so rapid changes in the project is supported .The following
schedule contains 10 days grace period depending on any changes made by client .Going late form
schedule will be deduction of total cost by 2 % per week till 4 weeks and after that project agreement
will be declared as rejected.
Completion of project on time will be considered as feasible otherwise not feasible

REQUIREMENT
SPECIFICATIONS

Hardware and Software Requirements of the project:-
1. Hardware Requirements:-
 Operating System:- Windows 7 and above
 Processor:- i3
 Installed Memory(RAM):- Minimum 1 GB
 System Type:- 32-bit or 64-bit Operating System
2. Software Requirements:-
 Front End: - HTML,CSS,JavaScripts.
 Back End: - PHP, MySQL Server.
TOOLS AND TECHNOLOGY USED
 TOOLS:-PHP: Hypertext Preprocessor (PHP) is a technology that allows software developers to

create dynamically generated web pages, in HTML, XML, or other document types, as per client
request. PHP is open source software.
 MySQL: MySql is a database, widely used for accessing querying, updating, and managing data
in databases.
 TECHNOLOGY:-HTML: – It is used for giving eye catching look to the website. And also
providing easy to use GUI.
 CSS: – CSS is cascading style sheet which is used to give designer look to HTML using the
external file.
 Java script: – Java script is used for client side scripting which can help in using validation on the
website and many more other functions

.
DESIGN PHASE

ENTITY RELATIONSHIP DIAGRAM
Entity–relationship model (ER model) in software engineering is an abstract way to describe a
database. Describing a database usually starts with a relational database, which stores data in tables.
An ERD is a logical representation of an organization’s data, and consists of three primary components:
 Entities
Major categories of data and are represented by rectangles. An Entity is a person, place, object, event,
or concept that an organization wants to maintain data on. Each entity has a unique identity that
differentiates it from other entities. A point of distinction must be made between entity types and entity
instances. An entity type is a collection of entities that share common properties. Entity types are also
known as entity classes. An entity instance is an individual occurrence of an entity type. A data model
describes an entity type only once; however there may be numerous instances of that type within a
database.
 Attributes –
Characteristics of entities and are listed within entity rectangles. When defining an attribute, an
analysis should state why the attribute is important, what is included in the attribute’s value, the source
of the value, and whether or not that value can change. Again, a sound understanding of an
organization’s business should assist the analyst in compiling relevant attributes.
 Relationships
Relationships between entities and are represented by lines.Relationships link the various components
in an E-R diagram together. It is usually best to think of relationships as verbs and entities as nouns,
which together comprise a complete sentence. The three most common relationship degrees are: Unary
(between instances of one entity type), Binary (between instances of two entity types), and Ternary
(between three entity types).

Symbol Used
Sr.No
Symbol Name Description
1 Rectangles Represent entity sets
2 Ellipses Represent attributes
3 Represent relationship sets
Diamonds
Link attributes to entity sets

4 and entity sets to
Lines relationship set
Indicate total participation

Double lines of an
entity in a relationship set
5
6 Represent weak entity sets
Double
rectangles

USE CASE DIAGRAM
A use case diagram at its simplest is a representation of a user's interaction with the system and
depicting the specifications of a use case. A use case diagram can portray the different types of users of a
system and the various ways that they interact with the system. This type of diagram is typically used in
conjunction with the textual use case and will often be accompanied by other types of diagrams as well.
Use case diagrams depict:
1) Actor
An actor portrays any entity that performs certain roles in system. An actor in use case diagram
interacts with the use case. It is shown outside the system hierarchy. It is denoted by
2) Use case
A use case is a visual representation of a business functionality in a system .each use case
is the sequence of transaction performed by the system. It is shown as ellipse in use case diagram. It
is denoted by
3) System Boundary
A system boundary defines the scope of what a system will be. a system cannot have
infinite functionality. A system boundary defines the limits of the system. The system boundary is
shown as a rectangle spanning all the use case in the system.
It is denoted by
4) Association
This is used to show the participation of actor in use case.
It is denoted by
Relationships in Use Case-

1) Includes
Include is used when 2 or more share some common portion in the flow of events. The stereotype
<<include>>identifies relationship include. The arrowhead points towards child use case which is
included in the parent use case.
2) Extend
In an extend relationship between two use cases. The child use case adds to the existing
functionality characteristics of the parent use case.
It is represented as <<extend>>.
3) Generalization
A generalization relationship is also a parent child relationship between the two use cases. The
child use case in the generalization relationship has the underlying business process meaning but is an
enhancement of the parent use case.
System Use Case:

DATA FLOW DIAGRAM
A data flow diagram is a graphical view of how data is processed in a system in terms of input and output
The Data flow diagram (DFD) contains some symbol for drawing the data flow diagram.
Data flow diagram symbol
Context level DFD – 0 level
The context level data flow diagram (dfd) is describe the whole system. The (o) level dfd describe the
all user who operate the system.

1st Level Admin Side DFD
The Admin side DFD describe the functionality of Admin, Admin is a owner of the website. Admin can
first add category of item and then add items by category wise. and admin can manage order and payment
detail.
1st Level Admin Side DFD

2nd Level Admin side DFD
3rd Level Admin side DFD

4th Level Admin side DFD
1st level – User side Data flow Diagram

The user is all people who operate or visit our website. User is a customer of a website. User can
first select product for buy, user must have to register in our system for purchase any item from our
website. after register he can login to site and buy item by making online payment through any bank debit
card or credit card

1st Level User Side DFD

2nd Level User Side DFD
3rd level User side DFD

CLASS DIAGRAM
The class diagram is the main building block of object oriented modeling. It is used both for general
conceptual modeling of the systematic of the application, and for detailed modeling translating the models into
programming code. Class diagrams can also be used for data modeling. The classes in a class diagram represent
both the main objects, interactions in the application and the classes to be programmed.
In the diagram, classes are represented with boxes which contain three parts:
 The upper part holds the name of the class

 The middle part contains the attributes of the class
 The bottom part gives the methods or operations the class can take or undertake
In the design of a system, a number of classes are identified and grouped together in a class diagram which helps to
determine the static relations between those objects. With detailed modeling, the classes of the conceptual design
are often split into a number of subclasses.
Multiplicity:
A. 0..1 no instance or one instance

B. 1Exactly one instance
C. 0..* Zero or more instance
D. 1..* One or more instance
Elements of Class Diagram:
Class
The class name typically has the first alphabet capitalized. If

you class has more than more one
word and capitalize the first alphabet of both
Awolirsdtsoafnadttrjoibinuttehseotfwyoo.uFrocrlaesgs.:gCouesstionmh
List of Attributes eerre. The
Syntax is:attribute:Type=’default value (if any)’ For eg.customerId:int
A list of methods goes here.The Syntax is:

List of Methods MethodName(list of param.)”Return type For e.g.
string createBill();

TABLES AND DATADICTIONARY

CATEGORY TABLES
Column name Data type Key constraint
Cat_id int Primary key not null
Cat_name Char(20) Not null
PRODUCT TABLES
Prod_id int Primary key not null
Cat_id int Foreign key not null
Prod_name Char(20) Not null
Prod_descp Char(40) Null
Price double Not null
ADMIN LOGIN TABLES
Colu_mn name Data type Key constraint
User_id int Primary key not null
password Char(20) Not null
LOGIN TABLES

User_id int Primary key not null
password Char(20) Not null
STORE TABLES
Order_no int Primary key not null
Report Char(20) null
USER TABLES
Column name Data type Key constraint Extra
User_id Int Primary key not null Auto_increment
Password Char(20) Not null
User name Char(20) Not null
Address Char(40) Not null
Date of birth Date Not null
Phone no Char(10) Not null
email Char(30) Not null

SELL TABLES
Prod_id int Not null
Prod_name Char(20) Not null
Price Double Not null
Items Int Not null
User_id Int Not null
Purchase_date Date Not null
Order_no Int Not null

TESTING

Testing
Introduction
Software testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding. In fact, testing is the one step in the software engineering
process that could be viewed as destructive rather than constructive.
A strategy for software testing integrates software test case design methods into a well-planned
series of steps that result in the successful construction of software. Testing is the set of activities that can
be planned in advance and conducted systematically. The underlying motivation of program testing is to
affirm software quality with methods that can economically and effectively apply to both strategic to both
large and small-scale systems.

SCREEN LAYOUTS

DEPLOYMENT

DEPLOYMENT
In our project deployment of application is done automatically by online furniture shopping.
It is very easy to run website and an easy to understand for the user and admin.
An website is generated automatically is directly run through any window system.

Maintenance
It is easy to maintain an online system and maintaining timely updates for new features by
simply creating an new activity file within our project.
Maintenance of database is very simple sql keeps track of database and changes in the
database can be backup using export and import feature of sql DB.
A backup is needed to be taken periodically to maintain complete security and clean performance.

BENEFITS
• Easy to access and user friendly
• Real time database facility
• Online Booking , fare check and availability of seat check
• One click Google Sign In
LIMITATIONS
• Time consumed accessing in customer record
• Not Accessible without Internet
FUTURE IMPROVEMENT
• Online payment through debit card, Credit Card and Net Banking
• Discount Facility to regular customer

Coding Part
Index.php
<?php include_once("header.php"); ?>
<link href="pagecss.css" rel="stylesheet" type="text/css" />
<tr>
<td align="left" valign="top" style="padding-right:8px; padding-left:8px;"><table
width="100%" border="0" align="center" cellpadding="0" cellspacing=" 0">
<tr>
<td width="22%" height="495" align="left" valign="top"><?php
include_once("categories.php"); ?></td>
<td width="53%" align="left" valign="top"><table width="99%" border="0"
align="center" cellpadding="0" cellspacing=" 0">
<tr>
<td height="45" colspan="3" align="left" valign="middle" style="padding-
left:10px;" class="header12">Featured Products</td>
</tr>
<?php $tbl_name="products"; //your table name
// How many adjacent pages should be shown on each side?
$adjacents = 2;
$query = "SELECT COUNT(*) as num from $tbl_name where
feature=1 and parent_id=0";

$total_pages = mysql_fetch_array(mysql_query($query));
$total_pages = $total_pages[num];
/* Setup vars for query. */
$targetpage = "index.php"; //your file name (the name of this file)
$limit = 12;
/*echo $_GET['page'];
exit(); */ //how many items to show per
page
$page = $_GET['page'];
if($page)
$start = ($page - 1) * $limit; //first item to display on this page
else
$start = 0; //if no page var is
given, set start to 0
/* Get data. */
$pro = "SELECT * FROM $tbl_name where feature=1 and parent_id=0 order by pid DESC
LIMIT $start, $limit";
$prores = mysql_query($pro);
/* Setup page vars for display. */

if ($page == 0) $page = 1; //if no page var is given, default to
1.
$prev = $page - 1; //previous page is page - 1
$next = $page + 1; //next page is page + 1
$lastpage = ceil($total_pages/$limit); //lastpage is = total pages / items per page,
rounded up.
$lpm1 = $lastpage - 1; //last page minus 1
/*
Now we apply our rules and draw the pagination object.
We're actually saving the code to a variable in case we want to draw it more than once.
*/
$pagination = "";
if($lastpage > 1)
$pagination .= "<div class=\"pagination\">";
//previous button
if ($page > 1)
$pagination.= "<a href=\"$targetpage?page=$prev\">« previous</a>";
else
$pagination.= "<span class=\"disabled\">« previous</span>";
//pages
if ($lastpage < 7 + ($adjacents * 2)) //not enough pages to bother breaking it up

{
for ($counter = 1; $counter <= $lastpage; $counter++)
if ($counter == $page)
$pagination.= "<span class=\"current\">$counter</span>";
else
$pagination.= "<a
href=\"$targetpage?page=$counter\">$counter</a>";
elseif($lastpage > 5 + ($adjacents * 2)) //enough pages to hide some
//close to beginning; only hide later pages
if($page < 1 + ($adjacents * 2))
for ($counter = 1; $counter < 4 + ($adjacents * 2); $counter++)
$pagination.= "<span
class=\"current\">$counter</span>";
else
$pagination.= "<a

$pagination.= "...";
$pagination.= "<a href=\"$targetpage?page=$lpm1\">$lpm1</a>";
$pagination.= "<a
href=\"$targetpage?page=$lastpage\">$lastpage</a>";
//in middle; hide some front and some back
elseif($lastpage - ($adjacents * 2) > $page && $page > ($adjacents * 2))
$pagination.= "<a href=\"$targetpage?page=1\">1</a>";
for ($counter = $page - $adjacents; $counter <= $page + $adjacents;
$counter++)
else
$pagination.= "<a
$pagination.= "<a href=\"$targetpage?page=$lpm1\">$lpm1</a>";

$pagination.= "<a
href=\"$targetpage?page=$lastpage\">$lastpage</a>";
//close to end; only hide early pages
else
for ($counter = $lastpage - (2 + ($adjacents * 2)); $counter <=
$lastpage; $counter++)
else
$pagination.= "<a
//next button

if ($page < $counter - 1)
$pagination.= "<a href=\"$targetpage?page=$next\">next »</a>";
else
$pagination.= "<span class=\"disabled\">next »</span>";
$pagination.= "</div>\n";
} if($total_pages<=0)
{ ?>
<tr>
<td align="left" valign="top"> </td>
</tr>
<tr>
<td align="center" valign="top"><strong>There Are No Featured
Products</strong> </td>
</tr>
<tr>
<td align="left" valign="top"> </td>
</tr>
<?php } else {
$cnt=0;
while($prorow=mysql_fetch_array($prores)) {
$cnt++;
if($cnt%1==1)

echo "<tr>";
if($cnt%3==1)
echo "</tr><tr><td align=\"right\" colspan=\"3\"> </td></tr><tr>";
?>
<form action="addtocart.php" name="formno<?php echo $prorow['pid']; ?>"
method="post">
</form>
<td align="left" valign="top"><table width="165" border="0" align="left"
cellpadding="0" cellspacing=" 0">
<tr>
<td align="left" valign="top" style="border:#CCCCCC solid 1px;"><table
width="95%" border="0" align="center" cellpadding="0" cellspacing=" 0">
<tr>
<td height="20" colspan="2" align="center" valign="middle"><a
href="detailspage.php?productid=<?php echo $prorow['pid']; ?>&category_id=<?php echo
$prorow['cat_id']; ?>" class="menu7"> <?php echo $prorow['pname'] ?></a></td>
</tr>
<tr>

<td colspan="2" align="center" valign="middle"><img
src="images/products/detail/<?php echo $prorow['pid']; ?>.jpg" width="100" height="137"
/></td>
</tr>
<tr>
<td height="25" align="center" valign="middle" class="text_2"
colspan="2"> </td>
</tr>
<tr>
<td height="25" align="center" valign="middle" class="text_2"
colspan="2"><a href="detailspage.php?productid=<?php echo $prorow['pid'];
?>&category_id=<?php echo $prorow['cat_id']; ?>"><img src="images/details.gif"
width="64" height="21" border="0" /></a></td>
</tr>
<tr>
<td height="8" colspan="2" align="center" valign="middle"><input
type="hidden" name="prodid" value="<?php echo $prorow['pid']; ?>" />
<input type="hidden" name="prodprice" value="<?php echo
$prorow['oprice'] ?> " />
<input type="hidden" name="prodname" value="<?php echo
$prorow['pname']; ?>" />
<input id="qty" size="1" name="qty" type="hidden" value="1" />
</td>
</tr>

</table></td>
</tr>
</table></td>
<?php } }?>
<tr>
<td align="right" colspan="3"> </td>
</tr>
<tr>
<td align="right" colspan="3"><?php=$pagination?></td>
</tr>
</table></td>
<td width="25%" align="left" valign="top"><?php include_once("rightside.php"); ?>
<form name="form1" method="post" action="">
<p> </p>
<p> </p>
</form></td>
</tr>
</table></td>
</tr>
<?php include_once("footer.php"); ?>
Header.php
<?php session_start();

ob_start();
include_once("dbconnect.php");
?>
<link rel="shortcut icon" href="images/images.jpeg" />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Welcome to Furniture Showroom</title>
<style type="text/css">

</style>
<link href="css.css" rel="stylesheet" type="text/css" />
<script type="text/javascript" src="js/quenty.js"></script>
<script>
function searchvalid()
var d=document.king;
if(d.keyword.value=="")
alert("Please Enter Keyword For Search");
d.keyword.focus();
return false;
return true;
</script>
</head>
<body>

<table width="980" border="0" align="center" cellpadding="0" cellspacing=" 0">
<tr>
<td height="1034" align="left" valign="top"><table width="100%" border="0"
cellspacing=" 0" cellpadding="0">
<tr>
<td height="70" align="left" valign="middle"><table width="100%" border="0"
<tr>
<td width="69%" height="110" rowspan="2" align="left" valign="middle"><img
src="images/logo3.jpg" width="640" height="100" /></td>
<td height="64" colspan="2" align="left" valign="middle"><table width="60%"
border="0" align="center" cellpadding="0" cellspacing=" 0">
<tr>
<td width="19%" rowspan="2" align="center" valign="middle"><img
src="images/shopping-cart.gif" width="13" height="11" /></td>
<td width="81%" height="25" align="left" valign="middle" class="spacer">
Shopping Cart:</td>
</tr>
<tr>
<td align="left" valign="top">now in your cart<a href="shoppingcart.php"
class="menu1"><strong> <?php echo $_SESSION['count']; ?> items</strong></a></td>
</tr>
</table></td>

</tr>
<tr>
<form action="search.php" method="get" name="king">
<td width="24%" align="left" valign="middle" style="padding-
left:20px;"><strong>Search :</strong>
<input type="text" name="keyword" value="<?php echo $_GET['keyword'];?>"
/></td>
<td width="7%" align="left" valign="middle"><input type="image"
src="images/go_botton.gif" width="50" height="23" onClick="return searchvalid();" /></td>
</form>
</tr>
</table></td>
</tr>
<tr> <?php if($_SESSION['compuserid']=="") { ?>
<a href="contactus.php" class="menu7">Contact
us </a>
<?php } else { ?>
<a href="logout.php" class="menu7">Logout </a>
<?php } ?>
</td>
</tr>
</table>
<a href="contactus.php" class="menu7"> </a> </td>

</tr>
<tr>
<td align="left" valign="top" style="padding-top:10px;"><table width="100%"
border="0" cellspacing=" 0" cellpadding="0">
<tr>
align="center" cellpadding="0" cellspacing=" 0">
<tr>
<td width="1%" align="left" valign="top"><img src="images/flash_td_top_left.gif"
width="6" height="6" /></td>
<td width="98%" align="left" valign="top"
background="images/flash_td_top_spacer.gif"> </td>
<td width="1%" align="left" valign="top"><img
src="images/flash_td_top_right.gif" width="6" height="6" /></td>
</tr>
<tr>
<td align="left" valign="top" background="images/flash_td_left_spacer.gif"> </td>
<td align="left" valign="top"></td>
<td align="left" valign="top" background="images/flash_td_right_spacer.gif">
</td>
</tr>
<tr>

<td align="left" valign="top"><img src="images/flash_td_bottom_left.gif"
<td align="left" valign="top"
background="images/flash_td_bottom_spacer.gif"></td>
<td align="left" valign="top"><img src="images/flash_td_bottom_right.gif"
</tr>
</table></td>
<tr>
<td align="center" valign="middle"><a href="#"></a></td>
</tr>
<tr>
<td height="5" align="center" valign="middle"> </td>
</tr>
<tr>
<td align="center" valign="middle"><a href="#"></a></td>
</tr>
</table></td>
</tr>
</table></td>
</tr>

REFERENCES
&
BIBILOGRAPHY

Conclusion
A project means a set of works done in a specific period of time.during this time of
The project we have taken help from several books,documents,papers,journals,websites etc.
For Reference
www.google.com
www.tutorials.com
www.stackoverflow.com
For Video Tutorials and examples Files

www.youtube.com
www.github.com

Ravi Furniture Project Blackbook

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

Ravi Furniture Project Blackbook

Transféré par

Droits d'auteur :

Formats disponibles

SYNOPSIS

Made By Ravishankar Pathak Page 1

OBJECTIVE OF THE PROJECT

 Helps furniture shops to automate furniture selling online.

Made By Ravishankar Pathak Page 2

SOLUTION FOR EXISTING SYSTEM

TOOLS AND TECHNOLOGY USED

 TOOLS:-PHP: Hypertext Preprocessor (PHP) is a technology that allows software developers to

Made By Ravishankar Pathak Page 3

Made By Ravishankar Pathak Page 4

Made By Ravishankar Pathak Page 5

FACT FINDING TECHNIQUES:-

USED FACT FINDING TECHNIQUES

Made By Ravishankar Pathak Page 6

Made By Ravishankar Pathak Page 7

Made By Ravishankar Pathak Page 8

1. Front End: - HTML,CSS,JavaScripts.

Made By Ravishankar Pathak Page 9

Made By Ravishankar Pathak Page 10

 Help you to plan out the tasks that need to be completed.

Made By Ravishankar Pathak Page 11

Made By Ravishankar Pathak Page 12

Made By Ravishankar Pathak Page 13

system. SDLC consist of fivephases as the following diagram:

software, as well as required function interface representation, behavior and performance.

Made By Ravishankar Pathak Page 14

required result as stated in SRS.

The Unified Modeling Language (UML)

It is used to communicate the Business System’s processes to the various stakeholders, it is a

Made By Ravishankar Pathak Page 15

Made By Ravishankar Pathak Page 16

This product is operationally feasible as it is designed specifically for EGovernance, This

Made By Ravishankar Pathak Page 17

The technical feasibility assessment is focused on gaining an understanding of the present

Made By Ravishankar Pathak Page 18

So Economic Feasibility in this project can be calculated as

Benefit= No of Years the project will work * Cost saved on

Made By Ravishankar Pathak Page 19

Work Type Days

Made By Ravishankar Pathak Page 20

Completion of project on time will be considered as feasible otherwise not feasible

Made By Ravishankar Pathak Page 21

Made By Ravishankar Pathak Page 22

TOOLS AND TECHNOLOGY USED

 TOOLS:-PHP: Hypertext Preprocessor (PHP) is a technology that allows software developers to

Made By Ravishankar Pathak Page 23

Made By Ravishankar Pathak Page 24

Made By Ravishankar Pathak Page 25

1 Rectangles Represent entity sets

2 Ellipses Represent attributes

3 Represent relationship sets

Link attributes to entity sets

Indicate total participation

6 Represent weak entity sets

Made By Ravishankar Pathak Page 26

Use case diagrams depict:

Relationships in Use Case-

Made By Ravishankar Pathak Page 28

Made By Ravishankar Pathak Page 29

Data flow diagram symbol

Context level DFD – 0 level

Made By Ravishankar Pathak Page 31

1st Level Admin Side DFD