A

Project Report
On

“Firework Management System”

 ACKNOWLEDGEMENT
At the very outside I am very thankful to “Firework Management System”, Jalgaon
for giving me this opportunity to develop this project and making all available
kinds of resources with intention to the success of the project.

We are also grateful to our project guide Prof. Minakshi Yeole for the guidance,
inspiration and constructive suggestions that helpful to us in the preparation of this
project.

Finally, I appreciate my colleagues and friends who kindly

offered their suggestions, comments and criticism for improvement of this report.

With warm regards,

Rahul Vilas Mali

Yash Avinash Patil

Yash Hitendra Kolhe

 Index

Sr. Chapter Name

1. About Organization

2. Existing System

3. Proposed System

4. Need Of The System

5. Software & Hardware requirements

6. DFD(Data Flow Diagrams)

7. ERD(Entity Relationship Diagram)

8. Database Design

9. Input Forms

10. Output Forms

11. User manual

12. Conclusion

13. References
 1. About Organization
“Firework Management System” is a service oriented establishment in which
people receive service about Crackers. This organization was established in 2
March 2000 and well settled in Jalgaon. The owner of this organization is Mr.
Nandkumar Chaudhary. The name of the organization is “Firework Management
System”. The ultimate aim is the customer’s satisfaction.

Providing Service in purchasing, selling and creating crackers to people is

the most important activity of a Firework Management system.

The use of various types of crackers vary from person to person as per need.
In the present project good management is represented by application.

In this there are number of types of crackers which are used by

customers like,

 Double Shot
 Kothi
 Naag Goli
 Tikli
 Sutali Bom
 2. About Project
Firework Management System provides knowledge and practical
perspectives of all aspects of management of crackers shop.

Firework Management System is one of the most tedious processes, which

involves the regular updating of many files and records and registers in case of
fully manual. As new customer needs registrations, it has to issue a unique
customer code for that computer. For this they have to keep a track of many
records such as Crackers Master, Customer Master, Supplier Master , Received
payments, Etc..And maintain a number of registrations also. Doing this manually,
it involves lot of time and labor. Hence this can be made easy through automation.
Using this project admin (the default user) can be known all information
about
The crackers management system controls all the things automated. Also he or she
can be managing it very effective.
Admin finds it very easy way to obtain the customer, supplier and Bill
information.
 User friendly.
 Admin can get the Timely Information from the database without any
delay regarding the query.
 This reduces the delay of response.
 System provides Reports to admin for making quick decisions.
 3. Need the of project
This software is a mirror in which we can see the real picture of firework
management system. The main benefits of this software will be paper saving and
most important one: Time saving. Earlier these records were maintained on a
paper on daily basis but now these can be easily done using this software.

All the transactions can carried out (with details) in this software.
Firework Management System is ideal for all travel shops. The travel
management software can be installed on any Operating System. The product
features include: details of customers, details of suppliers, and all processes happen
during the transport. This software does not require special templates, frames,
coding, or server-side technology.

1) Large amount of data handling:

System can handle large no. of daily transactions.

2) Final statements and reports:

This application generates reports like customer registration, Bills, transport
details as per the business requires

3) Reliability:
As the data is saved one can add, search & delete data whenever required.

4) Speed & accuracy:

Records are manipulated with high speed and accuracy. It saves the time.

5) Security:
Providing full Security to data is the main objective.

6) Cost Effective:
The decision at the right time makes it possible to keep the stock in control
& thus provide right investment.
 4. Proposed System
If the existing manual system will connected into computerized system then
it will be more advantageous for handling organizational transaction.

Through computerized data processing should be accurate & instantaneous

and any information will be retrieved any time in seconds. Manual work should be
brought to minimum.

Any report required by the management would be accurately generated

without any lapse of time.

And the system would be user friendly so that the operator can operate the
system easily.

Data security will be provided by the system to avoid unauthorized data. It

minimizes the record keeping through storage devices.
 5. Software & Hardware
Requirement
A major element in building system is selection of compatible hardware &
software. Hardware selection they begin with requirements analysis following by a
request for proposal, evaluation & validation, post installation review.

While selecting the software various criteria is considered such as

reliability (gives consistent results), functionality (function to standards),
capacity (satisfies volume requirements), flexibility (adapts to changing
needs), usability (user friendly), security (to prevent unauthorized access),
performance (capacity to deliver as expected), serviceability (good
documentation), minimal cost (affordable for intended application).

 Software Requirement:
1. Operating System-widows 7
2. Microsoft Visual Studio 2008.
3. Microsoft Access 2007.
4. .NET framework 3.5.

 Hardware Requirement:
1. Pentium IV.
2. Minimum 1GB RAM.
3. Maximum 40 GB HDD.
4. Input Devices: Keyboard, Mouse.
 5. DFD

User
Login
1.0 Login Master

Customer
Sale Master

Sale
Management

SaleItem Master SaleItem Master

Reports

First Level DFD

 1.0 2.0 4.0
3.0 4.0
Sale Purchase Payment
Reports
Management Management Management

SaleItem Purchase Purchaseitem

Sale Master Payment Master
Details Master Details

First Level DFD

2.1 2.2

List Purchase Purchase

Items Process

Company Purchase Purchase Item

Item Master SubItemDetails
Master Master details

DFD for 0.2

 3.1

Payment
Process

Purchase Paymentinfo
Master Master

Second level DFD for

0.3
 7. Entity Relationship Diagram:-
ER Diagram:-

Customer M To Crackers To M Supplier

Bill
M
M
Books Paid M M
Orders
Order Supply
Bill Give
M
M Amt
To Crackers To Give

1 1 1
1
To Firework 1 M Crackers
1 To
Management
M 1 System
Crackers provides
1
maintain M Stock

Update

1
8. Database Design
UserMaster:-

Field Name Data Type Constaints Description

user_id Text Primary Key User Id

UserName Text Not Null User Name

Password Text Not Null Password

ProductMaster:-

Field Name Data Type Constaints Description

Prod_Id Number Primary Key Product ID

ProdName Text Not Null Product Name

SaleRate Text Not Null Sale Rate

PurchaseRate Text Not Null Purchase Rate

Stock Date/Time Not Null Stock

Purchase:-
Field Name Data Type Constraints Description
PurchaseInvoiceNo Number Primary key PurchaseInvoiceNo
PurcInvoiceDate DateTime Not Null Purchase InvoiceDate
SuppCode Number Not Null Supplier Code
TaxValue Number Not Null TaxValue
TaxAmt Number Not Null TaxAmount
DiscValue Number Not Null Discount Value
DiscAmt Number Not Null Discount Amount
GrossAmt Number Not Null Gross Amount
TotalAmt Number Not Null Total Amount

PurchaseDetails:-

Field Name Data Type Constraints Description

PurchInvoiceNo Number Primary key Purchase InvoiceNo
Prod_ID Number Not Null Product ID
ProdName Text Not Null Product Name
Qty Number Not Null Quantity
Rate Number Not Null Rate
Amount Number Not Null Amount

CustomerMaster:-

Field Name Data Type Constraints Description

CustId number Not Null Customer id

CustName text Not Null Customer name

Adress text Not Null Address

City text Not Null City

MobileNo text Not Null Contact No

9. Input Forms
Login Form
Customer Page
Supplier Page
Product Form
Purchase Invoice Form
Sale Invoice Form
Payment Receipt Form
10. Out Put Forms
Report Forms
Product Report
Customer Report
Supplier Report
Application Menu
11. User Manual
USER REQUIREMENTS:
Every user interacts with the system with some needs and requirement such as:-

1) Basic knowledge of computer should be required.

2) User should know basic knowledge about the computerized Services.
3) Comprehensive information accessing and retrieving so as to provide
valuable report and figures.
4) Data security and priority is not to be ignored.
5) At the time of generating the reports, where the corresponding reports are to
be set in the computerized system.
6) Every user must know the function of each Master entry, Transaction entry
and Reports.
7) The format, field within a format, data types, what type of data is to be
entered, what is the maximum size of each entry module. The user must
know each thing.
8) In short, operating environment about the computerized “Travel
Management System “must be familiar to the user.
9) Every Text Box should be filled with Data .If data is not available put at list
‘.’(DOT) for character, as well as for numeric data’0’ (ZERO) should be
placed.
 12. Limitation of System
In this system online payment transfer facility is not available.

It is also needed skilled workers to handle the computerized system.

It requires having knowledge about the working process of the organization.

 13. Conclusion
The software quality depends upon the phases included in the system.
Application software should be easy to operate & understand. A high Quality
software product satisfies the user requirements regarding design specification
& maintains flexibility as well .These aspects are accomplished in designing
and developing this Particular software “Firework Management System”. The
system is-

 User Friendly- The system is totally user friendly & easy to operate
& understand.
 Duplicity- As data is completely normalized, so that no duplicate
entries exists
 Menu driven- This system is totally menu driven for the best result.
 Security- A high level security by means of password and validation at
different level she as been incorporated into the system as per user
requirement.
 14. References
 Visual Basic.NET Black Book

 MS Access 2007 BPB publication

 Www. dotnetspider.com.

 www.codeproject.com