PROJECT REPORT

ON

PARLE PRODUCT SYSTEM

SUBMITTED AS THE PARTIAL FULFILLMENT OF DEGREE OF
BACHELOR OF COMPUTER APPLICATION

By
Rohit Vishal And Nikunj Dabhi
Exam No.:

Under the Guidance of

Nishant Joshi

ANAND COMMERCE COLLEGE, ANAND

SARDAR PATEL UNIVERSITY
VALLABH VIDYANAGAR
MARCH 2021-2022
 Anand Commerce College

Certificate

This is to certify that Rohit Vishal And Nikunj Dabhi of

T.Y.B.C.A. (SEM VI) Exam No.:_ _ Roll No.:56,39, of
Anand Commerce College, Anand has satisfactorily
completed their project work during year 2021-21 as per
the university curriculum and here with, it is to be
submitted to S.P. University, Vallabh Vidhayanagar, for
their final Examination.
 PREFACE

It gives me great pleasure in placing in the handling of my esteemed faculties this

Group report, which, I believe, Will go through the documentation of the project work done
by me.

The objective of this report is to provide both a conceptual understanding of the

system as well as working guidelines.

The need for software development today is a competence in G.U.I based front-end
tools as far as the database programming is concerned. A typical scenario today involves
an application consisting of a visual front-end for presenting data and reporting options to
the enterprise user and a connection to a database for piping data to the controls such as
textboxes, tables etc.

As a student of BCA when I acquire all the theoretical knowledge, it is both

necessary and advisable to acquaint the real situation through. Well-planned project in
relevant fields. The project is important as the student not only learns to develop efficient
real world application but also gets a chance of self-development.

I have done a project PARLE PRODUCT SYSTEM fulfillment of Bachelor of

Computer Applications (BCA) program. Now a day, Internet is one of the best mediums for
providing information to the students or Employees of any Educational Institutes or
Organizations. There are Lots of manual efforts and processes that go into the keeping
track on the user while accessing Internet, which consume a lot of time.

PARLE PRODUCT SYSTEM efforts and hence brings significant gains in time.
Aimed for providing the reader with easier and in knowledge of report contains the
literature of almost all the things, which I have gone through from the point of view of any
system development life cycle. An effort has been made of exhaustively deal with every
part of the system developed.
 ACKNOWLEDGEMENT

It gives us great pleasure and gratification to present my Project PARLE

PRODUCT SYSTEM which has been completed in Third Year B.C.A.

On this stage we would like to thank all people who were behind and along with us,
and who constantly guided me during the time of difficulties we faced while developing this
project.

First and foremost we would like to thank the Teacher of Anand Commerce
college, Anand to whom we are highly indebted towards their invaluable contribution in
making my project presentable and without them this project would have not been
completed.

I would like to give very special thank to our Project Guide, Nishant Joshi for
helping me to develop the Project. He is always ready with his invaluable Suggestions
through his complete Perseverance.

Next, I would acknowledge staff members and Teachers of ACC who have
contributed a help with their active suggestions to the development of my project, which
provided to be of great help.

Lastly, we would express our whole hearted appreciation to the ACC family for the
continuous support, encouragement and invaluable tips.

ROHIT VISHAL AND NIKUNJ DABHI

Sr. Description of Topic Page
No. No.
1 Introduction To The Project
2 Scope Of Work
3 An Existing System
4 Need of proposed System
5 Feasibility Study
6 System Features
7 Hardware and Software
8 Data Flow Diagram / OOAD / UML
9 Database Layout / File Layout
10 Design Of Input Screens
11 Design Of Output Screens & Reports
12 Testing Procedures & Implementation Phases
13 User Guide / User Manuals (OPTIONAL)
14 Limitations
15 Proposed Enhancement (OPTIONAL)
16 Conclusion
17 Glossary & Technical Terms (OPTIONAL)
18 Bibliography (OPTIONAL)
 Introduction of the System

 “Parle Product system” is user friendly & easy understandable system.

 The has very simple language and format that people can understand each form
and they don’t have any difficulty to use the system.

 In the “Parle Product System” billing process and other process is done manually.

 This system is fully computerized system each process is done on computer.

 Scope of work

 The main work of this system is to manage the distributor detail and purchase
detail, selling detail and also keep record of distributor detail.

 Another job of the system is to some of the product price and bill print.
 An Existing system

 The current system has no facility to customer information.

 The current system has not good designing of form.

 In this system all detail of the payment will be done on paper work.

 Existing system is based on manual work and all the process are done
manually.

 This system has new latest photo.

 Purchase entry is mad in to the purchase register and stock will be update.
