A Project Report ON Online Market

A PROJECT REPORT
ON
ONLINE MARKET
A PROJECT
Submitted in partial fulfillment of the requirements for the award of the degree
OF
BACHELOR OF COMPUTER APPLICATION

Submitted By
Vikramjeet Singh
(07890202015)
UNDER THE SUPERVISION OF:

Mr. Amandeep Singh Arora
(Asst.Professor SGTBIMIT)
SRI GURU TEGH BHAHADUR INSTITUTE OF MANAGEMENT AND

INFORMATION TECHNOLOGY
GURUDWARA NANAK PIAO CAMPUS G.T. KARNAL ROAD,DELHI-110033
(Approved By AICTE Ministry of HRD, Govt. of India)
AFFILIATED TO GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY,DELHI
2015-2018
CANDIDATES’S DECLARATION
I hereby certify that the work which is being presented in the project is the project
report entitled ONLINE MARKET in partial fulfilment of the requirement for the
awards of the degree of “BACHELOR OF COMPUTER APPLICATION “ ,
submitted in the Sri Guru Tegh Bahadur of Management and Information
Technology,Guru Gobind Singh Indraprastha University is an authentic record of
my work carried out under the supervision of Mr. Amandeep Singh Arora
The matter embodied in this project report has not been submitted by us for the award
of my other degree or diploma.
Date: Vikramjeet Singh

CERTIFICATE
This is to certify that the project entitled: “ONLINE MARKET” done by Mr.
Vikramjeet Singh University Enrolment Number 03490202014 is an authentic work
carried out by them at Sri Guru Tegh Bahadur Institute Of Management &
Information Technology. The matter embodied in this project work has not been
submitted earlier for the award of any degree or diplomas to the best of my
knowledge and belief .The suggestion as approved by the faculty was duly
incorporated.
DATE:
HOD: Dr. Harshita Tuli
Guide: Mr. Amandeep Singh Arora

ACKNOWLEDGEMENT
I sincerely thank Mr. Amandeep Singh Arora Assistant Professor Sri Guru Tegh
Bahadur Institute of Management & Information Technology for giving me the
opportunities to work under their able guidance.
As a write through these pages my mind recollects their invaluable suggestions, their
encouragement at every step which was my guiding light.
Last but not the least my sincere thanks to my family and my friends for their valuable
suggestions at every time.
Place: New Delhi Vikramjeet Singh

BCA – 6th SEM.
TABLE OF CONTENT
Chapter Topic Page

No. No.
1. INTRODUCTION
1.1 Introduction to the Project 11
2. REQUIREMENT & ANALYSIS
2.1 Software Requirement Specification 13
2.2 Software Development Life Cycle 13
2.3 Project Category 17
2.4 Software Requirements 18
2.5 Technologies Used 18
2.6 Use Case Diagram 19
3 SOFTWARE DESIGN
3.1 Introduction 21
3.2 High Level/Detailed Design (HLD/DD) 21
3.3 Context Diagram(Level 0) 22
3.4 Data Flow Diagram (Level 1) 23
3.5 Data Flow Diagram (Level 2) 24
4 DATABASE DESIGN
4.1 Introduction 29
4.2 Database Field Specifications 29
4.3 Entity-Relationship Diagram 31
5 TESTING
5.1 Introduction 33
5.2 Methods adopted for testing 33
5.3 Test cases 34

6 ROLES AND RESPONSIBILITIES
6.1 Project roles and responsibilities 37
7 CONCLUSION & ACHIEVMENTS 39
APPENDICES Coding & Snapshots 40
BIBLOGRAPHY 55
LIST OF FIGURES
Figure Page
Number
Figure 1: The Waterfall Model 15
Figure 2: Requirement Analysis 18
Figure 3:Use Case 20
Figure 4: Context Flow Diagram 23
Figure 5: Data Flow Diagram Level-1 24
Figure 6: Data Flow Diagram Level-2 for Admin 25
Figure 7: Data Flow Diagram Level-2 for User 26
Figure 8: Data Flow Diagram Level-2 for Login 27
Figure 9: E-R Diagram 31
LIST OF TABLES
Table Page
Number
Admin 29
Register 29
Card 30
LIST OF SCREENSHOTS
Table Page Number

