Title of the Project: PET BOTTLES DISTRIBUTION

1.Project Synopsis
Objective
 “Pet Bottles” is a web-based application to build a customer relationship
management which helps in easy management of Pet Bottles Package
Factory as well as the admin for a better relation with the customer.
 The application provides a easy to use interface for the distributor to manage
their day to day accounts and prices about the respective product.
 The user is allowed to interact with the admin in case of any queries.
 Details of product such as benefits are provided.

Input of the project:

As this system is going to be computerized, we need entries to be done like this-

 Customer details - It consists of customer details.

 Pet Bottles Packaging’s - It consist of different types of packaging based on
quantity.
 Supplier records
 Raw materials for packaging.

Output of the project:

This system provides the facilities like-

 Sales report
 Purchase report

 Payments report
 Stock details

1
PROCESS DIAGRAM:

INPUT PROCESS OUTPUT

Customer Details Order Report

Login
Product Details Sales Report
Place Orders

Vendors Detail Purchase Report

Generates Bills

1. Hardware requirements:

• RAM :512MB
• HDD :120GB
• OS : Windows 7 and above
• Processor : Intel core i3 and above
• System bus : 32bits

2. Software requirement:

• Front end : HTML, PHP, CSS.

• Back end : MYSQL phpMyAdmin
• Server side : WAMP
• Browser : Google Chrome, Mozilla Firefox, Opera

2
Are you doing this project for any industry/Client?

 Yes

Duration of the project

 2 Months

Members of the project

Limitations of the project:

• Employee attendance has to be taken manually and entered in the application

• Vendor order has to be generated in our software and sent it through the mail.

Future scope:

• We can provide hardware-based attendance through which we can take attendance in

our software.

• Payment gateway can be added.

2.Technologies

3
2.1 Introduction to programming language [php] :

PHP is a server-side scripting language designed for web development but also used as a
general-purpose programming language. Originally created by Rasmus Lerdorf in 1994, the
PHP reference implementation is now produced by The PHP Group. PHP originally stood for
Personal Home Page, but it now stands for the recursive backronym PHP: Hypertext Pre-
processors.

PHP code may be embedded into HTML code, or it can be used in combination with various
web template system, web content management system and web frameworks. PHP code is
usually processed by a PHP interpreter implemented as a module in the web server or as a
Common Gateway Interface (CGI) executable. The web server combines the results of the
interpreted and executed PHP code, which may be any type of data, including images, with the
generated web page. PHP code may also be executed with a Command Line Interface (CLI)
and can be used to implement Standalone Graphical Applications.

The standard PHP interpreter, powered by the Zend Engine, is free software free software
released under the PHP License. PHP has been widely ported and can be deployed on most
web servers on almost every operating system and platform free of charge.

The PHP language evolved without a written formal specification formal specification or
standard until 2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014
work has gone on to create a formal PHP specification.

PHP development began in 1994 when Rasmusledor wrote several common gateway interface
(CGI) programs in C, which he used to maintain his personal homepage. He extended them to
work with web forms and to communicate with databases and called this implementation
"Personal Home Page/Forms Interpreter" or PHP/FI.

PHP/FI could be used to build simple, dynamic web application. To accelerate bug reporting
and improve the code, Lerdorf initially announced the release of PHP/FI as "Personal Home
Page Tools (PHP Tools) version 1.0" on the UseNet discussion group
comp.infosystems.www.authoring.cgi on June 8, 1995. This release already had the basic
functionality that PHP has as of 2013. This included Perl like variables, form handling, and
the ability to embed HTML. The syntax resembled that of Perl but was simpler, more limited
and less consistent.

Early PHP was not intended to be a new programming language, and grew organically, with
Lerdorf noting in retrospect: "I don’t know how to stop it, there was never any intent to write a
programming language […] I have absolutely no idea how to write a programming language, I
just kept adding the next logical step on the way. A development team began to form and, after
months of work and beta testing, officially released PHP/FI 2 in November 1997.

The fact that PHP was not originally designed but instead was developed organically has led to
inconsistent naming of functions and inconsistent ordering of their parameters. some cases, the
function names were chosen to match the lower-level libraries which PHP was "wrapping

4
while in some very early versions of PHP the length of the function names was used internally
as a harsh function, so names were chosen to improve the distribution of hash values.

This release already had the basic functionality that PHP has as of 2013. This included Perl-
like variables form handling, and the ability to embed HTML. The syntax resembled that of
Perl but was simpler, more limited and less consistent. Early PHP was not intended to be a
new programming language, and grew organically, with Lerdorf noting in retrospect: "I don’t
know how to stop it, there was never any intent to write a programming language […] I have
absolutely no idea how to write a programming language, I just kept adding the next logical
step on the way." A development team began to form and, after months of work and beta
testing, officially released PHP/FI 2 in November 1997.

The fact that PHP was not originally designed but instead was developed organically has led to
inconsistent naming of functions and inconsistent ordering of their parameters. In some cases,
the function names were chosen to match the lower-level libraries which PHP was
"wrapping”, while in some very early versions of PHP the length of the function names was
used internally as a, so names were chosen to improve the distribution of hash values.

2.2 MY SQL:

What is MySQL?

 MySQL is a database server

 MySQL is ideal for both small and large applications
 MySQL supports standard SQL
 MySQL compiles on a number of platforms
• MySQL is free to download and use
What is a database? Quite simply, it’s an organized collection of data. A database management
system (DBMS) such as Access, FileMaker Pro, Oracle or SQL Server provides you with the
software tools you need to organize that data in a flexible manner. It includes facilities to add,
modify or delete data from the database, ask questions (or queries) about the data stored in the
database and produce reports summarizing selected contents.