Need of proposed system: -----

 Computerizes bill facility available for Distributor series with product detail.

 To provide the store Distributor information.

 To Distributor provide all detail of payment will be done on system work.

 To provide better interface.

 Feasibility Study

Feasibility study is undertaken to determine the possibility of either

improving the existing system or developing a completely new system. It
helps to obtain an overview of the problem ant to get rough assessment of
whether feasible solution exits.

Need for feasibility study: ----

 Answer the question whether a new system is to be installed or not?

 Avoid crash implementation of a new system.

 Avoid the hardware approach.

 Define the problem and objective involved in a project. Avoid costly

repairs at later stage.

 Determine the potential of existing system.

 Know what should be embedded in the new system.

There are three types of feasibility: ----

1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility
1. Technical Feasibility:--

Technical feasibility should ask question related to:---

 Adequacy of available technology.
 Adequacy of hardware
 Available of computer.
 Operating time and support facilities.

Technical feasibility in the proposed system deals with

technology used in the system. It deals with hardware and software
used in the system whether they are of latest technology or not. It is
important because of whenever our system is prepared a new
technology arise and user want the system based on technology.

2. Economical Feasibility:--

Economical feasibility is closed related to the project “bank

salary system” because of economical feasibility for a system, it is
necessary to place actual money value against any purchase or
activities needed to implements the project. The support plan to get
the system and there is no interruption.

3. Operational Feasibility:--

In Operation feasibility determines how the proposed system

will fit in the current operation, if any jobs reorganize and retrying may
be needed to implement the system. In operation feasibility check
whether you or user is comfort
With the work. If user dose not understand of the system further
development of waste.
 System Feature

 Modification is easy.

 Save time.

 Save money.(By reducing paper work)

 Quick output.

 Easy to rebuild.

 Mostly every system must be developed for some specific

requirement of a system.

 Distributor and supplier record.

 Records of purchase and sells of “Parle Product System”

 Stock and cash management

 This system is providing a log time store the all information.

 This system is provide print out all type of bill.

 This system is Do not Probability of the any mistake of Distributor

order bill because it is a Computer rise System.

 This system is provide better interface.

 And this system is easily operation in create a Distributor order bill.

 Parle Agency detail.

 Hardware Specification

1. Hardware Requirements of the system:----

This phase of the software development process

deals with a brief study of different hardware used in the computerized
system. There is a list of hardware system. Requirement of a computer is
must. All the hardware needed here are generally the basic configuration of
a typical office computer. A list of the hardware requirement used in the
system given below:

Minimum configuration:--

1. Intel dual core processor

2. 1 GB RAM
3. 10 GB HDD
4. Mouse
5. keyboard
6. monitor
2. Software requirement of the system:--

Along with the hardware used in the system it requirement o

make a system as well as to run a system with the computer hardware.
Collection of different type of hardware into specific type and from a computer
but it can not execute different process on it’s on for efficient and proper
working of any system software must be installed.

This software may be in the form of operating system or

application software. To make the system one also needed to use software.

To make BCA information system for “AMCOST” I have to

use certain software which proposed system are the latest variation of them
selves and give up-to-date and perfect result to every process in the system.

Software used in designing of the system: ---

 Operating system: windows application XP

 Application software:VB.NET 2008 (front end)

SQl server 2005 (back end)
 Context Level DFD for Parle Product System

Request for item

DISTRIBUTOR

Request for item

Payment
1.0 Item / Bill
Item / Bill
Invoice
Process
Payment

SUPPLIER
 Context Level DFD for Parle Product System

Ask for item

Invoice Invoice
Details
Information

Distributor

Item & Bill

1.0
Invoice
Payment Process

Update
Stock Info
Request for Item

Update Stock
Master
Supplier 2.0 Items
Stock
Mgt.
Update Supplier

Stock
Information

Sales Distributor
3.0 Info Master

Report
Generate Supplier Supplier
Master
Detail
 First Level DFD for Process 1.0

Distributor on Item Product Master

Order
Proces
s

1.2
Billing
Bill Invoice

Proces
s
 First Level DFD for process 2.0

Supplier
2.1 Item
Available Invoice
Receipt Stock Details Master

Low Stock
Details

Update Item Master

Purchase Order

Items
2.0
Bill Sales
Purchase Sales Bill Detail
Process
Payment
 Database Layout

1. Table Name: - Login

Field Data Type Constraint Description

Name
Username nvarchar(50) Not null It contains Username
Password nvarchar(50) Not null It contain Password

 The login table contains the information about userid and password which are
used to access the system.

2. Table Name: - cust_inq

Field Data Type Constraint Description

