Eco dairy environment friendly dairy farming practices

A Major Project Report on
Web App Based Eco-Dairy Environment Friendly Dairy
Farming Practices
Submitted to
Jawaharlal Nehru Technological University, Hyderabad
in partial fulfillment of the requirements for the award of the degree
BACHELOR OF TECHNOLOGY
IN
COMPUTER SCIENCE & ENGINEERING
BY
Rabindra Raj Sah (16831A05J4)
Under the Esteemed Guidance of
Mrs. B. Ranjitha
Assistant Professor
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
GURU NANAK INSTITUTE OF TECHNOLOGY
(Affiliated to JNTUH-Hyderabad)
Ranga Reddy District -501506

i
(Affiliated to JNTUH-Hyderabad)
Ranga Reddy District -501506
CERTIFICATE
This is to certify that the project entitled ―Web App Based Eco-Dairy Environment Friendly
Dairy Farming Practices” is being presented with report by Rabindra Raj Sah
(16831A05J4) in partial fulfillment for the award of Degree of Bachelor of Technology in
Computer Science and Engineering, to Jawaharlal Nehru Technological University,
Hyderabad.
INTERNAL GUIDE PROJECT COORDINATOR
HEAD OF THE DEPARTMENT EXTERNAL EXAMINER
PRINCIPAL

ii
Ibrahimpatnam, R.R. Dist. – 501 506.
VISION OF GNIT
To be a world – class educational and research institution in the service of humanity by
promoting high quality Engineering and Management Education.
MISSION OF GNIT
M1: Imbibe soft skills and technical skills.
M2: Develop the faculty to reach the international standards.
M3: Maintain high academic standards and teaching quality that promotes the analytical
thinking and independent judgment.
M4: Promote research, innovation and Product development by collaboration with reputed
foreign universities.
M5: Offer collaborative industry programs in emerging areas and spirit of enterprise.

iii
VISION
To be a premier department of Computer Science and Engineering in the region.
MISSION
 Nurture young individuals into knowledgeable, skillful and ethical professionals in
their pursuit of Computer Science and Engineering.
 Nurture the faculty to expose them to world-class infrastructure.
 Sustain high performance by excellence in teaching, research and innovations.
 Extensive partnerships and collaborations with foreign universities for technology
upgradation.
 Develop Industry-Interaction for innovation and product development.

iv
Program Educational Objectives (PEO’s)
PEO-1: Graduates shall have the ability to apply knowledge and technical skills in emerging
areas of Computer Science and Engineering for higher studies, research, employability,
product development and handle realistic problems.
PEO-2: Graduates shall maintain ethical conduct, sense of responsibility to serve the society
and protect the environment.
PEO-3: Graduates shall possess academic excellence with innovative insight, soft skills,
managerial skills, leadership qualities, knowledge of contemporary issues for successful
professional career.
Program Outcomes (PO’s)
PO1- Engineering knowledge: Apply the knowledge of mathematics, science, engineering
fundamentals, and an engineering specialization to the solution of complex engineering
problems.
PO2- Problem analysis: Identify, formulate, review research literature, and analyze complex
engineering problems reaching substantiated conclusions using first principles of
mathematics, natural sciences, and engineering sciences.
PO3- Design/development of solutions: Design solutions for complex engineering problems
and design system components or processes that meet specified needs with appropriate
consideration for public health and safety, and the cultural, societal, and environmental
considerations.
PO4- Conduct investigations of complex problems: Use research-based knowledge and
research methods including design of experiments, analysis and interpretation of data, and
synthesis of the information to provide valid conclusions.

v
PO5- Modern tool usage: Create, select, and apply appropriate techniques, resources, and
modern engineering and IT tools including prediction and modeling to complex engineering
activities with an understanding of the limitations.
PO6- The engineer and society: Apply reasoning informed by the contextual knowledge to
assess societal, health, safety, legal and cultural issues and the consequent responsibilities
relevant to the professional engineering practice. PO7- Environment and sustainability:
Understand the impact of the professional engineering solutions in societal and
environmental contexts, and demonstrate the knowledge of, and need for sustainable
development.
PO8- Ethics: Apply ethical principles and commit to professional ethics and responsibilities
and norms of the engineering practice.
PO9- Individual and team work: Function effectively as an individual, and as a member or
leader in diverse teams, and in multidisciplinary settings.
PO10- Communication: Communicate effectively on complex engineering activities with the
engineering community and with society at large, such as being able to comprehend and write
effective reports and design documentation, make effective presentations, and give and
receive clear instructions.
PO11- Project management and finance: Demonstrate knowledge and understanding of the
engineering and management principles and apply these to one‘s own work, as a member and
leader in a team, to manage projects and in multidisciplinary environments.
PO12- Life-long learning: Recognize the need for, and have the preparation and ability to
engage in independent and life-long learning in the broadest context of technological change

vi
MAPPING WITH PO’S AND PEO’S
Sl. No. Content PO’s PEO’s
1 Introduction PO3 PEO2
2 Abstract PO6 PEO1
3 System Specifications PO5 PEO3
4 Architecture Design PO3 PEO1
5 HDFS CLI Commands PO PEO
6 Implementation PO4 PEO2
7 Results PO6 PEO3

vii
DECLARATION
I hereby declare that major project report entitled ―Web App Based Eco-Dairy
Environment Friendly Dairy Farming Practices” is the work done by Rabindra Raj Sah
bearing the roll no. 16831A05J4 towards the fulfillment of the requirement for the award of
the Degree of Bachelor of Technology in Computer Science and Engineering, to
Jawaharlal Nehru Technological University, Hyderabad, is the result of the work carried
out under the guidance of Mrs. B. Ranjitha Guru Nanak Institute of Technology,
Hyderabad.
I further declare that this project report has not been previously submitted before
either in part or full for the award of any degree or any diploma by any organization or any
universities.
Mr. Rabindra Raj Sah (16831A05J4)

viii
ACKNOWLEDGEMENT
"Task successful" makes everyone happy. But the happiness will be gold without
glitter if i didn't state the persons who have supported me to make it a success.
I would like to express my sincere thanks and gratitude to our Principal,
Dr. S. SREENATHA REDDY and Head of the Department Dr. S. DEEPAJOTHI,
Department of Computer Science and Engineering, Guru Nanak Institute of Technology for
having guided me in developing the requisite capabilities for taking up this major project.
I thank Project Coordinator Mr. FAROOQ MOHAMMED Assistant Professor
CSE, GNIT for providing seamless support and right suggestions that are given in the
development of the major project.
I specially thank my internal guide Mrs. B RANJITHA Assistant Professor for her
constant guidance in every stage of the major project. I would also like to thank all my
lecturers for helping me in every possible way whenever the need arose.
On a more personal note i thank our beloved parents and friends for their moral
support during the course of my major project. .

ix
ABSTRACT
The objective of project explains about Dairy Farming assistant web service is a web
project to help the farmers working with the motive of greater profitability by direct
communication between; farmer-to- supplier and farmer-to-farmer. This service boosts
business communication and brings transparency in the system. This innovative site
allows a good farmer, retailer and supplier communication. It provides an option of login
to farmers and communicates to respective dealers. Farmers are notified whenever dealers
publish an advertisement or offer on the website through SMS message. The farmers also
have an option to submit their grievances and complaints to respective dealers or
authorities using their farmer login on a separate complaints page and authorities will get
access to that page regularly using their login id and passwords.
Keywords: Admin, Retailer, Farmers, Notifications.

x
TABLE OF CONTENTS
Contents Page No
CERTIFICATE.................................................................................................................i
VISION AND MISSION ..................................................................................................ii
MAPPING WITH PO’S AND PEO’S.............................................................................vi
DECLARATION...............................................................................................................vii
ACKNOWLEDGEMENT................................................................................................viii
ABSTRACT.......................................................................................................................x
LIST OF FIGURE ............................................................................................................xiii
LIST OF TABLES............................................................................................................xv
LIST OF SYMBOL...........................................................................................................xvi
1. PROJECT INTRODUCTION..................................................................................1
1.1. GENERAL...........................................................................................................1
1.2. OBJECTIVES......................................................................................................3
1.3. EXISTING SYSTEM ..........................................................................................5
1.4. PROPOSED SYSTEM ........................................................................................6
1.5. SCOPE AND IMPORTANCE OF SYSTEM ....................................................7
1.5.1. SCOPE FOR DAIRY FARMING AND ITS NATIONAL IMPORTANCE7
1.5.2. MANAGEMENT OF DIARY.......................................................................7
1.6. STATEMENT OF RESEARCH HYPOTHESIS ................................................9
2. LITERATURE SURVEY .........................................................................................10
2.1. OVERVIEW ...........................................................................................................10
2.2. INTRODUCTION ..................................................................................................10
2.3. THE LITERATURE REVIEW PROCESS ............................................................11
2.4. LITERATURE REVIEW AIMS AND METHODS ..............................................11
2.4.1. RESEARCH GAP..........................................................................................12
3. SYSTEM ANALYSIS................................................................................................19
3.1. GENRAL………….. ..............................................................................................19