MySQL is a multithreaded, multi-user SQL database management system (DBMS). The basic
program runs as a server providing multi-user access to a number of databases. Originally
financed in a similar fashion to the JBoss model, MySql was owned and sponsored by a single
for-profit firm, the Sidish company MySQL now a subsidiary of Sun Micro system, which
holds the copyright to most of the codebase. The project’s source code is available under terms
of the GNU General Public License, as ill as under a variety of proprietary agreements. MySql
is a database. The data in MySql is stored in database objects called tables. A table is a
collection of related data entries and it consists of columns and rows. Databases are useful
when storing information categorically.

5
Steps to create a database in PHPMyAdmin:
1) The following figure shows your PHPMyAdmin interface, just enter your
database name and click the 'Create' button to create your database.

2) Now to create a new table enter your table name and the number of fields in the
table, then click the 'Go' Button.

3) The next step is to create the fields, just enter values for each field name, type,
length of the field, null option and mention whether it is a primary key or not.
Then click the 'Save' button to complete your table creation.

4) The following figure is displayed upon successful creation of your table

6
Steps to Drop Table in PHPMyAdmin :
 Login to phpmyadmin.Click 'databases'

 A list of your databases will appear. Click the one that is your WordPress
database.

 Note the size of the 'wp_bad_behaviour_log' table - this is one to be emptied in

this example.

 Now tick the box to the left of the table you wish to empty.
Note: your table may well have a different name, and unless you have been told
otherwise, do NOT empty a table that is used by the Word Press core.

7
 

SQL Server:
Microsoft SQL server 2000 is a set of components that work together to meet the data
storage and enterprises data processing system. The SQL Server architecture
descrwebing how the various components work together to manage data effectively.

Features:
MS SQL features includes: -

 Internet Integration: -
The SQL Server 2000 database engine includes XML support. It also has the
scalability, availability& security features required to operate as data storage
component of the largest website.

 Scalability & Availability: -

The same database engine can be used across platforms ranging from laptop
comps running MS Windows® 98 through, large multiprocessor server running
MS Windows 2000 Data Centre Edition.

 Enterprise-Level Database Features: -

The SQL Server 2000 relational database engine supports the feature required to
supports demanding data processing environment. The database engine protects
data integrity while minimizing the overhead of managing thousands of users
concurrently modifying the database.

 Easy of Installing, Development & Use: -

SQL Server 2000 includes a set of administrative &development tools that
improve upon the process of installing developing managing, & using SQL
Server across several sites.

8
 Data Warehousing: -
SQL Server 2000 includes tools for extracting & analysing summary data for
online analytical processing SQL Server also include tools for visually designing
database and analysing data using English- based question.

2.3 HTML:

HTML means Hypertext Markup Language. HTML is a method of descrwebing the

format of document, which allows them to be vied on computer screen. Web browsers
display HTML documents, program which can navigate across networks and display a
wide variety of types of information. HTML pages can be developed to be simple text or
to be complex multimedia extravaganzas containing, moving images, virtual reality, and
java applets.

The global publishing format of the Internet is HTML. It allows authors to use not only
text but also format that text with headings, list and tables, and also includes still
images videos, and sound within text. Readers can access pages information from
anywhere in the world at the click of mouse button information can be downloaded to
readers own PC or workstations HTML pages can also be used for entering a data and
as a front end for commercial transaction.

2.4 Queries:

A query is a question or a request. With MySql, we can query a database for specific
information and have a record set returned.

Create a connection to a database:

Before you can access data in a database, you must create a connection to the
database. In PHP, this is done with the mysql_connect() function.

Syntax: Mysql connect (server name, username, password);

Server name: Optional Specifies the Server to connect.

2.5 WAMP Server:

AMP is an acronym for Apache (an HTTP Server), MySQL (a relational database) and
PHP (a server-side programming platform). These are industrial-strength, open-source
software that collectively can be used to develop, deploy and run web applications.
Depending on the operating platform, we have:

• WAMP: Windows-Apache-MySQL-PHP
• LAMP: Linux-Apache-MySQL-PHP

9
 • MAMP: Mac-Apache-MySQL-PHP

Setting up WampServer:

WampServer bundles Apache, MySQL and PHP for Windows in a single package. It
also includes tools such as PhpMyAdmin (a MySQL database administration tool), SQL
Buddy (an alternative to PhpMyAdmin), XDebug (a PHP Debugging Tool), Web Grind
(a PHP Profiling Tool).

Installing WampServer:

To install the WAMPServer, simply run the dwnloaded installation file. Choose your
installation directory. I shall assume that WampServer is installed in "d:\WampServer",
denoted as <WAMPSERVER_HOME>, in this article.

Starting WampServer:

To start the WampServer, choose "start WampServer" from the "Start" menu; or run
"wampmanager.exe" from the WampServer installed directory. An icon will appear on
the icon tray. "Green" icon indicates that all the services have started. "Red" indicates
that all the services have stopped. You can put the server online (so that user can access
the server over the Internet) by selecting the option "Put Online". Alternatively, you
could put the server "Offline", such that it is accessweble only within the localhost.

Verifying the Installation:

By default, a directory called "www" was created under the WampServer installed
directory, which serves as the root directory of the Apache Server. A welcome page
called "index.php" was also created in the "www" directory.

To verify the installation:

1. Start the WampServer. Wait for the icon to appear green (indicates that all
services have started). Otherwise, click the icon and select "Start All Services".
For testing, put the server "offline" to disable external access (i.e., it can be
accessed only in local host).
2. Start a browser and issue URL http://localhost. This will in turn request for
"index.php". Observe the output and compare with "index.php" source.

How to run Php script in wamp server:

10
How to run Php script in wamp server. Php Stands for Hypertext Preprocessor. To run php
script we need server (tomcat) as php is server-side programming language. This post will
demonstrate running php script on wamp server. So before getting started with it, we need to
install wamp server on your computer. Now let us make a very basic php script, to print
hello world. This script is as shown below. ‘Echo’ prints the statement.

How to run Php script in wamp server

<html>

<head>

<title>PHP sript</title>

</head>

<body>

<?php echo 'Hello World'; ?>

</body>
</html>
save it as hello.php or with any name that you want to save it with.
Note: The directory you need to chose to save a php file in c:\\wamp\www\ or in the
directory where you have installed wamp server in root directory.

