Automation of Super Market

Automation of Super Market Sonali Das Computer Science and Applications, College of Agricultural Engineering and technology OUAT, Bhubaneswar, Orissa, India E-mail: sonalidas80@gmail.com Abstract This paper presents procedures for automating the Super Market. Super Market maintains all the details related to the various customers and vendors involved in the transaction of the super market. It keeps all the details of the products required in the transaction of the market. It maintains the flow of products. It records all the day to day transactions invoices which record the details of sales made by the market.it handles all the proceedings of payments made by the different customers of the super market. It makes the regular entry of the issues and receipts of the products indulged in the transaction of the super market. Super Market also generates various types of reports in order to keep all the activities under proper control. The software package Automation of Super Market can be said to be a benchmark for betterment of the service in Super Market as it takes care of the system administration. The system has been developed in such a way that the user will find them absolutely essential in generating details of the market. Programming language- Java Development Kit 1.4.0(JDK1.4.0), RDBMS backend- SQL server 7.0, ernet Technology- HTML, Java Server Pages (JSP), Web server- Java Web Server 2.0 (JWS 2.0) and TOMCAT 4.1.0 are used to develop the software package Automation of Super Market Keywords: DFD, ER-Diagram, Database, JSP, HTML, Reports I. INTRODUCTION Super Market is a shopping center engaged in purchasing consumer goods from solo vendor and manufactures and selling to customers and retailers. Before the proceeding of Super Market was handled manually, but this method has to face a lot of difficulties of problems when the super market started to deal with a large volume of transaction and data. Some of the common problems are illustrated as under: (i) The storage and preservation of large volume of data becomes difficult. (ii) The recording of the data on manual system is very costly because the writing and reading process is very low. (iii) There are always good chances of errors. (iv) A manual system does not help to provide quick view of stock available, invoices, payments etc. After knowing the various limitations of manual system, the super market realized that the computerization methods, as it provided them the following advantages: The storage and preservation of large volume of data becomes very simple and easy. The recording process on a computerized system is very cheap. The reading process of data is very fast and easily readable on machine. There negligible chances of errors in a computerized system. The computerized system helps to provide a quick view of all the details of a super market. II. SOFTWARE AND HARDWARE REQUIREMENT SPECIFICATIONs Hardware Requirements: el chipset motherboard 1GB RAM 120 GB Seagate hard disk Pentium-III 1 giga hertz processor LG studioworks563 N 15 inch monitor mercury scroll mouse Maple keyboard Software Requirements: Operating system- windows Millennium on wards. 52

Programming language- Java Development Kit 1.4.0 (JDK1.4.0) RDBMS backend- SQL server 7.0 SQL Server 7.0 ernet Technology- HTML, Java Server Pages (JSP), Web server- Java Web Server 2.0 (JWS 2.0),TOMCAT 4.1.0 Microsoft SQL Server 7.0 is one of the powerful, high performances, preferred Relational Database Management System. It is capable of supporting hundreds of simultaneous users, depending on application and the hardware environment. It is designed as a central repository for all the data of the organization and to meet the demanding requirements of distributed client/server computing. JAVA Since there are problems in C & C++ compilers that the compilers are expensive and time consuming to create, so an easier and more cost-efficient solution was needed. JAVA is a portable, platform-independent language that could be used to produce code that would run on a variety of CPU s under differing environments. JSP (Java Server Pages) Anything you can do with PHP, you can do with JSP; the reverse is not true. JSP is much more powerful, since it has access to all the Java libraries. PHP only has access to PHP libraries. JSP technology is created to support authoring of HTML and XML pages. It makes it easier to combine fixed or static template data with dynamic content. Apache Tomcat Web Server Tomcat is an open source product maintained by the Jakarta Project of the Apache Software Foundation. Tomcat replaces the old Java Servlet Development Kit (JSDK) that was previously provided by sun. It contains the class libraries, documentation, and run-time support that need to create and test jsp. III. SYSTEM DESIGN System Design is the first step in the development phase for any engineered product of system. System design is an activity concerned with making major decisions, often of a structural nature. It shares with programming a concern for abstraction information representation and processing sequences, but the level of details is quite different at the extremes. Design builds coherent, well-planned representation of programs that concentrate on the interrelationship of parts at the higher level and the logical operations involved at the lower levels. Software design is a process through which requirement are translated into a representation of the software. The system design is carried out in two phases. Preliminary Design Detailed design A. Preliminary Design This design aims to identify the modules that should be in the system, the specification of these modules and how they interact with each other to produce the desire results. At the end of preliminary design all major data structures, files formats, output formats, and major modules in the system and their specifications are decided. The tools that assist in Preliminary design process are Data Flow Diagrams (DFDs) and Entity- Relationship Diagram (ER-Diagram). Data Flow Diagram (DFD): Data Flow Diagram (DFD) depicts information flow, the transformation flow and the transforms that are applied as data move from input to output.. DFD of Automation of super market is given on Figure-1. Entity-Relationship (ER) Diagram: ER-Diagram is a primary tool, which helps in Database Design. The overall logical structure of a database can be expressed graphically by ER-Diagrams. ER diagram of Automation of super market is given on Figure-2. B. Detailed Design Input Design: Input design is the process of converting useroriented inputs to a computer-based format. The goal of designing input data is to make data entry easy, logical and free from errors. The data is fed into the system using simple interactive forms. The forms have been supplied with message so that the user can enter data without facing any difficulty. The data is validated during data entry and if any errors are found then appropriate error message and displayed. This ensures that only correct data is stored in the database. Sample Screen inputs are shown in Figure-3 53

