Adobe Marketo Engage Deep Dives: Using Webhooks to Transfer Data
Fruit Product Management System
1. PROJECTPROJECT REPORTREPORT
ONON
Submitted By:
Saiyad Sanobar S.
Reg.no:06-0164-2014
Semester:-4th
Guided By:
Dr.H.k.Patel
College of Agricultural Information Technology
Anand Agricultural University
Fruit product and Quality Management System Page 1
2. Anand- 388110
This is to certify that Saiyad Sanobar of 4th
semester have
satisfactorily completed the Project work titled Fruit Product
and Quality Management System as an Project requirement
of the Bachelor of Technology in Agricultural Information
Technology ,of the Anand Agricultural University , Anand.
Major Guide:
Dr. R.S.Parmar
(Associated
Professor)
Signature:
Date:
Place:
Minor Guide:
Dr. H.K.Patel
(Assistant
Professor)
Signature:
Fruit product and Quality Management System Page 2
3. Date:
Place:
“The favors that a mother does for child are indeed beyond
Acknowledgement”. Many people have contributed to my achievements in
this project. I am taking opportunity to thank each of them.
I sincerely thank all the people who co-operate and encourage us
throughout the year and make our project work successful.
I also thankful our project guide for giving us guidance and advice at every
step when we needed. The opportunity to study and work here added a lot
to our knowledge, experience, confidence, skills and real field awareness.
I extend my project guide professor Dr.R.S.Parmar and Dr.H.K.Patel who
has constantly remained helpful in suggesting directions and providing us
guidance throughout this project.
It is good fortune that we had support and well wishes of many. We thank
all those, whose means have not appeared here but whose contributions
have not gone unnoticed.
Fruit product and Quality Management System Page 3
4. - Saiyad
Sanobar
In Forth semester of CAIT, I developing website is called “FRUIT
PRODUCT AND QUALITY MANAGEMENT SYSTEM” for started with
the introduction of the Fruit processing and definition of the project. I
have also mentioned about the front end and back end, which I have
used in my application. Then I have explained the information system
and development strategy, which I have used for our system. Next I
have provided the process of the development.
Any solution is the result of integration of the theory as well as
practice. Hence this report too, is mix of theory and works done. This
would enable the understanding of the methodologies adopted for
the implementation of the application system more rounded.
One of the important uses of project report is to provide information
so that anybody can understand the whole system at a glimpse. It is
thus very important for me to know how to make project report so
that is contains all important aspects of the real system.
Fruit product and Quality Management System Page 4
5. Next I have displayed the screen layouts and reports, which make my
reports more effective. At the ending part, I have stated the coding of
my actual application. At the last I have explained the
implementation and testing of my system.
Contents
..........................................................................................................................2
Contents....................................................................................................5
1.Introduction:...................................................................................................6
1.2Objective:...............................................................................................................6
1.2Scope:....................................................................................................................6
2.Hardware and Software Requirement:............................................................7
2.1.Software Configuration:........................................................................................7
2.2.Hardware Configuration:.......................................................................................7
2.3.Technology Review:..............................................................................................7
3.Requirement of System:..................................................................................9
4.Module list:...................................................................................................10
5.Data Flow Diagram:......................................................................................11
5.1Context level diagram:.........................................................................................12
5.2Level-1 Diagram:..................................................................................................13
6.Entity Relationship Diagram:........................................................................14
7.Data Dictionary:...........................................................................................17
7.1Admin:.................................................................................................................17
7.2Employee:............................................................................................................18
7.3Salary...................................................................................................................18
7.4Attendance:.........................................................................................................18
7.5Supplier:...............................................................................................................19
7.6Payment detail:....................................................................................................19
7.7Stock:...................................................................................................................19
7.8Production_detail:................................................................................................20
7.9Product:...............................................................................................................20
7.10Category:............................................................................................................21
Fruit product and Quality Management System Page 5
6. 7.11Customer:...........................................................................................................21
7.12Order:.................................................................................................................21
8.Project Planning and Scheduling:..................................................................22
9.Screen Shot:..................................................................................................24
..............................................................................................................................................26
10.Testing:.......................................................................................................32
11.Conclusion:.................................................................................................33
12.Bibliography:..............................................................................................33
1. Introduction:
This system is used for online management of fruit product. Through this system
admin not only maintain records of products but also maintaining raw materials’
record, suppliers’ and their payment records, customers’ and their order record,
employee’ and their salary record and generates daily & monthly report.
This system automatically sending message to admin on decreasing of product
and stock quantity and manage the whole process of order and processing. The
order confirmation message sending to the customer, this process will be
managed properly by this system.
This system also contains some calculator like moisture content in product,
weights of ingredients which helpful in fruit processing and quality control.
1.2 Objective:
• To allow the administrator of any fruit processing unit to edit and
find out the details of employee, supplier, products, customer,
purchase details of raw material, product processing details, sales
details and allows the customer to send order.
• It’ll also facilitate keeping all the records of employee, supplier, and
customer such as their id, name, mailing address, phone number
etc. So all the information about of them will be available in a few
seconds.
1.2 Scope:
• The scope of ‘Fruit Product and Quality management system’ is to
improve sales. The system can easily track of all records of
employee, supplier, stock, product, customer, order and send
threshold message when stock and product quantity goes low.
• The system can also generate of requested parameter on the base
of sale, production and purchase detail.
Fruit product and Quality Management System Page 6
7. 2. Hardware and Software Requirement:
2.1. Software Configuration:
Front End : Visual Studio 2015(ASP.NET)
Back End : SQL Server management studio
Technology : .Net Framework 4.0
Programming Language : C#
Operating System : Windows 10
2.2. Hardware Configuration:
Processor : Pentium 2.42 GHz
RAM : 2 GB
2.3. Technology Review:
About the ASP.Net 2005:
ASP.NET is more than the next version of Active Server Pages
(ASP); it is a unified Web development platform that provides the
services necessary for developers to build enterprise-class Web
applications. While ASP.NET is largely syntax compatible with ASP,
it also provides a new programming model and infrastructure for
more secure, scalable, and stable applications. You can feel free to
augment your existing ASP applications by incrementally adding
ASP.NET functionality to them.
ASP.NET is a compiled, NET-based environment; you can author
applications in any .NET compatible language, including Visual
Basic .NET, C#, and JScript .NET. Additionally, the entire .NET
Framework is available to any ASP.NET application. Developers can
easily access the benefits of these technologies, which include the
managed common language runtime environment, type safety,
inheritance, and so on.
Developers can use Web Forms or XML Web services when
creating an ASP.NET application, or combine these in any way they
see fit. Each is supported by the same infrastructure that allows
Fruit product and Quality Management System Page 7
8. you to use authentication schemes, cache frequently used data, or
customize your application's configuration, to name only a few
possibilities.
Web Forms allow you to build powerful forms-based Web pages.
When building these pages, you can use ASP.NET server controls
to create common UI elements, and program them for common
tasks. These controls allow you to rapidly build a Web Form out of
reusable built-in or custom components, simplifying the code of a
page.
Accessing databases from ASP.NET applications is an often-used
technique for displaying data to Web site visitors. ASP.NET makes
it easier than ever to access databases for this purpose. It also
allows you to manage the database from your code.
ASP.NET takes advantage of performance enhancements found in
the .NET Framework and common language runtime. Additionally,
it has been designed to offer significant performance
improvements over ASP and other Web development platforms.
All ASP.NET code is compiled, rather than interpreted, which
allows early binding, strong typing, and just-in-time (JIT)
compilation to native code, to name only a few of its benefits.
ASP.NET is also easily factorable, meaning that developers can
remove modules (a session module, for instance) that are not
relevant to the application they are developing. ASP.NET also
provides extensive caching services (both built-in services and
caching APIs). ASP.NET also ships with performance counters that
developers and system administrators can monitor to test new
applications and gather metrics on existing applications.
ASP.NET configuration settings are stored in XML-based files,
which are human readable and writable. Each of your applications
can have a distinct configuration file and you can extend the
configuration scheme to suit your requirements.
LocalDB:
It is a new version of SQL Server Express dedicated to developers to help
them avoid a full installation of other editions of SQL Server.
Benefits:
LocalDB doesn't create any database services; LocalDB processes are
started and stopped automatically when needed.
Fruit product and Quality Management System Page 8
9. LocalDB connections support AttachDbFileName property, which allows
developers to specify a database file location
Service packs of LocalDB can be used update a LocalDB installation or to
install a new LocalDB.
One LocalDB installation for all users on a computer.
It supports a silent installation
It works with ASP .NET
It supports XML,ADO .NET Sync Framework,LINQ,ODBC,OLEDB and
distributed transactions.
3. Requirement of System:
Customers can directly Order for fruit Product.
Customer, Employee, Supplier, Product, Production, Purchase data will
store in the database.
Allocation of product information will also store in the database.
Paper work is reducing.
Manager workload is reducing.
If the selected Product is available then the customer will order the
Product.
Fruit product and Quality Management System Page 9
10. 4. Module list:
There are two types of Users with their specific function in fruit product and
quality management system.
3.1 Admin Module:
After clicks on admin login link in home page admin will be directed to the
login page in which he will have to enter his username and password which
will help him in accessing the main content. Once he is authorized he will be
able to perform certain functions respective to particular fields those are-
a) Employee
b) Supplier
c) Productions
d) Sales
e) Report
3.1.1 Employee:
This panel will consist of four sub-panels that are-
i. Employee Detail
ii. Update Attendance
iii. Monthly Salary
Using these three panel admin can add new employee
information, count salary of every employee on the basis of working
day.
3.1.2 Supplier
This panel will consist of three sub-panels that are-
i. Supplier Detail
ii. Purchase Entry
iii. Stock Detail
Using these panels admin can add and view supplier details, add
purchase entry and check quantity of raw-materials.
3.1.3 Productions
This panel will consist of three sub-panels that are-
i. Product preparation details
ii. Product[add & view]
iii. Category
Using these panels admin can store details of production, add
new product and view the list of products.
3.1.4 Sales
This panel will consist of two sub-panels that are-
i. Order details
ii. Customer details
Fruit product and Quality Management System Page 10
11. Using these panel admin can see the new orders from the
customers, edit sales details and maintain data regarding all the orders
whether it is completed or are in pending.
3.1.5 Report
This panel will consist of two sub-panels that are-
i. Daily
ii. Monthly
Through this panel admin will be able to add all today’s process
data and he can also view it whenever needed by him.
3.2 Customer
In this system customer can place order after he registered. This page
consist five options.
a) Home
b) About Us
c) Products
d) Register
e) Contact Us
1.1 Home
This panel contains information regarding to what products are
made in processing unit and nutrient information of product.
1.2 About Us
This panel contains description about system and procedure to
order of product using this system by any customer.
1.3 Products
This section consist fruit wise pictures of products which being
produced in fruit processing unit.
1.4 Register
This panel allows customers to register themselves to place the
order.
1.5 Contact Us
This panel contains contact of fruit processing unit’s manager. If
customers face any problem, they can able to contact manager.
5. Data Flow Diagram:
Fruit product and Quality Management System Page 11
12. Data Flow Diagram (DFD) is a graphical representation of flow of data in
an information system. It is capable of depicting incoming data flow,
outgoing data flow, and stored data.
Symbole Description
Data Flow
Process
Entity
Data Store
5.1Context level diagram:
Highest abstraction level DFD is known as Level 0 DFD, which depicts the
entire information system as one diagram concealing all the underlying
details. context level DFDs are also known as Level 0 DFDs.
Fruit product and Quality Management System Page 12
13. 5.2Level-1 Diagram:
The Level 0 DFD is broken down into more specific, Level 1 DFD. Level 1 DFD
depicts basic modules in the system and flow of data among various modules.
Level 1 DFD also mentions basic processes and sources of information
Fruit product and Quality Management System Page 13
14. 6. Entity Relationship Diagram:
An entity relationship diagram is a specialized graphic that illustrates the
interrelationship between entities in a database.ER diagram often use
symbols to represent three different type of information. Boxes are
commonly used to represent entities. Diamonds are normally used to
represent relationship and ovals are used to represent attribute.
Fruit product and Quality Management System Page 14
15. The three main component of an ERD are:
Fruit product and Quality Management System Page 15
17. 7. Data Dictionary:
Data dictionary is the centralized collection of information about data. It
stores meaning and origin of data, its relationship with other data, data
format for usage, etc. Data dictionary has rigorous definitions of all names
in order to facilitate user and software designers.
Data dictionary is often referenced as meta-data (data about data)
repository. It is created along with DFD (Data Flow Diagram) model of
software program and is expected to be updated whenever DFD is
changed or updated.
Table-Index:
• Admin
• Employee
• Salary
• Product
• Category
• Supplier
• Stock
• Customer
• Order-detail
• Payement-Detail
• Production-Detail
7.1 Admin:
Field Name Data Type Constraint
Description
Username Varchar(20)
Username of
admin
Password Varchar(20)
Password of
admin
Email Varchar(50)
Email address of
admin
Fruit product and Quality Management System Page 17
18. 7.2 Employee:
Field Name Data Type Constraint Description
E_ID Integer(10) Primary key ID of employee
Name Varchar(50)
Name of
employee
Category Varchar(50)
Category of
employee
Address Varchar(50)
Address of
employee
Contact_No. Integer(10)
Contact number
of employee
Join_Date Date
Join date of
employee
7.3 Salary
Field Name Data Type Constraint Description
E_ID Integer(20) Foreign key
ID of employee
from employee
table
Month Integer(10)
Year Integer(10)
Working_Day Integer(10)
Salary Integer(10)
7.4 Attendance:
Field Name Data Type Constraint Description
E_ID Integer(20) Foreign key
ID of employee
from employee
table
Date Date
Stutas Integer(10)
Employee present
or not
Fruit product and Quality Management System Page 18
19. 7.5 Supplier:
Field Name Data Type Constraint Description
S_Id Integer(20) Primary key Id of supplier
Name Varchar(40)
Name of
supplier
contact_no Integer(10)
Supplier contact
number
Address Varchar(50) Supplier address
7.6 Payment detail:
Field Name Data Type Constraint Description
S_Id integer(20) Foreign key
Supplier Id from
supplier table
St_Id integer(20) Foreign key
Stock Id from
stock table
Quantity Integer(20)
Stock quantity
purchase from
supplier
Rate Integer(20)
Price of stock
per kilogram
Purchase_date Date
Date of
purchasing stock
total_amount Integer(20)
Total of amount
to pay
7.7 Stock:
Field Name Data Type Constraint Description
St_id integer(20) Primary key ID of each stock
Name Varchar(50 Name of stock
Available_quntity integer(20)
Available
quantity of stock
Threshold_value integer(20)
Threshold value
of stock quantity
Fruit product and Quality Management System Page 19
20. 7.8 Production_detail:
Field Name Data Type Constraint Description
Date Date
Date of
production
process
P_id integer(20) Foreign key
Product ID from
product table
P_qty integer(20)
Quantity of
product for
production
St_id integer(20) Foreign key
Id of stock from
stock table
st_qty integer(20)
Stock quantity
use during
production
7.9 Product:
Field Name Data Type Constraint Description
P_id Varchar Primary key Id of product
Name Varchar Product name
Number_of_category Integer
Numbers of
category for
product
Fruit product and Quality Management System Page 20
21. 7.10 Category:
Field name Type Constraint Description
Ct_id integer(20) Primary key Id of category
P_id integer(20) Foreign key
Product id from
product table
Qty_available integer(20)
Quantity
available of
quantity
Threshold_value integer(20)
Threshold value
for category
quantity
Price integer(20)
Price of each
category
Type Varchar(30) Type of category
7.11 Customer:
Field name Type Constraint Description
C_id integer(20) Primary key Id of customer
Name Varchar(40)
Name of
customer
Contact_no Integer(20)
Contact number
of customer
Address Varchar(100)
Address of
customer
E-Mail Varchar(50)
E-mail address of
customer
7.12 Order:
Fruit product and Quality Management System Page 21
22. Field name Type Constraint Description
O_id integer(20) Primary key
Id for place
order
Date Date Date of order
Ct_id integer(20) Foreign key
Category id
contain in order
Amount Varchar
Amount for pay
after order
Ct_Qty Integer
Quantity of
category in order
C_id integer(20) Foreign key
Id of customer
who place order
Confirm_date Date
Date of confirm
order
Status Varchar
Status of order
whether confirm
or pending
Expected_date Date
Expected Date
when customer
Receive product.
8. Project Planning and Scheduling:
Project planning is a discipline for the starting how to complete a project
within a certain time framework, usually with define stages and with
designated resources. It describes the technical tasks to be produced and
the resources that will be required, the work produced to be produced
and a work schedule.
Project Scheduling in a project refers to roadmap of all activities to be
done with specified order and within time slot allotted to each activity.
Project managers tend to define various tasks, and project milestones and
then arrange them keeping various factors in mind. They look for tasks
like in critical path in the schedule, which are necessary to complete in
specific manner (because of task interdependency) and strictly within the
time allocated. Arrangement of tasks which lies out of critical path are less
likely to impact over all schedule of the project.
8.1.Project schedule
Fruit product and Quality Management System Page 22
23. No Task Name Start Finish Duration
1 Project definition 2 January 16 January 15 days
2 Requirement specification 17 January 30 January 14 days
3 Database design 31 January 13 February 14 days
4 GUI design 10 February 1 March 21 days
5 Web developing/ coding 6 March 9 April 35 days
6 unit testing 10 April 24 April 18 days
7 Report creation 25 April 30 April 6 days
8.1.Gantt chart
8.2.PERT chart
Fruit product and Quality Management System Page 23
31. Sales, payment and production Report:
Fruit product and Quality Management System Page 31
32. 10. Testing:
Usename and Password Validation:
Employee Form Validation:
Fruit product and Quality Management System Page 32
33. Print message when Sufficient stock quantity is not available:
11. Conclusion:
The Fruit Product and Quality Management system runs efficiently and smoothly.
This system helps to save detail generate various reports. When stock Level of raw
material goes below define level this system give message. This System also send
message when customer order is confirmed.
12. Bibliography:
http://www.encorefruit.com/index.php
http://fruitsmart.com/
http://www.mysorefruits.com/
http://www.alphafnp.com/
http://www.malasfruit.com/
Fruit product and Quality Management System Page 33