xi
3.2. MODULES .............................................................................................................19
3.2.1. USER INTERFACE DESIGN.......................................................................19
3.2.2. ADMIN MODULE........................................................................................20
3.2.3. FARMER MODULE.....................................................................................21
3.2.4. SELLER MODULE.......................................................................................22
3.2.5. ADVISOR MODULE....................................................................................23
3.3. SYSTEM ARCHITECTURE .................................................................................24
4. SYSTEM REQIRMENTS.........................................................................................25
4.1. GENERAL..............................................................................................................25
4.2. HARDWARE REQUIREMENTS..........................................................................25
4.3. SOFTWARE REQUIREMENTS ...........................................................................26
4.4. FUNCTIONAL REQUIREMENTS .......................................................................26
4.5. NON-FUNCTIONAL REQUIREMENTS .............................................................26
4.5.1. EFFICIENCY ................................................................................................26
4.5.2. RELIABILITY...............................................................................................26
5. SYSTEM DESIGN....................................................................................................27
5.1. GENERAL..............................................................................................................27
5.2. UNIFIED MODELING LANGUAGE DIAGRAMS.............................................27
5.2.1. USE CASE.....................................................................................................27
5.2.2. CLASS DIAGRAM.......................................................................................29
5.2.3. SEQUENCE DIAGRAM...............................................................................30
5.2.4. ACIVITY DIAGRAM...................................................................................32
5.2.5. DEPLOYMENT DIAGRAM ........................................................................34
5.2.6. COMPONENT DIAGRAM...........................................................................35
5.2.7. COLLABORATION DIAGRAM .................................................................36
5.3. DATA-FLOW DIAGRAM..................................................................................38
5.4. ENTITY–RELATIONSHIP MODEL .................................................................39
5.5. DATABASE DESIGN TABLES ........................................................................40
5.5.1. ADMIN DATABASE TABLES....................................................................40
5.5.2. LOGIN DATABASE TABLES.....................................................................40
5.5.3. QUESTION DATABASE TABLES .............................................................41
5.5.4. RECORD DATABASE TABLES.................................................................41
6. IMPLEMENTATION ...............................................................................................42
6.1. GENERAL..............................................................................................................42

xii
6.2. TECHNOLOGIES USED.......................................................................................42
6.2.1. ANGULARJS ................................................................................................42
6.2.2. NODEJS.........................................................................................................43
6.2.3. EXPRESS.JS..................................................................................................43
6.2.4. MONGO DB..................................................................................................45
6.3. IMPLEMENTAION ...............................................................................................46
7. TESTING....................................................................................................................56
7.1. GENERAL..............................................................................................................56
7.2. DEVELOPING METHODOLOGIES....................................................................56
7.3. TYPES OF TEST....................................................................................................56
7.3.1. UNIT TESTING ............................................................................................56
7.3.2. INTEGRATION TESTING...........................................................................57
7.3.3. FUNCTIONAL TEST ...................................................................................57
7.3.4. PERFORMANCE TEST ...............................................................................57
7.3.5. ACCEPTANCE TESTING............................................................................57
7.4. TEST CASES..........................................................................................................58
7.4.1. REGISTRATION TEST CASE.....................................................................58
7.4.2. AUTHENTICATION TEST CASE ..............................................................59
7.4.3. ADD PRODUCTS TEST CASE ...................................................................59
7.4.4. ASK QUESTION AND GIVE SUGGESTION TEST CASE ......................60
8. SCREENSHOTS………………………………………………………………........61
8.1. GENERAL...........................................................................................................61
8.2. VARIOUS SNAPSHOTS....................................................................................61
8.2.1. INDEX PAGE................................................................................................61
8.2.2. REGISTRATION PAGE...............................................................................62
8.2.3. LOGIN PAGE................................................................................................62
8.2.4. ADMIN PAGE...............................................................................................63
8.2.5. FARMER PAGE............................................................................................63
8.2.6. SELLER PAGE .............................................................................................64
8.2.7. ADVISOR PAGE ..........................................................................................64
9. CONCLUSION AND FUTURE ENHANCEMENT..............................................65
REFERENCE....................................................................................................................66

xiii
LIST OF FIGURES
Contents Page No
Figure 3.1: User interface Diagram ....................................................................................19
Figure 3.2: Admin Module Diagram ..................................................................................20
Figure 3.3: Farmer Module Diagram..................................................................................21
Figure 3.4: Supplier Module Diagram................................................................................22
Figure 3.5: Advisor Module Diagram.................................................................................23
Figure 3.5: System architecture ..........................................................................................24
Figure 5.1: User case diagram for Administrator ...............................................................28
Figure 5.2: User case diagram for Farmer ..........................................................................28
Figure 5.3: User case diagram for Seller ............................................................................28
Figure 5.4: Class Diagram ..................................................................................................29
Figure 5.5: Sequence diagram for Administrator ...............................................................30
Figure 5.6: Sequence diagram for Farmer ..........................................................................31
Figure 5.7: Sequence diagram for Seller.............................................................................31
Figure 5.8: Activity Diagram for Administrator.................................................................32
Figure 5.9:- Activity Diagram for Farmer (staff)................................................................33
Figure 5.10:- Activity Diagram for Seller...........................................................................33
Figure 5.11: Deployment Diagram .....................................................................................34
Figure 5.12: Component Diagram ......................................................................................35
Figure 5.13: Collaboration diagram for Admin ..................................................................36
Figure 5.14: Collaboration diagram for Farmer (staff).......................................................37
Figure 5.15: Collaboration diagram for Seller....................................................................37

xiv
Figure 5.16: Data flow Diagram .........................................................................................38
Figure 5.17: ER-Diagram....................................................................................................39
Figure 5.18: Admin.............................................................................................................40
Figure 5.19: login................................................................................................................40
Figure 5.20: Question..........................................................................................................41
Figure 5.21: Record ............................................................................................................41
Figure 8.1: Index page ........................................................................................................61
Figure 8.2: Registration page..............................................................................................62
Figure 8.3: Login page........................................................................................................62
Figure 8.4: Admin page ......................................................................................................63
Figure 8.5: Farmer page......................................................................................................63
Figure 8.6: Seller page ........................................................................................................64
Figure 8.6: Advisor page.....................................................................................................64

xv
LIST OF TABLES
Contents Page No
Table 7.1: User registration.................................................................................................58
Table 7.2: User login...........................................................................................................59
Table 7.3: Add Products .....................................................................................................59
Table 7.4: Ask Question and Give Suggestion...................................................................60

xvi
LIST OF SYSMBOLS
S.NO
NOTATION
NAME NOTATION DESCRIPTI
ON
1. Class Represents a
collection of
similar entities
grouped
together.
2. Association
NAME Associations
represents
static
relationships
between
classes. Roles
represents the
way the two
classes see
each other.
3. Actor
It aggregates
several classes
into a single
classes.
4.
Aggregation
Interaction
between the
system and
external
environment
Class A
Class B Class B
Class A
Class Name
-attribute
-attribute
+operation
+operation
+operation
+ public
-private
# protected
Class BClass A
Class A Class B

xvii
5. State
State of the
processs.
6.
Relation
(uses)
uses
Used for
additional
process
communication.
7. Communication
Communication
between various
use cases.
8.
Message Message
Represents the
message
exchanged.
9. Initial State Initial state of
the object
10. Final state
F inal state of
the object
11. Control flow
Represents
various control
flow between
the states.
12. Decision box Represents
decision
making process
from a
constraint
13.
Usecase
Interact ion
between the
system and
external
environment.
Class A
Class A

xviii
14. Component
Represents physical
modules which is a
collection of
components.
15. Node
Represents physical
modules which are a
collection of
components.
16. Data
Process/State
A circle in DFD
represents a state or
process which has
been triggered due to
some event or acion.
17. External entity
Represents external
entities such as
keyboard,sensors,etc.
18.
Transition
Represents
communication that
occurs between
processes.
19. Object Lifeline Represents the
vertical dimensions
that the object
communications.

1
CHAPTER 1
INTRODUCTION
1.1. GENERAL
Dairy producers aim to ensure that the safety and quality of their raw milk will satisfy
the highest expectations of the food industry and consumers. In addition, on-farm practices
should ensure that milk is produced by healthy cattle under sustainable economic, social and
environmental conditions.
To that aim, this document provides a set of Practices for Environmental friendly Dairy
Farming for the mainstream market in all regions of the world. It is meant to be revised
regularly on the basis of practical experience. Furthermore, it is meant to be completed with
specific guidelines and practical tools based on local innovations and adapted to local
prevailing conditions (according to the region and its climates, ecological variables, farming
systems, cultures etc) as well as respecting national laws and regulations. As a basis for its
work on sustainability, the Sustainable Agriculture Initiative (SAI) Platform Working Group
on Dairy has adopted the Guide to Good
Dairy Farming Practice - a joint publication of the International Dairy Federation (IDF) and
the Food and Agriculture Organization of the United Nations (FAO), published in January
2004. This document supplements the IDF/FAO Guide with particular elements of economic,
environmental and social sustainability. It is important to note that the focus of these
Principles and Practices is on the desired outcomes, rather than on specific, prescriptive
actions/processes.
The Basic framework looks as follows:
1. Item. An item refers to an object of management.
2. Principles identify the objective(s) of what should be accomplished with regard to an
item.
3. Recommended Practices provide a set of identified non-exclusive tools and measures that
can be implemented to achieve the objective(s) of a principle.
It is important to note that good management of a farming system constitutes the grassroots
of the system‘s economic, environmental and social sustainability. Therefore, it first pays