Now startwamp server, by running start wamp server application, and right click on the
icon present in the system tray, as shown below and click on start services.

How to run Php script in wamp server:

11
  Now click on Localhost, which will run a default browser, and if everything goes
correct, it will open the web page as shown below :

 On the urltype :http://localhost/hello.php, and it will show up the output as :

2.6 DREAMWEAVER :

Adobe Dreamweaver is a web design and development application that provides a visual
WYSIWYG editor (colloquially referred to as the Design view) and a code editor with
standard features such as syntax highlighting, code completion, and code collapsing as
well as more sophisticated features such as real-time syntax checking and code
introspection for generating code hints to assist the user in writing code. [4] The Design
view facilitates rapid layout design and code generation as it allows users to quickly
create and manipulate the layout of HTML elements. Dreamweaver features an
integrated browser for previewing developed webpages in the program's own preview
pane in addition to allowing content to be open in locally installed web browsers. It
provides transfer and synchronization features, the ability to find and replace lines of text
or code by search terms or regular expressions across the entire site, and a templating
feature that allows single-source update of shared code and layout across entire sites
without server-side includes or scripting. The behaviors panel also enables use of basic
JavaScript without any coding knowledge, and integration with Adobe's Spry Ajax
framework offers easy access to dynamically-generated content and interfaces.

12
Dreamweaver can use third-party "Extensions" to extend core functionality of the
application, which any web developer can write (largely in HTML and JavaScript).
Dreamweaver is supported by a large community of extension developers who make
extensions available (both commercial and free) for most web development tasks from
simple rollover effects to full-featured shopping carts.Dreamweaver, like other HTML
editors, editsfiles locally then uploads them to the remote web server using FTP, SFTP,
or WebDAV. Dreamweaver CS4 not supports the Subversion (SVN) version control
system.

2.7 SECURITY:

View are basically used as a part of security, means in many organizations, the end
user will never be given original tables & all data entry will be done with the help of
views only. But the database administrator will be able to see everything because all the
operations done by the different users will come to the same table.

13
 3.PROJECT SUBJECTS

3.1 About project:

In the light of the current economic crisis, business has become very complex. On one hand,
the organizations have to meet the exceeding competitive consumer’s demands, and, on the
other hand, they must now add the new perspective of environment friendly business practices
as a social demand of civil society and government. The major challenge is to make the right
product available to the consumer at the right place, on the right time and at the right prices in
an eco-friendly manner with maximizing shareholders value. This underscores the importance
of green supply chain management in the organizations. The environmental performance of
product and processes often provide competitive advantage to the organizations. Therefore, it
is critically important for the business to create distribution networks which are able to deliver
the goods and services as per the consumer’s need, keeping in mind the environmental
concerns and profitability.

 In the modern days there is need of so many automation and fast access technique
which performs admin work efficiently with the help of internet.

 Internet is the rapidest growing media in the past decade especially online
advertisement is rapidly growing e-commerce area.
 To improve the performance of any business, providing information to the
customer plays a vital role in any field.
 Our goal is to make sure that our customers have a magnificent familiarity using
our facility.
 In the virtue of this, we are developing the application which helps the user to get
the details about Medical and Tablet

 This is a web application where any variations done through admin can be
observed by the customers.

3.2 Existing System:

 In present scenario workers explain features to the customers and there is a
possibility for them to miss some of the features of the medical related
products.

 The owner has to pay additional amount for advertisement each time.

 The customers can visit the shop only on the specified timings for any query
or product related details.

 Manual bill generations.

 Paper based stock management, sales report, purchase report.

14
3.3 Problem Statement:

• Paper works with lots of ledgers create unnecessary confusions.

• Confusions in packages and destinations.
• Calculation errors.
• Manual data maintenance makes it less secure than the software.
• Manual data has the risk of loss and burn as papers catch fire easily.

3.4 Proposed System:

 In the proposed system we are planning to develop a web based application for
the sales and ordering of the product for the customer.
 Admin can order to the vendor regarding raw materials

3.5 Modules:
 Admin
 Order
 Purchase
 Report

Admin:
Admin will be maintaining the complete system flow he will be managing the
product based on the categories and the composition

 Product entry
 View Order
 Manage Employee detail and their payments
 Payment detail
 Raw materials purchases
Order:
Customer can view details regarding different product and their packaging and can
give orders.

15
Purchase:
Admin needs to purchase raw materials such as pet bottles, card board boxes and Pet
Bottles from different vendors.

Report:
Based on the master entry different reports have to be generated such as sales report,
purchase report, salary report, stock records etc.

16
 4. SYSTEM REQUIREMENT AND ANALYSIS

4.1 Definition
System Analysis is the detailed study of the various operations performed by the system and
their relationships within and outside the system. Analysis is the process of breaking
something into its parts so that the whole may be understood. System analysis is concerned
with becoming aware of the problem, identifying the relevant and most decisional variables,
analysing and synthesizing the various factors and determining an optional or at least a
satisfactory solution. During this a problem is identified, alternate system solutions are
studied, and recommendations are made about committing the resources used to the system.

4.2 Analysis:

Object-oriented analysis is the process of analysing a task to develop a conceptual

model that can then be used to complete the task. A typical OOA model would describe
computer software that could be used to satisfy a set of customer-defined requirements.
During the analysis phase of problem-solving, the analyst might consider a written
requirements statement, a formal vision document, or interviews with stakeholders or other
interested parties. The task to be addressed might be divided into several subtasks (or
domains), each representing a different business, technological, or other areas of interest. Each
subtask would be analysed separately. Implementation constraints, (e.g., concurrency,
distribution, persistence, or how the system is to be built) are not considered during the
analysis phase; rather, they are addressed during object analysis design (OOD).

The conceptual model that results from OOA will typically consists of a set of use
cases, one or more UML class diagrams, and a number of interaction diagrams. It may also
include some kind of user interface mock-up.

