A

PROJECT REPORT
ON
“Dairy Management System”
SUBMITTED TO

SAVITRIBAI PHULE PUNE UNIVERSITY, PUNE

FOR THE PARTIAL FULLFILLMENT OF THE DEGREE OF MASTER

OF COMPUTER APPLICATION (MCA)
SUBMITTED BY
NAME OF STUDENT

PIRENS INSTITUTE OF BUSINESS MANAGEMENT AND

ADMINISTRATION (IBMA)
LONI (BK), TAL- RAHATA, DIST.AHMEDNAGAR.

SAVITRIBAI PHULE PUNE UNIVERSITY

2023-24
 SAVITRIBAI PHULE PUNE UNIVERSITY, PUNE

CERTIFICATE
This to certify that
NAME OF STUDENT
Seat Number – 5026
Student of Second Year of Master of Computer Application (MCA)
was examined in Project Report entitled

“Dairy Management System”

On - / /2024
At

PIRENS INSTITUTE OF BUSINESS MANAGEMENT AND

ADMINISTRATION, (IBMA) LONI (BK), TAL- RAHATA, DIST-
AHMEDNAGAR.

(………………..….) (………..…………)
Internal Examiner External Examiner
 CERTIFICATE BY GUIDE

This is to certify that Miss. NAME OF STUDENT and has completed the
project work under my guidance and supervision that I have verified the work for
documentation, problem statement and result presented in the project work.

Place: Loni (Dr. M. S. Langote)

Date: / /24 PIRENS IBMA, Loni
 ACKNOWLEDGEMENT

I wish to take opportunity to express our profound thanks & gratitude to all those who
have directly or indirectly helped us in the completion of this project.

I am also extremely thankful grateful to our project guide Dr. M. S. Langote

inspiration and constructive suggestions that helpful us in the preparation of this project.
We also thanks to our Academic Coordinator of MCAII (Master of Computer
Application) Prof. R.S. Tanpure who have helped in successful completion and
certification of the project.
 INDEX

Chapter Details Page

No No
1 INTRODUCTION 1-2
1.1 Introduction 3-4
1.2 Abstract 5
1.3 Existing System and Need for System 6
1.4 Scope of System 7
1.5 Operating Environment- Hardware and Software 8
1.6 Brief Description of Technology Used 9-12
1.6.1 Operating System Used (windows or Unix)
1.6.2 RDBMS/No SQL used to build database (MySQL/oracle, Teradata, etc.)
2 PROPOSED SYSTEM 13
2.1 Proposed System 14-15
2.2 Feasibility Study 16
2.3 Object of The System 17
2.4 Users of System 18
3 ANALYSIS & DESIGN 19
3.1 Entity Relationship Diagram (ERD) 20
3.2 Table Structure 21-23
3.3 Class Diagrams 24
3.4 Use Case Diagram 25-28
3.5 Activity Diagram 29-31
3.8 Sample Input and Output Screen 34-40
4 CODING 41
Code snippets 41-45
5 TESTING 46
5.1 Test Strategy 47
5.2 Unit Test Plan 48
5.3 Acceptance Test Plan 48
5.4 Test Case 49-50
6 Drawbacks & Limitations 51
7 Proposed Enhancement 52
8 Conclusion 53
9 Bibliography
 INTRODUCTION

CHAPTER 1: INTRODUCTION

1.1 Company Profile

1.2 Project Introduction
1.3 Existing System and Need for System
1.4 Scope of Work
1.5 Operating Environment - Hardware and Software
1.6 Brief Description of Technology Used
1.6.1 Operating System Used (windows or Unix)
 Chapter 1

1.1

INTRODUCTION

Dairy management system is a software that helps in managing dairy related day-to-day
activities. These include milk collection, sales, managing dairy members, customers, and
plant related other processes.
A dairy management system also comes with a credit and advance feature to ease your
collections and track upcoming payments. You can also track your daily expenses.
Dairy Management System in VB.Net base application.
The project Dairy Management system includes registration of Farmers, storing their
details into the system. The software has the facility to give a unique id for every Farmers
and stores the details of every Farmers.

The Dairy Management System can be entered using a username and password. It is
accessible either by an administrator. Only they can add data into the database. The data
can be retrieved easily. The interface is very user-friendly. The data are well protected for
personal use and make the data processing very fast.
Dairy Management System is an application or software designed to manage activities
related to your daily work such as milk collections from members, sales to the customer
and all the dairy-related processes. It became tough for dairy owners to manage all dairy
work manually. To reduce manual work, A dairy management System can help to make day-
to-day dairy related activities easier. It helps to maximize the profit by improving herd
fertility.
1.2 Abstract

The purpose of the project entitled as " Dairy Management System" is to

computerize the Front Office Management of admin to develop software which is
user friendly simple, fast. and cost effective. It deals with the collection of Farmers
information like add Farmers, update Farmers, delete Farmers, search Farmers, view
Farmers etc. Traditionally, it was done manually. The main function of the system
is register and store Farmers details and their milk details and retrieve these details
as and when required, and to manipulate these details meaningfully. The Dairy
Management System can be entered using a username and password. It is accessible
by an Admin. Only they can add data into the database. The data can be retrieved
easily. The data are well protected for personal use and makes the data processing
very fast.
System has powerful logical access management in place, each user must be
identified by login id and strict password policy is applied to secure the system.
1.3 Existing System and Need for System