Based on the proposed system, the database design was finalized. The main part of the database design is creation of tables and defining their relations. Figure 1. DFD of automation of Super Market Output Design: The objective of the output design is to convey the information of all that past activities, current status and to emphasize important events. The output generally refers to the results and information that is generated from the system. The output design of the system was accomplished keeping in mind the following objectives. Determine what information to display. Arrange the presentation of information in an acceptable format. Decide how to distribute the output to the intended recipients. Sample Screen outputs are shown in Figure-4. Database Design: Database Design is a process of organizing data pertaining to concerned organization in an orderly manner to provide easy access to the required information. ER-Diagrams and Normalization procedure are used in Database design. Figure 2. ER-Diagram of Super Market The tables for the SUPER database are in the normalization form. The data structure as follows. Data Structures Table: CUSTMAST Description: Details about the Customer Primary Key: Custcode 54

Data Size 1. Custcode Customer code,not Varchar 5 2. Custname Customer name Varchar 25 3. Custadd Customer address Varchar 25 4. Custcity Customer city Varchar 15 5. Pin Customer pin Varchar 6 6. Custtype Customer category Varchar 1 7. Custcred Customer credit Varchar 1 eligibility 8. Custcheq Customer can pay by Varchar 1 cheque 9. Custcrlmt Customer credit limit Decimal (10,2) 10. Custcrprd Customer credit peroid 11. Custdue Customer Amount due Decimal (10,2) 12. Custlttxn Customer Last transaction Datetime Table: VENDMAST Description: Details about the vendor Primary Key: Vcode Sl.No. Field Description Data Size 1. Vcode Vendor code,not Varchar 5 2. Vname Vendor name Varchar 25 3. Vadd Vendor address Varchar 25 4. Vcity Vendor city Varchar 15 5. Pin Vendor pin Varchar 6 Table: PRODMAST Description: Details about the Product Primary Key: Prcode 1. Prcode Product code,not Data Varchar 5 2. Prdesc Product description Varchar 25 3. Prdcat Product category Varchar 15 4. Prdqtyoh Product Quantity on hand 5. Prdunit Unit of measure Varchar 3 Size 6. Prdcost Current cost price Decimal (10,2) 7. Prdsell Current selling price Decimal (10,2) 8. Prdmax Product maximum quantity 9. Prdrol Product reorder level 10. Prdlstrxn Product last transaction date Datetime 11. Prodolsta Product reorder status Varchar 1 Table: INVHEAD Description: Details about the Cash bill/invoice Primary Key: Invno Data 1. Invno Invoice no,not 2. Invdate Invoice date Datetime Size 3. Custcode Customer code;foreign Varchar 5 key, Not null 4. Invvalue Invoice value Decimal (10,2) 5. Amtdue Amount due against invoice Decimal (10,2) Figure-3. Sample Screen inputs 55

Table: INVDETL Description: Details about the transaction details Primary Key: Invno Data Size 1. Invno Invoice number,not 2. Prcode Product code;foreign Varchar 5 key; Not 3. Invqty Invoice quantity Table: RECPHEAD Description: Details about the Receipt Primary Key: Recpno Data Size 1. Recpno Receipt number,not 2. Recpdt Receipt date Datetime 3. Vcode Vendor Varchar 5 code;foreign key; Not 4. Recpval Receipt value (10,2) Figure-4. Sample Screen outputs Table: PAYMENTS Description: Details about the Payments Primary Key: Payno Data Size 1. Payno Payment number,not 2. Paydt Payment date Datetime 3. Paymode Payment mode Varchar 2 4. Chqccno Cheque/Credit card Varchar 8 number 5. Bankcode Bank code Varchar 4 6. Paystat Payment status Varchar 1 7. Custcode Customer code;foreign key;not 8. Payamt Payment amount Decimal (10,2) Table: RECPDETL Description: Details about the receipt transaction Primary Key: Recpno Data Size 1. Recpno Receipt number,not 2. Prcode Product Varchar 5 code;foreign key; Not 3. Pqty Product quantity Table: BANK Description: Details about the Bank Primary Key: Recpno Data Size 1. Bankcode Bank code,not Varchar 4 2. Bankname Bank name Varchar 20 56

