Project Report_Food Bazar_Ver1

Project Report
2013
TEAM MEMBERS
Ashmika
Megha Jain
Surbhi Heda
Food Bazaar.com
Version 1.0
Date 27th
Dec 2013
Project Guide
Mr. Tulsi Gurjar, SSE
Pratham Solutions Pvt Ltd
S 23, Krishna Marg
Shyam Nagar
Jaipur

Food Bazaar.com 2013
Page 2
CERTIFICATE
This is to certify that Ashmika, Megha Jain, Surbhi Heda of B.Tech(CSE)7th Sem have
undertaken and completed the project entitled “Food Bazar.com” in the partial
fullfillment of the degree of B.Tech under my supervision during the period of July 2013
to December 2013.
The work done in this project is the result of their original work and effort.
Mr. Anil Sharma
COO-Pratham Solutions Pvt. Ltd.

Page 3
ACKNOWLEDGEMENT
The successful completion of this project is attributed to the great help received from
different people.
We express our sincere gratitude to Mr. Anil Sharma of Pratham Solutions for giving us
opportunity to work in this prestigious organization and encouraging us during our
project period.
We express our gratitude to our project guide Mr. Tulsi Gurjar for his valuable guidance
and encouragement during each step of the project and his constant help, support and
dedication throughout the making of this project successful.
We are thankful to our Technical Assistants for kind cooperation during the development
of the project.
Last but not the least we would like to thanks to all of our friends for giving useful
suggestions and ideas for improving our project.
Ashmika(BTBTC10219)
Megha Jain(BTBTC10232)
Surbhi Heda(BTBTC10241)

Page 4
ABSTRACT
E-commerce is fast gaining ground as an accepted and used business paradigm. More
and more business houses are implementing web site providing functionality for
performing commercial transactions over the web. It is reasonable to say that the
process of shopping on the web is becoming commonplace.
Users of the system: Retailers are the user of the system. An administrator of the
website is the Super-User. When the user type in the URL of the website, a Welcome
page is shown which has a menu on the top, after that a banner and category wise
product. User needs to login before placing their order. Login functionality should
check the authenticity of the user from the database.
Functional components of the project: Following is a list of functionality of the
system:
 Registration Screen: If the user is not registered, then registration screen should
be available
 Products Order: This screen will show all the types of different product with their
values and minimum quantity that should be ordered. If possible, provide the
image of each of the product. On selecting any one of the product, user is shown
the columns for the quantity to be entered.
 Seasonal: User can select the products according to season also.
 Search: Search option is available from where user can enter the product and
search it directly.
Food bazaar is an electronic market where shopkeepers and retailers can buy products for
their stock. They can purchase fruits, vegetables, nuts and dairy products.
The main objective of this website is to make all the items of daily use to be available at one
place so that retailers can easily purchase and maintain their stock for customers. It will
save their time, labor and money. Here, products will be acquired from the suppliers and
manufacturers .Thus, fresh and good quality products will be available at low cost.

Page 5
 Add to cart: The product selected by the user will be added to cart from where he
can proceed further.
 Terms and Conditions – A Brief text on the website explaining terms and
conditions and printable copy of it.
 Contact Information – Contact information regarding the office addresses with