4.3 Object-Oriented Analysis Design:

Object oriented analysis and design (OOAD) is a software engineering approach that models a
system as a group of interacting objects. Each object represents some entity of interest in the
system being modelled, and is characterized by its class, its state (data elements), and its
behaviour. Various models can be created to show the static structure, dynamic behaviour, and
runtime deployment of these collaborating objects. There are a number of different notations
for representing these models, such as the Unified Modelling Language (UML).

Object – oriented analysis (OOA) applies object – modelling techniques to analyze the
functions requirements for a system. Object – oriented design (OOD) elaborates the analysis
models to produce implementation specifications. OOA focuses on what the system does,
OOD on how the system does it.

17
4.4 Tools/platforms for languages to be used:
 Hardware requirements:

Processor Intel i3 and above

RAM 512 MB and above

Hard Disk 120GB and above

System bus 32 bit

 Software requirements:

Operating System Windows 7 and above

Front End PHP, CSS, HTML

Back end MYSQL phpMyAdmin

Server WAMP Server

Browser Chrome/Firefox/Internet Explorer

 Client-side requirements:

Processor Intel i3 and above

Operating system Windows 7 and above

RAM 512 MB and above

18
 4.5 SOFTWARE REQUIREMENT SPECIFICATION:
Overview of SRS:
The Software requirement specification is developed to address the user requirement for the
development of software. This document provides purpose scope functional and non-
functional requirements of ‘leave management system’ it also specifies user interface
performance etc, Using PHP and CSS, DREAMWEAVER(TOOLS) to develop the system.

INTRODUCTION:
SRS is the official statement of what is required of the system developers; it includes both
user requirements for the system and detailed specification of the system requirements. This
document is used while designing the proposed system and can also be used in the future if the
system is to be enhanced.

Scope of the project:

This software will provide the “PET BOTTLES DISTRIBUTION” (client) with many
efficient ways of managing daily task, as well as provide management with useful reports. The
system is going to be used by the admin of the edible Pet Bottles industry which is used to
save all the important data based on concepts the system is designed.
The scope includes the targeted user and function that involved in the system the scope
of this document lies between developer of the application and end user. The document can
also be used for future enhancement.

Purpose:
 To make the application of edible Pet Bottles industry usable for the Nagraj
Balganavar (Client).
 To access the employee’s records and get the desired information which may require.
 To automate the existing system of manually maintain the records of the employee
records and information of daily basis transaction.
 To increase data accuracy, make Company information and other data collection more
secure, effective and convenient.
 To access each employee details.

Definitions, Acronyms and Abbreviations:

 GUI: Graphical User Interface

 HTML: Hypertext Markup language. is the predominant markup language for
webpages.
 HTTP-Hyper Text Transfer Protocol.
 PHP: Pre-Hypertext Processor

19
  PHP Triad: PHP Triad installs a complete working PHP/MySql server environment
on Windows /Linux platforms Installs PHP, MySql, Apache, and PHPMyAdmin.
 DHTML: Dynamic Hypertext Markup language is the predominant markup
language for web pages.
 SRS-Software Requirement Specification.
 WAMP-Windows Apache MySQL Perl.

4.6 Specific Requirements:

External Interface Requirements:
 User Interface: Accomplishes via mouse and keyboard input to the GUI based forms.
 Software Interface: The product requires to runtime Php environment in server machine.

Functional Requirements:
Functional requirements are statements of the services that the system must provide or are
descriptions of how some computations must be carried out.The plan for implementing
functional requirements is detailed in the system design.

 Basic and advance admin facilities like add/update/delete Staff details are provided.

 Manages staff details.

Non-Functional Requirements
A non-functional requirement is a requirement that specifies criteria that can be used to judge
the operation of a system, rather than specific behaviours. This should be contrasted with
functional requirements that define specific behaviour or functions.The plan for implementing
non-functional requirements is detailed in the system architecture.

 The application is available from several locations and it is accessible 24x7 with the help
of internet.
 The code is easily understood and read because of the structure and coding style of the
application.
 Various components are provided in order to improve the performance at peak time

4.7 User Interface:

The user interface allows the users to remotely access the system via several
applications. Users will be able to use the service through applicationssuch as Mozilla
Firefox,Microsoft Internet Explorer, etc. Allow the user to access the information fast and
easily from remote locations.

20
 4.7.1 Compatibility
The software is compatible with Windows XP.It also works well with Windows
2000 or higher. It requires Microsoft Internet Explorer 5.0(or any latest web
browser) or above with WAMP Server.

4.7.2 Portability
The software is extremely portable in the sense that it can be run on any machine
with a web-browser.

4.7.3 Acceptance Criteria

The system must work well and compile with all the requirements and constraints
stated above. All conditions defined by the need user by the end user are to be
satisfied. The system should satisfy all the requirement and constraints of the
Student management system and must work well according to necessity.

4.8 Feasibility study:

Preliminary investigations examine project feasibility; the likelihood of how the system is
will be useful to the organization. Three tests of feasibility all equally important are studied.

4.8.1 Operational feasibility:

Operational feasibility is based on whether the user will accept the developed
application and will satisfy the needs of the user.

4.8.2 Technical feasibility:

Technical feasibility is based on whether the proposed system is capable of
holding the data required for the application.

4.8.3 Financial feasibility:

This concept is based on the financial status of the owner such that he must
have sufficient budget to develop the proposed system which is cost effective.

21
4.9 SYSTEM REQUIREMENT:

System specification forms the foundation on which the architecture, design

and implementation of a software is built. Documents containing system specifications
are critical because major expenses come along with having to fix the implementation
of incorrect requirements as a result of not having a specification document on hand.
System specification documents can thus be defined as the requirements
documentation that formally specifies the system-level requirements of a software
application.

System specification documents most predominantly contain information on basic

website
requirements which included are:

 Performance levels
 Reliability
 Quality
 Interfaces
 Security and privacy
 Constraints and limitations
 Functional capabilities
 Data structures and elements