Screenshot 1: Home Page 46
Screenshot 2: Login Page 46
Screenshot 3:Register Page 47
Screenshot 4:Mens Collection Page 47
Screenshot 5:Womens Collection Page 48
Screenshot 6:Electronics Collection Page 48
Screenshot 7:Add to Cart Page 49
Screenshot 8:Product View Page 49
Screenshot 9:Mode of Payment Page 50
Screenshot 10:Cash on Delivery Page 50
Screenshot 11: Credit Card Page 51
Screenshot 12:Debit Card Page 51
Screenshot 13:Internet Banking Page 52
Screenshot 14:Thanking you Page 52
CHAPTER-1
INTRODUCTION
10
1.1 Introduction to the Project
Online Market is a form of electronic commerce which allows consumers to directly buy
goods or services from a seller over the Internet using a web browser. Consumers find a
product of interest by visiting the website of the retailer directly or by searching among
alternative vendors using a shopping search engine, which displays the same product's
availability and pricing at different e-retailers. As of 2016, customers can shop online using a
range of different computers and devices, including desktop computers, laptops, tablet
computers and Smartphone’s.
1.1.1 Objective and Scope of the Project
The main purpose of this is to provide customer variety of range of products.

The goals of our website are to provide a Convenience of shopping .
11
CHAPTER-2
REQUIREMENT ANALYSIS
12
2.1 SOFTWARE REQUIREMENT SPECIFICATION
If a document that completely describes what the proposed software should do without
describing how the software will do it, The basic goal of requirements specific to produce the
requirements, which describes the complete external behavior of the proposed software.
However, producing the report is said to be done.
2.1.1 INTRODUCTION
The introduction states the goals and objectives of the software describing it in the context of the
computer -based system. Actually the introduction may be nothing more than the software
people of the planning document.
2.1.2 FUNCTIONAL DESCRIPTION

The project also provides the facility to contact the registered user easily without any admin
interaction. If you find an existing entry meeting your requirement, then you can contact the
concerned party directly. If there is no entry, which meets your requirement, you can register
your details on the site, so that others can find you. The project improves the efficiency and
effectiveness of the whole system.
2.1.3 BEHAVIORAL DESCRIPTION

It examine the operations of the software as a consequence of external events and internally
generated control characteristics. Here the Admin checks the classified entered by the registered
users. Admin is the only person who can activate or deactivate the classified entered by the
registered users.
2.1.4 PROJECT PLANNING
I was assigned the duty for developing a website known as “Online Market”. Working in team
reinstates the team for some common guidelines and standard to be followed by all the team
members across all team. For the optimum use of practical time it is necessary that every session
is planned. Planning of this project will include the following things:
 Topic Understanding.
 Module Break –Up Of The System.
 Processor Logic For Each Module.
 Database Requirements.
2.2. SOFTWARE DEVELOPMENT LIFE CYCLE MODEL

The software development life cycle (SDLC) is the process based standard practice to
develop any kind of software product. These processes are categories as phases in SDLC and
related to different activities. Different models are described in software engineering text
books, but none is fully satisfied all the need of a software companies. Some SDLC models
are Water Fall Model, Spiral Model, and Prototype Model etc.
13
Our Project is based on Waterfall Model.
Figure 1: The Waterfall Model
Phases in waterfall model:
1. Requirement Analysis & Specification

The goal of this phase is to understand the exact requirements of the customer and
to document them properly. The output of this phase is a documented in natural language
known as Software Requirement Specification (SRS) document.
We have gathered the following requirements after interacting with the Financial officials:
14
NO. REQUIREMENTS ESSENTIAL DESCRIPTION OF REMARKS
OR THE
DESIRABLE REQUIREMENTS
RS 1 The system should Essential A admin page should The id are’s

have a admin Sign In appear assigned by the
when the admin main- admin
clicks on
admin sign in
RS 2 The system should Essential A sign in box should Anyone can

have a User sign in. appear create a sign in
when the user clicks id by reistering
on sign in.
RS 3 The system should Essential It will allow the user

