I3 57 & 54 Manan - Aadi Production

HASMUKH GOSWAMI COLLEGE OF ENGINEERING
Information Technology Department
PRODUCTION MANAGEMENT SYSTEM
A PROJECT REPORT
SUBMITTED BY
MANAN SHAH (57)

AADIT SHAH (54)
in partial fulfillment for the award of the degree

of
BACHELOR OF ENGINEERING
IN
INFORMATION TECHNOLOGY
At

VAHELAL, AHMEDABAD
June – 2010
Production Management System


Teaching Technology for Mankind
Naroda-Dahegam Road,
Vahelal – Dascroi,
Ahmedabad – 382 330
DECLARATION
I hereby declare that the project entitled “PRODUCTION MANAGEMENT

SYSTEM ” submitted for the partial fulfillment of B.E.(IT) Degree is my original
work and the project has not formed the basis for the award of any degree,
associateship, fellowship or any other similar titles.
Signature of the Student:
Place: VAHELAL
Date :


Teaching Technology for Mankind
Naroda-Dahegam Road,
Vahelal – Dascroi,
Ahmedabad – 382 330
CERTIFICATE
This is to certify that the project entitled “PRODUCTION MANAGEMENT

SYSTEM” has been carried out by MANAN SHAH & AADIT SHAH under my
guidance in partial fulfillment of the degree of Bachelor of Engineering in
Information Technology of Gujarat University, during the academic year 2009-
2010. To the best of my knowledge and belief this work has not been submitted
elsewhere for the award of any other degree.
Guide Head of the Department

Mr. MANTHAN KHOPKAR Mr. MANTHAN KHOPKAR

ACKNOWLEDGEMENT
We take this opportunity to express our humble thanks to all those
concerned with our project entitled “PRODUCTION MANAGEMENT
SYSTEM“.
We express very sincere thanks to Mr. Manthan Khopkar for
providing us an opportunity to work on such an interesting project, and in a
congenial environment. Their invaluable guidance has proved to be a key to
our success in overcoming challenges that we have faced during the course
of the project work.
The knowledge that we have gathered , study of relevant literature for
understanding our project , planning of details and selecting the suitable
software platform by itself and acknowledgement to the industry , zeal and
technical competence of those many individuals who have contributed to it
with profound gratitude , we wish to acknowledge all of them.
With Regards,
MANAN SHAH (57)
AADIT SHAH (54)

ABSTRACT
 The Application is developed with a view to provide flexibility on the part of Inventory
to do transaction of Sales and Purchase, orders, returns and products.
 Visual Basic is based on the old BASIC (Beginning all –purpose symbolic instruction
code) language. What makes it “visual” is that you “paint” your interface, as opposed to
using lines and lines of code to describe the interface.
 The project should be flexible enough to be used in premises of different companies.

Also the system should store various data about Sales and Purchase, orders, returns and
products, companies, different Departments of the organization itself.
 It should also provide the facility to add, edit, delete, etc these records. Visual basic is a
programming language used to create Windows-based application.
 Visual Basic makes it very easy to get the user interface portion of your application up
and running. Using typical drag-and-drop techniques, common in Windows applications,
you will find that painting screens is very simple.
 The Project of company should be able to report of their daily Sales and Purchase, orders,
returns ,products, Clients and Suppliers.
 Visual Basic is also proving itself, little by little, as available tool for enterprise wide
applications and solutions. This is especially true with the advent of Internet
programming and object oriented programming

TABLE OF CONTENT :
NO CONTENT PAGENO.
1 List of figures 7
2 Chapters
2.1 Introduction 8
2.2 Objective 8
2.3 Scope 9
2.4 Hardware and software 9
3 Analysis
3.1 Existing System 10
3.2Proposed System 10
3.3 Incremental Model 10
4 Design
4.1 Data flow diagram 12
4.2 E R diagram 15
5 Data Dictionary 16
6 Software Testing
6.1 Validation and Verification 22
6.2 The Testing Process 23
6.3 The Level Of Testing 24
7 Screen Layout 27
8 Conclusion
8.1 Advantage 44
8.2 Limitation 44
8.3 Future Enhancement 45
9 Appendix
9.1 Login Forms 46
9.2 Master Form 46
9.3 Transaction Form 46
9.4 Utilities Form 47
10 List Of References
10.1 Name of Book Used 48
10.2 Other Material 48

