1.

INTRODUCTION

1.1 PROJECT OVERVIEW

The Following content are showing about “FRUIT SHOP MANAGEMENT

SYSTEM.This carry the details about Fruit Shop like, inventory, stock, sell, buy, billing,
supplier, amount and more detail maintenance.

This project is containing a more then features to compare between existing

systems of this project. This has a Report section. Previous project is does not have this
report section for using online management. However, this provides a report on the
specific date so that reports can be taken weekly or monthly

This FRUIT SHOP MANAGEMENT SYSTEM project is also making a

complete enterprise management via web application. This only the first Fruit Shop does
this type of facility. This is a one of the most important advantage of this project.

And also it has more over the advantages. This project is done using by the languages are
PHP and MySQL. Here this PHP as a frontend and MySQL as a back end. These are
making a best connectivity of front end and back end.

1
1.2 OBJECTIVE OF THE PROJECT

The project entitled as “FRUIT SHOP MANAGEMENT SYSTEM”. In this, we

manage the data and details are about the process of the Sales Market. It carry the details
are selling details, buying details, billing details, inventory details, supplier data’s and
etc…

Most of the Fruit Shops maintain their details in booklet vice only. These are the
most one of the disadvantage and drawback of the previous system. So, based that scope
this project has been created for rectify the problem of the existing system project.

Fruit Shop mainly created for calculate the final year accounting and calculate yearly
maintenance and data’s about the Sales market. Because the Fruit Shop are mostly
important in human life. Cause, need of the life things or any inventories is we want to
buy. So, that time we need a specific place for buy this all in a place. That facility is
provides by these Company (Fruit Shop).

2
 2. SYSTEM CONFIGURATION

2.1 SOFTWARE SPECIFICATION

COMPONENTS MINIMUM REQUIREMENTS

OPERATING SYSTEM : Microsoft windows 7 and above

GRAPHICS : Intel HD graphics

FRONT- END : PHP VERSION 5.5.11

BACK-END : MySQL VERSION 1.7.0

2.2 HARDWARECONFIGURATION

COMPONENTS MINIMUM REQUIREMENTS

PROSSOSOR : Intel® Pentium® CPU P6200 @

2-13GHz

RAM 2.00GB(1.74GB usable)

HARD DISK DRIVE 320GB

CACHE MEMORY : 2MB

INTERNET : Modem

BASIC COMPONENTS : Battery, Mouse and standard

QWERTY Keyboard.

3
 3. SYSTEM ANALYSIS

3.1 EXISTING SYSTEM

The Existing System is a time consuming process to find the information about
the different fields. It is difficult to communicate with the regarding sectors and
specifically for computer lab consumption based area, even then the students suffer a lot
to identify where to get an area of exact information and so.

After analysing the system studies, this existing system are has some features and
drawbacks. But this project reduced the drawbacks and adds some salient features.

DISADVANTAGES OF EXISTING SYSTEM

 Application errors occurring.

 Size of the Application is higher.
 Implementation cost is high.
 Nonsystematic Fruit Shop inventory maintenance.
 Stress in maintenance process.
 Less amount of database Storage

4
3.2 PROPOSED SYSTEM

The aim of the proposed system is overcomes the existing system. In this project it
provides “better and efficient service to users. These online systems that can be operate
from anywhere and anytime.

The “FRUIT SHOP MANAGEMENT SYSTEM” web application consists of

unique feature.

The structure of FRUIT SHOP MANAGEMENT SYSTEM will provides access

to much richer content to a more structure manner. We can easily move from the
catalogue to the particular book then to a particular chapter.

ADVANTAGES OF PROPOSED SYSTEM

 This “FRUIT SHOP MANAGEMENT SYSTEM” is developed as flat

user interface concept. The flat user interface website is look more
professional and user-friendly.
 This proposed system is mostly reduced the manual works from beginning
to ending.
 Easy Profit calculation
 Efficiency Report Generation
 Flat UI Based Admin Panel
 Securable Admin process.
 The database design of the project is very simple. So the admin can easily
understand the flow of the project.
 Systematic Fruit Shop inventory maintenance.
 The process of the report generation is very easy for the admin.

5
3.3MODULE AND DISCRIPTION

ADMIN

This module is access by admin only. Admin can login using

admin id and password. This admin panel is used to change (or) update
any data’s in this. Because, for a security purpose data maintenance
authority given to admin, he can only make any changes in this using login
id and password.

