Dairy Management System

Chapter 1

INTRODUCTION
1.1 Objectives

The online food ordering system has been developed to override the problems prevailing n
the practicing manual system This software is supported to eliminate and in some cases,
reduce the hardships faced by this existing system
The main objective of the online food ordering system is to manage the details of item
Category ,food, delivery address, shopping cart. It manages all the information about item
Category, customer, shopping cart. The purpose of the project is to build an application
program to reduce the manual work.
The application is used as much as possible to avoid errors while entering the data. It also
provides error iMessage while entering invalid data. No formal knowledge is needed for the
user to use this system Thus, it proves that it is user-friendly. Online Food Ordering System,
as described above, can lead to error free, secure, reliable and fast management system
Online Food Ordering System is a user friendly php/MySQL based project which helps users
to book movie tickets with cask.
The main goal of this project is to provide movie tickets to customers with a simple interface.
The web page uses HTML, CSS and JavaScript in the front end for better appearance and better
interaction with the users, a database engine known as MySQL is used for storing and
retrieving information from the database.
It was developed using a software known as Brackets which is particularly used for web
development.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 1

Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 2

 Dairy Management System

Chapter 2
REQUIREMENTS SPECIFICATION

A computerized way of handling information about property and user's details is efficient,
organized and time saving, compared to a manual way of doing so, this is done through a
database driven web application whose requirements are mentioned in this section.

2.1 Specific Requirements

The specific requirements of Online Food Ordering System are stated as follows:

2.1.1 Software Requirements

Software used:
Operating System-Windows XP with any Compatible Operating system
Front End-HTML with CSS
Controller-PHP
Back End – MySQL server

2.1.2 Hardware Requirements

Hardware Components used:

Hard Disk – Minimum of 2GB

RAM - 2GB
Peripherals - Standard PS/2 or USB Keyboard, Standard PS/2 or USB Wheel/Optical
Mouse
Processor – Intel Core Duo 2.0 GHz

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 3

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 4

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 5

 Dairy Management System

Chapter 3
SYSTEM DESIGN
The purpose of the design phase is to develop a clear understanding of what the developer wants
people to gain from his/her project. As the developer works on the project, the test for every
design decision should be efficient.
A purpose statement affects the design process by explaining what the developer wants the
project to do, rather than describing the project itself. The Design Document will verify that the
current design meets all of the explicit requirements contained in the system model as well as the
implicit requirements desired by the customer.

3.1 Structure of Design Document

Since end users are the ones who are finally going to use the system, their requirements need
to be identified. This involves questioning the end users what their expectations were. The
main requirement of the end user is that the system should be easy to use and take less time.
In addition to these another important factor was to eliminate the need for database
conversion and migration that had to be carried out presently. After conducting interviews
with the users, a document called the software requirement specification was created. This is
the most important document that forms the basis for system development. It should be
consistent, complete, unambiguous, traceable and inter-related. This document has the
following components:

ii) Functional Requirements

The functional requirements specify relationship between the inputs and outputs. All the
operations to be performed on the input data to obtain output are to be specified. This
includes specifying the validity checks on the input and output data, parameters affected by
the operations and the other operations, which must be used to transform the inputs into
outputs. Functional requirements specify the behavior of the system for valid input and
outputs

iii) Performance Requirements

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 6

 Dairy Management System

This section includes performance of the product that are set by user interaction and studying
the existing system of the organization. These are stated in complete measurable terms, so
that they can be verified during system evaluation phase.

3.2 Hardware Requirements

Processor : Intel Core Duo 2.0 GHz
RAM : 1 GB or More
Hard disk : 80GB or more
Monitor : 15” CRT, or LCD monitor
Keyboard : Normal or Multimedia
Mouse : Compatible mouse

3.3 Software Requirements

Front End : HTML with CSS and PHP
Back End : My SQL Server
Operation System : Windows 7 or higher

3.4 User Characteristics

i) Every user
Should be comfortable with basic working of the computer Must carry a login ID and password
used for authentication in dairy milk management manager, supervisor and clerk are the
employees. These characters only are allowed to authorized to login.