2
attention to planning and managing well the overall farm system itself. This document‘s
scope of management action is limited to what farmers or groups of farmers themselves can
achieve.
Farmers shall have taken into consideration applying the principles & practices to the whole
farm system within a philosophy of continuous improvement, starting with the livestock in
scope. The following headings and bullets summaries the sections and objectives when
applied to a whole farm system. The individual sections in the document contain greater
detail of practices.
All dairy farmers, suppliers to dairy farmers, milk carriers and haulers, dairy product and
food manufacturers, distributors and retailers should be part of an integrated food safety and
quality assurance management system. Good farming practices underpin the marketing of
safe, quality-assured milk-based products.
The role of dairy farmers is to ensure that good agricultural, hygienic and animal husbandry
practices are employed at the farm level. The focus should be on preventing a problem
(including animal diseases) rather than solving it after it has occurred.
Good dairy farming practices should contribute to ensuring milk and milk products are safe
and suitable for their intended use.
The scheme for diary, farming should include information on land, livestock markets,
availability of water, feeds, fodders, veterinary aid, breeding facilities, marketing aspects,
training facilities, experience of the farmer and the type of assistance available from State
Government, dairy society/union/federation.
Innovation in milking focused on mechanizing the milking parlor (known in Australia and
New Zealand as a milking shed) to maximize the number of cows per operator which
streamlined the milking process to permit cows to be milked as if on an assembly line, and to
reduce physical stresses on the farmer by putting the cows on a platform slightly above the
person milking the cows to eliminate having to constantly bend over. Many older and smaller
farms still have tie-stall or stanchion barns, but worldwide a majority of commercial farms
have parlors.

3
1.2 OBJECTIVES
Many dairy companies/cooperatives and countries are introducing on-farm quality
assurance programmers aimed at assuring their consumers about the safety of their dairy
products. This guide attempts to provide a generic framework for individual on-farm quality
assurance programmers, focusing on both consumer safety and the image of the dairy sector.
The objective of the document is to provide a farmer-orientated guide to practices that are
achievable all over the world covering those areas that are essential to manage.
The approach taken in this guide is to:
 highlight relevant areas on dairy farms that need to be managed;
 identify the objectives in dealing with each of these areas;
 identify GAP; and
 Suggest control measures that can be implemented to achieve the objectives.
The focus is on the desired outcomes, rather than on specific, prescriptive actions/processes.
The guide does not have any legal status and does not supersede national requirements.
Guiding objectives for good dairy farming practice
The guiding objective for good dairy farming practice is that milk should be produced on-
farm from healthy animals under generally accepted conditions. To achieve this, dairy
farmers need to apply GAP in the following areas:
 animal health;
 milking hygiene;
 animal feeding and water;
 animal welfare; and
 Environment.
For some of these areas, there are control points that must be managed to achieve defined
outcomes. The guide contains guidelines specific to the five areas listed above but is not
meant as a substitute for national legislation.

4
GAP also means that dairy farmers should ensure that appropriate records are kept, especially
those that enable adequate traceability of:
- the use of agricultural and veteran chemicals;
- the purchase and use of animal feed and
- The unique identification of individual animals.
Records should also be kept of:
-Milk storage and temperature (when available)
-Veterinary or medication treatments of individual animals.
The owner of a dairy farm should also ensure that people undertaking and supervising the
milking operations and management of the dairy farm are skilled in:
 animal husbandry;
 the hygiene milking of animals;
 the administration of veterinary drugs;
 the activities undertaken on the dairy farm in relation to food safety and food
hygiene; and
 Health and safety practices relating to dairy farm operators.
Appropriate measures are also needed to maintain these skills through ongoing training.
The Guidelines are presented in two forms:
 Good agricultural practice (GAP) and suggested measures are set out in tabular form
for each key area: animal health, milking hygiene, animal feeding and water, animal
welfare and environment.
 Individual Fact Sheets that provide more detail for each area, corresponding to the
GAP.
In developing individual, company or country-specific guidelines for good dairy farming
practices (or on-farm quality assurance programs), reference should be made to:

5
1.3 EXISTING SYSTEM
The existing system before the implementation of proposed system consists of only
limited features in dairy farming practices through websites. The user interface of existing
system was not user Friendly and it was complex to use. The existing dairy farming websites
did not consists of all the features implemented in the proposed system like quality
relationship with retailer and farmer, everyday acknowledgements of dairy farming fertilizers
and pesticides along with growth of farming practices with natural environment. In the
existing system buying and selling a product is done manually. Price of the product is fixed
by the seller. All the details of the product to be sold or purchased is maintained manually.
Sellers or buyers not able to get the complete information about the product. When we
Analysis the Manage about this firm then we face that they working with manual. And we all
know that the manual system has many disadvantages. Some are mentioned below
Drawbacks
 It is difficult to handle with various farming practices.
 It requires more critical work
 Complex to use.
 Limited features.
 Not suitable for whole dairy farming activities.
 Lacking of contact details.
 Not user friendly environment.
 More men power needed

6
1.4 PROPOSED SYSTEM
The proposed management system utilizes the application which gives support to the
village farmers who want to use this facility and who want to learn how it is possible and how
they can use e-farming to sell their products. Farming stock Trade Application is a project
developed, which will help farmers from to sell their products to different cities through
online system. This application will act as unique and secure way to perform agro-marketing.
The system allows farmers to sell their stock directly as a direct supplier throughout the
country without any middlemen so that, farmer earn optimum rates for his stock and also the
customer gets it at lowered costs. The proposed system is a solution to it all.
Advantages:
 It helps in maintaining livestock and agro farming activities.
 System required less time for completion of any work It helps in achieving higher.
 Growth rate with customer and farmer through retailer.
 Easy to identify customer relationship with the dealers.
 Good communication between farmers to supplier.
 Authorities can be given to farmer, so that he can make complaints and reports.
 Work smoothly and very fast.
 Saving time and manpower.
 Suitability for computerized data entry.
 User friendly and anyone having computer knowledge can handle it easily.

7
1.5 SCOPE AND IMPORTANCE OF DAIRY FARMING
Dairying is an important source of subsidiary income to small/marginal farmers and
agricultural labourers. The manure from animals provides a good source of organic matter for
improving soil fertility and crop yields. The goober gas from the dung is used as fuel for
domestic purposes as also for running engines for drawing water from well. The surplus
fodder and agricultural by-products are gainfully utilized for feeding the animals. The
small/marginal farmers and land less agricultural labourers play a very important role in milk
production of the country. Dairy farming is now taken up as a main occupation around big
urban centers where the demand for milk is high.
1.5.1 Scope for Dairy Farming and its National Importance:
The total milk production in the country for the year 2001-02 was estimated at 84.6
million metric tons. At this production, the per capita availability was to be 226 grams per
day against the minimum requirement of 250 grams per day as recommended by ICMR.
Thus, there is a tremendous scope/potential for increasing the milk production. The
population of breeding cows and buffaloes in milk over 3 years of age was 62.6 million and
42.4 million, respectively (1992 census).
1.5.2 Management of Diary:
The scheme for diary, farming should include information on land, livestock markets,
availability of water, feeds, fodders, veterinary aid, breeding facilities, marketing aspects,
training facilities, experience of the farmer and the type of assistance available from State
Government, dairy society/union/federation.
a) Technical Feasibility
 Nearness of the selected area to veterinary, breeding and milk collection centre and
the financing bank‘s branch.
 Availability of good quality animals in nearby livestock market.
 Availability of training facilities.
 Availability of good grazing ground/lands.
 Green/dry fodder, concentrate feed, medicines etc.
 Availability of veterinary aid/breeding centers and milk marketing facilities near the
scheme area.

8
b) Economic Viability
 Cost of for feeds and fodders, veterinary aid, breeding of animals, insurance, labour
and other overheads.
 Output costs i.e. sale price of milk, manure, gunny hags, male/female calves, other
miscellaneous items etc.
c) Farmers:
 Modern and well established scientific principles, practices and skills should be used
to obtain maximum economic benefits from dairy farming.
Some of the major norms and recommended practices are as follows:
1. Housing:
 Construct shed on dry, properly raised ground.
2. Feeding of Milch Animals:
 Feeding the animals with best feeds and fodders.
3. Milking of Animals:
 Milking the animals two to three times a day.
4. Protection against Diseases:
 Be on the alert for signs of illness such as reduced feed intake, fever, abnormal
discharge or unusual behavior.
5. Breeding Care:
 Animal should be closely observed and keep specific record of its coming in heat,
duration of heat, insemination, conception and calving.
6. Care during Pregnancy:
 Give special attention to pregnant cows two months before calving by providing
adequate space, feed, water etc.
7. Marketing of Milk:
 Production of milk produces for better storage to give more returns

9
1.6 STATEMENT OF RESEARCH HYPOTHESIS:
1. There is significant difference between farmers with and without training in dairy
farming in their mean scores of success factors adopted in dairy farming.
2. There is significant difference between member dairy farmers and non-member dairy
farmers in their level of awareness regarding programmers in diary sector.
3. There is a positive correlation between the perception on cooperation and
commitment to organization among the members of dairy cooperative society.
4. There is significant relationship between membership positions in dairy cooperative
society and level of participation of members in programmers of dairy cooperative
and local community.
5. There are significant correlations between the perception of cooperation,
commitment, awareness, participation and leadership effectiveness of the Presidents
of dairy cooperatives.