have register form to book their tickets
for new users
RS 4 If the Registration of Essential After the Registration Registration are

user is successfully of a user assigned by the
done. The system name or user ID it user
must redirect to must redirect to
homepage homepage to sign
his/her id.
RS 5 Registration form Essential Registration form of When new user

should be stored in a user registered
database. should be stored in himself/herself
database. all information
So admin must see stored in
them database
RS 6 If the admin is login, Essential All the rights of This page is

the system should admin are only
show the rights of the Shown access by the
administrator Admin not by
Others
15
RS 7 The administrator Essential The administrator The
have the right of have the administrator
adding, deleting and right of adding, have the
modifying the details deleting and right of adding,
modifying the details deleting and
modifying the
details
RS 8 The system should Essential After sign in the user User must
have a logout page must logout logout
from the system the page after
booking tickets
2. Design
In this phase the SRS in transformed into a structure that is suitable for
implementation in some programming language. Here overall system architecture is defined
and high level design work is performed.
3. Implementation and Unit Testing

During this phase, design is implemented. During testing small modules are tested in
isolation from the rest of the software.
4. Integration & System testing

Integration deals with testing of the interface between modules. System Testing involves the
testing of entire system, whereas the software is a part of this system.
5. Operation & Maintenance

The purpose of this phase is to preserve the value of the software over time.
Software maintenance includes error correction, enhancement of capabilities, deletion of
obsolete capabilities and optimization.
16
STEPS IN REQUIREMENT ANALYSIS
Draw the
context
diagram
Develop
prototype
(optional)
Model
the
requirements
Finalize
the
Requirements
FIGURE 2. REQUIREMENT ANALYSIS STEPS
2.3 PROJECT CATEGORY
Functional Requirements
There are registered people in the system. Some are approvers. An approver can also be a
requestor. In an organization, the hierarchy could be engineers/Managers/Business
Managers/Managing Director etc. In a college, it could be Lecturer/Professor/Head of the
Department/Dean/Principal etc.
The system should be able to:-
 Login a user.
 Login an admin
 Allow a user to enter his/her details.
 Admin can add/delete/modify the things.
DESIGN CONSTRAINTS
In our design phase we have come across following constraints:

 Technology-We have used PHP for our project. Regarding it we have to be careful about
following things:-
o Fonts-We have to use fonts that are properly visible.
o Forms-Number of forms used in our project are need to be less to avoid
complexity
17
o GUI- User interface should be easy to operate.
 Requirements-While designing we need to change design of project accordingly.
 Policies- new policies can be added as and when required.
2.4. SOFTWARE REQUIREMENTS
 For Server:-
Component Minimum Recommended
OS Windows 7 Windows Server 2003 SP 1
Software PHPmyadmin PHPmyadmin
 For Clients:-
Component Minimum Recommended
OS Windows XP SP 2 Windows 8.1
2.5. TECHNOLOGIES USED
Following is a tabular representation of the technology to be used for the development of the
proposed solution:
Operating System Windows 8.1
Technologies PHP
Tools Xampp
Data Base Microsoft MYSQL
18
2.6. USE CASE DIAGRAMS
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 we
FIGURE 3: USE CASE DIAGRAM
19
CHAPTER – 3
SOFTWARE DESIGN
20
3.1. Introduction
This chapter will focus on the design of the system using diagrams to illustrate graphically
certain sections of the software system.
3.2 High Level/Detailed Design (HLD/DD)
3.2.1 Data flow Diagrams (DFDs)
As information moves through software, it is modified by a series of transformations. A

data flow diagram is a graphical representation that depicts information flow and the
transforms that are applied as data move from input to output.
The data flow diagram may be used to represent a system or software at any level of
abstraction. In fact, DFDs may be partitioned into levels that represent increasing
information flow and functional detail. Therefore, the DFD provides a mechanism for
functional modeling as well as information flow modeling.
LIST OF SYMBOLS
SYMBOL NAME FUNCTION
Data Flow Connect process
Perform some transformation of

Process its input data to yield output
data.
A source of system inputs or