ii) Constraints
The GUI restricted to English
Login user mail and password is used for identification of users. There is no facility for a guest
login.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 7

 Dairy Management System

Chapter 4
DESIGN & ANALYSIS
4.1 Project Description
System design is essential to develop a model of system before writing any software that is
used to control the system or to interact with it during the design process, we try to develop
system at different levels of abstraction. the project is developed using the below objects: -

Planned approach toward working: The working in the organization will be well planned and
organized. The data will be stored efficiency with optimal disk space consumption in data
stores which will help in retrieval of information as well as its storage under resource
constraints.

Accuracy: The level of accuracy in the proposed system will be higher. All operations would
conform to integrity constraints and correctness and it will be ensured that whatever
information is received at or sent from the center is accurate.

Reliability: The reliability of the proposed system will be high due to the above-mentioned
reasons. This comes from the fact that only the data which conforms accuracy clause would
be allowed to commit back to the disk. Other properties like transaction management and
rollback during system or power failure etc. get automatically taken care of by the SQL
systems. Properties of atomicity, consistency, isolation and data security are intrinsically
maintained.

No redundancy: In the proposed system it will be ensured that no repetition of information

occurs. This economizes on resource utilization in terms of storage space. Also even in case
of concurrent access no anomalies occur and consistency is maintained. In addition to all this,
principles of normalization have been endeavored to be followed.

Immediate retrieval of information: The main objective of the proposed system is to provide a
quick and efficient platform for retrieval of information. Among the queries allowed for use
by the user, the query results are made available immediately, without time lapse, irrespective
query.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 8

 Dairy Management System

4.2 Tables Used

LOGIN
(usermail, username, password)

FARMER
(f_no, f_id, f_name, f_locallity, f_acc, last_paid, f_phone)

EMPLOYEES
(e_id, e_name, e_mail, username, e_pass,e_roll, e_payroll_no)

DELIVERY
(d_id, r_f_no, r_kg, r_dt, r_received_by, r_deliverer)

PAYMENT
(id, p_to, p_date, p_ac, p_method, p_transaction_code, p_transacted_by)

SETTINGS_RATES
(id, from, to, rate)

4.3 Description of Tables

1. Login page
 Login into the account
 The user should be either Manager, Supervisor or Clerk to access the database.
.

2. Farmers
 Add farmers into the database and their information.
 View, Update, and remove farmers information.

3. Deliveries
 Add Deliveries into the database and their information.
 View, update, and remove delivery information.

4. Employees
 Add employee into the database and their information.
 This table is only accessed by the Manager neither by Supervisor nor Clerk.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 9

 Dairy Management System

5. Payments
 The record of the Farmer is opened here.
 The payment for the Farmer and deliverer is processed.

6. Setting and rating

 The cost milk per liter is fixed here.
 Fixed cost is going to updated and follow the same for payment.

4.4 System Development Phases

Systems Development Life Cycle (SDLC) adheres to important phases that are essential for
developers, such as planning, analysis, design, and implementation, and are explained in the
section below. There are several Systems Development Life Cycle Models in existence. The
oldest model, that was originally regarded as "the Systems Development Life Cycle" is the
waterfall model: a sequence of stages in which the output of each stage becomes the input for
the next. These stages generally follow the same basic steps but many different waterfall
methodologies give the steps different names and the number of steps seems to vary between
4and 7. There is no definitively correct Systems Development Life Cycle model, but the steps
can be characterized and divided in several steps.

i) Initiation Phase
The Initiation Phase begins when a business sponsor identifies a need or an opportunity. The
purpose of the Initiation Phase is to:
· Identify and validate an opportunity to improve business accomplishments of the
organization or a deficiency related to a business need.
· Identify significant assumptions and constraints on solutions to that need.
· Assure executive business and executive technical sponsorship.

ii) System Concept Development Phase

The System Concept Development Phase begins after a business need or opportunity is
validated by the Agency/Organization Program Leadership and the Agency/Organization
CIO. The purpose of the System Concept Development Phase is to:
· Determine the feasibility and appropriateness of the alternatives.
· Identify system interfaces.
INFORMATION SCIENCE & ENGINEERING, SJCIT Page 10
 Dairy Management System