The current manual system has a lot of paper work. To maintain the records of sale
and service manually, is a Time-consuming task. With the increase in database, it
will become a massive task to maintain the database. Requires large quantities of
file cabinets, which are huge and require quite a bit of space in the dairy, which can
be used for storing records of previous details. The retrieval of records of previously
registered Farmers will be a tedious task. Lack of security for the records, anyone
disarrange the records of your system. If someone want to check the details of the
customer the previous system does not provide any necessary detail of this type.

All this work is done manually by the dairy manager and other operational staff and
lot of papers are needed to be handled and taken care of it. Dairy Manager must
remember various tasks available for completed and sometimes miss better
alternatives as they cannot remember them at that time.
-
1.4 Scope of System

A Dairy Management System serves as a comprehensive platform for efficiently

running dairy farm operations. It encompasses various aspects including livestock
management, feeding schedules, health records, and breeding cycles. This system
facilitates the tracking of milk production, ensuring both quantity and quality standards
are met through meticulous monitoring of milking processes and storage conditions.
Financial aspects such as expense tracking, revenue generation, and budgeting are
managed within the system, providing insights into the profitability of the operation.
Additionally, it handles supply chain logistics, from procurement of feed and supplies
to distribution of dairy products. Compliance with regulatory standards and reporting
requirements is streamlined, ensuring adherence to industry regulations, and enabling
performance evaluation. Data analysis capabilities within the system allow for the
extraction of actionable insights from historical data, supporting informed decision-
making. Integration with other systems and scalability features enable seamless
adaptation to the evolving needs of the dairy farm, whether it involves expanding
operations or diversifying product lines.
1.5 Operating Environment - Hardware and Software

HARDWARE REQUIREMENTS:

• Any processor after Pentium 4.

• Any version of Windows XP or later.
• Processor speed: 2.0 GHz
• RAM: 1GB
• Hard disk: 40GB to 80 GB

SOFTWARE REQUIREMENTS:

• Database: SQL
• Server: SQL server management studio
• Technology: VB.Net
• Software: VS Code
 1.6 Brief Description of Technology Used
1.6.1 Operating Systems Used (Windows or Unix)

All About Windows

Windows is an operating system designed by Microsoft. The Operating System is what

allows you to use a computer. Windows comes preloaded on most new personal
computers (PCs), which helps to make it the most popular operating system in the world.

Windows makes it possible to complete all types of everyday tasks on your computer. For
example, you can use Windows to browse the Internet, check your email, edit digital
photos, listen to music, play games, and do much more.
Including how to use the desktop, how to open different files and applications, and how to
move and resize windows. The information in this tutorial will apply to more recent
versions of Windows, including the ones mentioned above. However, once you have
learned the basics, you may also want to review one of our version-specific Windows
tutorials. Just select the version of Windows that is installed on your computer:
• Windows 10
• Windows 8
• Windows 7
• Windows XP

Windows 8 vs. other versions

While most versions of Windows are relatively similar, Windows 8 works very
differently from other versions. However, if you have Windows 8 on your computer, you
should now be able to upgrade to Windows 10, which is more like earlier versions,
including Windows 7. We recommend upgrading your computer to Windows 10 if you
can.
However, we will still point out any major differences between Windows 8 and other
versions, which means you will see some Windows 8-specific information from time to
time. If your computer uses Windows 8, you'll want to review both this tutorial and our
Windows 8 tutorial to learn more about the differences.
Navigating Windows

Whether you are new to computers or just Windows, it is important to learn the
basics of using your computer. If it all seems a little overwhelming right now, do
not worry! We will take you through it step by step and show you some of the most
fundamental things you will need to know, including how to work with the desktop,
open and close windows, and turn off your computer.

The desktop
Once your computer has finished starting up, the first thing you will see is the
desktop. You can think of the desktop as the main workspace for your computer.
From here, you can view and manage your files, open applications, access the
Internet, and much more.

Working with windows

Whenever you open a file, folder, or application, it will appear in a new window.
You can have multiple items open at the same time in different windows. You will
use windows all the time, so it is important to know how to switch between open
windows, how to move and resize windows, and how to close windows when you
are done using them.

In Windows 8, some programs will open on the Start screen, not the desktop. If you
are using Windows 8, note that the information below applies only to windows you
have opened on the desktop.
Switching between windows
If you have more than one window open at the same time, you can quickly switch
between them by clicking the icon for that window on the taskbar.

Shutting down your computer

When you are done using your computer, it is important to shut it down properly.
The procedure will vary slightly depending on which version of Windows you are
using.
To shut down your computer:
• If you are using Windows 10, click the Start button, then the Power icon, then
click shut down.

• If you are using Windows 8, click the Start button to access the Start screen, click
the Power icon near the upper-right corner, and select shut down. If you do not
see this option, it means you will need to upgrade to Windows 8.1. Review this
page from our Windows 8 tutorial to learn how.

• If you are using Windows 7 or earlier, click the Start button, then select shut down.

Restarting and Sleep mode:

You can also click the power button button for more options. For example, if your
computer has become unresponsive, you can choose Restart to quickly turn it off
and on again.

You can also choose to put your computer into Sleep mode. This turns off most of
your computer's processes, but it remembers which applications and files are open.
It allows the computer to start up more quickly because you will not have to wait
for the operating system and applications to load. Note that your computer may go
into Sleep mode automatically if you have not used it for more than a few minutes.

If you have a laptop, you can simply close the lid to put it into Sleep mode.

Waking your computer from Sleep mode:

If your computer is in Sleep mode, you will need to wake it to use it. To wake the
computer from Sleep mode, click the mouse or press any key on the keyboard.
 PROPOSED SYSTEM