PRODUCT PURCHASE

This product module is containing some details about product

details. This maintains data’s about stock of the product and supplier
details. It contains opening stock, closing stock, issued stock, available
stock, item cost, product name and product purchasing date. It used for
generate the report. This purchase module is containing all data’s about
purchasing details. In this purchase details, purchase id, supplier id,
quantity, amount and purchasing date are carried out.

SUPPLIER

This customer module is containing some details about supplier

profiles. This maintains data’s about suppliers and their details. It contains
we purchase the goods from who and with specified data’s. It used for
generate the report.

SALES

In this sales module is contain the details about billing details,

product name, generic name, category, price, quantity, amount and profit,
it manage all data’s and details about inventory section and goods section.
REPORT

The report module is used to manage the report of the application.

The report module is used to generate the report of the product details,
sales details, and etc. The module is also used to generate the organ
transaction report. The report was generate based on date and month. This
module is use to view the Fruit Shop static reports.

6
 4.SYSTEM DESIGN

4.1 ENTITY RELATIONSHIP DIAGRAM

Item_name
User_name Password Stock_id

Amount
M
Admin 1 Stock

Item_name
Customer_id Purchase_id
Name

Purchase
Customer M Quantity
Ph_num has
M

Date
Mail-id Add

Supplier_id

Item_name Sales_id

Supplier Sup_name
M
M
Amount Sales

Phone_num
Quantity

7
 4.2 DATA FLOW DIAGRAM

Level 0

Request
Admin Login
Fruit Shop
Admin Administration Database

Response

8
Level 1

Admin Login
Login
Admin Database

Sales Details
Sales Details

Product Details
Product Details

Stock Details
Stock Details

Supplier Supplier Details

Details

Customer Customer Details

Details

9
 LEVEL 2

SaleDetails
Sale Details

ProductDetails
Product Details
Fruit Process
System
Database
Stock Details
Stock Details

SupplierDetails
Supplier Details

Customer Details
Customer Details

10
 4.3 DATABASE DESIGN

DATABASE NAME: SALES

TABLE NAME: user

FIELD TYPE SIZE CONSTRAINTS DESCRIPTION

User_Name Varchar 15 Not Null User Name

Password Char 15 Not Null Password

TABLE NAME: PRODUCT TABLE

FIELD TYPE SIZE CONSTRAINTS DESCRIPTION

Prodcut_id Int 11 Primary Key Product ID (Auto

Increment)
Product_code Varchar 50 Not Null Product Code

Gen_name Varchar 50 Not Null Generic name

Product_name Varchar 50 Not Null Product name

Cost Varchar 50 Not Null Cost

O_price Varchar 50 Not Null Original price

Price Varchar 50 Not Null Price

Profit Varchar 50 Not Null Profit

Supplier Varchar 50 Not Null Supplier

Onhand_qty Int 20 Not Null On-hand quantity

Qty Int 20 Not Null quantity

Qty_sold Int 20 Not Null quantity sold

Expiry_date Date 10 Not Null Expiry date

Date_arrival Date 10 Not Null Date arrival

11
 TABLE NAME: SALES TABLE

FIELD TYPE SIZE CONSTRAINTS DESCRIPTION

Transaction_id Int 15 Primary Key Transaction id

Invoice_number Varchar 30 Not Null Invoice number

Cashier Varchar 30 Not Null Cashier

Date Date 30 Not Null Date

Type Varchar 30 Not Null Type

Amount Int 30 Not Null Amount

Profit Int 30 Not Null Profit

Due_date Date 30 Not Null Due date

Name Varchar 30 Not Null Name

Balance Int 30 Not Null Balance

TABLE NAME: SUPPLIER TABLE

FIELD TYPE SIZE CONSTRAINTS DESCRIPTION

Supplier_id Int 11 Primary Key Supplier id

Supplier_name Varchar 50 Not Null Supplier name

Supplier_address Varchar 50 Not Null Supplier address

Supplier_contact Varchar 50 Not Null Supplier contact

Contact_person Varchar 50 Not Null Contact person

12
 TABLE NAME: CUSTOMER TABLE

FIELD TYPE SIZE CONSTRAINTS DESCRIPTION

Customer_id Int 15 Primary Key Customer id

Customer_name Varchar 30 Not Null Customer name

Address Varchar 30 Not Null Address