10
CHAPTER 2
LITERATURE SURVEY
2.1. OVERVIEW:
Environmental friendly dairy farming is most important change in day-to-day life for
producing nature‘s dairy products to every individual in our society. The main aim of
literature review is to study and acknowledge the input of other researchers and authors and
their contributions to the body of knowledge in order to shed more light on the topic of
discussion. It will be organized to review literature, from global, regional, national and local
perspectives. This consists of an overview of the Global perspective of the Dairy Industry in
general with special reference to the dairy industry in USA, India, South Africa and Kenya
etc. Dairy Industry in India, role of Cooperative Milk Societies, Women and Dairy farming,
Socio Economic Impact of Dairy farming, Milk Production, Milk Marketing, Milk Products,
Dairy Farmers, Milk Prices and Dairy Farming in Tamilnadu.
2.2 INTRODUCTION:
Livestock play a vital role in rural economy of our country. Dairy is a high-value
agricultural commodity of which the production process is relatively labour-intensive. Poor
rural households are said to have easier access to productive assets for dairy production than
for crop production. As dairy production is a fairly traditional agricultural activity in many
Indian rural areas, improved insights in production structures and constraints seem to be
crucial to understand the potential implications of imminent changes in domestic and
international dairy markets. The Dairy Industry has a bright future in India and is a viable
alternative for farmers because of low cost of production. There is a huge potential for
capturing the large unorganized market base in dairy. Access to significant technological
innovations, development and creation of infrastructural facilities were also given
considerable boost to dairy development. Animal health and quantity breading practices were
also contributed for further development of dairy activities. This helped in improving quality
of life of the rural public apart from employment generation amongst the rural people.
The face of today‘s global dairy industry is changing. The technological advances in large-
scale production have dominated production systems of more developed nations, while small-
scale dairies have gained prominence in the developing world. In order to incorporate these

11
small-scale production systems into the larger global dairy industry, a working knowledge of
the benefits and challenges of small-scale dairy farms is necessary. To optimize the
development of small-scale dairies, the effects of management practices, farmer training,
culture, environmental issues as well as milk safety and the potential risk of milk borne
diseases are aspects that must be examined. A detailed survey on research and non-research
studies on various aspects relating to dairy industry both at national and international level
have been made and from the survey relevant and selected studies are presented below as
literature review.
2.3 THE LITERATURE REVIEW PROCESS:
I used the literature review to generate pertinent ideas that could be further refined. I
also engaged in critical reflection on these ideas in order to evaluate their origins, meaning
and status in the research. During the cause of the study I continuously returned to the
literature review to update it, refine it, and add new information and observations.
In order to make sense of the literature I attempted to examine literature that was current,
similar and relevant.
I used the following criteria as filter to determine whether include or exclude text from the
literature review process.
1. Is the material relevant in this study?
2. Is the proposed text by an author who was suggested by other author‘s reputable
authority?
3. Will the material augment the intellectual matrix of this study?
4. Will the proposed text shed light on the issues raised in this research?
5. Does the date of the material suggest that it is an up to date contribution in this field?
2.4 LITERATURE REVIEW AIMS AND METHODS:
There are two main aims to this literature review. The first aim is to establish the
characteristics and importance of formative, coursework assessment. The second aim is to
identify different apps based on dairy farming techniques, tools and approaches for this type

12
of assessment, to discuss what is known about their effectiveness and to uncover factors
influencing uptake.
For the first aim key articles and books that have shaped current theory on formative
assessment of student work have been identified and analyzed. For the second aim a
comprehensive search of apps based on dairy farming literature from 1987 to the present was
conducted. The farming practices are developed based on many different segments according
to their life style and nature of environmental behavior of certain countries population. For
example, priority in developing African dairy industries is to build marketing systems which
provide incentives for local farmers and supply consumers with the produce they demand.
Global milk production is expected to increase at a slower rate in the next decade as feed
based dairy operations struggle with high feed costs, while pasture based systems face land
competition and water shortages. Developing countries are expected to generate 74% of
global milk production gains over the next decade, with India and China alone accounting for
38% of the increase. Global consumption of dairy products in developing countries is
projected to grow faster than production, with higher exports from the United States, the
European Union, New Zealand, Australia and Argentina.
India has the largest cattle and buffalo population in the world. More than 67 percent of dairy
animals are owned by marginal and small farmers, which constitute the core milk-production
sector in the country. Many of these farmers own dairy animals primarily to supply milk for
their own consumption. Slightly more than 30 percent of the milk produced in the country is
retained in producer households. India has the most organized milk marketing system owned
by small scale milk producers in developing countries. Over the span of three decades, India
has transformed from a country of acute milk shortage to the world‗s leading milk producer,
with production exceeding 100 million tonnes in 2004
2.4.1 RESEARCH GAP
The review of literature covers the period from 1981 to 2014 ranging from dairy industry at
global level, National level to State Level. At Global level, the leading countries producing
milk like United States, New York, South Africa, Kenya, Ethiopia, Tanzania, Washington ,
Michigan, Japan, Western Turkey, Zimbabwe, Thailand, New England, Reunion Island,
Zambia, Tanzania and Brazil. Reviews on Indian dairy includes milk production, production

13
of dairy products, Operation Flood Program me, livestock population, buffalo milk, strategies
for the improvement of milk production, the role of cooperatives in the production and
marketing of milk, involvement of women in the dairy farming activities and the various
schemes available for women, role of dairy sector in the socio economic development of the
dairy farmers and generation of employment. The various places of India includes North
India, Andhra Pradesh, Punjab, Gujarat, Kerala, Orissa, Karnataka, West Bengal, Tamil
Nadu, Haryana, Western Maharashtra, Bangladesh, Uttaranchal, Uttarakhand, Hyderabad and
Rajasthan. Various studies revealed the fact that the United Nation‘s Food and Agriculture
Organization (FAO), which has declared India as the world‘s largest producer of milk.
Most of the total milk production in the country comes from indigenous cows, crossbred
cows and buffaloes. Goats and other animals contribute only a minor share to the total milk
production. Further it is found that the dairy co-operatives play a vital role in alleviating rural
poverty by augmenting rural milk production and marketing. Involvement of intermediaries,
lack of bargaining power by the producers and lack of infrastructure facilities for collection,
storage, transportation, and processing are the major constraints which affect the prices
received by producers in milk marketing. Milk quality, product development, infrastructure
support development, and global marketing are found to be future challenges of India's milk
marketing. A majority of consumers, irrespective of all income groups, considered thickness,
taste curd formation to be most important factors in judging the quality of milk.
The market for liquid milk, as well as value-added dairy products, is still largely dominated
by the unorganized sector. India has an insignificant share of the global dairy trade, less than
one per cent, despite being a leading producer of milk. The studies related to dairy farming in
Tamilnadu and Kanyakumari District are scanty and this study has taken an attempt to
evaluate the improvement of dairy farmers and the role of milk cooperatives from the point of
view of the farmers and milk cooperatives by considering both primary and secondary data.
When refrigeration first the equipment was initially used to cool cans of milk, which were
filled by hand milking. These cans were placed into a cooled water bath to remove heat and
keep them cool until they were able to be transported to collect facilities. As more automated
methods were developed for eating milk, hand milking was replaced and, as a result, the milk
can was replaced by bulk milk cooler. 'Ice banks' were the first type of bulk milk cooler. This
was a double wall vessel with evaporator coils and water located between the walls at the
bottom and sides of the tank.

14
Title : Dairy Management Practices
Author : Pander. B.L., Hill. W.G., Bennett, Charles D. Fullhage, and Donald L.
Year : 1993-1999
Description:
Pander. B.L. and Hill. W.G. (1993) argued that the genetic prediction of heifer‘s 305-day
lactation yield from complete test day records or from records in progress was investigated.
The accuracies of genetic indices predict breeding value for total yield from all 10 test day
records of milk, fat and protein yields were 0.71, 0.66 and 0.67, respectively. These
accuracies were slightly higher than if indices were computed to predict phenotypes and from
these breeding values of 305-day records. The accuracy for a repeatability model (giving
equal weight to each record) was not far below that of an optimal index. Inclusion of records
in progress in genetic evaluation was investigated using a repeatability model and a
phenotypic index to predict the phenotype for complete lactation from test day records. For
genetic prediction of heifer lactation yield from test day records, a repeatability model giving
equal weight to each record could be used without increasing computational facilities and
could be implemented directly in current genetic evaluation in the UK. Records in progress
could easily be incorporated.
Bennett, Charles D. Fullhage, and Donald L. (1999) conducted a comparative analysis of two
nutrient management systems for Missouri dairies. Annual ownership and operating costs
were computed for herd sizes of 100-1,000 cows. A break-even analysis was also provided
for irrigation systems used with the lagoon system. Lagoon systems consistently handled
dairy nutrient at a lower cost than liquid tank systems for all herd sizes. Even though
nutrients from liquid tank systems are more concentrated and valuable than nutrients from
lagoon systems, the liquid system's net cost was 1.5 to 2.4 times greater than the lagoon
system's net cost, depending on herd size. This can be an important consideration for
operations with limited acreage. Dairies with more than 300 cows benefited from purchasing
a travelling gun irrigator rather than relying on a custom operator to remove nutrients from
lagoon systems.

15
Title : Production and Marketing of Milk Products
Author : Chauhan. A.K., Raj Vir Singh, Raina. B.B. And Fengxia Dong
Year : 2006
Description:
Chauhan. A.K., Raj Vir Singh and Raina. B.B. (2006)63 examined the economics of
manufacturing of different dairy products, viz. ghee, full-cream milk, standardized milk,
toned milk, double-toned milk, skimmed milk and ice-cream (processing only) have been
reported. The study has been conducted in an ISO-9002 dairy plant situated in the north-
eastern part of Haryana. It has been observed that all the products, except the double-toned
milk are being produced above the recommended breakeven level. The double-toned milk has
revealed a loss. Therefore, the study has suggested that the quantity of double toned milk
production should be raised at least equal to the recommended break-even level to avoid
losses, if there is a market demand for this product or the resources of this product could be
shifted to some other profitable products.
Fengxia Dong (2006)64 presented a 10-year outlook for major Asian dairy markets (China,
India, Indonesia, Japan, South Korea, Malaysia, the Philippines, Thailand, and Vietnam)
based on a world dairy model. Then, using Heien and Wessellsï‘s technique, dairy product
consumption growth is decomposed into contributions generated by income growth,
population growth, price change, and urbanization and these contributions are quantified.
Using the world dairy model, the paper also analyzes the impact of alternative assumptions of
higher income levels and technology development in Asia on Asian dairy consumptions and
world dairy prices. The consumption decomposition suggests that the growth would be
mostly driven by income and population growth and, as a result, would raise world dairy
prices. The simulation results show that technology improvement in Asian countries would
dampen world dairy prices and meanwhile boost domestic dairy consumption.

