Super Market Management

CONTENTS1. INTRODUCTION 22. PROBLEM STATEMENT 33. SCOPE OF WORK 44. OBJECTIVE OF SOFTWARE 55. SOFTWARE REQUIREMENT SPECIFICATION 66. DATA FLOW DIAGRAM 77. E-R MODEL 108. DATA DICTIONARY 129. SCREEN SHOTS 14 10. SOURCE CODE 1911. REPORT SCREENS 5812. CONCLUSION 6013. BIBLIOGRAPHY 60

INTRODUCTION

The project named Supermarket Management System is completely focused on activities of Supermarket. This Project is developed in Microsoft Visual Basic Version 6.0 which is totally menu driven and windows environment. The project handles and stores the complete details of customer, supplier and item and subjects to billing system.

PROBLEM STATEMENTS

Supermarket management system is such a vast subject, which cannot be handled manually. It requires a lot of data, many interfaces, continuous work load for the whole day. Due to these reasons we suppose that it is very hard to carry perfect work manually. The main problems that come across: -

1. To record the entries is very time consuming in manual system.2. Neat and clean work may not be there in manual system.3. Storing such a large data in registers and notebook is not possible.4. Manual functioning is very slow.5. Accuracy may not be there in manual system.6. Data can be easily destroyed, it cannot be secured.7. In manual system, there may be calculation mistakes, which lead to the wrong entry of data.8. If the person forgets to enter any essential entry then no one is there to warn him/her.

SCOPE OF WORK

The primary goal of a Database Management System is to provide an environment that is both convenient and efficient to use in retrieving and storing database information. Database system is to manage large body of information. The management of data involves both the definitions of structures for the storage of information and provision of mechanisms for the manipulation of information. The collection of data, usually refer to as database, contents the information about one particular enterprise. The project may allow user to manipulate the information, may have number of application programs that manipulate the files including:

A program to save, delete and modify new customer, supplier and item. A program to find detail of customer, supplier and item. A program to generate reports. A program to save bill for sale and purchase. A program to save receipt and payment. A program for automatic search of customer, supplier and item during billing.

OBJECTIVE OF SOFTWARE

Many databases are used for storing information related to customer detail, supplier detail, item detail, sale bill, purchase bill, receipt and payment. Since this system is user friendly any user can operate it without having any knowledge about the package.The system uses one MDB file, different PRG files and many procedures to make it successful.Objectives of proposed system: - 1. Maintenance of the Customer Detail, Supplier Detail and item Detail. Entry of new Customer, Supplier or Item. Modification of Customer, Supplier or Item.2. Maintenance of Sale Bill, Purchase Bill, Receipt and Payment.3. Generation of report between two days.4. Reports (as and when required). Sale report Purchase report Receipt report Payment report

SOFTWARE REQUIREMENT SPECIFICATION(SRS)COMPUTER USEDSystem Used:-Intel Pentium 4Operating System :-Microsoft WindowsXP Professional Package Used :-Microsoft Visual Basic 6.0Database Used:-Microsoft AccessFront End:-Microsoft Visual Basic 6.0Back End:-Microsoft Access HARDWAREHardwareMinimumMaximumProcessorPentium IIor higherRAM64 MBor higherHardDisk1 GBor higherMonitorSVGA (256 color resolution) **************************

DATA FLOW DIAGRAMA data flow diagram (DFD) also known as a bubble chart has the purpose of clarifying system requirements and identifying major transformation that will become programs in the system design. So it is the starting point of the design phase that functionally decomposes the requirement specification down to lowest level of detail. A DFD consists of a series of bubbles joined by lines. The bubbles represent data transformation. There are two alternative but equivalent symbols sets for constructing the DFD:

1. Yourdon symbol set2. gane-sarson symbol set

It is suggested that you do not mix and match symbol sets.

Four simple notations are sufficient to complete a DFD. They are:

Notation Yourdon Gane-sarson

1. Data flow

2. Process

3. External entities

4. Data source

Data Flow DiagramThe 0-level DFD:

Super MarketReportUser

The 1-level DFD:

CUSTOMER