4.10 Overview:
 Design the proposed system
 Implementing the system
 the software
 Installing Testing the system for compliances
 Maintaining the system
 Perform validation and rectify error if any

22
 Overall Description:
Operational Environment:

Languages:
The application is implemented using the following:
 HTML
 CSS
 PHP
 MySql as a database

User Characteristics:
In common the USER should be familiar and must have the knowledge of windows operating
system. Basic computer knowledge of using keyboard, mouse and common windows
environment is required.
The primary user of the application is the admin who maintains the software or product
he should know about the data present and the data he wants to view, so that he can efficiently
use the function of the proposed system. The software is GUI based to reduce the user non-
friendliness towards the software.
There are various kinds of users for the product. Usually web products are visited by
various users for different reasons.

Admin:
Admin will be maintaining the complete system flow he will be managing the product
based on the categories and the composition

 Product entry
 View Order
 Manage Employee detail and their payments
 Payment detail
 Raw materials purchases

23
Order:
 Customer can view details regarding different product and their packaging and can
give orders.

Employee:

 Daily employee attendance will be generated and the salary will be generated
based on the same.

System Features:
In general, the user should be familiar and must have the knowledge of windows operating
system. Basic computer knowledge of using keyboard, mouse and common windows
environment is required. the primary user is admin who maintains the software or product he
should know about the data present and the data he want to view, so that he can effectively use
the function of the proposed system. The software is GUI based to reduce the user non-
affability towards the software. It is also provided with the proper information message when
clicked on the button.

24
 5.SYSTEM DESIGN

5.1 Introduction:
The purpose of the decision phase is to plan a solution of the problem specified by the
requirements document. This phase is the first step moving the problem domain to the solution
domain. It involves the process, in which conceiving, planning and the carrying out the plan by
generating the necessary report and inputs, in other words, the design phase act as a bridge
between SRS and implementation phase. The design of the system is perhaps the most critical
factor affecting the quality of the software and as a major impact on the later phase, particularly
the testing and maintenance.

5.2 System Design:

Design is the key phase of any project. It is the first step in moving from the problem
domain to the solution domain. The input to the design phase is the specifications of the system
to be designed. The output of the top-level design is the architectural design, or the system
design for the software system to be built. A design should be very clear, verifiable, complete,
traceable, efficient and simple.

5.2.1 Architecture Diagram:

The architecture design defines the relationship among major structural element of the
program. Architecture diagram shows the relationship between different components of
system. This diagram helps to understand the overall concept of system.

25
 5.2.2 Logical design:
The graphical representation of systems’ data and how the process transforms the data is known
as Data Flow Diagram. It shows the logical flow of the data.
The logical design describes the detailed specification for the system, describing its features,
an effective communication and the user interface requirements. The logical system of
proposed system should include the following.
1. External system structure.
2. Relationship between all the activities.
3. The physical construction and all the activities.
4. Global data.
5. Control flow.
6. Derived program structure.

5.2.3 Design Principles:

Basic design principles that enable the software engineer to navigate the design process are:
 The design process should not suffer from “Tunnel vision”.
 The design should be traceable to analysis model.
 The design should not reinvent the wheel.
 The design should minimize the intellectual distance between the software and the
problem, as it exists in the real world.
 The design should exhibit uniformity and integrity.
 The design should be structured to accommodate changes.
 The design not coding, the coding is not a design.
 The design should be assessed for the quality, as it is being created, not after the fast.
The design should be reviewed to minimize the conceptual errors.

Data flow diagrams:

1.Data Flow diagrams

A data flow diagram (DFD) is a significant modelling technique for analysing

and constructing information processes. Data-flow diagram (DFD) is a graphical
representation of the "flow" of data through an information system. DFDs can also be
used for the visualization of data processing (structured design). On a DFD, data items
flow from an external data source or an internal data store to an Internal data store or an
external data sink, via an internal process. A DFD provides no information about the

26
timing or ordering of processes, or about whether processes will operate in sequence or
in parallel. It is therefore quite different from a flowchart.

This shows the flow of control through an algorithm, allowing a reader to determine
what operations will be performed, in what order, and under what circumstances, but not
what kinds of data will be input to and output from the system, nor where the data will
come from and go to, nor where the data will be stored (all of which are shown on a
DFD). Dataflow diagrams provide the end user with a physical idea of where the data
they input ultimately has an effect upon the structure of the whole system from order to
dispatch to report. How any system is developed can be determi1.ned through a data-
flow diagram.

With a data-flow diagram, users are able to visualize how the system will operate,
what the system will accomplish, and how the system will be implemented. A designer
usually draws a context-level DFD showing the relationship between the entities inside
and outside of a system as one single step. This basic DFD can be then disintegrated to a
lower level diagram demonstrating smaller steps exhibiting details of the system that is
being modeled. Numerous levels may be required to explain a complicated system. The
different versions are Context Diagrams (Level 0), Partitioned Diagrams (single process
only -- one level), functionally decomposed, levelled sets of Data Flow Diagrams.

2.Data Flow Diagrams Symbols:

A DFD usually comprises of four components. These four components can be

represented by four simple symbols. These symbols can be explained in detail as follows:
External entities (source/destination of data) are represented by squares; Processes
(inputprocessing-output) are represented by rectangles with rounded corners; Data Flows
(Physical or electronic data) are represented by arrows; and finally, Data Stores (physical
or electronic like XML files) are represented by open-ended rectangles.

Data store

Or

27
 A data store stores data passively for later access. A data store responds to requests to
store and access data. It does not generate any operations.

A data store allows values to be accessed in an order different from the order in which
they were generated.

Input flows indicate information or operations that modify the stored data such as
adding or deleting elements or changing values. Output flows indicate information
retrieved from the store; this information can be an entire value or a component of a
value.

Data flow :

A data flow moves data between processes or between processes and data stores.
As such, it represents a data value at some point within a computation and an
intermediate value within a computation if the flow is internal to the diagram. This value
is not changed. The names of input and output flows can indicate their roles in the
computation or the type of the value they move. Data names are preferably nouns. The
name of a typical piece of data, the data aspect, is written alongside the arrow.