· Identify basic functional and data requirements to satisfy the business need.
· Establish system boundaries; identify goals, objectives, critical success factors, and
performance measures.
· Assess project risks, Identify and initiate risk mitigation actions, and
· Develop high-level technical architecture, process models, data models, and a concept of
operations.

4.5 Feasibility Study

A feasibility study is a test of a system proposal according to its workability impact on
organization, ability to meet user needs and effective use of resources. The objective of a
feasibility study is not to solve a problem but to acquire a sense of its scope. Feasibility study
was done in phases documented below.

i) Behavioral feasibility
People are inherently resistant to change and computers have been known to facilitate
change. There is always some reluctance among the users against the introduction of new
system but they were told that this system would eliminate the unnecessary overhead of
database migration and conversion. The objective this feasibility phase is to take the
operational staff into confidence

ii) Schedule feasibility

Time evaluation is the most important consideration in the development of project. The time
schedule required for the development of the project is very important of other systems. A
reliable Human Resource Database Management System can be developed in a considerably
appropriate amount of time.

iii) Economic feasibility

Economic feasibility is the most frequently used method for evaluating the effectiveness of
the candidate system. More commonly known as cost\benefit analysis, the procedure is to
determine the benefits and savings that are expected from a candidate system and compare
them with the costs.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 11

 Dairy Management System

iv)Technical feasibility
Technical feasibility centers on the existing computer system. (Hardware/software) and
to what extent it can support the proposed addition also the organization already has
sufficient high-end machines to serve the processing requirements of the proposed system.
So, there is no need to purchase new software as the organization has necessary software i.e.
tomcat 5.0, j2ee1.4, Microsoft SQL Server or hardware to support the proposed system.

4.6 Analysis Phase

Existing System Details and Problems

Lack of immediate retrievals: In the conventional system, information is distributed across
several files. In the event of a complex or nested query, the search has to scan several files,
thus making procurement of requested query results very cumbersome.

Maintenance of Accuracy and Reliability issues: With redundancy comes consistency issues
as the update of information in a single record should be echoed in all records containing the
same information. Also, atomicity issues i.e., completion of a transaction in totality or
nothing at all; has to be maintained. This is difficult in a multi-file system.

Lack of prompt update: Updates associated with a record in a file is to be reflected in all
records wherein the particular record is present. Errors in commit operation to some
particular files cause the grave issue of data inconsistency.

Error prone manual calculation: Manual calculations are error prone and relatively
immensely time consuming, in spite of which they may result in generation of incorrect
information. Verification is another overhead, which can be saved through efficient design
and implementation.

4.7 Technology Used

i) PHP

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 12

 Dairy Management System

PHP is a widely used, general-purpose scripting language that was originally designed for
web development to produce dynamic web pages. For this purpose, PHP code is embedded
into the HTML source document and interpreted by a web server with a PHP processor
module, which generates the web page document.
PHP source code is compiled on-the-fly to an internal format that can be executed by the PHP
engine. PHP is one of the most popular server-side scripting languages running today. It is
used for creating dynamic webpages that interact with the user offering customized
information. PHP offers many advantages; it is fast, stable, secure, easy to use and open
source (free).
PHP code is inserted directly into the HTML that makes up a website. When a visitor comes
to the website, the code is executed.
Another key advantage of PHP is its connective abilities. PHP uses a modular system of
extensions to interface with a variety of libraries such as graphics, XML, encryption, etc. In
addition, programmers can extend PHP by writing their own extensions and compiling them
into the executable or they can create their own executable and load it using PHP's dynamic
loading mechanism.
A huge advantage that PHP offers is its community. Since PHP is an open source project, the
PHP community is willing to share. A PHP scripting block always starts with <?php and ends
with?>. A PHP scripting block can be placed anywhere in the document. On servers with
shorthand support enabled you can start a scripting block with <? and end with?>.
For maximum compatibility, we recommend that you use the standard form (<?php) rather
than the shorthand form.
ii) MY SQL
MySQL is an o pen s our ce relational database management system (RDBMS). Its name is
a combination of "My", the name of co-found Wideness’s daughter and "S0QL", the
abbreviation for Structured Query Language. The MySQL development project has made
its source code available under the terms of the GNU General Public License, as well as
under a variety of proprietary agreements. MySQL was owned and sponsored by a single for
profit firm, the Swedish company MySQL AB, now owned by Oracle Corporation.
MySQL was created by a Swedish company, MySQL AB, founded by David Ax mark,
Allan Larsson and Michae “Monty” Widenius. Original development of MySQL by
Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May
1995. It was initially created for personal usage from MySQL based on the low-level

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 13

 Dairy Management System