CHAPTER 2: PROPOSED SYSTEM

2.1 Proposed System
2.2 Feasibility Study

2.3 Objective of Proposed System

2.4 Uses of System

2.1 Proposed System
The Dairy Management System is designed for any dairy to replace their existing
manual paper-based system. The new system is to control the information of
Farmers as well as Milk. These services are to be provided in an efficient, cost-
effective manner, with the goal of reducing the time and resources currently
required for such tasks. In this project we use VB.net and MySQL database. It has
only one module.

Admin Module

1. Dashboard: In this section admin customer records, payment details,

generated reports, etc
2. Admin: In this section, admin can add farmers and manage reports.
3. Customer: In this section, admin can view customer details and have
right to delete irrelevant user.
4. Payment: In this section, admin can view payment details.
5. Shares: In this section, admin can view shares.

Admin can also update his profile, change the password, and recover the password.
2.2 Feasibility Study
Feasibility study is a process to check possibilities of system development. It is a
method to check various requirements and availability of financial & technical
resources. Before starting the process various parameters must be checked like:

• Estimated finance is there or not?

• The man power to operate the system is there or not?

• The man power is trained or not? There are three different ways feasibility can be
tested

1) Economical Feasibility

2) Technical Feasibility

3) Operational Feasibility.

2.2.1 Economical Feasibility:

The economic feasibility analysis indicates that implementing a Dairy Management
System is financially viable. By increasing efficiency, improving decision-making,
and enhancing compliance and animal welfare, the DMS can provide significant
economic value to the dairy farm.

2.2.2 Technical Feasibility:

Technical feasibility centers on the existing computer system. (Hardware/software)

and to what extent it can support the proposed addition also the organization already
has sufficient high-end machines to serve the processing requirements of the proposed
system. So there is no need to purchase new software as the organization has necessary
software i.e. Microsoft SQL Server or hardware to support the proposed system
2.2.3 Operational Feasibility:
Once the system is designed there must be trained and expert operator. If there are
not trained, they should give training according to the needs of the system. From
the user’s perspective our system fully operational feasible as it just requires some
knowledge of computer. Operators only need add daily prices of various equities
and there are enough validations available so operator does not require any special
technical knowledge. So, our system also passes the test of operational feasibility.
2.3 Objective of The System:

• Automate Routine Tasks:

Implement automation for tasks such as feeding schedules, milking
processes, and health monitoring to reduce manual labor and increase
efficiency.

• Streamline Data Management:

Centralize data collection and management to eliminate redundancy and
ensure accurate, real-time information is available for decision-making.

• Ensure Quality Control:

Maintain high standards of milk quality through continuous monitoring and
traceability from production to delivery.

• Cost Reduction:
Identify areas for cost savings through detailed financial analysis and
optimization of resources.

• Analytics and Reporting:

Provide advanced analytics and reporting tools to help make informed
decisions based on accurate data.

• Predictive Analytics:
Use predictive models to forecast milk production, detect potential health
issues, and optimize feeding and breeding strategies.
2.4 Uses of System:

➢ Real-time Monitoring: Track milk yield and quality in real-time .

➢ Data Analysis: Analyze production data to identify trends, optimize milking

schedules, and improve overall milk yield.

➢ Quality Control: Monitor milk quality parameters (e.g., fat content, protein
levels) to ensure consistent product quality.

➢ Profitability Analysis: Use financial reports and analytics to assess the

profitability of different farm operations and identify cost-saving
opportunities.

➢ Record Keeping: Maintain comprehensive records of milk production,

animal health, feed usage, and financial transactions to comply with
regulatory requirements.

➢ Audit Preparation: Easily generate reports and documentation needed for

regulatory audits and inspections.
 ANLYSIS AND DESIGN

CHAPTER 3: ANLYSIS AND DESIGN

3.1 Entity Relation Diagram (ERD)

3.2 Table specifications

3.3 Class Diagram

3.4 Use Case Diagram

3.5 Activity Diagram

3.7 Sample Input and Output Screen

3.1 Entity Relationship Diagram (ERD)

An entity relationship diagram, also known as an entity relationship model, is a

graphical representation that depicts relationships among people, objects, places,
within an information technology (IT) system. An entity relationship diagram
shows the relationship of entity sets stored database.
3.2 TABLE STRUCTURE:
3.2.1 Customer Table:

Sr. Column Type Null Constraint

No

1 id int(11) No Primary key

2 cust_name varchar(255) No NULL

3 cust_address longtext Yes NULL

4 cust_email varchar(255) No NULL

5 cust_contactno bigint(11) No NULL

3.2.2 Admin Table:

Sr. Column Type Null Constraint

No

1 id int(11) No Primary Key

2 username varchar(255) No NULL

3 password int(10) No NULL

3.3 Class Diagram
The class diagram is a static diagram. It represent the static view of an application
or a system. The class diagram describes the attributes an operation of a class an
also the constraint imposed on the system. The class diagram is widely used in the
modeling of the object-oriented systems.
3.4.2 Use Case Diagram of Admin:
A Use Case Diagram is a vital tool in system design, it provides a visual representation
of how users interact with a system.
1.3 Activity Diagram

Activity diagram is another important behavioral diagram in UML diagram to

describe dynamic aspects of the system. Activity diagram is essentially an
advanced version of flow chart that modeling the flow from one activity to another
activity.

i. Activity Diagram of Admin

 SCREENSHOTS

Login Page: This page is used to login in the application.