Contact Varchar 30 Not Null Contact

Membership_number Varchar 30 Not Null Membership number

Prod_name Varchar 30 Not Null Product name

Expected_date Date 30 Not Null Expected date

13
4.4 INPUT DESIGN

Input design is the process of converting user-originated inputs format. Input design is
one of the most expensive phases of the operation of the major problem of a system.
Input facilities the entry of data into the computer system. Input design involves the
selection of the best strategy for getting data into the computer system at the right time
and as accurately as possible. This is because the most difficult aspect of input designs in
accuracy. The use of well- defined document can encourage used to record data
accurately without omission. Input design must capture all the data that the system needs,
without introducing any errors. Input errors can be greatly reduced when inputting
directly by using appropriate forms for data capture and well-designed computer screen
layout. . The input design is the part of overall system design, which requires very careful
attention. If the data going into the system is incorrect then the processing and output will
magnify the errors. The objectives considered during input design are:

 Nature of input processing.

 Admin login
 Flexibility and thoroughness of validation rules.
 Handling of properties within the input documents.
 Screen design to ensure accuracy and efficiency of the input
relationship with files. Careful design of the input also involves
attention to error handling, in the project; the input design is made in
various window forms with various methods.

14
4.5 OUTPUT DESIGN

Output design generally refers to the results and information that are generated by
the system for many end-users; output is the main reason for developing the system and
the basis on which they evaluate the usefulness of the application. In any system, the
output design determines the input to be given to the application.

Output design is very important concept in the computerized system, without

reliable output his user may feel the entire system is unnecessary and avoids using it. The
proper output design is important in any system and facilitates effective decision-making.

Output design is the process which involves designing necessary output which
helps the user according to their requirement.

Efficient output design should improve the system relationship with the user and
helps in decision-making.

Since the reports are directly required by the management for taking decision and
to draw the conclusion must be simple, descriptive and clear to the user. Option for
outputs and forms are given in the system menus.

15
 5. SYSTEM TESTING AND IMPLEMENTATION

5.1 SYSTEM TESTING

The software which has been developed has to be tested to prove its validity. Testing is
considered to be the least creative phase of the whole cycle of system design. In real
sense it is the phase, which helps to bring out the creativity of the other phases, and
makes it shine.

Web portal for college administration management system was tested along the
following guidelines to prove its validity. It was tested using the following techniques of
software testing.

WHITE BOX TESTING

1. By using the technique it was tested that all the individual logical paths were
executed at least once.
2. All the logical decisions were tested on both their true and false sides.
3. All the loops were tested with the data in between the ranges and especially at
the boundary values.

BLACK BOX TESTING

1. By the use of these techniques the missing functions are identified and placed
in their positions.
2. The errors in the interfaces were identified and corrected.
3. This technique was also used to identify the initialization and termination
errors and correct them.

SOFTWARE TESTING STRATERGIES

Any software has to be tested with pre-planned strategies. To carry out the testing
in an efficient manner certain amount of strategic planning has to be done. Any testing

16
strategy must incorporate test planning, test case design, test execution and the resultant
data collection and evaluation.

The system “Online College Admission” was tested with the help of the following
software testing strategies.

UNIT TESTING

In Unit testing, we have to test the programs making up the system. The software
units in a system are called modules and routines that are assembled and integrated to
perform a specific function. Unit testing focuses first on the modules, independently of
one another, to locate errors. This enables to detect errors in coding and logic that are
contained within the module. In the lines of this strategy all the individual functions and
modules were put to the test independently. This method was applied in combination with
white and black box testing techniques to find the errors in each module.

INTEGRATED TESTING

Again this software testing strategy has two different approaches namely the top-
down approach in which the integration is carried out from the top level module to the
bottom and the bottom-up approach in which the integration is carried out from the low
level modules to the top. The module was tested using the bottom up approach by
introducing stubs for the top level functions. This test was used to identify the errors in
the interfaces, the errors in passing the parameters between the functions and to correct
them.

VALIDATION TESTING

Software validation is achieved through a series of black box test that demonstrate
conformity with requirements. Both plan and procedure are designed to ensure that all
functional required area achieved. Using validation testing we have tested this project.
The user should not leave any input area blank and it is not allowed to enter improper
data. Many validations are needed for each and every file in the form like textbox
validations.

17
SYSTEM TESTING