language ISAM, which the creators considered too slow and inflexible. They created a
new SQL interface, while keeping the same API as MySQL.
MySQL is written in C and C++. MySQL dump is a logical backup tool included with both
community and enterprise editions of MySQL. It supports backing up from all storage
engines. MySQL Enterprise Backup is a hot backup utility included as part of the MySQL
Enterprise subscription from Oracle.
MySQL Fabric is an integrated system for managing a collection of MySQL servers, and
a framework on top of which high availability and database shading is built. MySQL Fabric
is open-source, and supports procedure execution in the presence of failure, providing an
execution model usually called resilient execution.
phpMyAdmin is a free and open source tool written in PHP intended to handle the
administration of MySQL with the use of a web browser. It can perform various tasks such as
creating, modifying or deleting databases, tables, fields or rows; executing SQL statements;
or managing users and permissions. The software, which is available in 78 languages, is
maintained by The phpMyAdmin Project.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 14

 Dairy Management System

4.8 ER Diagram

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 15

 Dairy Management System

4.9 Schema Diagram

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 16

 Dairy Management System

Chapter 5
IMPLEMENTATION

This phase is initiated after the system has been tested and accepted by the user. In this phase,
the
system is installed to support the intended business functions. System performance is compared
to performance objectives established during the planning phase. Implementation includes user

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 17

 Dairy Management System

notification, user training, installation of hardware, installation of software onto production

computers, and integration of the system into daily work processes.
This phase continues until the system is operating in production in accordance with the defined
user requirements.

5.1 SQL commands

Creating tables

CREATE TABLE ‘login’ (

userid int(11) NOT NULL auto_increment,
useremail varchar(50) NOT NULL default '',
password varchar(50) NOT NULL default '',
userlevel int(11) NOT NULL default '0',
PRIMARY KEY (userid) )";