Home page: This is the home page.
Center information: This shows the information about the different sections of the
application.
Registration of Organization: This page shows the information about the
registration of the organization.
Info regarding Exchange of Milk: This page shows the information regarding
exchange of milk.
Daily Collection & Record of Milk: This page shows the information of the daily
collection and records of milk.
Page of cash Voucher : This page shows the information about the cash voucher.
Page of Investment About Dairy Inventory: This page shows the information
about the investment about dairy inventory.
Page of Share Master List: This page shows the share master list.
Page Of Master Reports Dairy Inventory : This page shows the masters reports
of daily inventry.
Milk Share Information: This shows the Milk share information.
Deadstock Information: This shows the desktop information.
 Coding

CHAPTER 4: Coding for login page-

Public Class MainForm

Dim iCount As Integer = 0

Private Sub MainForm_Load(sender As Object, e As EventArgs) Handles Me.Load

StatusLabel1.Text = CoOpNameEng

StatusLabel2.Text = UserId

StatusLabel3.Text = Mtrandt

End Sub

Private Sub MainForm_Shown(sender As Object, e As EventArgs) Handles Me.Shown

MainFormProgressBar.Value = 0

UserMenuAuth()

End Sub

Private Sub MainForm_FormClosing(sender As Object, e As FormClosingEventArgs)

Handles Me.FormClosing
Dispose()

Application.Exit()
End Sub

Public Sub UserMenuAuth()

Dim MenuYesNo As Boolean

 Dim SubMenuYesNo As Boolean

Try

For Each objControl As Control In Controls

If TypeOf objControl Is MenuStrip Then

Dim objMenuStrip As MenuStrip = DirectCast(objControl, MenuStrip)

For Each objToolStripItem As ToolStripItem In objMenuStrip.Items

Try
Dim TempString As String = "Select MenuName from MenuAuth
Where UserSrNo=" & UserSrNo & " and MenuName='" & objToolStripItem.Name & "'"

Dim MyOdbcCmd As Odbc.OdbcCommand = New

Odbc.OdbcCommand(TempString, DsnConn)

If DsnConn.State = ConnectionState.Closed Then DsnConn.Open()

If IsDBNull(MyOdbcCmd.ExecuteScalar()) Or
MyOdbcCmd.ExecuteScalar() = "" Then

MenuYesNo = False

Else

MenuYesNo = True

End If

DsnConn.Close()

Catch ex As Exception

MessageBox.Show(Err.Description)

Exit Sub
End Try
 If MenuYesNo = True Then

For Each subMenuItem As ToolStripItem In

DirectCast(objToolStripItem, ToolStripMenuItem).DropDownItems

Try

Dim TempString As String = "Select SubMenuName from

MenuAuth Where UserSrNo=" & UserSrNo & " and MenuName='" &
objToolStripItem.Name & "' and SubMenuName='" & subMenuItem.Name & "'"

Dim MyOdbcCmd As Odbc.OdbcCommand = New

Odbc.OdbcCommand(TempString, DsnConn)
If DsnConn.State = ConnectionState.Closed Then
DsnConn.Open()

If IsDBNull(MyOdbcCmd.ExecuteScalar()) Or
MyOdbcCmd.ExecuteScalar() = "" Then

SubMenuYesNo = False

Else

SubMenuYesNo = True

End If
DsnConn.Close()

If SubMenuYesNo = True Then

subMenuItem.Visible = False

End If

Catch ex As Exception

MessageBox.Show(Err.Description)
 Exit Sub

End Try

Next

End If

Next

End If

Next

Catch ex As Exception

MessageBox.Show(Err.Description)

End Try

End Sub

Private Sub Timer1_Tick(sender As Object, e As EventArgs) Handles Timer1.Tick

StatusLabel4.Text = TimeOfDay

End Sub

#Region " MnuMgr_Click_Events "

Private Sub MnuMgr_1_Click(sender As Object, e As EventArgs)

Cursor = Cursors.WaitCursor

DayOpen.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMgr_2_Click(sender As Object, e As EventArgs)

Cursor = Cursors.WaitCursor
 DayClose.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMgr_4_Click(sender As Object, e As EventArgs) Handles

MnuMgr_4.Click

Cursor = Cursors.WaitCursor

If UserMaster.WindowState = FormWindowState.Minimized Then

UserMaster.WindowState = FormWindowState.Normal

YearEndProcess.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMgr_5_Click(sender As Object, e As EventArgs)

End Sub
Private Sub MnuMgr_6_Click(sender As Object, e As EventArgs) Handles
MnuMgr_6.Click

Cursor = Cursors.WaitCursor

If UserMaster.WindowState = FormWindowState.Minimized Then

UserMaster.WindowState = FormWindowState.Normal

UserMaster.ShowDialog()

Cursor = Cursors.Default

End Sub

Private Sub MnuMgr_7_Click(sender As Object, e As EventArgs) Handles

MnuMgr_7.Click
 Cursor = Cursors.WaitCursor

If DirectorMaster.WindowState = FormWindowState.Minimized Then

DirectorMaster.WindowState = FormWindowState.Normal

DirectorMaster.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMgr_8_Click(sender As Object, e As EventArgs) Handles

MnuMgr_8.Click

Cursor = Cursors.WaitCursor

Dim iResult As Integer = 0

Dim Path As String = ""

Dim directory As String = My.Application.Info.DirectoryPath

Path = "" & directory & "\DataBkp\Sangambkp_" & Today.Day & "" &
Today.Month & "" & Today.Year & "" & Hour(DateTime.Now) & "" &
Minute(DateTime.Now) & "_" & Second(DateTime.Now) & ".bak"