Data Process

Or

A process shows a transformation or manipulation of data flows within the system. The
symbol used is rounded rectangle or oval. A descriptive title is placed in the centre of the
circle.This should be asimple imperative sentence with a specific verb, for example
'maintain customer records' or 'find driver'. E.g.: May be a clerk computing discounts or
a combination of manual and electronic activities.

Source or Sink

Or

28
An external entity is a source or destination of a data flow which is outside the area of
study.
The symbol used is a rectangle or square containing a meaningful and unique identifier.
Only those entities which originate or receive data are represented on a business process
diagram E.g.: May be one customer or a number of customers with transactions (orders).
Rules for Creating DFD

• Processes should be named and numbered for easy reference. Each name should
be representative of the process.
• The direction of flow is from top to bottom and from left to right. Data
traditionally flow from the source (upper left corner) to the destination although
they may flow back to a source. One way to indicate this is to repeat the source
symbol as a destination. Since it is used more than once in the DFD, it is marked
with a short diagonal in the lower right corner.
• When a process is exploded into the lower-level details, they are numbered.
• The names of data stores, sources and destinations are written in capital letters.
Process and data flow names have the first letter of each word capitalized.

Data Flow Diagrams:

Overall DFD:

29
Level-0

Level-1

30
 6. E R Diagram

An entity-relationship diagram is a data modelling technique that creates a

graphical representation of the entities, and the relationships between entities, within an
information system. An entity-relationship model (ERM) is an abstract and conceptual
representation of data. Entity-relationship modelling is a database modelling method,
used to produce a type of conceptual schema or semantic data model of a system, often a
relational database, and its requirements in a top-down fashion. Diagrams created by this
process are called entity-relationship diagrams, ER diagrams, or ERDs

The first stage of information system design uses these models during the requirements
analysis to describe information needs or the type of information that is to be stored in a
database. The data modeling technique can be used to describe any ontology (i.e. an overview
and classifications of used terms and their relationships) for a certain area of interest. In the
case of the design of an information system that is based on a database, the conceptual data
model is, at a later stage (usually called logical design), mapped to a logical data model, such
as the relational model; this in turn is mapped to a physical model during physical design.
Sometimes, both of these phases are referred to as "physical design".

The three main components of an E-R Diagram are:

• The entity is a person, object, place or event for which data is collected. For
example, if you consider the information system for a business, entities would
include not only customers, but the customer’s address, and orders as well. The
entity is represented by a rectangle and labelled with a singular noun.
• The relationship is the interaction between the entities. In the example above, the
customer places an order, so the word “places” defines the relationship between
that instance of a customer and the order or orders that they place. A relationship
may be represented by a diamond shape, or more simply, by the line connecting
the entities. In either case, verbs are used to label the relationships.
• The cardinality defines the relationship between the entities in terms of numbers.
An entity may be optional: for example, a sales representative could have no
customers or could have one or many customers; or mandatory: for example,
there must be at leastone product listed in an order. There are several different
types of cardinality notations; crow’s foot notation, used here, is a common one.
In crow’s foot notation, asingle bar indicates one, a double bar indicates one and
only one (for example, a single instance of a product can only be stored in one
warehouse), a circle indicates zero, and a crow's foot indicates many. The three
main cardinal relationships are: one-to-one, expressed as 1:1; one-to-many,
expressed as 1: M; and many-to-many, expressed as M: N.

31
Entity Relationship Diagram Notations:
Peter Chen developed ER Diagram’s in 1976. Since then Charles Bachman and
James Martin have added some sleigh refinements to the basic ERD principles.

Entity:
An entity is an object or concept about which you want to store
information.An entity is a real-world item or concept that exists on its own.The set
of all possible values for an entity, such as all possiblecustomers, is the entity type.
In an ER model, we diagram an entity typeas a rectangle containing the type name.

Weak Entity:
A weak entity is an entity that must defined by a foreign key relationship with
another entity as it cannot be uniquely identified by its own attributes alone.

Attribute:

Each entity has attributes, or particular properties that describe the entity. Most of
the data in a database consists of values of attributes. The set of all possible values of an
attribute is the attribute domain. In an E R model, an attribute name appears in an oval
that has a line to the corresponding entity box.

Key attributes:

A key attribute is the unique, distinguishing characteristic of the entity. An attribute or set of
attributes that uniquely identifies a particular entity is a key. A key attribute in an ER Diagram
is represented by an oval that has a line inside it and a line to the corresponding entity box. For
example, an employee's social security number might be the employee's key attribute.

32
Multi-valued attribute:

A multi-valued attribute can have more than one value. We indicate this with a double
oval.
For example, an employee entity can have multiple skill values.

Derived attribute:

A derived attribute is based on another attribute. It is denoted by a oval and

dotted line within it. For example, an employee's monthly salary is based on the
employee's annual salary.

Relationships:

Relationships illustrate how two entities share information in the database

structure.An association among entities is called a relationship. An attribute can also be a
property of a relationship set. The association among the entities is described as one-to-
one, one-to-many, many-to-many. A relationship is indicated by a rhombus.

Identifying relationship:

Identifying relationship is denoted by double rhombus.

33
Composite Attribute
A composite attribute has multiple components and each component is atomic or
composite. We illustrate this composite nature in the ER model by branching off the
component attributes.

....

Total Participation:
Total participation is represented by a double line.

Cardinality:

Cardinality specifies how many instances of an entity relate to one instance of

another entity. O0rdinarily is also closely linked to cardinality. While cardinality
specifies the occurrences of a relationship, ordinarily describes the relationship as either
mandatory or optional. In other words, cardinality specifies the maximum number of
relationships and ordinarily specifies the absolute minimum number of relationships.

34
35
 7. DATABASE TABLES

ATTENDANCE TABLE

COLUMN TYPE KEY DEFAULT

Attendance Id int(30) Primary No

