dairy management system - ganpat universitygnu.inflibnet.ac.in/bitstream/123456789/2616/5/dairy...

Dairy Management System

Acharya Motibhai Patel Institute of Computer Studies Ganpat University, Kherva

Group –B23

Patel Bhavik

Patel Anil

Prof. Rina K Patel

AMPICS LIBRARY

of 57

Project Title:- Dairy Management System

Objective:- Create a window application for sales and

purchase

Front End Tool:- Microsoft Visual studio 2010 (VB.NET)

Back End Tool:- Microsoft Access (2007)

Application:- Window application

Operating

System:- windows 7

Develop For:- Shri Gozariya Dhudh Utpadak Sahkari Mandli

Limited

Develop At:- Acharya Motibhai Patel Institute of Computer

Studies

Team Member:- Patel Bhavik(11032211111)

Patel Anil(11032211104)

Project Guide:- Prof. Rina k Patel

Group No:- B23

AMPICS LIBRARY

of 57

Name of organization

Shri Gozariya Dhudh Utpadak Sahkari

Mandli Limited .

Address Main Bazar, Gozariya – 382825

Established

30 march 1964

Phone no

02762-264326

Manager

Patel Jagdishbhai

Patel Jitubhai

Employee 10

AMPICS LIBRARY

of 57

Current System is Totally Manual

In Shri Gozariya Dhudh Utpadak Sahkari Mandli Limited Customers Supply to milk they Supplies two times per day

From register they cannot find out the proper information and data immediately. This work become very difficult.

Gozariya dairy is purchase and supply milk.

Existing System uses registeres to maintain the records of sales ,purchase , supplay milk and payment.

AMPICS LIBRARY

of 57

AS The Existing System is manual.Data is Stored Manually

To keep track of each document, record serching is very fast

The new system is required to reduce the manual work and time

Also The new System will also keep records of milk sales and their payments.

AMPICS LIBRARY

of 57

Processor :- Pentium & above

RAM :- 1 GB

HDD :- 256 GB

Operating System :- Windows 7

Framework :- Microsoft Visual Studio 2010 (VB.NET)

Crystal Report :- 9.0

Back end tools :- M S Access 2007

HARDWARE REQUIREMENT

SOFTWARE REQUIREMENT

(Recommended)

AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

ADMIN

SALE

MILK

BILL NO C DATE TOTAL MILLK

SUP.CITY

SUPP.ADD SUPP.NO

SUPP.NAME

C DATE

ACC_NO BILL NO

NAME

SUBMIT

MILK

MANAGE

LOCALCUSTOMER

SUPPLAYER

DAIRY

1

1 1

AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

FIELD NAME TYPE SIZE CONSTRAINTS DESCRIPTION

USERID NUMBER 15 PRIMERY KEY USERID

USERNAME TEXT 15 NOY NULL

PASSWORD VARCHAR 10 NOT NULL PASSWORD

LOGIN_MST

AMPICS LIBRARY

of 57


SUPPLAYER_ID NUMBER 15 NOT NULL SUPPLAYER_ID

SUPPLAYER

NAME

TEXT 30 NOT NULL SUPPLAYER

NAME

CODE NO NUMBER 10 PRIMERY KEY CODE NO

ADDRES TEXT 50 NOT NULL ADDRES

CITY TEXT 15 NOT NULL CITY

STATE TEXT 15 NOT NULL STATE

MOBILE NO NUMBER 10 NOT NULL MOBILE NO

PIN CODE NUMBER 6 NOT NULL PIN CODE

TYPE TEXT 10 NOT NULL TYPE

SUPPLAYER_DETAIL

AMPICS LIBRARY

of 57


CODE NO NUMBER 10 FOREIGN KEY CODE NO

NAME TEXT 15 NOTNULL NAME

DATE DATE DATE

SHIFT TEXT 10 NOT NULL SHIFT

LITER NUMBER 3,1 NOT NULL LITER

FAT% NUMBER 2,1 NOT NULL FAT%

RATE NUMBER 3,2 NOT NULL RATE