1.0 List of Figures:
Data Flow Diagram 4.1.0

1st Level DFD 4.1.1
2nd Level DFD 4.1.2
Entity Relationship Diagram 4.2
Screen Layouts 7.0

Log in Form 7.1
Master Form 7.2
Transaction Form 7.3
Utilities Form 7.4
2.0 CHAPTERS :

2.1 Introduction:
First of all production management system is windows based

application. This Production Management System is basically the same as management
system with which we can store all the data of customer, vendor, stock and transport even
if all the transaction made by customer.
The project should be flexible enough to be used in premises of different
companies. It keeps track of all the users. The project is connected to the web hence it is
accessible by all the users of the system. The portal can only be accessed by the
administrator and the users. The Project of company should be able to report of their
daily Sales and Purchase, orders
2.2 Objective :
The main Objective of the project is to design and develop the software which enables the
user to input the data of vendor , customer, transport as well as stock at a factory. This
software provides the features like –
1. EASY HANDLING
The GUI system is the Easy Handling System facility . For getting any kind of info just click
on some switches and get info in few seconds
2. INFORMATION
The all information about this Production Management system know through this software
3. ATTRACTIVE LAYOUT
The GUI provides an attractive input and output screen to the user. It is the main advantages
of the GUI based Web Application.
4. BACKUP & RESTORE DATA The purposed systems provides the backup and restore
facility to entering the data by users.. So, in case of problem in the system users can easily
get their lost data with the restore facility.
5. SECURITY

The purposed system gives a security in this Windows based Application. Nobody can
changes in this Web Application during at run time on the Internet.
6. DATA ACCESS
This application benefits to access the data in the access forms entering from the Admin
users.
2.3 SCOPE :
 The scope of this project is to develop a Management Control System. The Project of
company should be able to report of their daily Sales and Purchase, orders, returns
,products, Clients and Suppliers. The Application is developed with a view to provide
flexibility on the part of Inventory to do transaction of Sales and Purchase, orders, returns
and products.
 The project should be flexible enough to be used in premises of different companies.

Also the system should store various data about Sales and Purchase, orders, returns and
products, companies, different Departments of the organization itself. It should also
provide the facility to add, edit, delete, etc these records.
2.4 Technology Used:
i) Software’s
 Front End : Visual Basic .Net
 Back End : Microsoft Access 2007
 Technology : .Net Framework 2.0
 Designing : Microsoft Visual Studio 2005
ii) Platform
 Operating System : Windows XP Professional
iii) Hardware Configuration

 Intel Pentium Dual 2.0 GHz
 256MB SDAM,250GB HDD
 52X DVD-RX DRIVE & keyboard

3. ANALYSIS :
3.1 Existing System:

 The company has manual system
 The system that company has is not user friendly
 They use MICROSOFT ACCESS to store the records
 The company system is very time consuming
3.2 Proposed System :

 Save User’s Time and also Remove all paper work.
 It is speedy and also easy to implement.
 If there will be any problem with the system then we have used the system maintenance
plan to backing Up the data and to recover data of the System.
 It is Portable System.
3.3 INCREMENTAL MODEL
Incremental model is an evolution of waterfall model. The product is designed, implemented,

integrated and tested as a series of incremental builds. It is a popular model software evolution
used many commercial software companies and system vendor.
PHASES OF THIS MODEL:
When an incremental model is used, first increment is often a core product. As a result of use and
evolution a plan is developed for the next increment. This process is repeated following the
delivery of each increment until the complete product is produced. The incremental model
applies linear sequences in a staggered fashion as calendar time progresses. Each linear sequence
produces a deliverable “increment” of the software. The incremental model delivers software in
small but usable pieces, called “increments”. In general each increment builds on those that have
already been delivered
Incremental software development model may be applicable to projects where:
 Software Requirements are well defined, but realization may be delayed.

 The basic software functionality are required early.

Increment 1 Analysis Design Code Test
Increment 2 Analysis Design Code Text
Analysis Design Code Test

Increment 3
Analysis Design Code Test

Increment 4
Advantage:
 Generates working software quickly and early during the software life cycle.
 More flexible - less costly to change scope and requirements. Easier to test and debug