Try

Dim Qstring As String = "Backup Database SamratSoft to disk=?"

MyCmd = New Odbc.OdbcCommand(Qstring, DsnConn)

MyCmd.CommandText = Qstring

MyCmd.Parameters.Add("@disk", Odbc.OdbcType.NVarChar).Value =
Path.ToString()

MyCmd.Connection.Open()

iResult = MyCmd.ExecuteNonQuery()
 If iResult < 0 Then

MsgBox("वँकप घेत7ा आहे ...!!!")

End If

Catch ex As Exception

'MsgBox("Backup Error !!")

MessageBox.Show(ex.Message.ToString())

Finally

End Try

DsnConn.Close()

Cursor = Cursors.Default

End Sub

#End Region

#Region " MnuMaster_Click_Events "

Private Sub MnuMaster_1_Click(sender As Object, e As EventArgs) Handles

MnuMaster_1.Click

Cursor = Cursors.WaitCursor

If CompanyMaster.WindowState = FormWindowState.Minimized Then

CompanyMaster.WindowState = FormWindowState.Normal

CompanyMaster.ShowDialog()

Cursor = Cursors.Default
End Sub
 Private Sub MnuMaster_2_Click(sender As Object, e As EventArgs) Handles
MnuMaster_2.Click

Cursor = Cursors.WaitCursor

If GeneralParameters.WindowState = FormWindowState.Minimized Then

GeneralParameters.WindowState = FormWindowState.Normal

GeneralParameters.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMaster_4_Click(sender As Object, e As EventArgs) Handles

MnuMaster_4.Click

Cursor = Cursors.WaitCursor
If MainGLMaster.WindowState = FormWindowState.Minimized Then
MainGLMaster.WindowState = FormWindowState.Normal

MainGLMaster.ShowDialog()
Cursor = Cursors.Default

End Sub

Private Sub MnuMaster_5_Click(sender As Object, e As EventArgs) Handles

MnuMaster_5.Click

Cursor = Cursors.WaitCursor

If GLCodeMaster.WindowState = FormWindowState.Minimized Then

GLCodeMaster.WindowState = FormWindowState.Normal

GLCodeMaster.ShowDialog()

Cursor = Cursors.Default

End Sub

Private Sub MnuMaster_6_Click(sender As Object, e As EventArgs) Handles

MnuMaster_6.Click
 Cursor = Cursors.WaitCursor

If CustomerList.WindowState = FormWindowState.Minimized Then

CustomerList.WindowState = FormWindowState.Normal

CustomerList.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMaster_7_Click(sender As Object, e As EventArgs) Handles

MnuMaster_7.Click

Cursor = Cursors.WaitCursor

If OpeningBalEntry.WindowState = FormWindowState.Minimized Then

OpeningBalEntry.WindowState = FormWindowState.Normal
OpeningBalEntry.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMaster_8_Click(sender As Object, e As EventArgs) Handles

MnuMaster_8.Click

Cursor = Cursors.WaitCursor

ItemGroupMaster.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMaster_9_Click(sender As Object, e As EventArgs) Handles

MnuMaster_9.Click
Cursor = Cursors.WaitCursor

ItemMaster.ShowDialog()

Cursor = Cursors.Default
 End Sub

Private Sub MnuMaster_10_Click(sender As Object, e As EventArgs) Handles

MnuMaster_10.Click

Cursor = Cursors.WaitCursor

ItemRateMaster.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMaster_11_Click(sender As Object, e As EventArgs) Handles

MnuMaster_11.Click

Cursor = Cursors.WaitCursor

MilkRateMaster.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMaster_12_Click(sender As Object, e As EventArgs) Handles

MnuMaster_12.Click

Cursor = Cursors.WaitCursor

CityMaster.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuMaster_13_Click(sender As Object, e As EventArgs) Handles

MnuMaster_13.Click

Cursor = Cursors.WaitCursor

BankMaster.ShowDialog()

Cursor = Cursors.Default
 End Sub

#End Region

Private Sub MnuHelp_1_Click(sender As Object, e As EventArgs) Handles

MnuHelp_1.Click
Cursor = Cursors.WaitCursor
If DateMaster.WindowState = FormWindowState.Minimized Then
DateMaster.WindowState = FormWindowState.Normal

DateMaster.ShowDialog()

Cursor = Cursors.Default

End Sub

Private Sub MnuHelp_2_Click(sender As Object, e As EventArgs) Handles

MnuHelp_2.Click

End Sub

Private Sub MnuHelp_3_Click(sender As Object, e As EventArgs) Handles

MnuHelp_3.Click

Cursor = Cursors.WaitCursor

PassWordChange.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuHelp_4_Click(sender As Object, e As EventArgs) Handles

MnuHelp_4.Click
Cursor = Cursors.WaitCursor

If FindMember.WindowState = FormWindowState.Minimized Then

FindMember.WindowState = FormWindowState.Normal
 FindMember.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuExit_Click(sender As Object, e As EventArgs) Handles

MnuExit.Click

Dispose()

Application.Exit()
End Sub

Private Sub MnuDStock_1_Click(sender As Object, e As EventArgs) Handles

MnuDStock_1.Click

Cursor = Cursors.WaitCursor

If DsTrnMaster.WindowState = FormWindowState.Minimized Then

DsTrnMaster.WindowState = FormWindowState.Normal

DsTrnMaster.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuDStock_2_Click(sender As Object, e As EventArgs) Handles