Source or sink sink of system outputs
A repository of data, the
arrowhead indicate net
Data Store input and net outputs
to store
3.3 Context Diagram
A level 0 DFD is called fundamental system model or context model represents
21
entire software element as a single bubble with input and output data indicating by incoming
and outgoing arrows.
FIGURE 4: CONTEXT DIAGRAM
22
3.4 First Level DFD
FIGURE 5: DFD LEVEL 1
23
3.5. Second Level DFD
1. ADMIN
24
2. USER
25
3. LOGIN
26
CHAPTER – 4
DATABASE DESIGN
27
4.1 Introduction
This article/tutorial will teach the basis of relational database design and explains how to
make a good database design. It is a rather long text, but we advise to read all of it. Designing
a database is in fact fairly easy, but there are a few rules to stick to. It is important to know
what these rules are, but more importantly is to know why these rules exist, otherwise you
will tend to make mistakes!
4.2 Database Fields Specification
A small write-up on the database, giving the fields, explaining each field etc should be
written. This write-up can be evaluated on the following points.
1. Clarity and conciseness of the database design. Like, whether key is defined, whether
any redundant fields are there etc.
2. Whether data-storage calculations are made, and if so, whether they are done properly
etc.
3. Whether any data-backup/recovery mechanism is discussed or being thought of.
Employee Number/Registration Number is the Key of the database. The range of valid values
entered below as examples need not be taken as such. They can be modified by the team.
TABLE NAME DESCRIPTION

REGISTER CONTAINS ALL THE REGISTRATION
DETAIL OF THE USERS.
ADMIN CONTAINS ADMIN’S LOGIN
INFORMATION
A) Admin
Field Name Data Type Size Constraint

Id varchar 10 Not Null
Username Varchar 10 Not Null
Name Text Primary Key
Email Varchar 20 Not Null
Address Varchar 500 Not Null
Phone tinyint 10 Null
B) Register

Name Varchar 20 Not Null
Email Varchar 20 Not Null
Username Varchar 20 Primary key
Password Varchar 30 Not Null
Birth Month Varchar 15 Not Null
28
Birth Day varchar 5 Not Null
Birth Year Year 4 Not Null
Gender Varchar 8 Not Null
Phone timyint 10 Not Null
C) Card

Id varchar 10 Primary Key
Username Varchar 30 Not Null
Name Text 30 Not Null
Description Varchar 50 Not Null
Price Double Not Null
4.3 Entity-Relationship Diagram
It is a detailed logical representation of data for an organization and uses

three main constructs.
Entities
It is a fundamental thing about which data may be maintained. Each
entity has its own identity.
Entity Type is the description of all entities to which a common definition
and common relationships and attributes apply.
Attributes
Attributes are properties of entities. Attributes are represented by means

of eclipses. Every eclipse represents one attribute and is directly
connected to its entity (rectangle).
Relationship
Relationships are represented by diamond shaped box. Name of the

relationship is written in the diamond-box. All entities (rectangles),
participating in relationship, are connected to it by a line.
29
FIGURE 9: ER DIAGRAM
30
CHAPTER-5
TESTING
31
5.1 Introduction
Executing a program with the intent of finding errors is called testing. Testing is
vital to the success of any system. Testing is done at different stages within the
development phase. System testing makes a logical assumption that if all parts
of the system are correct, the goals will be achieved successfully. Inadequate
testing or no testing at all leads to errors that may come up after a long time
when correction would be extremely implementation. The testing of the system
was done on both artificial and live data. In order to test data test cases are
developed. Following are the various methods that are employed for testing:
5.2 Methods employed for Testing
5.2.1 Unit Testing
In unit testing the module is tested independently. It is done to test that

the module does satisfy the functional specification. This is done to
check syntax and logical errors in programs. At the time of preparation
of technical specifications, unit test data was also prepared. The coding
for that program was considered after verifying its output against this
test data.
Following are the unit testing methods:
 In Conditional Testing, the logical conditions that are given in the
module were checked to see whether they satisfy the functionality of
the module. This is done by using the test data was prepared.
 In Loop Testing, different loops in the module like nested loops
were tested using the data. Attempts to execute the loops to their
maximum range are done.
5.2.2 Integration Testing
In Integration testing whole system was checked when all the