during a smaller iteration.
 Easier to manage risk because risky pieces are identified and handled during its iteration.
Disadvantage:
 Each phase of an iteration is rigid and do not overlap each other.

 Problems may arise pertaining to system architecture because not all requirements are
gathered up front for the entire software life cycle.

4.0 DESIGN
4.1 Data Flow Diagram
Check for the available stock

Product Admin
Give stock detail
If stock not available then store

order in pending order list
Give bill
Give stock detail
Give order
Check for available
stock
Production
Management
system
Sends row material & bill
Give bill
Order the row
material
Give
Order
Pay bill
Pay bill
Vendor Customer
Give receipt

4.1.1 1ST LEVEL DFD
1
Admin Provide Username & Password Validated
Login
Validates
If not valid then relogin

& Create new user Login
2
Product+
Give Order Purchase
Stock detail
Process
Vendor
detail Purchase detail
Vendor Purchase stock
If stock defected then do 3

Return to the vendor Purchase
Update Stock
Return
Process
Purchase Return
Product
Customer
Paybill
Product detail
Order detail
4
Bill detail Give order
Salse
Payment
Give quation & Confirmation
Bill
Payment
Sales
4
Return the defected
Sales
goods
Return
Refund
Sales return
detail
Sales Return

4.1.2 2nd LEVEL DFD
Product Vendor
Vendor detail
Product detail
Admin 2.1 Order detail

Give order Order Vendor
process
bill Bill detail
Purchase Detail Purchase
Bill detail
2.2
Pay bill Payment Payment detail
process
Receipt
Receipt
Payment

5.0 DATA DICTIONARY

TABLE NAME: - LOGIN
FIELDNAME DATATYPE CONSTRAINT DESCRIPATION
Username Nvarchar(50) PK It contains

username
password Nvarchar(8) Not null It Contains
password
Description: - This table can store the login details.
TABLE NAME: - PRODUCTMASTER
Product Id Bigint PK It contain product

id
Product name Nvarchar(50) Not null It contain product
name
Price Numeric(8,2) Not null It contain price
Height Int Not null -
Hunit Nchar(10) Not null Enter height’s
map(cm,mm,nm)
Width Int Not null -
Wunit Nchar(10) Not null Enter width’s
map(cm,mm,nm)
Unit Nvarchar(15) Not null It contain no. of
units
Description: - This table can store the vendor master details

TABLE NAME:-VENDOR MASTER
Vendor id Bigint PK It contain unique

id
Vname Nvarchar(50) Not null Vender name
Cname Nvarchar(50) Not null Company name
Address Nvarchar(100) Not null -
City Nvarchar(20) Not null -
Pincode Numeric(8,0) - -
Contact no Nvarchar(15) Not null -
Mobile no Nvarchar(15) - -
EmailId Nvarchar(30) - -
Description: - This table can store the vendor master details.
TABLENAME: - STOCKDETAIL
Productid Bigint Foreign key It Contains

product id
Vendorid Bigint Foreign key It contains
vendor id
Cur Int - It display current
product available
or not
Sdate Datetime It display the
system date
Description: - This table can store the vendor master details.

TABLENAME :- CUSTOMERMASTER
Cust id Bigint Primary key It contains

customer id
Cname Navarchar(50) Not null Customer name
Company name Nvarcahr(50) Not null Contain company
name
Address Nvarchar(100) Not null contain address
City Nvarchar(30) Not null contain city
Pincode Numeric(6,0) - contain pincode
Contact no Nvarchar(15) Not null contain customer
contact no.
Mobile no Nvarchar(15) -
Email Id Nvarchar(30) - It contains
customer email id
Description:- This table can store the customer details.
TABLENAME:-PURCHASE
Bill no Bigint PK It contains bill no

Vendor id Bigint FK It contains
vendor id
Do order Datetime - It contains order
date
Amount Numeric(10,2) - It contains
amount
St Numeric(5,2) - It contains service
tax
Total Numeric(10,2) - It contains
amount total
Outstanding Numeric(10,2) - It contains
remaning amount
Status Nchar(10) -
Description: - This table can store the purchase details.

TABLENAME:-PURCHASE RETURN
Sr no Bigint Primary Key It contains sr no.