MnuDStock_2.Click

Cursor = Cursors.WaitCursor

If DsItemMaster.WindowState = FormWindowState.Minimized Then

DsItemMaster.WindowState = FormWindowState.Normal

DsItemMaster.ShowDialog()
Cursor = Cursors.Default

End Sub
#Region " All_Reports_Menu"

Private Sub MnuRpt_1_Click(sender As Object, e As EventArgs) Handles

MnuRpt_1.Click

Cursor = Cursors.WaitCursor

If RptMasterReport.WindowState = FormWindowState.Minimized Then

RptMasterReport.WindowState = FormWindowState.Normal

RptMasterReport.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuRpt_2_Click(sender As Object, e As EventArgs) Handles

MnuRpt_2.Click

Cursor = Cursors.WaitCursor

If RptCustReport.WindowState = FormWindowState.Minimized Then

RptCustReport.WindowState = FormWindowState.Normal
RptCustReport.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuRpt_3_Click(sender As Object, e As EventArgs) Handles

MnuRpt_3.Click

Cursor = Cursors.WaitCursor

If RptDailyReport.WindowState = FormWindowState.Minimized Then

RptDailyReport.WindowState = FormWindowState.Normal
RptDailyReport.ShowDialog()

Cursor = Cursors.Default
End Sub
 Private Sub MnuRpt_4_Click(sender As Object, e As EventArgs) Handles
MnuRpt_4.Click

Cursor = Cursors.WaitCursor

If RptMonthlyReport.WindowState = FormWindowState.Minimized Then

RptMonthlyReport.WindowState = FormWindowState.Normal

RptMonthlyReport.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuRpt_5_Click(sender As Object, e As EventArgs)

Cursor = Cursors.WaitCursor

If RptCustReport.WindowState = FormWindowState.Minimized Then

RptCustReport.WindowState = FormWindowState.Normal

RptCustReport.ShowDialog()

Cursor = Cursors.Default

End Sub

Private Sub MnuRpt_6_Click(sender As Object, e As EventArgs) Handles

MnuRpt_6.Click

Cursor = Cursors.WaitCursor

If RptCustReport.WindowState = FormWindowState.Minimized Then

RptCustReport.WindowState = FormWindowState.Normal

RptCustReport.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuRpt_7_Click(sender As Object, e As EventArgs) Handles

MnuRpt_7.Click
 Cursor = Cursors.WaitCursor

If ShareReport.WindowState = FormWindowState.Minimized Then

ShareReport.WindowState = FormWindowState.Normal

ShareReport.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuRpt_8_Click(sender As Object, e As EventArgs) Handles

MnuRpt_8.Click

Cursor = Cursors.WaitCursor

If RptCustReport.WindowState = FormWindowState.Minimized Then

RptCustReport.WindowState = FormWindowState.Normal
RptCustReport.ShowDialog()

Cursor = Cursors.Default

End Sub

#End Region

#Region " All_Counter_Menu"

Private Sub MnuCounter_1_Click(sender As Object, e As EventArgs) Handles

MnuCounter_1.Click

Cursor = Cursors.WaitCursor

CashEntry.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuCounter_2_Click(sender As Object, e As EventArgs) Handles

MnuCounter_2.Click
 Cursor = Cursors.WaitCursor

TransferEntry.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuCounter_12_Click(sender As Object, e As EventArgs) Handles

MnuCounter_12.Click

Cursor = Cursors.WaitCursor

If DayBook.WindowState = FormWindowState.Minimized Then

DayBook.WindowState = FormWindowState.Normal

DayBook.ShowDialog()

Cursor = Cursors.Default

End Sub

Private Sub MnuCounter_9_Click(sender As Object, e As EventArgs) Handles

MnuCounter_9.Click

Cursor = Cursors.WaitCursor

Cursor = Cursors.Default

End Sub

#End Region

#Region " All_Share_Menu"

Private Sub MnuShare_0_Click(sender As Object, e As EventArgs) Handles

MnuShare_0.Click
 Cursor = Cursors.WaitCursor

If ShareMasterList.WindowState = FormWindowState.Minimized Then

ShareMasterList.WindowState = FormWindowState.Normal

ShareMasterList.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuShare_1_Click(sender As Object, e As EventArgs) Handles

MnuShare_1.Click

Cursor = Cursors.WaitCursor

If ShareTransactions.WindowState = FormWindowState.Minimized Then

ShareTransactions.WindowState = FormWindowState.Normal
ShareTransactions.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuShare_2_Click(sender As Object, e As EventArgs) Handles

MnuShare_2.Click

Cursor = Cursors.WaitCursor

If SharesParameters.WindowState = FormWindowState.Minimized Then

SharesParameters.WindowState = FormWindowState.Normal

SharesParameters.ShowDialog()

Cursor = Cursors.Default

End Sub

Private Sub MnuShare_3_Click(sender As Object, e As EventArgs) Handles

MnuShare_3.Click

Cursor = Cursors.WaitCursor
 If ShareValueMaster.WindowState = FormWindowState.Minimized Then
ShareValueMaster.WindowState = FormWindowState.Normal

ShareValueMaster.ShowDialog()

Cursor = Cursors.Default

End Sub

Private Sub MnuShare_5_Click(sender As Object, e As EventArgs) Handles

MnuShare_5.Click

Cursor = Cursors.WaitCursor
If ShareDivIntMaster.WindowState = FormWindowState.Minimized Then
ShareDivIntMaster.WindowState = FormWindowState.Normal