16
Title : Dairy Industry in India
Author : Waghmare P.R, Hedgire D.N, Radha Krishnan, Nigam.S, Shantanu Kumar
Year : 2007-2008
Description:
Waghmare P.R. and Hedgire D.N. (2007) opined that Milk productions in India during 1950-
51 were 17 million tonnes which has reached 78 million tonnes in 1997-98. Presently India
ranks first in the world in milk production. The Operation Flood Programme was
instrumental in dairy development activities. These programmes are useful in upgrading the
standard of living of farmers.
Radha Krishnan, Nigam.S, and Shantanu Kumar (2008) in their opinion growing human
population, rising per capita income and increasing urbanization are fuelling rapid growth in
the demand for food and animal origin in developing countries. India possesses the largest
livestock population in the world. Contrary to the large population of livestock in India
productivity of Indian livestock is low compared to many developing countries. According to
Indian Mirror (2011), despite its huge production volume, India faces a milk supply gap due
to increasing demand from a growing middle class population. Estimation suggests that
Indian dairy production is growing at a rate of about four percent per year, yet consumer
demand is growing at approximately double that rate. In response to increasingly strong
demand for milk products, the Indian dairy industry is growing its milk production in several
ways. In addition, those farmers working directly with buyers from the organized sector
generally have access to modern extension services, which provide support for the dairy
farmers to improve management, feeding, fertility and veterinary care. Out of all bovine
population in India, 40 percent are indigenous cows, 46 percent are buffaloes and 14 percent
are imported European or North American cattle crossbreeds. Out of the nation‘s total milk
production, about 55 percent comes from buffaloes and the remainder from dairy cows .

17
Title : Global perspective of Indian Dairy Industry
Author : Morgan, Russell M., Luther H. Keller, Hansen and Brandon.
Year : 1987-1993
Description:
Emphasized the need for reliable and complete cost and benefit data in their evaluation of
nutrient management systems for Tennessee dairy farms. Considering alternative herd sizes,
they computed direct construction and instalment costs, annualized costs, and stability of
cost/return relationships of different nutrient systems. They also conducted a sensitivity
analysis of nutrient loss rates of different nutrient management systems during storage and
varying nutrient values after application to land. They noted the substantial cost of all nutrient
management systems and the fact it could be expected to increase significantly should more
stringent environmental regulations be applied to the dairy farm sector.
Hansen and Brandon. D. (1993) viewed that the primary objective of his study was to
develop a series of worksheets to analyse the economic, financial, risk, and environmental
impacts of alternative nutrient management methods for a representative western Washington
dairy farmer. He examined capital investment required, annual costs, financing, cash flow,
nutrient values of the waste, and financial and environmental risks. The dairy selected by
Hansen needed a larger nutrient handling system to accommodate expansion for 69 additional
mature cows and 42 additional heifers. He considered two alternatives: (1) add a second
lagoon, use a solid separator, and purchase a big-gun pumping system for distribution of
liquid nutrients on land, or (2) add a second lagoon without a solid separator, and hire a
custom service to pump liquid nutrients from the lagoons. Alternative 2 had a lower capital
investment, a net annual cost advantage, a lower net annual cash outflow and lower financial
risk because of less debt. Alternative 1 had a lower risk of environmental damage because of
excess lagoon capacity.

18
Title : Cooperative Milk Society
Author : Rawal , Vikas, Basu, Chakraborty and Kaur
Year : 2001-2010
Description:
Rawal and Vikas (2001) analysed that the comparison of caste, education and land holding of
MS farmers with NMS farmers points to a larger proportion of households belonging to the
backward caste, being less educated and holding lower size of land are not able to participate
in dairying. A recent study of two dairy co-operatives in Gujarat argued that inequality in
land ownership, caste, illiteracy and undemocratic functioning of co-operatives are the
barriers to entry. Illiteracy might not be a factor in Kerala but land ownership could be one,
as among the lower size class of land owners smaller proportion seem to be keeping cattle.
Basu and Chakraborty (2008) find in a study of two villages in North East India that and land
ownership is a major determinant for participation in dairy cooperatives. They point out that
agriculture and dairying have to be seen as interrelated and a diversification into dairying
does not decrease the dependency on agriculture.
Kaur (2010)32 analyses data from 200 rural dairy households in Punjab that are selling either
to private or cooperative dairies, including mixed-gender and women dairy cooperatives. She
observes that membership for women in the mixed cooperative are restricted to women who
are head of the household. In the village with a women cooperative, female membership is
compulsory. According to the researcher who promoted by authorities in order to make the
milk society economically more successful.

19
CHAPTER 3
SYSTEM ANALYSIS
3.1 GENERAL:
The concept of module comes from modular programming which advocates that
software should be composed of separate, interchangeable components called modules by
breaking down program functions into modules, each of which accomplishes one function
and contain everything necessary to accomplish this here they are the modules mentioned
below.
3.2 MODULES:
This project having the following four modules:
 User Interface Design
 Admin module
 Farmer module
 Seller module
 Advisor module
3.2.1 User Interface Design
Figure 3.1: -User interface diagram
Admin
Farmer
(user)
 Login page
 otherpages
Server
Database
Supplier
(user)
Advisor
(user)

20
Description:
This diagram depicts how users are getting accessed into the social networking sites
through the login page. Then the information provided by the user will be saved in the
databases. While the users in logging into the site, he need to enter the fields required. After
the fields are filled by the exact data, and the data is checked by the server.
3.2.2 Admin Module:
Figure 3.2:-Admin Module Diagram
Description:
In this module, Admin can login securely to the application with valid email address
and password. Farmer and supplier can login securely to the application with valid email
address and temporary password for the first time and they can change their own password to
login from next time. Admin will help both farmer and supplier in solving their needs in
purchasing and selling of their dairy products through the site. It also helps in giving tips to
the farmers in matters related to dairy farming website.
Admin Login
Database

21
3.2.3 Farmer Module:
Figure 3.3:-Farmer Module Diagram
Description:
In this module, the farmer first needs to be registered to login. The farmer need to
login in to get access to the system. The page where farmers can post their complaints and
only assigned administrators can read and edit this page. In this page farmers can view the
complaints details by viewing the status of complaints is read or unread. This page consists of
crop advertisement details post by the supplier and the status of the sell crop accepted.
Farmer Login
Database
Queries
Add products
Remove products
View products

22
3.2.4 Supplier Module:
Figure 3.4:- Supplier Module Diagram
Description:
In this module, the supplier first need to be registered himself to login. The supplier
need to login in to get access to the system. Pages where dealers and retailers may post their
ads and notifications. The post consists of crop id, crop name, crop image and quantity
required. Farmers are notified of these notifications via SMS. It is result of post that notified
that the crop is accepted or not to the farmers.
View
products
Remove
products
Add productsSMS Notification
Supplier
Login
Data Base

23
3.2.5 Advisor Module:
Figure 3.5:- Advisor Module Diagram
Description:
In this module, the supplier first need to be registered himself to login. The Advisor
need to login in to get access to the system. Pages where farmer may post their question. The
Advisor can give suggestions.
Advisor Login
Database
Suggestions

24
3.3 SYSTEM ARCHITECTURE:
System architecture is the conceptual model that defines the structure, behavior, and
more views of a system. An architecture description is a formal description and
representation of a system, organized in a way that supports reasoning about the structures
and behaviors of the system.
A system architecture can consist of system components and the sub-systems developed, that
will work together to implement the overall system. There have been efforts to formalize
languages to describe system architecture, collectively these are called architecture
description languages.
The basic system architecture of the project includes the seller side that is Farmer and
customer side which is other user‘s option available in the system, they contain all the
features available in the system for both the end users.
Figure 3.6:- system architecture

25
CHAPTER 4
SYSTEM REQIRMENTS
4.1 GENERAL:
System requirements are what are necessary for a client to install the web application
in their system and be used hopefully without any difficulties. The aim of this is to help
clients make sure they have all required tools or equipment.
With analysis there are some objectives for hardware, software and any other thing that
would be the minimum requirements to install the system. The minimum requirements are as
follows.
4.2 HARDWARE REQUIREMENTS
The hardware requirements may serve as the basis for a contract for the
implementation of the system and should therefore be a complete and consistent specification
of the whole system. They are used by software engineers as the starting point for the system
design. It should what the system do and not how it should be implemented.
HARDWARE
PROCESSOR : Intel ® Core ™ i3-7100 CPU @ 3.90GHz 3.91GHz
RAM : 1 GB
MONITOR : 15‖ COLOR
HARD DISK : 128 GB

26
4.3 SOFTWARE REQUIREMENTS
The software requirements document is the specification of the system. It should
include both a definition and a specification of requirements. It is a set of what the system
should do rather that how it should do it. The software requirements provide a basis for
creating the software requirements specification. It is useful in estimating cost, planning team
activities, performing tasks and tracing the team‘s progress throughout the development
activity.
SOFTWARE
Front end : AngularJS,
Backend : ExpressJS, NodeJS, MongoDB And ExpressJS,
Operating system : Windows 7 or above
IDE : Microsoft Visual Studio Code, Notepad++
4.4 FUNCTIONAL REQUIREMENTS
A functional requirement defines a function of a software-system or its component. A
function is described as a set of inputs, the behavior, and outputs. The proposed system is
achieved by suppression-based and generalization-based k-anonymous and confidential
databases.
4.5 NON-FUNCTIONAL REQUIREMENTS:
4.5.1 EFFICIENCY
To address the scalability issue, we propose an edge-centric clustering scheme to
extract sparse social dimensions. In sparse social dimensions, the social dimension based
approach can efficiently handle networks of millions of actors while demonstrating
comparable prediction performance as other non-scalable methods.
4.5.2 RELIABILITY
The dynamic nature of networks entails efficient update of the model for collective
behavior prediction.