Name
Custid nvarchar(50) Primary key It contains Custid
Inqdate nvarchar(50) Not null It contains Inquiry date
Custnm nvarchar(50) Not null It contains Cust name
Custadd nvarchar(50) Not null It contains Cust address
Custcity nvarchar(50) Not null It contains Cust city
Itemid nvarchar(50) Not null It contains Item id
Itemnm nvarchar(50) Not null It contains Item name
custcont nvarchar(50) Not null It contains Cust contact

 The Cust_inq table contains the information about the all Distributor which are
maintains by the Organization.
3. Table Name: - invoice_dtls

Field Data Type Constraint Description

Name
Invono nvarchar(50) Not null It contains Invoice no
Itemid nvarchar(50) Not null It contains Item Id
Itemnm nvarchar(50) Not null It contains Item name
Qty numeric(2) Not null It contains Quantity
unitprice numeric(10,2) Not null It contains Unit Price

 The invoice_dtls table contains the information about the all Invoice No Details
which are maintains by the Organization.

4. Table Name: - invoic_info

Field Data Type Constraint Description

Name
Invoiceno nvarchar(50) Primary key It contains Invoice No
Custname nvarchar(50) Not null It contains Cust Name
Surname nvarchar(50) Not null It contains Sure Name
Custcontact numeric(13,0) Not null It contains Cust contact
Invoicedate nvarchar(50) Not null It contains Invoice date
Custadd nvarchar(50) Not null It contains Cust Address
Totalquan numeric(3) Not null It contains Total Quantity
totalamount numeric(18,0) Not null It contains Total amount

 The invoice information table is use for all invoice/customer information data.
 5.Table Name: - rec_stock

Field Data Type Constraint Description

Name
orderno nvarchar(50) Primary key It contains Order No
supp_id nvarchar(50) Not null It contains Supplier Id
tot_que Numeric(3) Not null It contains Total Quantity
final_amt Numeric(18,2) Not null It contains Final Amount

 This form is use for store the received stock available information .

6.Table Name:- receive_dtls

Field Data Type Constraint Description

Name
orderno nvarchar(50) Primary key It contains Order No
Itemid nvarchar(50) Not null It contains Item Id
Qty Numeric(2) Not null It contains Quantity
unitprice Numeric(7,2) Not null It contains Unit Price

 This form is use for store the received stock details in order no, Itemed,
Quantity and Unit price.
 7.Table Name: - item_dtls

Field Data Type Constraint Description

Name
Itemid nvarchar(50) Primary key It contains Item Id
Itemnm nvarchar(50) Not null It contains Item Name
salesprice nvarchar(50) Not null It contains Sales Price
totalquantity nvarchar(50) Not null It contains Total Quantity

 This form is use for store the Item Details Information Data record.

8.Table Name: - stock_dtls

Field Data Type Constraint Description

Name
Ordno nvarchar(50) Primary key It contains Order No
itemid nvarchar(50) Not null It contains Item Id
itemnm nvarchar(50) Not null It contains Item Name

 This form is use for store the Stock details information.

9.Table Name: - supp_info

Field Data Type Constraint Description

Name
supp_id nvarchar(50) Primary key It contains Supplier Id
comp_name nvarchar(50) Not null It contains Comny name
supp_name nvarchar(50) Not null It contains Supp Name
address nvarchar(50) Not null It contains Supp Address
City nvarchar(50) Not null It contains Supp City
pincode Numeric(10,0) Not null It contains Pincode
contact_no Numeric(10,0) Not null It contains Supp Contact

 The supplier Information table contains the information about the different
supplier.
 Input or Output Screen: ---

1) Login:--

 Administrator can login with username and with specified password.

 By use of this form you can enter in particular system.
2) MDI Form:--

 Main screen (MDI) of the system.

 This form provides the option of a Parle Product System. This allows you
interact system.
3) Distributor Information:--

 This form is use for store the data in all Distributor Information.
 Save button is allows to insert the new record.
 Change button allows to modify the selected old record.
 Remove button allows to Delete the selected record.
 Close button allows to close current form.
 The navigation button is display the First, Next, Last and Previous record.
4) Stock Master:--

 This form is use for store information is check our available stock.
 Save button is allows to insert the new record.
 Change button allows to modify the selected old record.
 Remove button allows to Delete the selected record.
 The navigation button is display the First, Next, Last and Previous record.
5) Received Stock:--

 This form is use for store received stock’s information form supplier That
order number, Item Id, Quantity and Unit Price.
 Save button is allows to insert the new record.
 Change button allows to modify the selected old record.
 Remove button allows to Delete the selected record.
 Close button allows to close current form.
  The navigation button is display the First, Next, Last and Previous record.