The software and hardware are integrated and a full range of system tests are
conducted in an attempt to uncover error at the software and hardware interface. Before
the system is released to user, testing is the sole duty of the developer to see that the
system is free from all kinds of bugs. The main purpose of testing an information system
is to find out errors and correct them. Testing was done in two phases

1. Foreground testing
2. Background testing

The Foreground testing includes the testing of all kinds of bugs that would be
visible to the user on the screen.

1. Testing for validity of inputs.

2. Testing whether the help message is displayed properly.
3. Testing for the proper flow of sequence.
4. Testing whether the system is user friendly.

The background testing includes, whether the database get updated as required. A
message such as “Record Stored Successfully” on the monitor may ensure that data has
really been updated in the required tables.

Table updating and Data Validation test.

1. Date Retrieval, Calculation and Report generation test.

2. Date and Form Security test.

18
5.2 SYSTEM IMPLEMENTATION

System Implementation is the stage of the project when the theoretical design is
tuned into working system. If the implementation system stages is not carefully
controlled and planned, it can cause chaos. Thus it can be considered to be the most
critical stage in achieving a successful new system and in giving the user a confidence
that the system will work and be effective.

After the management has given the approval of the design phase, report for this
project, further the development activities are preceded.

The major activities done in this project are

1. The most important development activity is prepared to computer program

needed for the system. The system flowcharts, Input charts, Output charts are
transferred into program.
2. In each stage of preparation the programs have been tested and errors are
corrected if any. All necessary measures are also falls into account while
testing the program.
3. The change over method is the process where the existing system is to be
replaced by the new computerized system.
4. Change over plan has to be made carefully so as to minimize the problem that
may arise from human errors.

The activities to be performed during the changeover plan have to be identified and the
responsibilities should be assigned to individuals in the organization.

19
 6. SCOPE FOR FUTURE DEVELOPMENT

The project is designed in such a way that it is flexible for changes in future user
requirements. Further extensions in the system can be made to submit more reports to the
managements, this will give the management is clear picture of the process of the current
system. The existing system has good scope for further development and it can be
integrated with the major systems like hospital management system. The project is
designed as a webpage that we can further module in future. As this project is developed
in PHP and HTML languages, which is an open source language and to retrieve the
information stored in the database is because of MYSQL. The system is currently
developed and ready for implementation to include the system is highly feasible and user
friendly. To provide better facility regarding security, it uses security provider software.
It can have an enhancement on proper in the future according to the user’s requirements.

Since this project is developed in PHP and HTML, it can diametrically change current
project into ASP.NET platform by viewing the status of this system because most of the
controls used in this project can support in ASP.NETplatform.

20
 7. CONCLUSION

We successfully designed and implemented afruit shop management system that

allows direct interaction with our system. We are assessing the impact of this advanced
informatics tool for manage product, product and stock information in online.

This is to summarize, this system is a well-developed on satisfying all the

requirements of the users with best performance.

Though the present system is a well performing one, performance will still increase if the
power consumption and office expenses are computerized. The various timely reports by this
project would be more useful for the users.

21
 BIBILIOGRAPHY

REFERENCE BOOKS

 PHP Cook Book”, Adm Trachtenberg, Orreilly& Associates Publication, First

Edition, 2003.
 “PHP Black Book”, Peter Moulding, Coriolis Group Publications, Fifth Edition,
2005.
 “New PHP Program with MySQL”, Dongosselin, Course Technology
Publication, 2008.
 “Learning PHP, MySQL”, Robin Nikson, Orreilly& Associates Publication, Third
Edition, 2009.
 Advanced PHP for Flash by Steve Webster, et al .friends of ED. Paperback-
September 2002.
 Advanced PHP for Web Development (The Prentice Hall PTR Advanced Web
Development Series) by Christopher Cosentino.Prentice Hall PTR. Paperback- 1
October, 2002.

REFERENCE WEBSITES

 www.codeproject.com
 www.w3school.com
 www.sourcecode.com
 www.wikipedia.com
 www.php.com

22
 APPENDICS
A.SCREEN SHOT

Admin Login Form

Dashboard

23
Sales

24
Products Available:

Add product

Existing Customer

25
Adding new customer

Existing Supplier

26
Adding Supplier

Sales report

27
B.SAMPLE CODING