27
CHAPTER 5
SYSTEM DESIGN
5.1 GENERAL:
Design Engineering deals with the various UML [Unified Modeling Language]
diagrams for the implementation of project. Design is a meaningful engineering
representation of a thing that is to be built. Software design is a process through which the
requirements are translated into representation of the software. Design is the place where
quality is rendered in software engineering. Design is the means to accurately translate
customer requirements into finished product.
System design is the process of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements. Systems design could be seen as the
application of systems theory to product development. There is some overlap with the
disciplines of systems analysis, systems architecture and system engineering.
5.2 UNIFIED MODELING LANGUAGE DIAGRAMS
Following are the different types of a UML diagrams
 Use case diagram
 Class diagram
 Activity diagram
 Sequence diagram
5.2.1 USE CASE
Here source and destination is the actors and peer server also the actors of the use
Case flows. The client need to distribute one content to the destination, the use case diagram
represent the flow. This is the type of behavioral diagram defined by and creates from a Use-
Case analysis.
This diagram depicts the what information should be entered into the and what activities can
be performed in the social networking site and the information in sent into the network. The
network stores the information into the social cloud. Social cloud can access into the social
database.

28
User case diagram for Administrator:
Figure 5.1:- User case diagram for Administrator
User case diagram for Farmer:
Figure 5.2:- User case diagram for Farmer
User case diagram for Seller:
Figure 5.3:- User case diagram for Seller

29
5.2.2 CLASS DIAGRAM:
A class diagram in the Unified Modeling Language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects.
The class diagram is the main building block of object-oriented modeling. It is used for
general conceptual modeling of the structure of the application, and for detailed modeling
translating the models into programming code. A number of classes are identified and
grouped together in a class diagram that helps to determine the static relations between them.
With detailed modeling, the classes of the conceptual design are often split into a number of
subclasses.
Figure 5.4:- Class diagram

30
5.2.3 SEQUENCE DIAGRAM:
Sequence diagrams are typically associated with use case realizations in the Logical
View of the system under development. Sequence diagrams are sometimes called event
diagrams or event scenarios. A sequence diagram shows, as parallel vertical lines (lifelines),
different processes or objects that live simultaneously, and, as horizontal arrows, the
messages exchanged between them, in the order in which they occur. This allows the
specification of simple runtime scenarios in a graphical manner.
This diagram shows how processes operate with one another and in what order. In this
project admin enter the login. After we get login and enter in to the optimization technique
after we have to calculate the total performance of user and identifying the number of active
users in the server.
Sequence diagram for Administrator:
Figure 5.5:- Sequence diagram for Administrator

31
Sequence diagram for Farmer:
Figure 5.6:- Sequence diagram for Farmer
Sequence diagram for Seller:
Figure 5.7:- Sequence diagram for Seller

32
5.2.4 ACTIVITY DIAGRAM:
Activity diagram are a loosely defined diagram to show workflows of stepwise
activities and actions, with support for choice, iteration and concurrency. UML, activity
diagrams can be used to describe the business and operational step-by-step workflows of
components in a system, UML activity diagrams could potentially model the internal logic of
a complex operation. In this diagram first we have to create a network and path selection, the
path that is dynamic at that attacker will interrupt in that network after attacker interrupt our
system then we detect the attacker and prevent network. In this diagram represents the
behavior of path selection.
Activity Diagram for Admin:
Figure 5.8:- Activity Diagram for Admin

33
Activity Diagram for Farmer (staff):
Figure 5.9:- Activity Diagram for Farmer (staff)
Activity Diagram for Seller:
Figure 5.10:- Activity Diagram for Seller

34
5.2.5 DEPLOYMENT DIAGRAM:
A deployment diagram in the Unified Modeling Language models the physical
deployment of artifacts on nodes. To describe a web site, for example, a deployment diagram
would show what hardware components ("nodes") exist (e.g., a web server, an application
server, and a database server), what software components ("artifacts") run on each node (e.g.,
web application, database), and how the different pieces are connected (e.g. JDBC, REST,
RMI).
The nodes appear as boxes, and the artifacts allocated to each node appear as rectangles
within the boxes. Nodes may have sub nodes, which appear as nested boxes.
Figure 5.11:- Deployment diagram

35
5.2.5 COMPONENT DIAGRAM:
A component diagram allows verification that a system's required functionality is
acceptable. These diagrams are also used as a communication tool between the developer and
stakeholders of the system. Programmers and developers use the diagrams to formalize a
roadmap for the implementation, allowing for better decision-making about task assignment
or needed skill improvements. System administrators can use component diagrams to plan
ahead, using the view of the logical software components and their relationships on the
system. The component diagram extends the information given in a component notation
element. One way of illustrating the provided and required interfaces by the specified
component is in the form of a rectangular compartment attached to the component element.
Another accepted way of presenting the interfaces is to use the ball-and-socket graphic
convention. A provided dependency from a component to an interface is illustrated with a
solid line to the component using the interface from a "lollipop", or ball, labeled with the
name of the interface. A required usage dependency from a component to an interface is
illustrated by a half-circle, or socket, labeled with the name of the interface, attached by a
solid line to the component that requires this interface. Inherited interfaces may be shown
with a lollipop, preceding the name label with a caret symbol. To illustrate dependencies
between the two, use a solid line with a plain arrowhead joining the socket to the lollipop.
Figure 5.12:- Component diagram

36
5.2.6 COLLABORATION DIAGRAM:
A communication diagram models the interactions between objects or parts in terms
of sequenced messages. Communication diagrams represent a combination of information
taken from Class, Sequence, and Use Case Diagrams describing both the static structure and
dynamic behavior of a system.
However, communication diagrams use the free-form arrangement of objects and links as
used in Object diagrams. In order to maintain the ordering of messages in such a free-form
diagram, messages are labeled with a chronological number and placed near the link the
message is sent over. Reading a communication diagram involves starting at message 1.0,
and following the messages from object to object. Communication diagrams show a lot of the
same information as sequence diagrams, but because of how the information is presented,
some of it is easier to find in one diagram than the other. Communication diagrams show
which elements each one interacts with better, but sequence diagrams show the order in
which the interactions take place more clearly.
Collaboration diagram for Admin:
Figure 5.13:- Collaboration diagram for Admin

37
Collaboration diagram for Farmer (staff):
Figure 5.14:- Collaboration diagram for Farmer (staff)
Collaboration diagram for Seller:
Figure 5.15:- Collaboration diagram for Seller

38
5.3 DATA-FLOW DIAGRAM
A data-flow diagram (DFD) is a way of representing a flow of a data of a process or a
system (usually an information system). The DFD also provides information about the
outputs and inputs of each entity and the process itself. A data-flow diagram has no control
flow, there are no decision rules and no loops. Specific operations based on the data can be
represented by a flowchart.
There are several notations for displaying data-flow diagrams. The notation presented above
was described in 1979 by Tom DE Marco as part of Structured Analysis.
For each data flow, at least one of the endpoints (source and / or destination) must exist in a
process. The refined representation of a process can be done in another data-flow diagram,
which subdivides this process into sub-processes.
Figure 5.16:-Data flow Diagram

39
5.4 ENTITY–RELATIONSHIP MODEL:
An entity–relationship model (or ER model) describes interrelated things of interest in
a specific domain of knowledge. A basic ER model is composed of entity types (which
classify the things of interest) and specifies relationships that can exist between entities
(instances of those entity types).An entity–relationship diagram for a MMORPG using Chen's
notation.
In software engineering, an ER model is commonly formed to represent things a business
needs to remember in order to perform business processes. Consequently, the ER model
becomes an abstract data model, that defines a data or information structure which can be
implemented in a database, typically a relational database. Entity–relationship modeling was
developed for database and design by Peter Chen and published in a 1976 paper. However,
variants of the idea existed previously. Some ER models show super and subtype entities
connected by generalization-specialization relationships, and an ER model can be used also
in the specification of domain-specific ontologies.
Figure 5.17: Entity–relationship model

40
5.4 DATABASE DESIGN
Database design is the organization of data according to a database model. The designer
determines what data must be stored and how the data elements interrelate. With this information,
they can begin to fit the data to the database model.
5.4.1 Admin database:
Figure 5.18:-Admin
5.4.2 Login database:
Figure 5.19:- Login

41
5.4.1 Question database:
Figure 5.20:- Question
5.4.1 Record database:
Figure 5.21:-Record

