supermarket billing system

T.Z.A.S.P MANDAL’S

PRAGATI COLLEGE OF ARTS, COMMERCE & SCIENCE

DOMBIVLI

Case Study on

Presented By,

VIVEK WANI (21)

VIJAY DUBAL (18)

(Students of B.SC (I.T) IV- Semester)

Guided By,

Mrs. Rupali Patil

INDEX

Sr. No. Topic. Page.

1 Organization Overview. 1

2 Objectives of Proposed System. 2

1

3 Current System. 3

4 Limitations of Current System. 4

5 Advantages of Proposed System. 5

6 GNATT Chart. 6

7 E-R Diagram. 7

8 Context Level Diagram. 8

9 Functional Decomposition. 9

10 Logical DFD. 10

11 DFD Fragmentation. 11

12 System Flowchart. 13

13 Menu Tree. 14

14 Table Listing. 15

15 Report Listing. 16

16 Form Layout. 17

17 Conclusion. 18

18 Reference. 19

CERTIFICATE

This is to certify that VIVEK WANI (21) & VIJAY DUBAL (18) has completed the prescribed

Case Study satisfactorily during the academic year 2009-10.

2

Grade: A/B/C/D/E/F

Date: ______________

Seal:

PROFESSOR-IN-CHARGE

(B.SC IT)

3

Organization Overview

The project is on Supermarket Billing. Supermarket is the place where customers come to

purchase their daily using products & pay for that. So there is a need to calculate how many

products are sold & to generate the bill for the customers.

In this project, we have 3 users. First is the data entry operator who will enter the

products in the database. Second one is the administrator who will decide the taxes &

commissions on the products & can see the report of any product. Third one is the bill

calculating operator who will calculate the bill & print.

4

Objectives of Proposed System

To make software fast in processing, with good user interface so that user can change it

& it should be used for a long time without error & maintenance.

5

Current System

Many supermarkets use this type of billing system for a decade. It is improved many

times according to requirements of sellers & customers. It does the same work i.e. calculating the

bill, gives it to the customer & maintain proper database. They are accurate in calculation &

printing, they also generate records.

A new concept is also added in the billing system is that they also maintain relationships

with the customers who purchase more products from the store regularly. System also concerns

their requirements & gives them more commission. It also shows the overall reports which items

are required & which have cross their expiry date.

6

Limitations of Current System

Every system has pros & cons so existing system have many advantages &

disadvantages. So the limitations of existing are as follows:

User Interface:

User interface is not so much good that operators feel some problems in working.

Graphical User Interface:

GUI is not good so the operators get bored by watching screen.

Processing Speed:

Processing speed of the software is not so much good to operate fast.

Flexible:

Existing system is not so much flexible that can be changed according to the operators &

customers.

Automatic Generation of Reports:

Not able to automatic generate the reports & documents.

Workload:

Sometimes the system hangs when workload is more.

Error Free:

Sometimes the system gives error in the calculation in making the bill & in the

information of the products due to workload.

Man Power:

Existing system uses so many people to operate the system.

Resources:

System does not use the resources properly.

7

Advantages of Proposed System

To reduce the limitations of the existing system there is a need to develop a new system.

The new system should concern the requirements of the customers & the sellers. It has following

quality:

Reduction in processing cost.

Error reduction.

Automatic posting.

Improve reporting.

Automatic production of documents & reports.

Faster response time.

Ability to meet user requirements.

Flexibility.

Reduced dependency.

Improves resource users.

Reduction in use of paper.

Reduction in use of man power.

Proposed system includes these above qualities including existing qualities.

8

GNATT CHART

9

E-R Diagram

10

Customer

Cust_Name Cust_No

Address

Purchase Product

PriceProduct_No Pur_Date

Weight

Barcode_No

Supplies

Sales

Employee

Emp_Name Emp_No

SalaryAddress

DesignDealer

Dealer_Code

Dealer_Date

Phone_No

Organization

Dealer_Cust_Name

Address

BillGiven To

Context Level Diagram

Pays Treats Customers Of

Comes To Appoints

Gives Service To

Gives Bill To

11

Customer Employee0

SUPER

MARKET

Functional Decomposition

12

0

SUPER

MARKET

1.0

Entry of

Customers

2.0

Search Products

3.0

Services

4.0

Bill

5.0

Employees

Logical DFD

Gives information to

Included Services

Account

Employee ID

Services

Bill

Bill Registered

13

Customer Employee

1

Login

Process

2

Searching

Process

3

Provides

Services

4

Bill Process

DFD Fragmentation

Process ID: 1.0

Customer’s details are saved in

Customers

Process ID: 2.0

Cust_Det

Product Emp_Det

Services

Process ID: 3.0

Provides Details to go

Services

14

Customers

1.0

Entry of customers

2.0

Product

Searching

Employee

3.0

Services

Process ID: 4.0

Gets Bill

Bill

Registered

Receives Services

Process ID: 5.0

Emp_Det

15

Customers

Bill

4.0

Bill

Employee5.0

Add new Employee

System Flowchart

16

Customer Enters

Process of CustomerReport

SUPER

MARKETServices

Employee

Employee Details

BillCalculate Bill

Report

Services

Menu Tree

17

User Name

PasswordLogin Form

Add

Delete

Details

Employee

Add

Delete

Details

Bill

Bill No

Customer

Add

Delete

Details

Code

Dealer

Add

Delete

Details

Updates

Product

Table Listing

Customer Table. Employee Table. Dealer Table. Product Table.

The above tables are listed below:

Customer Table

Field Datatype SizeCust_Name char 1 Byte

Cust_ID int 2 BytesCust_Add int/char 4 BytesTel_No int 2 Bytes

Employee Table

Field Datatype SizeEmp_Name char 1 Byte

Emp_ID int 2 BytesEmp_Add int/char 4 Bytes

Tel_No int 2 Bytes

Dealer Table

Field Datatype SizeDealer_Name char 1 Byte

Dealer_ID int 2 BytesDealer_Add int/char 4 Bytes

Tel_No int 2 Bytes

Product Table

Field Datatype SizeProd_Name char 1 Byte

Prod_ID int 2 BytesProd_Amt float 4 Bytes

Report Listing

18

Form Layout

19

Conclusion

20

Our project is on supermarket Billing System. We have successfully completed it. We

take this opportunity to express our sense of indebtedness and gratitude to all those people who

helped us in completing this project.

We are immensely grateful to our guide Mrs. Rupali Patil for their supervision and

guidance without which this work would not have been possible. This project has contributed a

lot to my knowledge that has proved to be a value addition for me.

Reference

21

The system is designed to perform task of multiple users. Case Study is referenced through many books. The main source is internet.

22