SUPPLIER

ITEMS

AdminSALEDatabase

PURCHASE

RECIEPT

PAYMENT

E-R Diagram: The overall logical structure of database can be expressed graphically by an E-R diagram. The relative simplicity and pictorial clarity of this diagramming technique may well amount in large part of widespread use of E-R model. Such a diagram consists of following major components:

Rectangles, which represents entity set. Ellipses, which represents attributes. Diamonds, which represents relationship sets. Lines, which represents to entity sets to relationship sets. Double ellipses, which represents multi valued attributes. Dashed ellipses, which represent derived attributes. Double lines, which denotes total participation of an entity in a relationship set.

E-R Diagram for Super Market:

S_ADDRESSC_NAME

PH_NOS_NAMEC_ADDRESSC_CODE

OP_BALS_CODEPH_NOCUSTOMERSUPPLIER

CLO_BAL

CLO_BALOP_BAL

BILL_NOsaleI_NAMEI_CODESUPER MARKET

BILL_DTITEM

BILL_TYPESALE_RATEPUR_RATEOP_STOCK

CUS_ADDCUS_NAMEBILLINGCL_STOCK

TTL_AMTpur receipt payment

TOT_AMTBAL_AMTAMT_PAIDBALANCE

SUP_ADDBILLINGC_ADDAMT_PAIDP_NOBILLINGBILLING

SUP_NAMEBILL_TYPEC_NAMEREC_NOS_NAME

BILL_DTBILL_NOREC_DTP_DATES_ADDRESS

Data Dictionary1. CUSTOMER MASTER:

2. SUPPLIER MASTER:

3. ITEM MASTER:

4. SALE MASTER:

SCREEN SHOTS:1. LOGIN SCREEN:

2. MDI FORM: 3. CUSTOMER DETAIL SCREEN:

4. SUPPLIER DETAIL SCREEN:

5. ITEM DETAIL SCREEN:

6. SALE ENTRY SCREEN:

7. PURCHASE ENTRY SCREEN:

8. RECIEPT ENTRY SCREEN:

9. PAYMENT ENTRY SCREEN:

SOURCE CODE1. LOGIN FORM:Dim i As IntegerDim t As IntegerDim vapppath As String

Private Sub cmdexit_Click() EndEnd Sub

Private Sub cmdexit_MouseMove(Button As Integer, Shift As Integer, X As Single, Y As Single) cmdexit.Width = 1695 cmdexit.Height = 495 cmdexit.Left = 5160 cmdexit.Top = 4740 cmdexit.BackColor = &HFFFFC0 cmdexit.Font.Size = 20End Sub

Private Sub cmdok_Click() If UCase(txtpassward.Text) = "ALISHA" Then txtpassward.Visible = False lblpassward.Visible = False cmdok.Visible = False cmdexit.Visible = False lblpas.Visible = True lblmatch.Visible = True t2.Enabled = True Else txtpassward.Visible = False lblpassward.Visible = False cmdok.Visible = False cmdexit.Visible = False lblpas1.Visible = True lblmis.Visible = True 'MediaPlayer1.FileName = vapppath + "\MIS.wav" tm.Enabled = True End IfEnd Sub

Private Sub cmdok_MouseMove(Button As Integer, Shift As Integer, X As Single, Y As Single) cmdok.Width = 1695 cmdok.Height = 495 cmdok.Left = 5160 cmdok.Top = 3900 cmdok.BackColor = &HFFFFC0 cmdok.Font.Size = 20End Sub

Private Sub t1_Timer() If pic1.Left >= -6120 Then pic1.Left = pic1.Left - 600 Else frmSUPERMARKET.Show Unload frmpassword t1.Enabled = False lblpassward.Visible = False txtpassward.Visible = False cmdok.Visible = False cmdexit.Visible = False End If If pic2.Top >= -4800 Then pic2.Top = pic2.Top - 400.8 Else frmSUPERMARKET.Show Unload frmpassword t1.Enabled = False lblpassward.Visible = False txtpassward.Visible = False cmdok.Visible = False cmdexit.Visible = False End If If pic3.Left