individual modules were integrated together in order to test whether the
system is performing as according to the requirements specified.
Interface errors if any were corrected.
Test data was prepared was fed into the system to check whether the
system fails to detects an error.
5.2.3 Functional Testing
This is done foreach module/sub module of the system.Functional

testing serve as a means of validating wheater the functionality of the
32
system confers the original user requirement i.e. does the module do
what it wa supposed to do? Seprate schedules were made for functional
testing. It involves prepration of test data,writing test cases,testing for
conformance to test cases and preparation of bug’s listing for non-
comformities.
5.2.4 System Testing
System testing is done when the entire system has been fully integrated.
The purpose of the system testing is to test how the different modules
interact with each other and whether the entire system provides the
functionality that was expected.
System testing consists of the following steps:
 Program Testing
 System Testing
 System Documentation
 User Acceptance Testing
5.3 Test-Cases (TC)
The test-cases is basically a list of test cases that need to be run on the system.
Some of the test cases can be run independently for some components (report
generation from the database, for example, can be tested independently) and
some of the test cases require the whole system to be ready for their execution.
It is better to test each component as and when it is ready before integrating the
components.
No Testcase Title Description Expected Result

. Outcome
1 Successful User The login to the Login should be Passed
Verification system should successful and the
be tried with the user should be
login name and connected to
the correct server.
password.
2 Unsuccessful Login to the Login should fail Passed
User Verification system with a with an error
33
due to wrong wrong password ‘Invalid password’.
password
3 Unsuccessful Login to the Login should fail Passed
User Verification server with a with an error
due invalid ‘Invalid password’.
to invalid Login login id
id
4 The server should An option for Option for Passed
provide the admin allowing new adding/removing
for allowing users and users is shown.
newly registered deleting old
user to access the users of the
website. system
5 The system A form for Form for register Passed

should provide creating new users is shown
sign up form for users login id of
creating new user the system
Login id
6 Unsuccessful Filling the Field can’t be Passed
User Verification registration empty
if they does not form without
enter his whole entering the
detail. whole details
34
CHAPTER-6
ROLES AND RESPONSIBILITIES
35
6.1.Project Roles and Responsibilities
6.1.1 ROLE
 Work as a developer, designer, tester of the application.
6.1.2 RESPONSIBILITIES
 Work on definition of development requirements and priorities.

 Data migration.
 Interfaces with other systems.
 Reporting configuration and deployment.
 Set up and maintence of security rights and access permission.
 Contributing to technical strategy,policy and procedure.
 Development and operation of technical testing programmes.
 Production of technical documentation to agreed quality standards.
 Reporting on progress/issues to management and users.
36
CHAPTER-7
CONCLUSION
AND
ACHIEVEMENTS
37
CONCLUSION
The reason to have this project is to make our website wide. The main purpose
of this is to provide the users with lots of information and even admin can
fetch any data he needs in easier and faster way then making it done
physically.
The project is a complete dummy website. We have released all the version
which will make easier to start up their work on it. Further we will also provide
more features that could make it better then now.
Future Scope
The scope of this project is to provide the users with the bundle of
information. As till now if the client wanted to know one detail he use to go
through many process to get any information. But we have provided them to
make it on a click and also it will have many features to add on which will make
up their work on a click to fetch any data needed.
38
Screenshots
1.Homepage of my website.
2.This is the login procedure of my website.
39
3.This Is the sign up page of my website.
4.These are the products which are provided by my

website.
40
41
5.Pop-up notification display.
42
43
6.Order placement section.
7.This is payment gateway of my website.
44
Coding of my website.
Home page
<!DOCTYPE html>
<html>
<head>
<title>PHPGURUKUL Shopping</title>
<link href="themes/1/js-image-slider.css" rel="stylesheet" type="text/css" />
<script src="themes/1/js-image-slider.js" type="text/javascript"></script>
<link href="generic.css" rel="stylesheet" type="text/css" />
<script type="text/javascript" src="clients.js"></script>
</head>
<body>
<div style="width:100%; height:auto;">

<div style="height:120px; width:100%; background-color:#8B8A90;border:0px solid
#000000;">