Employee Id int(40) No

Attendance Date date No

Status varchar(50) No

BILLINGS TABLE

COLUMN TYPE KEY DEFAULT

Bill Id int(30) Primary No

Bill Date date No

Order Id int(30) No

Amount int(40) No

Tax double No

Total amount int(50) No

DISTRIBUTOR TABLE

36
 COLUMN TYPE KEY DEFAULT

Distributor Id int(20) Primary No

Distributor Name varchar(50) No

Address varchar(100) No

Email varchar(50) No

Contact int(20) No

Route varchar(50) No

City varchar(50) No

EMPLOYEE TABLE

COLUMN TYPE KEY DEFAULT

Employee Id int(30) Primary No

Employee Name varchar(40) No

Employee Contact int(30) No

Employee Address varchar(40) No

Joining Date Date No

LOGIN TABLE

COLUMN TYPE KEY DEFAULT

37
 Username varchar(40) No

Password int(20) No

Usertype varchar(40) No

Hintq varchar(40) No

Hinta varchar(40) No

ORDER TABLE

COLUMN TYPE KEY DEFAULT

Order Id int(20) Primary No

Order date date No

Distributor Id int(20) No

ORDER DETAIL TABLE

38
 COLUMN TYPE KEY DEFAULT

Detail Id int(20) Primary No

Order Id int(20) No

Product Id int(20) No

Quantity int(20) No

Amount int(20) No

Total int(20) No

PAYMENT TABLE

COLUMN TYPE KEY DEFAULT

Product Id int(20) Primary No

Product date date No

Bill Id int(50) No

Total Amount int(50) No

Paid Amount int(40) No

Balance Amount int(50) No

PRODUCT TABLE

COLUMN TYPE KEY DEFAULT

39
 Product Id int(20) Primary No

Product Name varchar(30) No

Category Type varchar(50) No

Product Quantity int(20) No

Price int(20) No

Product Description varchar(30) No

RAW MATERIAL TABLE

COLUMN TYPE KEY DEFAULT

Raw_m_Id int(20) Primary No

Raw Name varchar(30) No

Raw Detail varchar(50) No

Used for varchar(30) No

Stock int(20) No

Updated Date date No

RAW PRODUCT TABLE

COLUMN TYPE KEY DEFAULT

40
 Raw_p_Id int(20) Primary No

Payment Date Date No

Raw_m_Id int(20) No

Quantity int(20) No

Price Quantity int(20) No

Amount int(20) No

SALARY TABLE

COLUMN TYPE KEY DEFAULT

Salary Id int(20) Primary No

Salary Date Date No

Employee Id int(20) No

Month varchar(50) No

Present Days int(60) No

Daily Wages int(40) No

Amount int(30) No

STOCK TABLE

COLUMN TYPE KEY DEFAULT

41
 Stock Id int(30) Primary No

Distributor Id int(40) No

Product Id int(40) No

Quantity int(40) No

8.SCREENSHOT

42
43
 Source code
LOGIN CODE;

<!DOCTYPE html>
<html lang="en">
<head>
<title>Transparent Sign In Form A Responsive Widget Template :: w3layouts</title>
<!-- Meta tag Keywords -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="keywords" content="Transparent Sign In Form Responsive Widget,Login form
widgets, Sign up Web forms , Login signup Responsive web form,Flat Pricing table,Flat Drop
downs,Registration Forms,News letter Forms,Elements" />
<script type="application/x-javascript"> addEventListener("load", function()
{ setTimeout(hideURLbar, 0); }, false);
function hideURLbar(){ window.scrollTo(0,1); } </script>
<!-- Meta tag Keywords -->
<!-- css files -->
<link rel="stylesheet" href="css/font-awesome.css"> <!-- Font-Awesome-Icons-CSS -->
<link rel="stylesheet" href="css/style.css" type="text/css" media="all" /> <!-- Style-CSS -->
<!-- //css files -->
<!-- web-fonts -->
<link href="//fonts.googleapis.com/css?family=Raleway:400,500,600,700,800"
rel="stylesheet">
<link href="//fonts.googleapis.com/css?family=Roboto:300,400,500,700" rel="stylesheet">
<!-- //web-fonts -->
</head>
<body>
<!--header-->
<div class="header-w3l">
<h1>Login Form</h1>

44
</div>
<!--//header-->
<!--main-->
<div class="main-content-agile">
<div class="sub-main-w3">
<h2>Sign In</h2>
<form action="#" method="post">
<h6>Swiftly sign in with</h6>
<div class="navbar-right social-icons">

<div class="clear"></div>
</div>
<h6>Or use your email</h6>

<div class="icon2">
<input placeholder="username" name="username" type="username" required="">
</div>
<div class="icon2">
<input placeholder="Password" name="Password" type="password" required="">
</div>
<label class="anim">
<input type="checkbox" class="checkbox">
<span>Remember Me</span>
<a href="#">Forgot Password</a>
</label>
<div class="clear"></div>
<input type="submit" value="Sign in">
</form>
</div>

45
</div>
<!--//main-->
<!--footer-->
<div class="footer"><p>&copy; 2017 Transparent Sign In Form. All rights reserved | Design
by <a href="http://w3layouts.com">W3layouts</a></p>
</div>
<!--//footer-->
<!-- js -->
<script type="text/javascript" src="js/jquery-2.1.4.min.js"></script>
<script src="js/jquery.vide.min.js"></script>
<!-- //js -->
</body>
</html>

DATEBASE CONNECTIVITY:

<?php

$con=mysql_connect('localhost','root','');

mysql_select_db('eopd',$con);

?>

46
 $id=$_REQUEST['id'];

$sql="delete from employee where emp_id='$id'";

$res=mysql_query($sql);

?>

<script>

alert('deleted');

document.location="employee_view.php";

</script>

47
 10.Testing

10.1 Introduction:
Testing is a process of executing program with an indent of finding error. Testing is
vital to success of the system. Testing demonstrates that the software functions appear to
be working according to the specifications and performance requirements appeared to
have been met. If a test is conducted successfully, it will discover errors in the software.