phones and faxes are provided on this screen
In order to develop an e-commerce website, a number of Technologies must be
studied and understood. These include multi-tiered architecture, server and client
side scripting techniques, programming language (such as C#, Java), relational
databases (such as MySQL, Access).
 This is a project with the objective to develop a basic website where retailers are
provided with online food bazaar of all the products of daily need.

Page 6
Table of Contents
Description Page No
1. Software Requirement Specification …….………..………...7—12
1.1 Introduction
1.1.1 Model
1.1.2 Purpose
1.1.3 Scope
1.1.4 Definitions
1.1.5 Tools
1.1.6 Technologies to be used
1.7 References
2. Overall Description……………………………..…………………12—15
2.1 Product Perspective
2.2 Software Interface
2.3 Hardware Interface
2.4 Constraints
2.5 Architecture Design
2.6 Use Case Model
2.8 Database design
3. Specific Requirements…………………….………………………15—23
3.1 Functional Requirements
3.2Use-case Report
3.2.1 Admin use-case
3.2.2 Retailer use-case
3.3 Activity diagram
3.4 Attributes
4. Software design Specification………………………………….24----56
4.1 System Architecture Design
4.1.1 Data Flow Diagrams
4.2 Data Design (E-R Diagram)
4.3 Sequence Diagram
4.4 Detailed Description of Components (Tables)
4.5 User Interface Design (Screen Layouts)
5. System Testing ………………………………………………… 57----58
6. Conclusion……………………………………………………………. 59
7. References

Page 7
Business Requirement Specification
The client wanted to provide effective easy efficient and hassle free method of making
the fresh food items available to the business community. This is B to B (Business to
Business) project. This is a hub for buying the stocks for resale of fresh fruits, vegetables,
nuts and dairy products. The whole process will be online.
This is a new concept for the retailers to buy their stock online. The main objective of this
website is to make all the items of daily use to be available at one place so that retailers
can easily purchase and maintain their stock for their customers. It will save their time,
labor and money and would provide at competitive prices.
The retailers’ must have the internet connection to shop online or order the goods. The
payment would be Cash-on-Delivery (COD) which further makes the purchases more
reliable and trust worthy.
The business would manage the stocks of the food items. This is done through tie ups
with the suppliers. But most of the slow moving items would even not have the stocks
and thus would save on resources and would be supplied directly from the suppliers.

Page 8
Software Requirement Specifications
1.1 INTRODUCTION
1.1.1 MODEL
The model that is basically being followed is the WATER FALL MODEL, which
states that the phases are organized in a linear order. First of all the feasibility study is
done. Once that part is over the requirement analysis and project planning begins. If
system exists one and modification and addition of new module is needed, analysis of
present system can be used as basic model.
The design starts after the requirement analysis is complete and the coding
begins after the design is complete. Once the programming is completed, the testing is
done. In this model the sequence of activities performed in a software development
project are: -
 Requirement Analysis
 Project Planning
 System design
 Detail design
 Coding
 Unit testing
 System integration & testing
Here the linear ordering of these activities is critical. End of the phase and the
output of one phase is the input of other phase. The output of each phase is to be
consistent with the overall requirement of the system. Some of the qualities of spiral
model are also incorporated like after the people concerned with the project review
completion of each of the phase the work done.
WATER FALL MODEL was being chosen because all requirements were known
beforehand and the objective of our software development is the
computerization/automation of an already existing manual working system.

Page 9
Fig 1.1 : Water Fall Model
Process
Input output
1.1.2 PURPOSE
Food Bazaar (electronic daily products market) is an online website which provides
services to retailers. It provides a convenient market for the use of retailers to buy daily
products like vegetables, fruits, dairy products and nuts in bulk all at one place. Thus,
saves time and labor of retailers and provide good quality food to them at lower cost.
With the help of this cost reduces as no intermediate organizations are there between
suppliers and sellers.
Communicated
Requirements
Requirements
Specification
Design
Specification
Executable
Software
Modules
Integrated
Software
Product
Delivered
Software
Product
Changed
Requirements
Requirements
Engineering
Design
Programming
Integration
Delivery
Maintenance
Product Product

Page 10
1.1.3 SCOPE
The basic users are Administrator (Admin) and Retailers.
Registered people can have the entire view of website prices in market,
Prices updated by government of different items. Not registered people can also have
the view of site but they will have to register before purchasing any good.
Admin should be able to monitor all the records of users.
Retailer have facility of booking vegetables, fruits, dairy products and nuts on a certain
minimum scale.
Updated prices given by government bodies are maintained.
User can give feedback for the site.
User can also view the products according to their season.
1.1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
HTML (Hyper Text Markup Language): It is used to create static web pages.
JSP (Java Server Pages): It is used to create dynamic web content.
J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to
the Java platform, which is used for developing and running distributed java
applications.
HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/
server protocol between a web browser and a web server.
XML (Extensible Markup Language): It is a markup language that was
designed to transport and store data.
AJAX (Asynchronous Java Script and XML): It is a technique used in java
script to create dynamic web pages
UML (unified modeling language): is a standard language used for making
blue prints of software projects
JQUERY: It is a fast, small, and feature-rich JavaScript library. It makes things like HTML
document traversal and manipulation, event handling, animation, and Ajax much simpler
with an easy-to-use API that works across a multitude of browsers. With a combination of
versatility and extensibility, jQuery has changed the way that millions of people write
JavaScript.
JAVASCRIPT: It is the scripting language of the Web. All modern HTML pages are using
JavaScript to add functionality, validate input, communicate with web servers, and much
more.

Page 11
1.1.5 TOOLS
Architecture design: JAVA, J2EE
JAVA:
Java is an object-oriented programming language developed by Sun Microsystems a
company best known for its high end UNIX workstations. Java language was designed to
be small, simple and portable across platforms, operating systems, both at the source
and at the binary level, which means that Java programs (applet and application) can run
on any machine that has the Java virtual machine (JVM) installed.
J2EE:
Java Platform, Enterprise Edition or Java EE is a widely used platform for server
programming in the Java programming language. The Java platform (Enterprise Edition)
differs from the Java Standard Edition Platform (Java SE) in that it adds libraries which
provide functionality to deploy fault-tolerant, distributed, multi-tier Java software, based
largely on modular components running on an application server.
DREAMWEAVER: Dreamweaver combines HTML and CSS plain text editing with a
WYSIWYG tool which lets you check progress as you go or edit WYSIWYG on the fly. It's
the industry standard tool for this sort of thing, although there are many, many programs
which do more-or-less the same thing.
APACHE TOMCAT 7.0: Apache Tomcat is an open source software implementation of the
Java Servlet and Java Server Pages technologies. The Java Servlet and Java Server Pages
specifications are developed under the Java Community Process. Apache Tomcat powers
numerous large-scale, mission-critical web applications across a diverse range of
industries and organizations.
DESIGN TOOLS: SMART DRAW AND EDRAW
SMART DRAW: Smart Draw includes more than 70 different kinds of charts, diagrams
and other visuals. No matter which type you need to create, chances are there's a quick-
start template to help you get it finished in no time.
E-DRAW: Versatile diagramming program, with features that make it perfect not only for
professional-looking flow diagrams, organizational charts, business diagrams and charts,
but also network diagrams, building plans, mind maps, workflows, fashion designs, UML
diagrams, electrical engineering diagrams, science illustration... and that's just the
beginning.
DATABASE: MYSQL 5.3
MySQL, the most popular Open Source SQL database management system, is developed,
distributed, and supported by Oracle Corporation.

Page 12
1.6 TECHNOLOGIES USED
J2EE
 MYSQL
APACHE TOMCAT
UML
DREAMWEAVER
2. OVERALL DESCRIPTION
2.1 Product Perspective:
The distributed food bazaar database system stores the following Information as shown
below
Updated prices: these are maintained by admin regularly. The info is gained from the
govt bodies and the suppliers.
User description: contains the details of registered users.
Admin database: he has only rights to modify the databases and giving permissions for
registration. He monitors the project and provides services.
2.2 Software Interface:
Client on internet: Web browser, any operating system
Client on intranet: Web browser, any operating system
Web server: APACHE TOMCAT SERVER
Data Base server: mysql, any operating system
Development End: DREAMWEAVER ( Java, Java Bean, Servlets, HTML, XML, AJAX),
MYSQL, OS (Windows), APACHE TOMCAT (Web Server).
2.3 Hardware Interface:
CLIENT SIDE
PROCESSOR RAM DISK SPACE
INTERNET EXPLORER
6.0
Pentium IV & Above 1GB 1GB
SERVER SIDE
 APACHE TOMCAT SERVER 7.0.21
 MYSQL

Page 13
2.4 Constraints:
Login and password are used for identification of users.
Registered users only have the rights to enroll the complaints and give
suggestions.
Limited to Http/Https
2.5 Architecture Design:
BROWSER
(RETAILER)
DATABASE
MYSQL
APPLICATION SERVER
BROWSER(ADMIN)
Fig 2.1: logical design
FOOD BAZAAR
JVM
OS
APACHE TOMCAT

Page 14
2.6 Use case model (Admin & Retailer)
Fig 2.2: Use-Case model for admin and retailer.
Admin: manages database and updates prices every day, registers complaints.
Retailer: view the site gone through the price details of product and can purchase any
item.
Update
Login
Delete
Add
Manage user
View product
Feedback
About us
Home
Sign in
Purchase
Logout
Category id
Cat_ name
Season
Product id
Name
Price
Quantity
Category
Product
Category
Product
ADMIN
RETAILER

Page 15
2.7 Database Design:
login
 Loginid (PK)
 password
Category
 Categoryname
 Id (PK)
Newsletter
 Emailid
Placeorder
 Id (PK)
 retailerName
 type
 name
 quantity
 price
Product
 Type
 Name
 Quantity
 Price
 Date
 Imagepath
 Id (PK)
 Season
Signup
 Name
 Address
 Emailid
 Password
 confirmPassword
 phonenumber
 id (PK)
Stock
 Stock_id (PK)
 Type
 Name
 Quantity

Page 16
3. SPECIFIC REQUIREMENTS
3.1 EXTERNAL INTERFACE
1. Login Screen:
UserName
Password
Role:
 Following users are available- Administrator and User.
 Change password: This allows admin or user to change
password.
2. Main Screen (Dashboard): The main screen contains the various options
2.1 Admin
2.1.1 sales manager: maintain the record of stock after purchase.
2.1.2 product manager: can add ,update or delete product.
2.1.3 category manager: can add or delete category.
2.1.4 change password : can change the password if required.
2.1.5 subscribe manager: update users with latest offers and product.
2.2 User
2.2.1 add to cart: selected product will be added here.
2.2.2 view cart: user can view their product.
2.2.3 contact us: user can contact for help.
2.2.4 how to order: contain steps for the help of user.
2.2.5 subscribe us: user can subscribe for latest update.
2.2.6 Feedback: user can give feedback.

Page 17
3.2 USE CASE REPORTS
3.2.1ADMIN USECASE
Fig 3.1: Use-Case diagram for admin
Use case Description
Sign in admin login to website
manage data Manage the details of product
Update Update product
Delete Delete unnecessary things
add Add product
View data Can view entire data
View feedback Can view feedback given by the customer
Logout Logging out
ADMIN
Sign in
Manage data
Update
Delete
Add product
View data
View feedback
logout

Page 18
3.2.2RETAILER USE_CASE:
Fig 3.2: Use-Case diagram for retailer.
use case description
Sign in Login to the site to purchase products.
View products View the available product
View details view product details
Purchase Purchase the available product
Give feedback Can give feedback about the site
Logout Logging out
RETAILER
Sign in
View products
View details
Purchase
Give feedback
Logout

Page 19
3.3 ACTIVITY DIAGRAM
Login activity:
Fig 3.3: Login activity diagram

Page 20
REGISTRATION ACTIVITY:
Fig 3.4: Registration activity diagram.

Page 21
ADMIN ACTIVITY:
[Enter user name and password]
[Submit]
[No]
[Manage product] [Manage category] [Subscribe manager]
[No] [No] [No]
Yes Yes
[Data processing]
Yes
Yes
Fig 3.5: Admin activity diagram.
Get details
Validate
Get data Get data Get data
Validate Action set Validate
Get data
Validate

Page 22
RETAILER ACTIVITY:
[Enter user name]
[Submit]
No
View product Order product
Submit Submit
No
No
Yes Yes
Fig 3.6: Retailer activity diagram.
Get data
Validate data
Get data Get data
Validate data
Validate data

Page 23
3.4 Software System Attributes
3.4.1 Reliability
 Our website can be fully operated if internet is available and is 100% reliable.
3.4.2 Availability
 Our website is available 24 hours for users.
 The user should have his login account to enter into the system and if not, then
the admin will create the user account
3.4.3 Security
 The authorization mechanism of the system will block the unwanted attempts
to the system.
 It also let the system to decide the privileges of the user and admin.
 Data integrity for critical variables will also be checked.
3.4.4 Maintainability
 The requirement modules that are explained in this document are enough to
satisfy the customers’ needs and wants.
 The maintenance can be easily done by integrating new modules and offering
new software solutions for the system.
3.4.5 Portability
It is compatible on all Windows operating system having SQL server installed on server.

Page 24
4. Software Design Specification
4.1 System Architecture Design
4.1.1 Data flow diagram
0-Level DFD:
Login Login
Manage data Add to cart
Add, update, delete prod View cart
Manage details View product
Change password Purchase
View feedback Give feedback
Fig 4.1: Data flow diagram
FOOD BAZAAR
A
D
M
I
N
U
S
E
R

Page 25
4.2 E-R DIAGRAM
Fig 4.2: Entity-Relationship diagram.
ADMIN
pricing view profile
sells
view data
manage update
has VEGETABLE,FRUI
TS
NUTS,DAIRY
seasoncategory
has
QUANTITY
id
name
category
quantity
price
register
has
RETAILER
purchase
view
login
logout
give
feedback
can
place_order
email type
quantity
price
name
id

Page 26
4.3 SEQUENCE DIAGRAM
Administrator Login Sequence Diagram
Fig 4.3
Admin Add Product Sequence Diagram:
Fig 4.4
Admin Login Bal : AdminLogin Dal : SqlHelper DataBase
1 : Login()
2 : CheckUser()
3 : Execute NonQuery()
4 : Exeute NonQuery()
5 : Response to ExecuteNonQuery()
6 : Get Response()
7 : Show Result()
Admin Product BAL : clsProduct DAL : Sqlhelper DataBase
1 : Add Product()
2 : InsertProduct()
3 : ExecuteNonQuery()
5 : Response To ExecuteNonQuery()
6 : Retrun Response()
7 : Show Result()

Page 27
Admin Add Category Sequence Diagram:
Fig 4.5
User Account Details Sequence Diagram:
Fig 4.6
Admin
Category
BAL : clscategory DAL : Sqlhelper DataBase
1 : Add Category()
2 : InsertCategory()
7 : Show Result()
User
Account Details
BAL : clsAccountDetails DAL : Sqlhelper DataBase
1 : Add Account()
2 : InsertAccount()
7 : Show Result()

Page 28
User Placed Order Details Sequence Diagram:
Fig 4.7
User
Order Products
BAL : clsOrderProducts DAL : Sqlhelper DataBase
1 : Add Order Products()
2 : InsertOrder Products()
7 : Show Result()

Page 29
SEQUENCE DIAGRAM (Overall System View)
Login Login
Manage data
Update Display welcome page
Delete
Add product view products
View data buy products
Give feedback
Purchase
Fig 4.8: Sequence Diagram.
ADMIN DATABASE RETAILER
ADMIN DATABASE RETAILER

Page 30
4.4 Detailed Description of Components (Tables)
Login Table:
Field Type Constraint Description
Loginid Varchar(45) Primary key Id provided
password Varchar(45) Not null Password of user
Category Table:
categoryName Varchar(45) Not null Name of the
category
id Integer Primary key Id provided to it
Newsletter Table:
emailId Varchar(45) Not null Email id of the user

Page 31
PlaceOrder Table:
id Integer Primary key Id provided
retailerName Varchar(45) Not null Name of retailer or
store
type Varchar(45) Not null Category of product
quantity Float Not null Quantity of product
price Float Not null Price of product
name Varchar(45) Not null Name of product
Product Table:
type Varchar(45) Not null category
name Varchar(45) Not null Name of product
quantity Float Not null Quantity of product
price Float Not null Price per kg
date Date Not null Date on which data
inserted
imagePath Varchar(45) Path of image of
product
season Varchar(45) Not null Season in which
particular product is
available

Page 32
Stock Table:
stockid Integer Primary Id provided
type Varchar(45) Category of product
name Varchar(45) Name of product
quantity Float Quantity of
particular product
Signup Table:
name Varchar(45) Name of user
address Varchar(70) Address of user or
store
emailid Varchar(45) Not null Emailid of user
password Varchar(45) Not null Password of user
confirmPassword Varchar(45) Not null Re-enter password
of user
phoneNumber Bigint(20) Not null Contact number

Page 33
4.5 User Interface Design :( Screen Layouts)
Frontend: Home Page
Home Page: This is the home page which will be viewed by the user.

Page 34
Registration page: user will register through this page.

Page 35
Login page: Retailers will login through this page.

Page 36
Fruit Page: This is the page where all the fruits will be displayed.

Page 37
Vegetables Page: This page will display all the vegetables.

Page 38
Nuts Page: This page will display various nuts.

Page 39
Dairy Page: This page will display all the dairy products.

Page 40
Add to cart Page: This page will display the items which user selected to purchase.

Page 41
How to order: This page shows the steps to order any product.

Page 42
About Us Page: This page gives the information about the site and product.

Page 43
Search: user can search any particular product directly.

Page 44
Contact Us page: Through this page user can contact or give feedback.

Page 45
Backend:
Admin login: Admin will login through this page and proceed further.

Page 46
Dashboard: This is the home page of admin

Page 47
Category Manager: Here admin can manage category.

Page 48
View category: By click on view icon on category manager page admin can view category.

Page 49
Edit Category: By click on edit icon admin can edit the category.

Page 50
Product: Admin can insert ,edit , delete and view through this page.

Page 51
View: Admin can view product on this page.

Page 52
Edit Product: Admin can edit product through this page.

Page 53
Change Password: Admin can change his password through this page if required.

Page 54
Subscribe Manager: this page shows the list of id of user who has been subscribed for
updates.

Page 55
View user: this page shows the list of user who has been registered to our site.

Page 56
Sales Manager: This page keep the track of stock.

Page 57
5. System Testing
Software Testing is the process of evaluating a system by manual or automated
means to verify that it satisfies specified requirements in terms of SRS, functionality,
and performance.
Testing Objectives
1. Testing is a process of executing a program with the intent of finding error.
2. A good test case (a document which defines each test case in detail) is one that
has a high probability of finding an as-yet-undiscovered error.
3. A successful test is one that uncovers an as-yet-undiscovered error.
Testing process
Testing Issues
 Unit Testing :
Module are tested independently.
 Integration Testing :
After connecting the modules the integration testing takes place.
 System Testing:
System testing is done to check whether system is working properly or not
against the requirements specified.

Page 58
Test Cases:
Test Case no. Testing Item Testing Process Remarks Result
001 Signup Fill all the details Only new user
are allowed
Pass
002 Login Enter loginid and
password
Registered user
Check
Password Rule
Pass
003 Add to Cart Select product
and add it to
cart
Login first Pass
004 Search Enter any
product name
All users are
allowed
Pass
005 Seasonal
Product
Automatic It will only
display the
products of
current month.
Pass

Page 59
6. Conclusion
 Our food bazaar provides the retailers with online facilities of purchasing so that the
time of customer can be managed efficiently.
 It provides a convenient market for the use of retailers to buy daily products like
vegetables, fruits, dairy products and nuts in bulk all at one place
 Here, products will be acquired from the suppliers and manufacturers .Thus, fresh
and good quality products will be available at low cost.

Page 60
7. References
Websites:
www. w3schools.com
www.css-tricks.com
www.sun.com for java
www.javatpoint.com
www.agilemodling.org
Data base management systems

Project Report_Food Bazar_Ver1

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (6)

Ähnlich wie Project Report_Food Bazar_Ver1

Ähnlich wie Project Report_Food Bazar_Ver1 (20)

Project Report_Food Bazar_Ver1