CREATE TABLE `employees` (

`id` int(11) NOT NULL,
`e_name` varchar(50) NOT NULL,
`e_mail` varchar(50) DEFAULT NULL,
`username` varchar(50) NOT NULL,
`e_pass` varchar(50) NOT NULL,
`e_role` varchar(50) DEFAULT NULL,
`e_payroll_no` varchar(50) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

CREATE TABLE `farmers` (

`f_no` varchar(50) NOT NULL,
`f_id` text NOT NULL,
`f_name` varchar(50) NOT NULL,
`f_locallity` varchar(50) DEFAULT NULL,
`f_ac` varchar(50) DEFAULT NULL,
`last_paid` date DEFAULT NULL,
`f_phone` varchar(20) DEFAULT NULL
);

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 18

 Dairy Management System

CREATE TABLE `settings_rates` (

`id` int(11) NOT NULL,
`from` date NOT NULL,
`to` date NOT NULL,
`rate` float NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

CREATE TABLE `delivery` (

`id` int(11) NOT NULL,
`r_f_no` varchar(50) NOT NULL,
`r_kg` float NOT NULL,
`r_dt` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
`r_received_by` varchar(50) NOT NULL,
`r_deliverer` varchar(50) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

CREATE TABLE `payment` (

`id` int(11) NOT NULL,
`p_to` varchar(50) NOT NULL,
`p_date` date NOT NULL,
`p_ac` bigint(20) NOT NULL,
`p_method` varchar(30) NOT NULL,
`p_transaction_code` int(11) NOT NULL, `p_transacted_by` varchar(50) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 19

 Dairy Management System

Inserting values
INSERT INTO `admin` (`admin_id`, `user`, `pass`,`d_id`) VALUES
(101, '[email protected]', 'harshith',2),(102, '[email protected]',
'hemanth',2);

INSERT INTO `department` (`did`, `dname`) VALUES (1, 'CSE'),(2, 'ISE'),(3, 'EC'),
(4, 'MECH'),(5, 'TCE'),(6, 'CIVIL'), (7, 'AUTO');

INSERT INTO `commonnotice` (`cnid`, `subject`, `Description`, `cndate`,`d_id`) VALUES

(2, 'Main_Notification', 'WELCOME TO SJCIT', '2019-11-26 15:04:33',2);

i) Inserting values

INSERT INTO ‘login’ (‘userid’,’usermail’,’password’,’userlevel’ ) VALUES (‘1’ ,

’[email protected]’ , ‘nayan123’ , ‘1’);

INSERT INTO `employees` (`id`, `e_name`, `e_mail`, `username`, `e_pass`, `e_role`,

`e_payroll_no`) VALUES
(3, 'nayan', '[email protected]', '', '827ccb0eea8a706c4c34a16891f84e7b', 'Manager', '3456'),

INSERT INTO `farmers` (`f_no`, `f_id`, `f_name`, `f_locallity`, `f_ac`, `last_paid`, `f_phone`,
`f_photo`) VALUES
('1', '23456779', 'alexandar jones', 'kk', '9890485987', '2017-04-30', '0721274242', NULL);

INSERT INTO `delivery` (`id`, `r_f_no`, `r_kg`, `r_dt`, `r_received_by`, `r_deliverer`)

VALUES
(2, '49', 66, '2017-04-07 23:00:00', '', 'kumar');

INSERT INTO ‘payment’ ( ‘id’ , ‘p_to’, ‘p_date’ , ‘p_ac’, ‘p_method’ , ‘p_transaction_code’ ,

‘p_transacted_by’) VALUES (21,’2017-11-31’, ‘’2017-12-31’, ‘ 0721274242’ , ‘cheuue’ ,
‘62468264823’);

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 20

 Dairy Management System

INSERT INTO `settings_rates` (`id`, `from`, `to`, `rate`) VALUES

(4, '2017-01-01', '2017-01-31', 20);

5.2 PHP Code

i) Connecting to Database

<?php
define('db_host', 'localhost');
define('db_user', 'root');
define('db_password', '');
define('db_database', 'dairy');
$conn= mysqli_connect(db_host, db_user, db_password, db_database);
mysqli_select_db($conn, db_database);
?>

ii) Login Page

<?php
include __DIR__ . "/../incl/config.incl.php";
include("auth.php");
$log = new logmein();
$log->encrypt = false; //set encryption
if(isset($_REQUEST['action']) && $_REQUEST['action'] == "login"){
$hashed_pass= md5($_REQUEST['password']);
if($log->login("logon", $_REQUEST['username'], $hashed_pass) == true){

//do something on successful login

header("location:".PAGE_URL);
}
}
//do something on FAILED login
header("location:".PAGE_URL );

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 21

 Dairy Management System

?>
Chapter 6

SOFTWARE TESTING

6.1 Levels of Testing

Testing is the process of executing then programs with the intention of finding out error.
During the process, the project is executed with set of tests and the output of the website is
evaluated to determine if the project is performing as expected. Testing includes after the
completion of the coding phase. The project was tested from the very beginning and also at
each step by entering different type of data.

Testing is vital to the success of the system. Testing makes a logical assumption that if all the
parts of the system are correct, the goal will be successfully achieved. A small system error
can conceivably explode into a much larger problem. Effective testing early in the process
translates directly into long-term cost savings from a reduced number of errors.

The aim of the testing process is to identify all the defects in the website. It is not practical to
test the website with respect to each value that the input request data may assume. Testing
provides a practical way of reducing defects in the website and increasing the user’s
confidence in a developed system. Testing consists of subjecting the website to a set of test
inputs and observing if the program behaves as expected.

A test case is the triplet [I, S, O] where I am data input to the system. S is the state of t h e
state of the system at which the data is input, O is the expected output of the system A test
suite is the set of all test cases with which a given software product is to be tested. The
following things are associated with testing:

i) Functional Testing
Here the system is a black box whose behavior is determined by studying its inputs and
related outputs. The key problem is to select the inputs that have a huge probability of being
members of a set in many cases.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 22

 Dairy Management System