AMOUNT NUMBER 4,2 NOT NULL AMOUNT

TYPE TEXT 10 NOT NULL TYPE

PURCHASE MILK_DETAIL

AMPICS LIBRARY

of 57


BILL NO NUMBER 10 PRIMARY KEY L_S_ ID

DATE DATE NOT NULL DATE

SHIFT TEXT 10 NOT NULL SHIFT




LOCAL SALE INFO

AMPICS LIBRARY

of 57


DAIRY_ID NUMBER 5 NOT NULL DAIRY_ID

DAIRY NAME TEXT 25 NOT NULL DAIRY NAME

DATE DATE NOT NULL DATE




DAIRY SUPPLY INFO

AMPICS LIBRARY

of 57

Step 1. Start

Step 2. Login

If admin login username and password is correct then go to step 3.

Else then go to step 2.

Step 3. Add,Update supplier information.

Step 4. Purchase a milk by supplier.

Step 5. Selling

In daily routing every next day morning we were on the milk and

supply to the here dairy or if the local customer or come then some

milk to them in this process.

Step 6. Stop

Process Algo AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

login AMPICS LIBRARY

of 57

Login successfully AMPICS LIBRARY

of 57

Home page AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

Supplier detail AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

Purchase milk detail AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

Dairy supplay detail AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

Local sale AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

Report AMPICS LIBRARY

of 57

SUPPLIER DETAIL REPORT AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

LOCAL SALE DETAIL REPORT AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

PURCHASE MILK DETAIL REPORT AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

DAIRY SUPPLAY DETAIL REPORT AMPICS LIBRARY

of 57

Extra AMPICS LIBRARY

of 57

calculator AMPICS LIBRARY

of 57

About us AMPICS LIBRARY

of 57

I have performed following steps to test the application. While is

suitable for the testing of application according to size and complexity.

(1) Objective Test I have first Written objectives that can understand system. In

addition to documenting objectives, I have prioritized objectives.

(2) Test Environment Set up a test environment that is separate from your

development and production environment. This includes a separate web server, database server and client application. By this testing we can check ability to utilize existing computers to setup separate test environment.

(3) Unit testing Unit testing is the smallest unit of software design_the

software component or module such as. The .net code complies and run process etc.

AMPICS LIBRARY

of 57

(4) Integration testing After all the modules of our system were integrated we go

for integrated testing. And assure the flow form one module to

other is going on smoothly or not. (5) System testing Software and hardware are integrated and a full range of

System test is conducted in and attempt to uncover errors at the

software/hardware interface.

1. A good test case is one that has a high probability of finding

the undiscovered error.

2. A successful test is one that uncovers all the undiscovered

errors.

AMPICS LIBRARY

of 57

After the system is implemented and conversion is completed,

a review of system is usually conducted by users and analyst. This is

called post implementation review.

Supplier supplies milk daily and after 15 days payment are

made according. Supplier wise total payment should be calculate.

Mehsana dairy after receiving milk for 15 days total

amount for control dairy should be calculate.

whether the system can be considered successful.

AMPICS LIBRARY

of 57

I think that not a single project is ever considered as complete

forever because our mind is always thinking new and our

necessities also are growing day by day. I always want something

more than what I have . Our application also, if you see at the first

glance than you find it to be complete but I want to make it still

mature and fully automatic.

1. Bill will be generated fortnightly for dairy.

2. Supplier wise bill will be generated after 15 days by giving

alarm.

3. Cow milk and Buffalo milk separate repot and bill will be

generated.

AMPICS LIBRARY

of 57

During the development of our system, we have taken the

reference from Books and Journals, which we would like to mention

in this section.

These books acted as our tutors during the system

development.

1. System Analysis and Design

_ _ C J Date

2. Microsoft vb.net step by step

_ _ Michel Halvorsan

(PHIPublication)

Besides these we were referring dairy system

reference book from the library.

AMPICS LIBRARY

of 57

AMPICS LIBRARY

of 57

dairy management system - ganpat universitygnu.inflibnet.ac.in/bitstream/123456789/2616/5/dairy...

Documents