Test Objectives:
The system is tested with variety of inputs. The System is tested for accuracy and
correctness of the results obtained. Finally, the system is tested for inter-operability.
Testing Principles
 All tests should be traceable to end user requirements
 Tests should be planned long before testing begins
 Testing should begin on a small scale and progress towards testing in large
 Exhaustive testing is not possible
 To be most effective testing should be conducted by a independent third party
The primary objective for test case design is to derive a set of tests that has the highest
livelihood for uncovering defects in software. To accomplish this objective two different
categories of test case design techniques are used. They are
 White box testing.
 Black box testing.

10.2 Test Approaches:

Black Box Testing:
This method focuses on the functional requirements of the software. This testing
enables to derive set input conditions that will fully exercise all functional requirements
of the program. Black Box Testing attempts to find errors in the following category.
• Incorrect or missing functions.
• Interface errors.
• Performance errors.
• Initialization and Termination errors.

48
 White Box Testing:
This is performed early in the testing process; white Black Box testing is
applied during the last stage of testing. In this test cases are generated on the logic of
each module by drawing flow graphs of that module and logical decisions are tested
on all the cases.
It has been used to generate the test case in the following test cases:

• Guarantee that all independent paths have been executed.

• Execute all logical decisions from their True and False side.
• Execute all loops at their boundaries and within their operational bounds.
• Execute internal data structures to ensure their validity.

10.3 Testing Strategies:

A strategy for software testing must accommodate low-level tests that are necessary to
verify that all small source code segments has been correctly implemented as well as
high-level tests that validate major system functions against customer requirements.

There are two general strategies for testing software. These are as follows:

Code Testing:
This examines the logic of the program. To follow this test, cases are developed such
that every path of program is tested.

Specification Testing:
Specification Testing examines the specification starting what the program should do
and how it should perform under various conditions. Then test cases are developed for each
condition and combinations of conditions and to be submitted for processing

10.4 Levels of Testing

Testing process the stages in is:

Unit Testing:
Individual components are tested to ensure that they operate correctly. Each
component tested independently without other system components. Ex. Checked for Username
and Password with the table, after the next module is loaded session allocation.

49
 Integration Testing:
Integration testing is a systematic technique for constructing the program structure
while at the same time conducting test to uncover errors associated with interfacing. This testing
is done using the bottom-up approach to integrate the software components of the software
system in to functioning whole.

System Testing:
System testing is actually a series of different tests whose primary purpose is fully to
exercise the computer-based system. The system tests that where applied are recovery testing
and performance testing. Finally a review or audit is conducted which is a final evaluation that
occurs only after operating the system long enough for user to have gained a familiarity with it.
System testing was done by the inspection team to verify that all the functionality identified is
the software requirement specification has been implemented. Defects that crept in the system
has been found defect free and is working well. System testing is concerned with interfaces,
design logic, control flow recovery, procedures throughput, capacity and timing characteristics
of the entire system. For blank field, alphabets, number and special character validation.

Security Testing:

This attempts to verify whether the protection mechanism is built into the
system. In this testing the authentication of the users is checked and authorized users
are allowed to access the database.

Performance Testing:

Performance testing can serve different purpose. It can demonstrate that

the system meets the performance criteria. It can compare two systems to find which
performs better, or it can measure what parts of the system or workload cause the
system to perform badly. In the diagnostic case, software engineers use tools such as
profilers to measure what parts of a device or Software contributes most to the poor
performance.

Acceptance Testing:
User acceptance of the system is the key factor for the success of any system. This is
done by user. The system is given to the user and they test it with live data. Acceptance testing
involves the planning and execution of functional test. Performance tests, stress tests in order to
demonstrate that the implemented system satisfies its requirements. Two sets of acceptance test
can be run, those developed by the customer. The system has been tested for its performance at
unit level by the individuals through performance testing that is designed to test the run time

50
performance of the software. The performance of the fully integrated system is tested and was
found good.

Unit Module Sub-System System Acceptan

ce
Testing Testing Testing
Testing

Test Cases and Result

Test case 1:
Test Case Name Customer/Admin Login

Test Case Description Verifies the login of particular Admin or

User

Procedure/(inputs) url of the website

Expected output Homepage opens

Observed output Homepage opens

Remark Successful

51
 11. CONCLUSION

The ultimate aim of the project ' PET BOTTLES DISTRIBUTION ' is to provide the
user-friendly website to the administrator,distributor and customer as well. Where
administrator can update and store the over information about the industry (daily transactions,
information about the employees, information of the customers, billing details transportation
details etc). He can contact admin and fetch the information about the industry through
website.

52
 LIMITATIONS

LIMITATIONS OF THE SYSTEM:

 Agencies have to manually approach us for registration to our site.

 Online payment is not being used in our system. The user has to manually
contact agencies for payment.

FUTURE SCOPE OF THE SYSTEM

1.Outcome

This project is mainly developed to reduce the burden of maintaining the papers
and records in paper format, this project mainly focuses on making the job of
maintaining the records and generating the bill easy and maintain the records perfectly in
an organized manner. this software as it has two different access portals for the admin
and the agency person it will stay well organized.

2. Future Enhancement

This software will further be developed in android to reduce the burden of using the
computers and makes it easy to access anywhere freely.

In the later part the tracking will be improvised using the bar codes and the
parcels will be tracked for every instance it reaches.

53
 12. Bibliography

Online references:

https://en.wikipedia.org/wiki/MySQL
https://en.wikipedia.org/wiki/PHP
http://www.w3schools.com/php/php_mysql_intro.asp
http://www.w3schools.com/php/
http://searchsqlserver.techtarget.com/definition/database
Book references:

Complete Reference on PHP by Robert Sebezta

HTML how to program by RohitKhurana

Data Base Management System by Raghuramkrishnan

Software Engineering by Roger S Bressman

54
55
56
57
58
59
60
61
62
63
64