ii) Structural Testing

A great deal can be learnt about the strength and the limitation of the application by examinee
the manner in which the system breaks. This type of testing has two limitations. It tests
failure behavior of the system circumstances may arise through an unexpected combination
of events where the node placed on the system exceeds the maximum anticipated load. The
structure of each module was checked at every step.

iii) Unit Testing

In unit testing the entire individual functions and modules were tested independently. By
following this strategy all the error in coding were identified and corrected. This method was
applied in combination with the white and black box testing techniques to find the errors in
each module. Unit test case design was started after source level code had been developed,
reviewed, and verified for correct syntax. Each test case was coupled with a set of expected
results.

6.2 Snapshots

Login Page: This is the login page through which admin going to access the database.

Figure 6.21 : Login page

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 23

 Dairy Management System

HOME PAGE: this is Home page where we get options like Farmer, Delivery, Payment,
Employee and Setting.

Figure 6.22 : Home Page

FARMER PAGE: In this page user is going to add or edit the Farmer information

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 24

 Dairy Management System

Figure 6.23 : Farmers Page

EMPLOYEE PAGE: This page is only for the overall Manager of the system.

Figure 6.24 : Employee Page

DELIVERIES PAGE: In this page Deliverer is going to delivers the milk into the destination
location by collecting the milk from Farmer.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 25

 Dairy Management System

Figure 6.25 : Deliveries Page

PAYMENT PAGE: In this page both Farmer and Deliverer is going get the payment through
the bank.

Figure 6.26:Payment Page

REPORT PAGE: In this page milk by each Farmer and Total Farmer delivery is reported.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 26

 Dairy Management System

Figure 6.27 : Reports

Page

SETTING RATE PAGE: By considering this page user is going to fix the cost of the milk per
liter.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 27

 Dairy Management System

Figure 6.28: Settings Page

Chapter 7
CONCLUSION

With the theoretical inclination of our syllabus it becomes very essential to take the Atmos
advantage of any opportunity of gaining practical experience that comes along. The building
blocks of this Mini Project” DAIRY MANAGEMENT SYSTEM” was one of these
opportunities. It gave us the requisite practical knowledge to
supplement the already taught theoretical concepts thus making us more competent as a
computer engineer. The project from a personal point of view also helped us in understanding
the following aspects of project development:
• The planning that goes into implementing a project.
• The importance of proper planning and an
organized methodology.
• The key element of team spirit and co-ordination in a successful project.
The project also provided us the opportunity of interacting with our teachers and to gain from
their best experience.
An application has been developed using
My Sql and PHP database programming connectivity via Xampp Server so as to meet the
requirements of an organization, thereby ensuring quality performance.
The data can be accessed, manipulated and
retrieved very easily. To conclude this software has proved to be a user-friendly interface.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 28

 Dairy Management System

Chapter 8

REFERENCES

1. Simple Snippets.(2016, October).Retrieved 2017, from

https://www.youtube.com/watch?v=E9MyRFjh8oo
2. phptpoint. (n.d). Retrieved from https://www.phpypoint.com
3. Refsnes Data. (1998). W3Schools. Retrieved 2017, from www.w3schools.com
4. Roberts’s, B. (n.d). THENEWBOSTON. Retrieved 2017, from
https://thenewboston.com/videos.php?cat=87
5. MohtashimMr.Tutorialspoint. Tutorialspoint.com. [Online] jine 2014.
https://www.tutorialspoint.com/tutorialslibrary.htm.
6. Ramakrishnan R. (2003). Database Management System. Mcgraw-Hill.

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 29

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 30

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 31

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 32

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 33

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 34

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 35

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 36

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 37

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 38

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 39

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 40

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 41

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 42

 Dairy Management System

INFORMATION SCIENCE & ENGINEERING, SJCIT Page 43