<div style="height:118px; width:1150px; margin:auto; border:0px solid #990000;">

45
<div style="width:150px; height:115px; float:left; border:0px solid #FFF;"><a
href="index.php">
<img src="images/LOGO.PNG" height="118" width="150"/></a></div>

<div style="height:115px; width:990px; margin-top:0px; border:0px solid #FF0000;
float:left;">

<div style="width:900px; height:30px; float:left; border:0px solid #CCCC00; font-
size:12px;" align="right">
<a href="index.php" style="text-decoration:none;color:#FFFFFF;"><img
src="images/home.png" height="40" width="63" />
</a>

<a href="signup.php" style="text-decoration:none;color:#FFFFFF;">
<img src="images/ggh.png" width="60" height="50"/>
</a>
<a href="myaccount.php" style="text-decoration:none;color:#FFFFFF;">

<input type="button" value="MY ACCOUNT" style="border-radius:5px; background-
color:#269FB2;; border:0px solid #0033FF; font-family:'Monotype Corsiva'; height:22px;
color:#FFFFFF;">
</a>
<a href="cartdetails.php" style="text-decoration:none;color:#FFFFFF;">
<input type="button" value="MY CART" style="border-radius:5px; background-
color:#269FB2;; border:0px solid #0033FF; font-family:'Monotype Corsiva'; height:22px;
color:#FFFFFF;">
</a>
<a href="login.php" style="text-decoration:none;">
<input type="button" name="signin" value="SIGN IN" style="border-radius:5px;
background-color:#269FB2;; border:0px solid #FFFFFF; font-family:'Monotype Corsiva';
height:25px; color:#FFFFFF; box-shadow: 0px 0px 10px #CCCCCC;">
</a>
</div>
<div style="height:80px; width:490px; border:0px solid #FF0000; float:left;" align="center">
<strong style="color:#FFFFFF; font-size:32px; font-family:"Courier New", Courier,
monospace; margin-top:0px;" align="center"><b>PHPGURUKUL Shopping</b></strong>
</div>
<div style="border:0px solid #FF0000; width:400px; margin-top:30px; height:50px;

float:left;" align="right">
46
<br />
<b>Fatal error</b>: Uncaught Error: Call to undefined function mysql_connect() in
C:\xampp\htdocs\abc\phpgurukulshopping\dbconnection.php:6
Stack trace:
#0 C:\xampp\htdocs\abc\phpgurukulshopping\header.php(47): include()
#1 C:\xampp\htdocs\abc\phpgurukulshopping\index.php(39): include('C:\\xampp\\htdocs...')
#2 {main}
thrown in <b>C:\xampp\htdocs\abc\phpgurukulshopping\dbconnection.php</b> on line
<b>6</b><br />
My Account
<?php
session_start();
if(!isset($_SESSION['email']) ||(!isset($_SESSION['pwd'])))
header('location:login.php');
$email=$_SESSION['email'];
$pwd=$_SESSION['pwd'];
?>
<!DOCTYPE html>
<html>
<head>
<title>PHPGURUKUL Shopping/Myaccount</title>
47
</head>
<body>
<div style="height:120px; width:100%; background-

color:#8B8A90;border:0px solid #000000;">
<?php include ('header.php'); ?>
</div>
 <div style="height:45px; width:100%; background-color:#269FB2; border:0px

solid #269FB2;">
<?php include ('menu.php'); ?>
<div style="height:auto; width:100%;border:0px solid #269FB2;">
 <div style="height:328px; margin:auto; width:1050px; border:0px solid

#990000; ">
<?php include ('slider.php');?>
</div>
48

<table style="height:auto; width:1050px; margin:auto; border:0px solid #000000;

background-color:#FFFFFF; ">
<tr><td>
<div style="height:35px; width:1050px; border:0px solid #000000; margin-top:10px;

background-color:#D3D1D1; border-radius:5px; color:#1C7582;">
<font style=" font-size:18px; margin-left:10px;"><b>My Account</b></font>
</div>
<div style="margin-top:5px; border:0px solid #CC0000;">
<div style="width:200px; height:248px;background-color:#FFFFFF;border:0px