<?php
//Start session
session_start();
//Unset the variables stored in session
unset($_SESSION['SESS_MEMBER_ID']);
unset($_SESSION['SESS_FIRST_NAME']);
unset($_SESSION['SESS_LAST_NAME']);
?>
<html>
<head>
<title>
FRUIT SHOP
</title>
<link rel="shortcut icon" href="main/images/pos.jpg">
<link href="main/css/bootstrap.css" rel="stylesheet">
<link rel="stylesheet" type="text/css" href="main/css/DT_bootstrap.css">
<link rel="stylesheet" href="main/css/font-awesome.min.css">
<style type="text/css">

28
body {
padding-top: 60px;
padding-bottom: 40px;
}
.sidebar-nav {
padding: 9px 0;
}
</style>
<link href="main/css/bootstrap-responsive.css" rel="stylesheet">
<link href="style.css" media="screen" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="container-fluid">
<div class="row-fluid">
<div class="span4">
</div>
</div>
<div id="login">
<?php
if( isset($_SESSION['ERRMSG_ARR']) &&is_array($_SESSION['ERRMSG_ARR']) &&
count($_SESSION['ERRMSG_ARR']) >0 ) {
foreach($_SESSION['ERRMSG_ARR'] as $msg) {
echo '<div style="color: red; text-align: center;">',$msg,'</div><br>';
}
unset($_SESSION['ERRMSG_ARR']);
}
?>
<form action="login.php" method="post">
<font style=" font:bold 44px 'Aleo'; text-shadow:1px 1px 15px #000;
color:#fff;"><center>FRUIT SHOP</center></font>
<br>
<div class="input-prepend">

29
<span style="height:30px; width:25px;" class="add-on"><i class="icon-user icon-
2x"></i></span><input style="height:40px;" type="text" name="username"
Placeholder="Username" required/><br>
</div>
<div class="input-prepend"><span style="height:30px; width:25px;" class="add-on"><i
class="icon-lock icon-2x"></i></span><input type="password" style="height:40px;"
name="password" Placeholder="Password" required/><br>
</div>
<div class="qwe">
<button class="btnbtn-large btn-primary btn-block pull-right" href="dashboard.html"
type="submit"><i class="icon-signin icon-large"></i> Login</button>
</div>
</form>
</div>
</div>
</div>
</div>
</body>
</html>
<?php
//Start session
session_start();
//Array to store validation errors
$errmsg_arr = array();
//Validation error flag
$errflag = false;
//Connect to mysql server
$link = mysql_connect('localhost','root',"");
if(!$link) {
die('Failed to connect to server: ' . mysql_error());
}
//Select database
$db = mysql_select_db('sales', $link);
30
if(!$db) {
die("Unable to select database");
}
//Function to sanitize values received from the form. Prevents SQL injection
function clean($str) {
$str = @trim($str);
if(get_magic_quotes_gpc()) {
$str = stripslashes($str);
}
return mysql_real_escape_string($str);
}
//Sanitize the POST values
$login = clean($_POST['username']);
$password = clean($_POST['password']);
//Input Validations
if($login == '') {$errmsg_arr[] = 'Username missing';
$errflag = true;
}
if($password == '') {$errmsg_arr[] = 'Password missing';
$errflag = true;
}
//If there are input validations, redirect back to the login form
if($errflag) {$_SESSION['ERRMSG_ARR'] = $errmsg_arr;
session_write_close();
header("location: index.php");
exit();
}
//Create query
$qry="SELECT * FROM user WHERE username='$login' AND password='$password'";
$result=mysql_query($qry);
//Check whether the query was successful or not
if($result) {if(mysql_num_rows($result) > 0) {
//Login Successful
31
session_regenerate_id();
$member = mysql_fetch_assoc($result);
$_SESSION['SESS_MEMBER_ID'] = $member['id'];
$_SESSION['SESS_FIRST_NAME'] = $member['name'];
$_SESSION['SESS_LAST_NAME'] = $member['position'];
//$_SESSION['SESS_PRO_PIC'] = $member['profImage'];
session_write_close();
header("location: main/index.php");
exit();
}
else {
//Login failed
header("location: index.php");
exit();
}
}else
{
die("Query failed");
}
?>

<?php
/* Database config */
$db_host= 'localhost';
$db_user= 'root';
$db_pass= '';
$db_database= 'sales';
/* End config */
$db = new PDO('mysql:host='.$db_host.';dbname='.$db_database, $db_user, $db_pass);
$db->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
?>

32