Table: PAYDETL Description: Preliminary details regarding the payments made by customer Primary Key: Payno Sl.No. Field Description 1. Payno Payment number,not 2. Invno Invoice number;foreign key; Not 3. Invamt Invoice amount deducted Data Size Decimal (10,2) IV. MODULES AND THEIR DESCRIPTION There are 18 modules are in the Automation of Super Market in which all the functional requirements are covers. (1) Addition of customer record module: In this module a new custom record is added along with various details required to be maintained. (2) View of customer record module: In this module, detail of a particular customer whose code is specified by the user is displayed from the customer master file. (3) Modify the customer records: In this module a particular record of customer master file is modified or changed in the customer master file. (4) Deletion the customer records: In this module the details of a particular customer whose code is specified by the use is deleted and then the master file is updated. (5) Product-Addition module: In this module a record of a new product is added along with various details required to be maintained. (6) Product-View module: In this module necessary details of a particular product is displayed whose code is specified by the user from the product master file. (7) Product-Modify module: In this module a particular record of the product master file is modified or changed. (8) Product-Deletion module: In this module a details of a particular product whose code is specified by the user is deleted. (9) Vendor-Addition module: In this module a record of a new vendor is added along with various details required to be maintained. (10) Vendor-View module: In this module necessary details of a particular vendor is displayed whose code is specified by the user from the vendor master file. (11) Vendor-Modify module: In this module a particular record of the vendor master file is modified or changed. (12) Vendor-Deletion module: In this module, a detail of a particular vendor whose code is specified by the user is deleted. (13) Vendor-Transaction module: In this module transaction held up with vendor is recorded. The details of the receipts transactions are then updated in the receipt book. (14) Customer Transaction module: In this module the payment made by the customer is recorded. The details of the payment transaction are then updated into the payment database and payment details database. (15) Invoice-view module: In this module the invoice of the cash bills entries made in the invoice books is viewed. (16) Payment-view module: In this module, details of the payments made to different vendors are viewed. (17) Receipt-View module: In this module all the details of the receipts receive from the different customer is displayed. (18) Report Generation module: In this module all the reports are generated like Daily Sales reports, Credit-Card Transaction reports, Non-moving Items reports, Over-Stock items reports, Re-order level reports, Over-due reports 57

V. VALIDATION CHECK, IMPLEMENTATION AND MAINTENANCE, TESTING, SYSTEM SECURITY MEASURES Validation check Validation succeeds when software functions in a manner that can be reasonably expected by the customer. This system use a process called alpha and beta testing to uncover errors that only the end-user seems able to find. Implementation and maintenance There are three aspects of Implementation, they are: Users Training: The users are given training about, computer hard wares, software and languages. Conversion: Conversion is the process of converting the old system into a new one as we are changing the present manual system into the newly computerized system. Post Implementation: The post implementation review will be conducted later after the complete implementation of the system at the client side. Software Maintenance traditionally denotes the process of modifying a software product after it has been delivered to the customer. Testing The Testing techniques applied to this software are White box Testing White box testing is a test case design method that uses the control structure of the procedural design to derive test cases. Black box Testing Black box testing focuses functional requirements of the software. It derives sets of input conditions that will fully exercise all requirements of a program. System Security Measures Security of data is of paramount importance. It is an irreplaceable asset and it is vital in enterprise application. During online processing of data various security functions should be enforced at different levels. The online system uses to client-server database in which discretionary security mechanism and mandatory security mechanism is effectively implemented. The discretionary access control is based on the granting and revolving of privileges. The mandatory access control is especially used to maintain multilevel security. VI. CONCLUSION At the end of this project, we hope that, the system will provide a full proof Automation of a Super Market. I expect that, the system will fulfill all the requirements, inquiries of any Super Market even if they are very small or large number of transaction occurs. So as per my knowledge the procedure and methodology will satisfy all the needs/requirements. So it can be properly implemented to the best of expectation and strategies. In future we can use it in ernet also. We can make another nice project without creating a new project. VII. REFERENCES [1] Segre, L.M.; Bastos, R.M., "Electronic commerce: creating competitive opportunities in Brazilian supermarkets," Management of Engineering and Technology, 1999. Technology and Innovation Management. PICMET '99. Portland ernational Conference on, vol.1, no., pp.194 vol.1,, 1999. [2] Irene Yousept, Feng Li,(2004):Online Supermarkets: Emerging Strategies And Business Models In The UK." Proceedings of the 17th Bled ecommerce Conference Herbert Schild, The Complete Reference Java 2, 5 th ed. Tata McGraw-Hill Education, 2002. [3] Roberts, M., Xu, X. M. and Mettos, N., (2003): ernet Shopping: Supermarket Model and Customer Perceptions. Journal of Electronic Commerce in Organisations Vol. 1, No. 2 pp. 32-43. Phillip Hanna, JSP 2.0 Complete Reference, 2 nd ed., Tata McGraw-Hill Education, 2003. [4] http://www.scribd.com/doc/27828662/abstra CT-the-Project- %E2%80%9Csupermarket%E2%80%9D-Deals- With-The [5] http://www.studymode.com/essays/final-report- Hardware-Project-1443938.html [6] https://domino.fov.unimb.si/proceedings.nsf/0/14a2c9e1e988dccac1256 ee000272c96/$file/03yousept.pdf 58