#CCCCCC solid;float:left;"><?php include('left.php'); ?></div>
<div style="border:0px solid #999999; border-radius:5px;

height:400px; width:700px; float:left; margin-left:50px; margin-top:20px;">
</div>
</div>
</td></tr>
</table>
<?php include('marquee.php'); ?>
49
</div>
<div style="width:100%; background-color:#414040; height:150px;

border:1px solid #000000; ">
<?php include('footer.php'); ?>
</div>
</div> 
</div>
</body>
</html>
Db connection
<?php session_start(); ?>
<?php
if(isset($_POST['submit']))
include 'dbconnection.php';
$email=$_POST['email'];
$password=$_POST['password'];
//echo"$email<br>$password";
$que="select * from user_details where email='$email'

and password='$password'";
//echo"$que<br>";
50
$res=mysql_query($que);
$count=mysql_num_rows($res);
// echo"QQQQQQQQQQ---------------$count";
//echo"$res";
while($data=mysql_fetch_array($res))
//echo"$data[name]";
if($count!=0)
$_SESSION['email']="$email";
$_SESSION['pwd']="$password";
header('location:cartdetails.php');
?>
<!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>
<title>PHPGURUKUL Shopping/login</title>
</head>
<body>
51
<div style="height:120px; width:100%; background-

color:#8B8A90;border:0px solid #000000;">
<?php include('header.php'); ?>
</div>
 <div style="height:45px; width:100%; background-color:#269FB2; border:0px

solid #269FB2;">
<?php include ('menu.php'); ?>
<div style="height:auto; width:100%;border:0px solid #269FB2;">
 <div style="height:328px; margin:auto; width:1050px; border:0px solid

#990000; ">
<?php include ('slider.php');?>
</div>

<div style="height:500px;; width:1050px; margin-top:20px; margin:auto; border:0px

solid #000000; background-color:#FFFFFF; ">
52
<div style="height:35px; width:1050px; border:0px solid #000000; margin-top:10px;
background-color:#F1F0F0; border-radius:5px; color:#1C7582;">
<font style=" font-size:18px;"><b>Login</b></font>
</div>
<form name="form2" method="post">
<table border="0" style="background-color:#F1F0F0; margin-top:50px ;

width:500px; border:1px solid #999999; border-radius:5px; height:300px;" align="center">
<tr><td>
<table border="0" style="background-color:#F1F0F0; margin-top:10px ;

width:400px; border:0px solid #999999; border-radius:5px; height:300px;" align="center">
<tr><td style="color:#828282; font-size:18px;" colspan="2">Already a

Customer</td></tr>
<tr><td colspan="2">Please Login Below</td></tr>
<tr><td colspan="2"><b>Email Address</b><br><input type="text"

name="email"></td></tr>
<tr><td colspan="2"><b>Password</b><br><input type="password"

name="password"></td></tr>
<tr><td>
<input type="submit" name="submit" value="submit" style="border:0px solid

#000000; border-radius:5px; background-color:#269FB2; height:25px;
color:#FFFFFF;"></td><td><a href="signup.php" style="text-decoration:none;
color:#828282; font-size:20px;"><b>New User Sign Up</b></a></td></tr>
</table>
</td></tr></table>
</form>
53
</div>
<?php include('marquee.php'); ?>
</div>
<div style="width:100%; background-color:#414040; height:150px;

border:1px solid #000000; ">
<?php include('footer.php'); ?>
</div>
</div> 
</div>
</body>
</html>
Marquee
<div style="height:30px; width:1000px; border:0px solid #000000;">
<script type="text/javascript">
var leftrightslide = new Array();
leftrightslide[0]='<a > <img

src="images/canon.jpg"></a>'

src="images/aoc.jpg"></a>'
54
src="images/blackberry.jpg"></a>'

src="images/bajaj.jpg"></a>'
leftrightslide[4]='<a> <img
src="images/canon.jpg"></a>'

src="images/compas.jpg"></a>'

src="images/daikin.jpg"></a>'

src="images/dell.jpg"></a>'

src="images/electrolux.jpg"></a>'

src="images/faber.jpg"></a>'
leftrightslide[10]='<a ><img
src="images/forbes.jpg"></a>'