ShareDivIntMaster.ShowDialog()

Cursor = Cursors.Default

End Sub

Private Sub MnuShare_6_Click(sender As Object, e As EventArgs) Handles

MnuShare_6.Click

Cursor = Cursors.WaitCursor

If ShareDividendCal.WindowState = FormWindowState.Minimized Then

ShareDividendCal.WindowState = FormWindowState.Normal

ShareDividendCal.ShowDialog()

Cursor = Cursors.Default

End Sub

Private Sub MnuShare_8_Click(sender As Object, e As EventArgs) Handles

MnuShare_8.Click

Cursor = Cursors.WaitCursor

If ShareReport.WindowState = FormWindowState.Minimized Then

ShareReport.WindowState = FormWindowState.Normal
 ShareReport.ShowDialog()

Cursor = Cursors.Default

End Sub

#End Region

#Region " All_Investment_Menu"

Private Sub MnuInvest_1_Click(sender As Object, e As EventArgs) Handles

MnuInvest_1.Click

Cursor = Cursors.WaitCursor

InvestmentMasterList.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuInvest_3_Click(sender As Object, e As EventArgs) Handles

MnuInvest_3.Click
Cursor = Cursors.WaitCursor

InvestmentMaster.ShowDialog()

Cursor = Cursors.Default
End Sub

#End Region

#Region " All_Inventory_Menu"

Private Sub MnuInv_1_Click(sender As Object, e As EventArgs) Handles

MnuInv_1.Click
 Cursor = Cursors.WaitCursor

DailyMilkCollection.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuInv_2_Click(sender As Object, e As EventArgs) Handles

MnuInv_2.Click

Cursor = Cursors.WaitCursor

DailyMilkCollMachine.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuInv_3_Click(sender As Object, e As EventArgs) Handles

MnuInv_3.Click

Cursor = Cursors.WaitCursor

BillMaster.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuInv_4_Click(sender As Object, e As EventArgs) Handles

MnuInv_4.Click

Cursor = Cursors.WaitCursor

BillMasterList.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuInv_5_Click(sender As Object, e As EventArgs) Handles

MnuInv_5.Click
 Cursor = Cursors.WaitCursor

'AnamatDividendCal.ShowDialog()

Cursor = Cursors.Default
End Sub

Private Sub MnuInv_7_Click(sender As Object, e As EventArgs) Handles

MnuInv_7.Click

End Sub

Private Sub MnuInv_10_Click(sender As Object, e As EventArgs) Handles

MnuInv_10.Click

Cursor = Cursors.WaitCursor

GLSetting.ShowDialog()

Cursor = Cursors.Default
End Sub

#End Region

End Class
 Testing

CHAPTER 5: Testing
1.1 Testing Strategy.
1.2 Unit Test Plan.
1.3 Module Testing
1.4 Integration Testing.
1.5 Security Testing.
1.6 Regression Testing.
1.7 Acceptance Testing.
1.8 Beta Testing.
1.9 Tools.
5.1 Test Strategy:

Testing Software testing is a process used to identify the correctness, completeness,

and Quality of developed software. Testing is process of exercising and evaluating
a system component by manual or automated means to verify that it satisfies the
specified requirement. Testing is concerned with errors, faults, failures, and
incidents. Software Testing is a method to check whether the actual software product
matches expected requirements and to ensure that software product is Defect free.
It involves execution of software/system components using manual or automated
tools to evaluate one or more properties of interest. The purpose of software testing
is to identify errors, gaps, or missing requirements in contrast to actual requirements.

Why Software Testing is Important?

Software Testing is Important because if there are any bugs or errors in the
software, it can be identified early and can be solved before delivery of the software
product. Properly tested software product ensures reliability, security, and high
performance which further results in time saving, cost effectiveness and customer
satisfaction.

5.1.Types of Testing
1.White box testing:
White box testing is a security testing method that can be used to validate whether
code implemented security functionality and to uncover exploitable vulnerabilities.
White Box Testing is software testing technique in which internal structure, design
and coding of software are tested to verify flow of input-output and to improve
design, usability, and security. In white box testing, code is visible to testers so it is
also called Clear box testing, Open box testing, Transparent box testing, Code-based
testing, and Glass box testing.
2. Black box testing:
Black box testing is based on the software’s specification or requirement without
reference to its internal Working. Gray box testing combines white box techniques
vulnerable areas and black box testing is then used to develop working attacks
against these areas.
Black Box Testing is a software testing method in which the functionalities of
software applications are tested without having knowledge of internal code
structure, implementation details and internal paths. Black Box Testing mainly
focuses on input and output of software applications and it is entirely based on
software requirements and specifications. It is also known as behavioral Testing.

3. Unit testing:
Unit testing is a method by which individual units of source code sets of one or
more computer program modules together with associated control data, usage
procedures, and operating procedures are tested to determine if they are it for use.
Unit testing is defined as a type of software testing where individual components
of a software are tested. Unit testing of the software product is carried out during
the development of an application. An individual component may be either an
individual function or a procedure. Unit testing is typically performed by the
developer. In SDLC or V Model, Unit testing is the first level of testing done before
integration testing. Unit testing is such a type of testing technique that is usually
performed by developers. Although due to the reluctance of developers to test,
quality assurance engineers also do unit testing.

4. Integration testing:
Testing of integrated modules to verify combined functionality after integration.
Modules are typically code modules individual application client and server
application on a network. This type of testing is especially relevant to client/server
and distributed system.
Integration testing is the process of testing the interface between two software units
or modules. It focuses on determining the correctness of the interface. The purpose
of integration testing is to expose faults in the interaction between integrated units.
Once all the modules have been unit tested, integration testing is performed.