42
CHAPTER 6
IMPLEMENTATION
6.1 GENERAL
The implementation of this project describes the Security and Efficiency of Content
Distribution on the Server. On the security and Efficiency of Content Distribution on
Network implementation programmatically. We used many language like MongoDB,
Express.js, AngularJS (or Angular), and Node.js
6.2 TECHNOLOGIES USED
6.2.1 ANGULARJS:
AngularJS is a JavaScript-based open-source front-end web framework mainly
maintained by Google and by a community of individuals and corporations to address many
of the challenges encountered in developing single-page applications. It aims to simplify both
the development and the testing of such applications by providing a framework for client-side
model–view–controller (MVC) and model–view–viewmodel (MVVM) architectures, along
with components commonly used in rich Internet applications.
AngularJS is the frontend part of the MEAN stack, consisting of MongoDB database,
Express.js web application server framework, Angular.js itself, and Node.js server runtime
environment. Version 1.7.x is on Long Term Support until July 1st 2021. After that date
AngularJS will no longer be updated and Angular (2.0+) is suggested instead. The AngularJS
framework works by first reading the Hypertext Markup Language (HTML) page, which has
an additional custom HTML attributes embedded into it. Angular interprets those attributes as
directives to bind input or output parts of the page to a model that is represented by standard
JavaScript variables. The values of those JavaScript variables can be manually set within the
code, or retrieved from static or dynamic JSON resources.
AngularJS is built on the belief that declarative programming should be used to create user
interfaces and connect software components, while imperative programming is better suited
to defining an application's business logic. The framework adapts and extends traditional
HTML to present dynamic content through two-way data-binding that allows for the
automatic synchronization of models and views. As a result,.

43
6.2.2. NODE.JS:
Node.js is an open-source, cross-platform, JavaScript runtime environment that
executes JavaScript code outside of a web browser. Node.js lets developers use JavaScript to
write command line tools and for server-side scripting—running scripts server-side to
produce dynamic web page content before the page is sent to the user's web browser.
Consequently, Node.js represents a "JavaScript everywhere" paradigm, unifying web-
application development around a single programming language, rather than different
languages for server- and client-side scripts.
Though .js is the standard filename extension for JavaScript code, the name "Node.js" doesn't
refer to a particular file in this context and is merely the name of the product. Node.js has an
event-driven architecture capable of asynchronous I/O. These design choices aim to optimize
throughput and scalability in web applications with many input/output operations, as well as
for real-time Web applications (e.g., real-time communication programs and browser games).
The Node.js distributed development project was previously governed by the Node.js
Foundation,and has now merged with the JS Foundation to form the OpenJS Foundation,
which is facilitated by the Linux Foundation's Collaborative Projects program.
Corporate users of Node.js software include GoDaddy, Groupon,IBM, LinkedIn, Microsoft,
Netflix, PayPal, Rakuten, SAP, Voxer, Walmart, and Yahoo!.
6.2.3 EXPRESS.JS:
Express.js, or simply Express, is a web application framework for Node.js, released as
free and open-source software under the MIT License. It is designed for building web
applications and APIs. It has been called the de facto standard server framework for Node.js.
The original author, TJ Holowaychuk, described it as a Sinatra-inspired server, meaning that
it is relatively minimal with many features available as plugins. Express is the back-end
component of the MEAN stack, together with the MongoDB database software and
AngularJS front-end framework
Following are some of the core features of Express framework −
 Allows to set up middlewares to respond to HTTP Requests.
 Defines a routing table which is used to perform different actions based on HTTP
Method and URL.

44
 Allows to dynamically render HTML Pages based on passing arguments to templates.
6.2.4 MongoDB:
MongoDB is a cross-platform document-oriented database program. Classified as a
NoSQL database program, MongoDB uses JSON-like documents with schema. MongoDB is
developed by MongoDB Inc. and licensed under the Server Side Public License (SSPL).
Main features:
1. Ad-hoc queries
MongoDB supports field, range query, and regular-expression searches.[9] Queries can return
specific fields of documents and also include user-defined JavaScript functions. Queries can
also be configured to return a random sample of results of a given size.
2. Indexing
Fields in a MongoDB document can be indexed with primary and secondary indices.
3. Replication
MongoDB provides high availability with replica sets.[10] A replica set consists of two or
more copies of the data. Each replica-set member may act in the role of primary or secondary
replica at any time. All writes and reads are done on the primary replica by default.
Secondary replicas maintain a copy of the data of the primary using built-in replication.
When a primary replica fails, the replica set automatically conducts an election process to
determine which secondary should become the primary. Secondaries can optionally serve
read operations, but that data is only eventually consistent by default.
4. Load balancing
MongoDB scales horizontally using sharding.The user chooses a shard key, which
determines how the data in a collection will be distributed. The data is split into ranges (based
on the shard key) and distributed across multiple shards. (A shard is a master with one or
more replicas.). Alternatively, the shard key can be hashed to map to a shard – enabling an
even data distribution.

45
5. File storage
MongoDB can be used as a file system, called GridFS, with load balancing and data
replication features over multiple machines for storing files.
This function, called grid file system, is included with MongoDB drivers. MongoDB exposes
functions for file manipulation and content to developers. GridFS can be accessed using
mongo files utility or plugins for Nginx and lighttpd. GridFS divides a file into parts, or
chunks, and stores each of those chunks as a separate document.
6. Aggregation
MongoDB provides three ways to perform aggregation: the aggregation pipeline, the map-
reduce function, and single-purpose aggregation methods.
Map-reduce can be used for batch processing of data and aggregation operations. But
according to MongoDB's documentation, the Aggregation Pipeline provides better
performance for most aggregation operations.
The aggregation framework enables users to obtain the kind of results for which the SQL
GROUP BY clause is used. Aggregation operators can be strung together to form a pipeline –
analogous to UNIX pipes. The aggregation framework includes the $lookup operator which
can join documents from multiple collections, as well as statistical operators such as standard
deviation.
7. Server-side JavaScript execution
JavaScript can be used in queries, aggregation functions (such as MapReduce), and sent
directly to the database to be executed.
8. Capped collections
MongoDB supports fixed-size collections called capped collections.This type of
collection maintains insertion order and, once the specified size has been reached,
behaves like a circular queue.

46
6.3 IMPLEMENTAION
home.component.html
<app-header></app-header>
<div>
<app-sidebar></app-sidebar>
<div id="rightSideWrapper">
<div class="ContentBox">

<main> <img src="../../assets/images/ggg.png" width="100%" height="600px"/>
</main>
 <footer>
<app-footer></app-footer>
</footer>
</div> </div> </div>
home.component.ts
import { Component, OnInit } from '@angular/core';
@Component({ selector: 'app-home',
templateUrl: './home.component.html',
styleUrls: ['./home.component.css']})
export class HomeComponent implements OnInit { constructor() { }token;
ngOnInit()
{
}}

47
home.component.css
#rightSideWrapper
{ /*Strictly Necessary */
width:84%;
float: right; /*Aesthetics*/
background: black; }
.ContentBox
{
margin-top: 50px;
/*The height of the header*/ /* display:flex; */ /* flex-flow: row wrap; */
}
main, section, footer
{
/*Aesthetics*/
background: lightgray;
/*border-radius: 7px;*/
/*margin: 5px;*/
/* padding: 0px; */
}
main
{
/*Strictly Necessary */
height: 600px;
/* order: 1; */
/* flex: 0 1 100%; */
}
Section

48
{ /*Strictly Necessary */
height: 400px;
order: 2;
flex: 0 1 100%;
}
footer {
/* height: 400px;
*/ display: block;
order: 3;
flex: 0 1 100%; }
Farmer.component.html
<app-header></app-header>
<div>
<app-sidebar></app-sidebar>
<div id="rightSideWrapper">
<div class="ContentBox">
<main>
<header class="navbar navbar-inverse navbar-expand-sm bg-info navbar-dark"
id="nhea">
<div class="container-fluid">
<ul class="nav navbar-nav navbar-left">
<li class="nav-item ">
<a class="nav-link" (click)='addquestion()'>Add Question</a>
</li>
<li class="nav-item">

49
<a class="nav-link" (click)='addproduct()'>Add products</a>
</li>
<a class="nav-link" (click)='showproduct()'>Show products</a>
</li>
<a class="nav-link" (click)='showanswer()'>Show Answer</a>
</li>
<a class="nav-link" (click)='showsuggetion()'>Show Suggetion</a>
</li></ul>
<ul class="nav navbar-nav navbar-right">
<li class="nav-item" >
<a class="nav-link" (click)='logout()'>LogOut</a>
</li>
</ul>
</div>
</header>
<div class="a" style="margin-left:16%">
<router-outlet></router-outlet>
</div>
</main>

<footer>
<app-footer></app-footer>
</footer>

50
</div>
</div>
</div>
Farmer.component.css
header {
position: fixed;
width: 100%;
height: 50px; /*Adjust the hight to your purposes*/
/*Aesthetics*/
background: lightSalmon;
/*border-radius: 7px;*/
}
Farmer.component.ts
import { Component, OnInit } from '@angular/core';
import { ActivatedRoute, Router, ParamMap } from '@angular/router';
import { AuthService } from '../auth.service';
@Component({
selector: 'app-farmer',
templateUrl: './farmer.component.html',
styleUrls: ['./farmer.component.css']
})
export class FarmerComponent implements OnInit {

51
constructor(private route: ActivatedRoute, private router: Router,private authservice:
AuthService) { }
ngOnInit() {
}
addquestion(){
this.router.navigate(['addquestion'], { relativeTo: this.route });
}
showanswer(){
this.router.navigate(['showanswer'],{relativeTo: this.route})
}
addproduct(){
this.router.navigate(['addproduct'],{relativeTo: this.route})
}
showproduct(){
this.router.navigate(['showproduct'],{relativeTo: this.route})
}
showsuggetion(){
this.router.navigate(['showsuggetion'],{relativeTo: this.route})
}
logout() {
this.authservice.logoutUser();
this.router.navigate(['/login']);
}
}

