Super Market Management System

MS Access - Super Market Management System

1. Data base project on :- Super-Market Management System By : Bittu Singh Guided by : Prof. Amar Tewari Shubham Singh

2. Introduction This project deals with Super-Market automation . A Super-Market is a self-service store offering a wide variety of items related to food, household or daily use. Includes both purchase and sale of products. Designed to make the existing system more informative, reliable, fast and easy for all the stake-holders.

3. Objective To produce software which manage the activities done in a Super-Market . To maintain the records of the sales done for a particular month. To maintain the stock details. To reduce time in calculation of Sales activities. To store large amount of data in the database which will reduce clumsiness. To reduce paper work; so that users can spend more time on monitoring the Super-Market .

4. Project Description Based on the transactions in a Super-Market . First activity is adding the items to the system along with their rates and names of the items which will be up for sale in the Super-Market. This authority is given only to Admin . Any modification to be done in the item name or item rate cane be done only by Admin. Right to delete any item details rest with the Admin too. As the customer buys the products and comes to the billing counter, the user is supposed to enter the item name purchased.

5. The system will display all the items a custom er wants to purchase. If the stock is not available, the supermarket orders and buys from a prescribed vendor. The amount can be paid either in cash or via online according to customer preference . Admin provides a unique username and password for each employee through which they can login. Project Description

6. Problems with the existing system Manual system faces a lot of inefficiencies. Hinders smooth flow of work. Lack of security of data. Although more man power But less efficiency. Time consuming. Consumes large volume of paper work. Needs manual calculations which are prone to errors. Poor communication may lead to serious inadvertent errors.

7. Requirement Analysis Supermarket and related information Details of products to sell Staff and employee related details Electronic card machine for accessing ATMs and Debit card Supplier details Customer details P roducts in stock Special training to the staffs that are not from IT background

8. Software Requirements Processor : I ntel dual core or above Processor speed : 2.0 GHZ or above RAM : 1GB or above Hard disk : 20 GB or above Programming language for coding : Microsoft Access

9. Work Flow The products will arrive in the store. Data entry operator will enter the information of the product in the database. The administrator will enter the taxes and the commissions for each product. The customer will come and take the basket with him/her and choose the product and take it to the counter. The bill calculating operator will check the products with the Bar C ode detecting machine; then it will match with Product-ID; then it will show its information and price and the bill will be calculated and total payment will be shown. Customer will pay for the products and they will be packed and delivered to the customer. Stock will be updated by reducing the quantity of the product.

10. Advantages of the proposed system Reduced processing cost. Error reduction. Automatic updation of product details. Improved report generation and analysis. Better equipped to meet user requirements. Reduction in use of paper. Reduction in man power. Faster response time.

11. Pre-Normalization List of Attributes : Customer – Customer Name , Customer ID , Address Line 1 , Address Line 2 , Address Line 3 , City , District , State , PIN , Contact No. , E-Mail ID , Membership Card No. Ordered Product – Product Name , Product Type , Product Brand , Product Model ID , Product Price , Product M anufacturing Descriptions Billing Counter – Bill No. , Bill Date , Customer ID details , Bill Amount Product Shelves – Product Category , Product Type , Product Brand , Product Model ID Accounts – User Designation , User ID , User Password , Login Time

12. Pre-Normalization Payment – Payment Receipt No. , Payment Amount , Payment Mode Stock – Product Name , Product ID , Product Type , Product Price , Manufacturing Details , Product Model Employee Details – Employee Name , Employee ID , Date of Joining , Designation Supplier Details – Supplier Name , Supplier ID , Contact No. , E-Mail ID , Address Line 1 , Address Line 2 , Address Line 3 , City , District , State , PIN Order placed for the Supplier – O rder No. , Product Type , Product Brand , Date of Order , Ordered Quantity

13. Primary Keys Customer – Customer ID Ordered Product – Product Model ID Billing Counter – Bill No. Account – User ID Stock – Product ID Supplier Details – Supplier ID Order given to Supplier – Order No. Employee Details – Employee ID Payment – Payment Receipt No.

14. Relationships Customer is related to Ordered Product and to Billing Counter Ordered Product is related to Product Shelves and to Billing Counter Billing Counter is related to Stocks , Account and Ordered Product Account is related to Product Shelves , Payment and Billing Counter Payment is the relation between Account and Stock Supplier Stock is related to Supplier Details and Billing Counter Order placed for the Supplier is related to Stock Supplier and Employee Details Employee Details is related to Order placed for the Supplier and Account

15. Remove Derived Quantities Remove Bill Amount from Billing Counter Remove Payment Amount from Payment Relationships between Tables Customer – Customer ID – O rdered Product Customer – Customer ID – Billing Counter Ordered Product – Product Model ID – Product Shelves Ordered Product – Product Model ID – Billing Counter Billing Counter – User ID – Accounts Billing Counter – Product Model ID – Stock Employee Details – Order No. – Order placed for Supplier Order placed for Supplier – Supplier ID – Stock Supplier

16. Reduce Data Redundancy Remove Product Name , Product Type , Product Brand , Product Description and Product Price from Ordered Products Remove Product Type and Product Name from Order for Supplier New List of Primary Keys Customer – Customer ID Ordered Product – P roduct ID Billing Counter – Billing No. Account ID – User ID Administrator – User ID Employee Details – Employee ID Supplier Details – Stock ID Stock – Product ID

17. Primary Keys Stock Details kept by Supplier – Supplier ID Order Details for Supplier – Employee ID Relationships Customer – Customer ID – O rdered Product Customer – Customer ID – Billing Counter Ordered Product – Product Model ID – Billing Counter Billing Counter – Product Model ID – Stocks

18. Relationships Billing Counter – User ID – Accounts Accounts – User ID – Employee Details Employee Details – User ID – Order Details for Supplier Order Details for Supplier – Order No. – Orders placed for Stock Supplier Order Details for Supplier – Supplier ID – Stock Supplier Stock Supplier – Supplier ID – Stock Details kept by Supplier Stock Details kept by Supplier – Product Model ID - Stocks

19. Conclusion With business opportunities increasing as never before, companies are in dire need of efficient management. One such key area is to maintain a methodical way of managing large databases, especially in the Retail sector. DBMS is a vital tool for future growth of business organizations. It offers a simple, efficient and reliable way of storing, managing and accessing data. The features offered by DBMS are : Query ability, Backup, Security and Computation which are the needs of a fast-paced corporate system. To churn profits, companies need to have a good plan along with affective DBMS.

20. Thank You!