6) Stock Details:--

 This form is use for store received stock details aspect order no, Item Id,
Quantity and Unit price.
 Save button is allows to insert the new record.
 Change button allows to modify the selected old record.
  Remove button allows to delete the selected record.
 Close button allows to close current form.
 The navigation button is display the First, Next, Last and Previous record.

7) Received Stock Details:--

 This form is use for store data about received Orderno, ItemId, Quantity
and Unit Price.
 Save button is allows to insert the new record.
 Change button allows to modify the selected old record
  Remove button allows to Delete the selected record.
 Close button allows to close current form.
 The navigation button is display the First, Next, Last and Previous record.

8) Supplier Information:--
  This form is use for store about supplierId, Company Name, Supplier
name, Contact no, Address, City, Pincode and Email.
 Save button is allows to insert the new record.
 Change button allows to modify the selected old record
 Close button allows to close current form.
 The navigation button is display the First, Next, Last and Previous record.

9) Biscuit Product:--
  This form is display the multi type of Parle Biscuit Product Images.

10) Chocolates Products:--

 This form is display the multi type of Parle Chocolates Product images.
11) Namkeen Product:--

 This form is display the multi type of Parle Namkeen Product Images.
 +12) Invoice Information:--

 This form is use for store information about Invoiceno, Customer Name,
Sure Name, Customer contact no, Invoice Date, Customer Address, Total
quantity and Total Amount.

 Save button is allows to insert the new record.

 Change button allows to modify the selected old record
 Remove button allows to Delete the selected record.
 Close button allows to close current form.
 The navigation button is display the First, Next, Last and Previous recor

13) Invoice Details:--

 This form is use for store data about BillNo, ItemId, Item Name, Quantity,
Unit Price and Total amount.
 Save button is allows to insert the new record.
 Change button allows to modify the selected old record
 Remove button allows to delete the selected record.
 Close button allows to close current form.
 The navigation button is display the First, Next, Last and Previous record.

Testing Procedures & Implementation Phases

System Testing

It is measure to check the quality of the software during development the errors in
requirement, design and coding phases. This phase starts with test plan, which give all
activities to be done for testing.

 Testing can be done by:-

1) Unit testing:--It is process to test an individual module of software.

2) Integration Testing: -- It is process to perform a testing after combine

modules.

3) System Testing: -- It is process to check whether the software is working according

to user.

4) Acceptance Testing:--It is process to check the software with actual data.

 Method Of Testing

In this system I was testing with both of functional and structural testing.

1) Functional Testing: -- It is also know as black-box testing. It is not know what is

inside code.

2) Structure Testing :--The test data is given to check the logic of the code called as
glass box testing

System Implementation
 System Acquisition :-

An important part of the system acquisition is the actual purchase of goods and
services. It Involves the purchase of hardware, package software and software
service. Here system analyst and designer work together to determine best
policy for this purchasing.

 Programming :-

Computer programmer performs programming. Programming is the writing the

coded instruction, testing each segment of the code and testing the entire
computer programmed one it is completed. Normally a team of programmer
work under the direction by system analyst.

 Testing :-

It consists of putting together the various coded pieces of a design, testing them
and correction the parts of the design that are not correct.

 Conversion :-

Once the system has been tested successfully then the putting into the
operation. The conversion team must manage the smooth changes from old
system to new system.

 This Requires :-

1) Training of personnel

2) Modifying parts of the old system

3) Running parallel both systems (old and new) until everything goes as
planed.
 Documentation :-

Documentation means the written from about how a system design or function.

a) Design Documentation: -- It describes overall system design and it includes

system.

b) Program Documentation: -- It consists of programming specification like

program logic.

c) Training Documentation:--It includes user training and materials to be used in

the conversion and the installation of new system.

d) Operation Documentation: -- It contains instruction for normal operation as

well as for handling problems.

e) Design Documentation: -- It should provide quick, clear answer like a

dictionary.
 Limitation

The following drawbacks of existing system emphasize the need for computerization:

1. A user must have computer knowledge.

2. User pass through many data of table.

3. User must have to do manually work of billing.

 Conclusion

This application avoids the manual work and the problems concern with it. It an easy
way to obtain the information regarding the different scheduled vehicles information
that is currently issued.

Well I and my team member have worked hard in order to

distributor an improved website batter than the existing one’s regarding the
information about the various activities.
 Bibliography

Here are the following names of the book referred during the
system development. This book referred by me at the time during difficulties and
doubt.

Books Names:--

 Microsoft Visual Basic 8.0….Black Book

By Holzer

 Visual Basic 8 complete reference Miscosoft

By Jerks

 System Analysis And Design:--Ellis Award

 System analysis And Design:--Sean