src="images/fujifilm.jpg"></a>'

src="images/godreg.jpg"></a>'

src="images/hcl.jpg"></a>'

src="images/hitachi.jpg"></a>'

src="images/ifb.jpg"></a>'
leftrightslide[16]='<a > <img src="images/joquar

(1).jpg"></a>'

src="images/kelvinator.jpg"></a>'
55
src="images/kenstar.jpg"></a>'

src="images/kent.jpg"></a>'

src="images/kodak.jpg"></a>'
src="images/lenovo.jpg"></a>'
leftrightslide[21]='<a > <img src="images/lg.jpg"></a>'
src="images/milagrow.jpg"></a>'
src="images/mitashi.jpg"></a>'

src="images/olympus.jpg"></a>'

src="images/morphurichards.jpg"></a>'
</script>
</div>
56
BIBLOGRAPHY
 http://www.google.co.in
 http://www.youtube.co.in
 http://www.wikipedia.com
 http://www.w3schools.com
PHP for the Web: Visual Quick Start Guide

Book by Larry Ullman
PHP and MySQL Web Development

Book by Luke Welling
57

A Project Report ON Online Market

Загружено:

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

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

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

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

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

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

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

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

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

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

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

A Project Report ON Online Market

Загружено:

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

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

A PROJECT REPORT

BACHELOR OF COMPUTER APPLICATION

UNDER THE SUPERVISION OF:

SRI GURU TEGH BHAHADUR INSTITUTE OF MANAGEMENT AND

Date: Vikramjeet Singh

HOD: Dr. Harshita Tuli

Guide: Mr. Amandeep Singh Arora

Place: New Delhi Vikramjeet Singh

Chapter Topic Page

2. REQUIREMENT & ANALYSIS

2.1 Software Requirement Specification 13

2.2 Software Development Life Cycle 13

2.3 Project Category 17

2.4 Software Requirements 18

2.5 Technologies Used 18

2.6 Use Case Diagram 19

3.2 High Level/Detailed Design (HLD/DD) 21

3.3 Context Diagram(Level 0) 22

3.4 Data Flow Diagram (Level 1) 23

3.5 Data Flow Diagram (Level 2) 24

4.2 Database Field Specifications 29

4.3 Entity-Relationship Diagram 31

5.2 Methods adopted for testing 33

5.3 Test cases 34

6.1 Project roles and responsibilities 37

7 CONCLUSION & ACHIEVMENTS 39

APPENDICES Coding & Snapshots 40

Table Page Number

1.1.1 Objective and Scope of the Project

The main purpose of this is to provide customer variety of range of products.

2.1.2 FUNCTIONAL DESCRIPTION

2.1.3 BEHAVIORAL DESCRIPTION

2.2. SOFTWARE DEVELOPMENT LIFE CYCLE MODEL

Figure 1: The Waterfall Model

Phases in waterfall model:

1. Requirement Analysis & Specification

RS 1 The system should Essential A admin page should The id are’s

RS 2 The system should Essential A sign in box should Anyone can

RS 3 The system should Essential It will allow the user

RS 4 If the Registration of Essential After the Registration Registration are

RS 5 Registration form Essential Registration form of When new user

RS 6 If the admin is login, Essential All the rights of This page is

3. Implementation and Unit Testing

4. Integration & System testing

5. Operation & Maintenance

FIGURE 2. REQUIREMENT ANALYSIS STEPS

2.3 PROJECT CATEGORY

In our design phase we have come across following constraints:

2.4. SOFTWARE REQUIREMENTS

Component Minimum Recommended

OS Windows 7 Windows Server 2003 SP 1

Software PHPmyadmin PHPmyadmin

Component Minimum Recommended

OS Windows XP SP 2 Windows 8.1

2.5. TECHNOLOGIES USED

Operating System Windows 8.1

FIGURE 3: USE CASE DIAGRAM

3.2 High Level/Detailed Design (HLD/DD)

3.2.1 Data flow Diagrams (DFDs)

As information moves through software, it is modified by a series of transformations. A

Data Flow Connect process

Perform some transformation of

A source of system inputs or