52
Auth.Service.ts
import { Injectable } from '@angular/core';
import { HttpClient } from '@angular/common/http';
import { Router } from '@angular/router';
@Injectable({
providedIn: 'root'
})
export class AuthService {
constructor(private http: HttpClient,private router:Router) { }
signup(user)
{
return this.http.post('http://localhost:3000/users/register',user)
}
login(user){
return this.http.post('http://localhost:3000/users/authenticate',user)
}
loggedIn(){
console.log("loggedIn")
if(localStorage.getItem('token')==null)
{
return false
}
else
return true
}
curruserdata(){

53
if(localStorage.getItem('token') !== null)
return localStorage.getItem('token');
else
return '';
}
logoutUser() {
localStorage.removeItem('token')
this.router.navigate(['/login']);
}
getuserbyid(user){
return this.http.post('http://localhost:3000/getuserbyid',user)
}
getuser(data){
return this.http.post('http://localhost:3000/getuser',{'phnno':data})
}
useredit(user){
return this.http.post('http://localhost:3000/useredit',user)
}
}
Server.js
require('rootpath')();
const express = require('express');
const app = express();
const cors = require('cors');
const bodyParser = require('body-parser');
const jwt = require('_helpers/jwt');
const errorHandler = require('_helpers/error-handler');

54
app.use(bodyParser.urlencoded({ extended: false }));
app.use(bodyParser.json());
app.use(cors());
// use JWT auth to secure the api
app.use(jwt());
// api routes
app.use('/users', require('./routes/users.controller'));
app.use('/donors', require('./routes/users.controller'));
app.use('/records', require('./routes/records.controller'));
app.use('/quotes', require('./routes/quotes.controller'));
app.use('/notifications', require('./routes/notifications.controller'));
app.use('/question', require('./routes/question.controller'));
// global error handler
app.use(errorHandler);
// start server
const port = process.env.NODE_ENV === 'production' ? (process.env.PORT || 80) : 3000;
const server = app.listen(port, function () {
console.log('Server listening on port ' + port);
});
db.js
const config = require('config.json');

55
const mongoose = require('mongoose');
console.log(process.env.MONGODB_URI || config.connectionString)
mongoose.connect(process.env.MONGODB_URI || config.connectionString, {
useCreateIndex: true, useNewUrlParser: true });
mongoose.Promise = global.Promise;
module.exports = {
User: require('../models/user.model'),
Record: require('../models/record.model'),
Quote: require('../models/quote.model'),
Notification: require('../models/notification.model'),
Question: require('../models/question.model')
};
config.json
{
"connectionString": "mongodb://localhost/farm",
"secret": "secret"
}

56
CHAPTER 7
TESTING
7.1 GENERAL
Software testing is an investigation conducted to provide stakeholders with
information. Software testing can also provide an objective, independent view of the software
to allow the business to appreciate and understand the risks of software implementation. Test
techniques include the process of executing a program or application with the intent of
finding software bugs (errors or other defects), and verifying that the software product is fir
for use.
7.2 DEVELOPING METHODOLOGIES
The test process is initiated by developing a comprehensive plan to test the general
functionality and special features on a variety of platform combinations. Strict quality control
procedures are used.
The process verifies that the application meets the requirements specified in the system
requirements document and is bug free. The following are the considerations used to develop
the framework from developing the testing methodologies.
7.3 TYPES OF TESTS
7.3.1 UNIT TESTING
Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program input produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual software
units of application. It is done after the completion of an individual unit before integration.
This is a structural testing, that relies on knowledge of its construction and is invasive. Unit
tests perform basic tests at component level and test a specific business process, application,
and /or system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined inputs and
expected results.

57
7.3.2 INTEGRATION TESTING
Software integration testing of two or more integrated software components on a
single platform to produce failures caused by interface defects. The task of the integration test
is to check that components or software applications, e.g. components in a software system or
– one step up – software applications at the company level – interact without error.
7.3.3 FUNCTIONAL TESTING
Functional tests provide systematic demonstrations that functions tested are available
as specified by the business and technical requirements, system documentation, and user as
specified by the business and technical requirements, system documentation, and user
manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : Identified functions must be exceried.
Output : identified classes of application outputs must be excersied.
Systems, Procedures : interfacing systems or procedures must be invoked.
7.3.4 SYSTEM TEST
System testing ensures the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing is
the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.
7.3.5 PERFORMANCE TEST
The performance test ensures that the output be produced within the limits, and the time
taken by the system for compiling, giving response to the users and request being send to the
system for to retrieve the results.
7.3.6 ACCEPTANCE TESTING
User Acceptance testing is a critical phase of any project and requires significant
participation by the end user. It also ensure that the system meets the functional requirements.

58
7.4 TEST CASES:
7.4.1 REGISTRATION TEST CASE:
Requirement : Farmer/supplier registration
Testing method : Unit testing
Table 7.1:-User registration
Test case
id
Test
Scenario
Test Steps Test Data Expected
result
Pass/fail
Tc1 Check user
registration
with valid
data
1.Role type
2.Name
3. Phone No.
4. Password
5.Conf.password
6.State
7.Email
1.seller
2. Rab
3. 9876543201
4.123456789
5.123456789
6. TS
7. rab@g.com
Successful
user login
on valid
data
Pass
Tc2 Check user
registration
with invalid
data
1. Role type
2. Name
3. Phone No.
4. Password
5.Conf.password
6. State
7. Email
1. seller
2. Rab
3. 9876543201
4. 123456789
5. 123456789
6. TS
7. rab@g.com
Registration
failure
or left
mandatory
field
pass

59
7.4.2 AUTHENTICATION TEST CASE:
Requirement : Farmer/Supplier authentication
Table 7.2:-User login
Test case
id
Test
Scenario
result
Pass/fail
Tc3 Check
teacher and
student
login with
valid Data
1. Phone
No.
2.password
3.click
Login
1. Phone No.=
9876543201
2.Password=123456789
Successful
user login
on valid
data
Pass
Tc4 Check
login with
invalid data
1. Phone
No.
2.password
3.click
Login
1. Phone No.
=9876543201
2.Password=12345
Login
failure
pass
7.4.3 ADD PRODUCTS TEST CASE:
Requirement : Add product
Table 7.3:-Add products
Test case
id
Test
Scenario
result
Pass/fail
Tc5 Check
product data
with valid
1.Role type
2.Name
1.Farmer
2.Cow Milk
Add Product
Successfully
Pass

60
data. 3.Unit
4.Price
5.Description
3.litre
4.60
5.Good
Tc6 Check
product data
with invalid
data.
1.Click
submit
Null Add Product
Unsuccessful
Pass
7.4.4 ASK QUESTION AND GIVE SUGGESTION TEST CASE:
Requirement : Ask Question and Give Suggestion
Table 7.4:- Ask Question and Give Suggestion
Test case id Test
Scenario
result
Pass/fail
Tc7 Send
question or
answer with
entering data
1.Enter
question or
answer
Mandatory
2.Click send
Question or
answer
should send
with Enter
Data
Mandatory
Question Sent
or receive
answer
Successfully
Pass
Tc8 Send
question or
answer
without
entering data
1. Enter
question or
answer
Mandatory
2.Click send
NULL Question Sent
or receive
answer
Unsuccessfully
Pass

61
CHAPTER 8
SCREENSHOTS
8.1 GENERAL
Snapshot is nothing but every moment of the application while running. It gives the clear
elaborated of application. It will be useful for the new user to understand the application.
8.2 VARIOUS SNAPSHOTS
8.2.1 Index page
Figure 8.1:-index page
Description: Above is the Index page where user can choose sign in or sign up.

62
8.2.2 Registration page:
Figure 8.2:- Registration page
Description: Above is the Login page where user can register.
8.2.2 Login page
Figure 8.2:- Login page
Description: Above is the Login page where user can Login.

63
8.2.3 Admin page
Figure 8.3:- About page
Description: Above is the Admin page where Admin manage the website.
8.2.4 Farmer page:
Figure 8.4:- Farmer page
Description: Above is the Farmer page where farmer can add products, ask questions etc.

64
8.2.5 Seller page:
Figure 8.5:- Seller page
Description: Above is the Seller page where seller can manage products.
8.2.6 Advisor page:
Figure 8.6:- Advisor page
Description: Above is the Advisor page where user can give suggestions on framer
questions.

65
CHAPTER 9
CONCLUSION AND FUTURE ENHANCEMENT
9.1 CONCLUSION
In conclusion, our project has been successfully implemented the idea of online
business. Buyers and sellers can purchase anything from anywhere. Our project helps buyers
and sellers in saving a lot of time and money. By the help of this farming stock trade people
will be able to get fresh milk to drink and will be able to explore parts of their nearby villages
for picking up their purchases and exploring the place establishing relation with farmers and
gaining profit by saving their money, adding profit directly to the farmer helping farmers too.
9.2 RECOMMENDATION ACTIONS
Modern dairies should work by judiciously building an efficient system integrating
the activities of several factors.The entire cow's need should be supplied in its immediate
environment so that the cow's energy is devoted to milk production. The dairy industry has to
integrate the feeding system, genetic data, advanced milking system, milk transport and
processing facilities, administrative tasks, and skilled manpower. The second
recommendation action is that final year projects should be done in groups, because with the
little knowledge student are, it would help students develop more advanced systems than if
they do the alone. It would also easy some of the challenges that students undergo during the
project.
9.3 FUTURE ENHANCEMENT
 Seller can see purchase sell milk show to online.
 Seller can her payment direct in her/his account.
 Customer also will be an user of the system.
 System need to be improving performance.

Eco dairy environment friendly dairy farming practices

Eco dairy environment friendly dairy farming practices

Recommended

Recommended

More Related Content

Similar to Eco dairy environment friendly dairy farming practices

Similar to Eco dairy environment friendly dairy farming practices (20)

Recently uploaded

Recently uploaded (20)

Eco dairy environment friendly dairy farming practices