Bill no Bigint Foreign key It contains bill no.
Do return Datetime Not null It contains date of
return
Product id Bigint Not null It contains
product id
Return units Int Not null It contains return
units
Refund Numeric(10,2) Not null It contains refund
Description: - This table can store purchase return details.
TABLENAME : - PAYMENT
Sr no Bigint Primary key It contains sr no.

Bill no Bigint Not null It contains bill no.
Mode Nvarchar(15) Not null It contains mode
of payment
Cheque_DD Nvarchar(15) Not null It contains
cheque/dd no
Cheque date Datetime Not null It contains
cheque date
Bank Nvarchar(30) Not null It contains bank
name
Branch Nvarchar(30) Not null It contain branch
name
Amount Numeric(10,2) Not null It contains
amount
Dop Datetime Not null It contain date of
paymnet
Description: - This table can store the payment details.
TABLENAME : - SALESDETAIL

Sales detail id Bigint Primary key It can store

unique id
Bill no Bigint Not null It contains bill no
product id
Qua Bigint Not null It contains
quantity
Total decimal(8,2) Not null It contains total
Description: - This table can stores the sales details.
TABLENAME:-SALESRETURN
Sr no Bigint Primary key It contains sr no

Bill no Bigint Not null It contains bill no
Do return Datetime Not null It contains return
date
product id
Return units Int Not null It contains return
units
Refund Numeric(10,2) Not null It contains refund
Description: - This table can store sales return details.
TABLENAME : - RECEIPT

Orderc id Bigint Primary key It contains order

customer id
Receipt no Nvarchar(50) Not null It contains receipt
no
Mode Nvarchar(15) Not null It contains Mode
of receipt
Cheque no Numeric(6,0) Not null It contains
cheque number
Bank Nvarchar(30) Not null It contains bank
name
Branch Nvarchar(30) Not null It contain Bank
branck
Dd Int Not null It contain dd
number
Amount Decimal(10,2) Not null It contain amount
R Date Datetime Not null It contain rdate
Description: - This table can store receipt details.

6.0 Testing
Testing a program consists of subjecting the program to a set of test inputs (or test cases)
and observing if the program behaves as expected. If the program fails to behave as expected,
then the conditions under which failure occurs are noted for later debugging and correction. The
following are some commonly used terms associated with testing.
A failure is a manifestation of an error. But the mere presence of an error may not
necessarily lead to a failure.
A test case is the triplet [I, S, O], where I are the data input to the system, S is the state of
the system at which the data is input, and O is the expected output of the system.
A test suite is the set of all test cases with which a given software product is to be tested.
6.1 VALIDATIONS AND VERIFICATION

Validation and Verification is the name given to the checking and analysis processes that ensures
that software conforms to its specification and meets the needs of the customers who are paying
for that software. Validation and Verification is a whole life-cycle process. It starts with
requirements reviews and continues through design reviews and code inspections to product
testing.
SR.
Validation Verification
NO
1 Validation is the process of determining Verification is the process of
whether a fully developed system conforms determining whether the output of one
to its requirements specification. phase of software development
conforms to that of its previous phase
2 Validation: Are we building right product? Verification: Are we building the
Product right?
3 Validation ensures that the software meets Verification involves checking that the
the expectations of the customers. software conforms to its specification.
6.2 The Testing process

I test the software process activities such as Design, Implementation and Requirement
Engineering. Because design errors are very costly to repair once system has been started to
operate. Therefore, it is quite obvious to repair them at early stage of the system.
Unit
Testing
Module
Testing
Sub-Sytem
Testing
System
Testing
Acceptance
Testing
Involves executing an implementation of the software with test data and examining the
outputs of the software and its operational behavior to check that it is performing as required.
6.2.1 Unit Testing:

Unit testing plays very important role in the testing process.Unit testing is done to check
password is correct or not.Unit testing check the all the fields are correct or not.Unit Testing
is undertaken when a module has been coded and successfully reviled.
6.2.2 Module Testing:
Individual modules are tested in the module testing.
6.2.3 System Testing:
The system consists of sub systems. So it is necessary to test the sub systems.
The entire system is tested after unit, module and sub system testing.The system is tested to
ensure that the system do not fail to perform various kind of operations.
6.3 LEVELS OF TESTING :

6.3.1 Black-Box Testing