5. Incremental integration Testing:

Bottom-up approach for testing that is continuum testing of an application as new
functionality is added. Application functionality and modules should be
independent enough to test separately done by programmers or by testers.
How to Implement Testing
1. Requirement analysis:
Testing should begin in the requirements phase of the software development of life
cycle.
2. Test planning:
Test strategy, test plan, test bed creation.
3. Test development:
Test procedure, scenarios, test cases, test script to use in testing software.
4. Test execution:
Testers execute the software’s based on plans and test report any airs found to the
development team.
5. Test reporting:
Once testing is completed testers generate metrics and make final report on their
test efforts and whether the software tested is ready for release.
5.2 Test Plan
5.3 Acceptance Test Plan
5.4 TEST CASE RESULT

1. Test case for login page:

Description Steps Test Data Expected Actual Stat us

Test Result Result Pass/
case Id fail

Test case Login with valid 1.Enter Email Email=sai

01 data 2.Enter @ User
Password gmail.com Should As pass
3.Login password= login into expected,
sai Applicatio n
Test case Login with 1.Enter Userid Email= User
02 invalid data 2.Enter sai11@gm Should Not
Password ail.com login into As pass
3.Login password= Applicatio n expected
sai@12
 2. Test case For add Customer :-

Test case Description Steps Test Data Expected Actual Status

Id Result Result Pass/f
ail
Test case Customer Id 1.Enter id Id= 001 Department Department
01 2.Enter Name Name = HR Available added
pass
3.Enter Location Location=1st successfully
floar.

Test case Customer Name 1.Enter id Id= 002 Department Alert msg:
02 2.Enter Name Name = should Not
Pass
3.Enter Location Developer register
Location=2nd
floar.

Test case Blank field 1.Enter id Id= 001 Alert Please fill
03 2.Enter Name Name = message all the
Pass
3.Enter Location Finance fields
Location=
3. Test case For Admin table :-

Test Description Steps Test Data Expected Actual Stat

case Result Result us
Id Pass
/fail
Test User Name 1.Enter Name Name =sai
case 2.Enter Phone Phone= Display Success
98787656 Contact fully Pass
01 76 Submit
ted

Test Enter Valid 1.Enter Name Name=sai Alert

case Email 2.EnterEmail Email= message As
02 3.Enter Phone [email protected] expected Pass
4.Submit Phone=98787656
76
Enter
Text=Submit
Test Blank Contact 1.Enter Name Name= Alert Please
case Field 2.Enter Phone Phone= message fill all Pass
03 3.Enter Email Enter the
4.Submit Email= fields
 Limitations

CHAPTER 6: Limitations of Proposed System

• The high cost of software development and deployment.

• Complex design in terms of User Interface and User Experience (UI/UX Design)

• Fear of data security breach.

• Difficulty in migrating from manual processes, because both staff and patients are
used to the manual processes and so are unable to speedily cope with the new
system.

• Lack of IT-friendly medical personnel is also presenting several challenges.

• A Huge influx of patients visiting government hospitals makes the process of

migrating to automated processes highly difficult.
 Proposed Enhancement

CHAPTER 7: Proposed Enhancement/ Future Scope

➢ Advanced Genomics:

Genetic Engineering: Use CRISPR and other gene-editing technologies to improve herd
genetics for disease resistance and higher productivity.

Selective Breeding Programs: Enhance breeding programs using advanced genomic data
to select the best traits.

➢ Enhanced Health Monitoring:

Wearable Technology: Equip cows with wearable devices to continuously monitor vital
signs and detect health issues early.

Telemedicine: Implement telemedicine services for remote veterinary consultations and

diagnoses

➢ Enhanced Consumer Engagement:

Direct-to-Consumer Platforms: Develop platforms that allow consumers to buy directly

from farmers, ensuring fair prices and better quality control.
Educational Initiatives: Create educational programs and campaigns to inform
consumers about the benefits of sustainable dairy farming.
 Conclusion

1. Self-Analysis of Project Viabilities

This project is built keeping in mind that it is to be used by only one user that is
the admin. It is built for use in small scale organization where the number of workers is
limited. According to the requested requirement the admin can add, manipulate, update,
and delete all worker data in his dairy. The admin can also add predefined pay grades for
the workers. The required records can be easily viewed by the admin anytime time he wants
in an instant. Numerous validations implemented would enable the admin to enter accurate
data. The main objective of this framework is to save time, make the system cost effective
and management records efficiently.

2. Problem Encountered and Possible Solutions Hardware Limitations

The only limitation posed is when the disk space is exhausted. And it can be solved by
extending the disk space.

3. Summary of Project work

In whole procedure to prepare project, we first gather the requirement of the project and
decide the time schedule. After planning we design the documentation of project. After
the design we generate the code of system. In design the code we do the error estimation
and effort estimation. If error is occurred then solve it. Finally, when code is designed then
test the project and decide the cost of project.
 Bibliography

For VB.Net

➢ https://www.tutorialspoint.com/vb.net/vb.net_web_programming.htm
➢ https://www.javatpoint.com/vb-net
➢ Learning Visual Basic. NET
➢ Visual Basic .NET: The Complete Reference

For SQL
➢ https://www.w3schools.com/sql/
➢ Practical SQL: A Beginner's Guide to Storytelling with Data
➢ Learning SQL Alan Beaulieu