Black box testing is an approach to testing where the tests are derived from the program or
component specification. Black box testing is also known as “Functional Testing” because the
tester is only concerned with the functionality and not the implementation of the software. In my
project I input all the information that is necessary for it. I also check for validation. The numeric
field does not accept the character type of data or any other type of symbols.
6.3.2 White-Box Testing

White box testing is an approach to testing where the tests are derived from knowledge
of the software’s structure an d implementation.
This approach is sometimes called “Structural Testing”, “glass box testing” or
“clear-box testing”.
In my project I give meaningful name to all variables and constants, forms, labels, etc.
I made functions for validation checking. So there is no need to write the code for
validation multiple times.

Password not match
* Here user enter password and re-enter passwords are different.

* So Invalid Password Error Occur.
Field required

* Here user has not entered some required information.

* So syntax error occur.
7.0 SCREEN LAYOUTS

7.1 MAIN LOGIN ENTRY FORM:
LOGIN FORMS :
MENU > LOGI FORMS > SELECT OPTION

7.2 Master Forms:

Menu > Master > select option

VENDOR FORM:

STOCK MASTER FORM:

CUSTOMER MASTER FORM:


TRANSPORT MASTER FORM:
7.3 TRANSACTION FORMS:

MENU>TRANSACTION>SELECT OPTION
PURCHASE FORM:

PURCHASE RETURN FORM:

PAYMENT FORM:

SALES FORM:

SALES RETURN FORM:

RECEIPT:

7.4 UTILITIES FORM:

MENU>UTILITIES>SELECT OPTION
CALC FORM:

MS OUTLOOK FORM:

8.0 Conclusion
The Processing of Production management system has been developed by us
through applying our knowledge gained in class room. Referring to certain books and

through the help of external and internal and internal faculties and using our own
knowledge related to the subject itself.
8.1Advantage
 we can do our work very fastly because of it’s functionality and we can store all the
information related to our production.
 Provide highly detailed information from an external perspective on what actually occurs
in programs
 Less time consuming and expensive to administer than other methods. Can be
administered to large groups of individuals.
 Effective for assessing program satisfaction. Small focus groups may increase the
comfort level of participants.
8.2LIMITATIONS:
This software includes problems like lack of accuracy, high cost, security problems,
etc. There are many problems in this like:
 Speed
 High cost
 Security
 Complexity
 Maintenance
 Accuracy
 Storing
 Records might get lost or be insufficient due to manual errors.
 Maintaining and managing data is very costly and time consuming.
8.3 Future Enhancement:

 In this software we can also add the reports detail like invoice, vendor details,
customer details.
 After removing the limitation of this software anyone can simply use this software.
 We can help this company by add many options like sales, purchase, sales return
purchase return, outstanding payment and outstanding report facilities.
 We can also add “ON THE SPOT” feedback facility to queries of users.
 We can also add the MS word, excel, notepad, access ,one note ,publisher in the
utilities form.
9.0 APPENDIX

9.1 LOGIN FORMS:

Change User Form:
In this forms we can change the user. We can create new user name and pass
word .This is the main form of production management system.
Exit Form:
In this form we can a exit from this software by clicking on exit button.
9.2 MASTER FORMS:

 VENDOR MASTER:
In this form we can store the data like vendor id , vendor name
,residential no., bank branch, bank name, pan card no, and also the bank branch, bank
name, vat no., email, pin code, stc no., and account no.
 Stock Master:
In this form we can store the product id, product name and unit. Also we
can update and delete our data.
 Customer Master:
In this form we can store the data like customer id , name, address,
city, pin code, ph no., acc no, bank name, bank branch, acc no, pan card no, stc no, vat
no., and email.
 Transport Form:
In this form we can store the data like transport id, it’s name, address,
city, pincode, ph no., mobile no, Lr no. and email address.
9.3 TRANSACTION FORMS

 Purchase Form:
In this form we can store the data like bill no, vendor name, product name,
transport name, lr nu, units, service tax, excise duty, packing charges, insurance, freight
charge, cess tax, total amount, and rate point. Also we can see all the records step by step.

 Purchase Return Form:

In this form we can store the data like vendor name, product name,
transport name , Sr no, bill no, units, rate per units, basic units, return units, return
amount, and rate point. Also we can see the grid view of data that we enter.
 Payment Form:
We can store Sr no, payment date, vendor name, bill no, due amount, mode of
payment, cheque no, cheque date, bank name, bank branch name and total payment. Also
we can see all the record one by one. And we can also print the data.
 Sales Form:
We can store the bill no, vendor name, product name, customer name,
transport name, Lr no, unit, price per units, basic amount, service tax, insurance, excise
duty, packing charges, cess tax, freight tax, total amount, rate point.
 Sales Return Form:

We can store Sr no, bill no., customer name, vendor name ,transport
name, units, rate per units, basic amount, return unit, return amount, rate point. and also
we can see the grid view of data that we enter.
 Receipt Form:
We can store Sr no, payment date, customer name, bill nu, due amount, mode of
payment, cheque no, cheque date, bank name, bank branch, total payment and also we
can see all the record one by one.
9.4 UTILITIES:
 Calc Form:
In this form we can calculate all the calculation by calculator. We can use
multiple functions like add, subtract, division, multiplication. Percentage and also we
can use other scientific options.
no msg no call
 Ms Outlook Form:
In this form we can mail our documents. Also we can create account
in msn or in hotmail .than we can send the message as well as receive the message. we
can also create news group account and also we can store and create our contacts and we
can save in ms outlook. we can also find the messages. we can also save our mail one by
one and than we can send all the mail at a time. so we can save our time.

10.0 List Of References:
10.1 Name of Books Used:

 Black Book of Visual Basic
 Visual Basic 6.0 Teach by Paul Sheriff
 Master in Visual Basic
 Private Institute Books
 DBMS(For SQL Server)
10.2 Other Material:

 MSDN (Microsoft Development Network)
 Microsoft Office (Word, PowerPoint,
Microsoft Visio)
 Software’s PCs (Word, PowerPoint)
 Macromedia Flash 8.0

I3 57 & 54 Manan - Aadi Production

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

I3 57 & 54 Manan - Aadi Production

Uploaded by

Copyright:

Available Formats

HASMUKH GOSWAMI COLLEGE OF ENGINEERING

Information Technology Department

PRODUCTION MANAGEMENT SYSTEM

MANAN SHAH (57)

in partial fulfillment for the award of the degree

HASMUKH GOSWAMI COLLEGE OF ENGINEERING

Production Management System

HASMUKH GOSWAMI COLLEGE OF ENGINEERING

I hereby declare that the project entitled “PRODUCTION MANAGEMENT

Signature of the Student:

Production Management System

HASMUKH GOSWAMI COLLEGE OF ENGINEERING

This is to certify that the project entitled “PRODUCTION MANAGEMENT

Guide Head of the Department

Production Management System

We take this opportunity to express our humble thanks to all those

concerned with our project entitled “PRODUCTION MANAGEMENT

We express very sincere thanks to Mr. Manthan Khopkar for

providing us an opportunity to work on such an interesting project, and in a

congenial environment. Their invaluable guidance has proved to be a key to

of the project work.

The knowledge that we have gathered , study of relevant literature for

understanding our project , planning of details and selecting the suitable

software platform by itself and acknowledgement to the industry , zeal and

technical competence of those many individuals who have contributed to it

with profound gratitude , we wish to acknowledge all of them.

MANAN SHAH (57)

AADIT SHAH (54)

Production Management System

 The project should be flexible enough to be used in premises of different companies.

Production Management System

Production Management System

1.0 List of Figures:

Data Flow Diagram 4.1.0

Entity Relationship Diagram 4.2

Screen Layouts 7.0

Production Management System

First of all production management system is windows based

Production Management System

 The project should be flexible enough to be used in premises of different companies.

2.4 Technology Used:

iii) Hardware Configuration

Production Management System

3.1 Existing System:

3.2 Proposed System :

3.3 INCREMENTAL MODEL

Incremental model is an evolution of waterfall model. The product is designed, implemented,

PHASES OF THIS MODEL:

Incremental software development model may be applicable to projects where:

 Software Requirements are well defined, but realization may be delayed.

Production Management System

Increment 1 Analysis Design Code Test

Increment 2 Analysis Design Code Text

Analysis Design Code Test

Analysis Design Code Test

 Each phase of an iteration is rigid and do not overlap each other.

Production Management System

4.1 Data Flow Diagram

Check for the available stock

If stock not available then store

Production Management System

4.1.1 1ST LEVEL DFD