DEPARTMENTAL STORE MANAGEMENT SYSTEM

1. SYNOPSIS
1.1 Title of the Project:
Departmental Store Management System A department store is a retail establishment which specializes in selling a wide range of products without a single predominant merchandise line. Department stores usually sell products including apparel, furniture, appliances, electronics, and additionally select other lines of products such as paint, hardware, toiletries, cosmetics, photographic equipment, jewellery, toys, and sporting goods. Certain department stores are further classified as discount department stores. Discount department stores commonly have central customer checkout areas, generally in the front area of the store. Department stores are usually part of a retail chain of many stores situated around a country or several Countries. In other words, a departmental store is a large retail store suffering a variety of merchandise and services and organized in separate departments. The Departmental Store Management System is based on the departmental store, which keeps the track of Inventory, Sales, Purchase & personnel. The system is Management Oriented. This system gives the management an efficient way to handle their main operational areas such as customer care, inventory control, point of sales & analysis, Profits.

1.2 Problem:
In the departmental stores most of the work is done manually by maintaining registers. This involves many limitations such as:  Increases the paper work  The time to access the data increases  Chances of Information Leakage or Loss of Information increases  Maintaining records is not Integrated  Duplication of data They also use DOS based systems with monotonous Look & duplication of data having many gaps & inefficiency in forecasting due to batch process or lack of information due to either manual systems or old software. So, there is a Lack of Tools for manipulation of data.

1

DEPARTMENTAL STORE MANAGEMENT SYSTEM

1.3 Purpose of the Project:
Departmental store is a place where we get all our daily use products. These products are the basic requirements such as clothes, utensils, grocery, toys, watches etc. From the administrator point of view, the management of these products is not an easy job. Since they need to keep track of the products, their various suppliers, the customer details, their employees etc. All these jobs are done mostly manually or using some old software.

1.4 Scope & Objective of Project:
The project aims to develop software which will store data about their different products, their manufactures, product’s Inventory status, customer records and even the record of their employees. This system provides accounting, inventory, invoicing information in integrated fashion, preferably with Graphics User Interface (GUI). The objective of the project is to create a system that:  Provides Security to the data  According to the user, provides the relevant data  Handles the inventory, accounting & employee information  Auto Checking the stocks, Performance of the Employee  Less prone to errors  Efficient data storage that will reduce the redundancy of data  Less chances of information Leakage

1.5 System Architecture:

Fig 1.1

2

DEPARTMENTAL STORE MANAGEMENT SYSTEM

1.6 Hardware and Software to be used:
Front End: Visual Basics 6.0 Back End: MS Access Hardware Requirement: Minimum 10GB HDD Processor Type P-II & onwards Software: Operating Systems Windows98 & onwards

1.7 Modules:
Inventory Sales & purchase Employee details

1.8 Conclusion:
Here we have tried to develop a software that will help the administrator to have a quick access to all the information flow in the departmental store.

3

efficient and robust system that will handle all transactions related to the store. It sells a variety of different products like appliances cosmetics. INTRODUCTION 2. toys. etc.DEPARTMENTAL STORE MANAGEMENT SYSTEM 2. dvd’s. photographic equipment.e. jewellery.1 Organization Profile Apna Bazar is a reputed departmental store which specializes in selling a wide range of products without a single predominant merchandise line. Such a market carries large number of transactions on a daily basis like sale of various products. Departmental Store Management System will record details of all products and information relating sales and current stock of those products. The system is Management Oriented. This system gives the management an efficient way to handle their main operational areas such as customer care.2 Introduction to the Project: The main aim of developing departmental store management system is to build a user friendly. inventory control. buying these products from suppliers. point of sales & analysis. . Profits. making payments to the supplier etc. All the information will be stored in consistent and structured format which will allow easier retrieval of data. The DSMS i. recognizing goods that are need to be ordered. cd’s. 2. books. eatables. 4 . fashion accessories. and sporting goods clothes.

the proposed system is not developed) for a project to be judged feasible.2. To assure this one mist estimate following:  If the Organization has adequate cash flow for funding the development  The cost to conduct a full system investigation  The cost of hardware and software for the class of application being considered. Understanding the system properly so that all it’s problems are identified correctly. even all the various way to implement the alternatives. Also.2 Feasibility Study A feasibility study is the study of positive possibilities of the project. their sales. Developing a software the will be useful to the store administrators. SYSTEM STUDY & ANALYSIS 3. The different types of feasibility are as follows:     Economic feasibility Operational feasibility Technical feasibility Scheduled & Resource feasibility 3. payments etc.1 Economic Feasibility Higher level of automation most often requires more funds. Hence based on the hardware and software specification a desirable alternative costs and benefits to see if the investment made in creating / developing a new system is costlier or more beneficial Financial benefits must equal or exceed the costs. 5 .  The benefits in the form of reduced costs or fewer costly errors.1 Problem Definition: Development of user friendly departmental store database management system that provides solution for storing product information.e. orders and delivery information. If any one of these issues appears infeasible the decision must be reconsidered. it must pass all these tests. total stocks. customer accounts information. 3. It is also measure of how beneficial or practical development of information system would be to an organization.DEPARTMENTAL STORE MANAGEMENT SYSTEM 3. identifying all the alternatives that exists to achieve our objectives with respect to modifying the system.  The cost if nothing changes (i.

 Level of computer competency.2. The issues to be taken into concern are:  Corporate Culture.  Revisal of old. 3. Thus in the presence of required hardware.3 Technical feasibility The necessary software required for the development of admission & student profile systems were:  Visual Basic 6. Every company has its own culture and new system should fit the company culture.DEPARTMENTAL STORE MANAGEMENT SYSTEM 3. It has been designed to be pretty intuitive. Business functions are reengineered to achieve broader scope and higher level of automation. also there is required expertise for handling system.0  Microsoft Access The above as well as required hardware already available in the firm. software the proposed system is technically feasible.  Change of job responsibility.2 Operational Feasibility A system with an easy interface will always help the user to use the system. The new system has completely user friendly interface.  Loss of control on employee by staff/management.2. longstanding work procedures.  The nature & level of user involvement in the development & implementation of system. 6 .  It is usually a practice to include people trained in organizational behavior to assist in managing these changes. Manual processes too are modified.  Loss of employment due to increased automation. so that even an inexperienced person can easily handle the system.

e. Whenever the upper management indicates that their has to be a change in the system then the schedule has to be adjusted again and the schedule is revised. which is invariably revised to suit use requirements. Schedule feasibility : It is measure of how reasonable the project schedule is Are the deadlines reasonable? Can the deadline be extended? Is the deadline desirable or compulsory if yes how much? Resource Feasibility: It is measure of availability of system resources Availability of people Do they have necessary skill? Availability of computing facilities Availability of support staff Availability of physical worksite For our system we discussed the schedule of the project it took 2 days for arranging the schedule also we have made research on the user requirements and what is the flow actually user wants. technician and user have to be managed. Their skills have to be continuous & updated & revised.2. analysts. It is the schedule makes to reach the prescribed deadline. the primary resource is the team member and their designation i. In the resource feasibility. This is carefully monitored. 7 .4 Scheduled & Resource feasibility The Schedule of the project is actually the periodic progress of the project.DEPARTMENTAL STORE MANAGEMENT SYSTEM 3. A new system variably has less capability than the organization ultimately desires.

3. 3. The output of this page results in model of system.3 SYSTEM ANALYSIS The phase is detailed appraisal of existing system.DEPARTMENTAL STORE MANAGEMENT SYSTEM 3. This appraisal includes how the system works & what it does.  Then we studied the config of database we noted the difficulty of that system which motivated them to have new system.  Then we analyzed the format of the report generated by that system. It also include finding out in more detail what are the problems with system & what user requires from a new system or any new changes in system. System study helps in finding different alternative for better solution.1 SYSTEM STUDY: It is always necessary to study & recognize the problem of existing. The phase also contains the detail set of user requirement & this requirement are used to set objectives for a new system. we collected all the information which they wanted to store . which will help in finding out the requirements for the new system. 8 . The project study basically deals with different operation & steps:      Data Gathering Study of Existing System Analyzing problem Studying various documents Feasibility study for further improvement Following are steps taken during the initial study:  Initially. The model describes the system function & data & system information flow.

3. electronics. This involves many limitations such as:           Unorganized data Error prone data Tedious calculation for user Time delay in calculating & generating reports Complications in analyzing stored data Poor report generation Increases the paper work Chances of Information Leakage or Loss of Information increases Maintaining records is not Integrated Duplication of data They also use DOS based systems with monotonous Look & duplication of data having many gaps & inefficiency in forecasting due to batch process or lack of information due to either manual systems or old software.DEPARTMENTAL STORE MANAGEMENT SYSTEM 3. making payments to the supplier etc.1 Limitations Of Current System: In the departmental stores most of the work is done manually by maintaining registers. Also the information stored on paper is not reliable and retrieval of any data becomes inconvenient and time consuming. and sporting goods clothes.4 Current System: A department store is a retail establishment which specializes in selling a wide range of products without a single predominant merchandise line. So. Such a market carries large number of transactions on a daily basis like sale of various products. photographic equipment. books. A departmental store is a store which sells a variety of different products like apparel. dvd’s. etc.4. eatables. appliances. toys. cd’s. there is a Lack of Tools for manipulation of data. fashion accessories. recognizing goods that are need to be ordered. cosmetics. This leads to wastage of a lot of time. Till recently. and additionally select other lines of products such as paint. effort and space. buying these products from suppliers. all such information was stored in the form of paper. jewellery. hardware. toiletries. Hence it becomes difficult to manage such vast amounts of information by the current manual system. furniture. 9 .

Store information about delivery of orders & their payments. Integration of all functions in to one system. it’s supplier information & their sales.  Also the system is intended to take very few inputs from the user.  The developed system will also print bills and reports and maintain various transactions of the super-market.5.1 Advantages of Proposed System:           User friendly. Remove inconsistency of data.  It will have a comfortable and user friendly GUI.5 Proposed system: The proposed system may include following features:  Creating a database for the stores containing the information present with them on the paper in the existing system. Security of data.  The user interface will be designed using VB 6. Production of bills.0 and database will be implemented in MS-ACCESS. 3. Store various product information. 10 . Remove redundancy of data. Manage stock of all products.  Access to database will be based on logon-id and password. Different person will have different login-id and a distinct set of access rights. accurate and robust system. Handle order placing and delivery.DEPARTMENTAL STORE MANAGEMENT SYSTEM 3.

and maintenance.1 WATERFALL MODEL The WATERFALL MODEL demands a systematic. coding. testing. It includes the following steps:       Requirement Gathering Analysis Design Coding Testing Maintenance 11 . 4. SYSTEM DEVELOPMENT We have used the waterfall model for developing the system. sequential approach to software development that begins at the system level and progresses through analysis. design.DEPARTMENTAL STORE MANAGEMENT SYSTEM 4. The Waterfall model flows from top to bottom.

We discard the unnecessary requirements & only consider the relevant requirements. Analysis: After gathering all the requirements from the user. we gathered information from the various developers and users to know about the existing system. identify whatever requirements are known.DEPARTMENTAL STORE MANAGEMENT SYSTEM Fig 4. we need to distribute the various requirements that we have already collected.1 Requirement Gathering: The works begins with the information gathering. Also some requirements that have not been considered but are very much needed also need to be discovered to avoid changes in the project in the later stages. Design: This step focuses on four distinct attributes of the program:     Data Structure Software Architecture Procedural Detail Interface Characterization 12 . Developer and customer meet and define the overall objectives for the software. and outline areas where further definition is mandatory. In our software development process. This will help us to develop a proposed system.

On the Entity-Relationship Diagram:  Rectangles represent data entities  Lines connecting the rectangles show the relationships among data entities.0 language.  Ellipse represents the attributes of the entity.2 E-R Diagram An ER-Diagram (Entity Relationship Diagram) is a graphical model of the data needed by a system. conducting testes to uncover errors and ensure that defined input will produce actual results that agree with required results. 4. That means. If design is performed in a detailed manner. which in turn used for the coding purposes. coding can be accomplished mechanistically. It is produced in structured analysis methods. The model used to define the data storage requirements is called the Entity-Relationship Diagram. The design process is documented and become a part of the software configuration. For coding purposes we used Visual Basic 6. Coding: In the coding process the design must be translated into a machine-readable form. This included the entities about which information is stored and the relationship among them. Maintenance: After all of these processes. their attributes. and the relationships among the data entities. ensuring that all statements have been tested. and on the functional externals. Data storage requirements include the data entities. in a design process we designed the form layouts of the system. For the Departmental Store: 13 .DEPARTMENTAL STORE MANAGEMENT SYSTEM The design process translates requirements into a representation of the software that can be assessed for quality before coding begins. The traditional approach to system development places a great deal of emphasis on data storage requirements for the new system. It is required because of the errors that have been encountered in the system or because the customer requires functional or performance enhancements. the maintenance of the system takes into consideration. Testing: The testing process focuses on the logical internals of the software. that is.

It is a weak entity set. Each product is identified by its product-id. product-id. Address. Customer may have accounts with the store for their purchasing purposes. It stores each customer’s name and address where the customer lives. Phone_no. salary of each employee. thus. Phone_no. Each branch is located in a particular area and is identified by a unique name. Hire_Date. Gender. Each supplier is identified by its supplier-id. 14 .  The EMPLOYEE entity set. Cname.  The STOCK entity set. location. Purchase.  Employees of the departmental store are identified by their employee-id values. Address and Phone_no. price and replaced. Address.  The SUPPLIER entity set. Order_Id. It also keeps track of the employee’s start date and. target and sales. The store monitors the assets of each branch. quantity. Salary. supplier-id.  The CUSTOMER entity set. Date of Birth. with attributes Emp_Id.  The departmental store also keeps the information of the suppliers. with attributes supplier-id. Branch_Id. supplier-name.  Customers of the departmental store are identified by their customer-id values. length of employee. and on the designer’s own analysis of the organization. category. product-id. with attributes Emp_Id.  The departmental store also keeps the information of all of the inventories. manager. with attributes Cust_Id. product-id. with attributes branch no.  The DAMAGES entity set. Position. with attributes supplier-id.DEPARTMENTAL STORE MANAGEMENT SYSTEM DATA REQUIRQMENTS: The data requirements process may be based on interviews with the database users. The major characteristics of the departmental stores are:  The departmental store is organized into branches. The management stores the name. addresses. quantity and pay rate. address and product-id that the supplier can supply. position. Total_Amt and Balance. ENTITY_SET DESIGNATION: From the characteristics of the data requirements we begin to identify entity set and their attributes:  The BRANCH entity set. It also stores the name. Ename.

DEPARTMENTAL STORE MANAGEMENT SYSTEM RELATIONSHIP SETS DESIGNATION: The relationship sets designation defines the relationship among the entity sets and mapping cardinalities:  GIVES ORDER.  WORK FOR. a one-to-one relationship set between employee and branch. E-R Diagram 15 .  CHECK TRANSACTION.  ORDER SUPPLIER. a one-to-many relationship set between employee and stock. a one-to-one relationship set between damages and employee.  CHECK FOR. a many-to-one relationship set between supplier and employee. a many-to-one relationship set between customer and employee.

2 4.DEPARTMENTAL STORE MANAGEMENT SYSTEM P C A d d n r a m e a i d id G O o r i d P T iv e s r d e r t y p a m t E E id n a m A e d d rP B i d h n o S D a l O P o s B w f o o r B r k s r n o L o c M a n c u id s t o m O B S r a n c h B a l C e r E m p l o y e e a l e s T a r g e t P h n o D R o r d e r s u p l a m e p g A o n v a i r o t g iv e s o r d e r P id c h k f o r C h k t r a n S i d S S u p p l i e r A d d u p d t u p d t d e l n a m e P h n o S id S n a m P e i d Q P t C t y a t e A d d r Q t y S id C i d S n S E n a c k s x p r y W a y r t t y S n a m e C a m e a t e T a m P a y Q t r t P a y r Ct a t e D a m a g e s S i d V r t e g _ P i d F rG u r t o P id S id s s a r y U C a t e P C n a m a t e e t e n s i l sS i d a y rT t y P a y P id P R r i e p l T S id id Q t y P a y q t y y p p n P id e Q t y S T Q o y s t y P S a m S id id S n a m e P M W e d i c i n e S r t id n a m P i d e H C o s i e r y P a y C r t l o i d S n t h e s Q P a m t y t E S c o l o r id e x p r y a t e Q P t y S a y r t C a t e Fig 4.3 Schema Diagram: 16 .

4 Data Flow Diagram 17 .DEPARTMENTAL STORE MANAGEMENT SYSTEM Fig 4.3 4.

The context diagram is useful for showing boundaries. showing the system in “context” but it does not show any detail about the processing that takes place inside the system.4. The context diagram provides a good overview of the scope of the system. External agents that supply or receive data from the system are outside of the system scope.DEPARTMENTAL STORE MANAGEMENT SYSTEM 4. The system scope is defined by what is represented within single process and what is represented as an external agent. The diagram shows the external entities of the system & how the data that flows through the system. The context diagram is simply the highest-level DFD. with the whole system represented as one process. Everything else is inside the system scope. This helps in determining the basic functionalities. The context diagram for the departmental store is shown below. Context Level Diagram (Level 0) 18 . The inputs & outputs of the store are shown in the fig.1 Context Diagram A DFD (Data Flow Diagram) that summarizes all processing activity within the system in a single process symbol is called Context Diagram. Data stores are not usually shown on the context diagram because all of the system’s data stores are considered to be within the system scope. A context Diagram is a DFD that describes the highest-level view of a system are shown in own diagram.

2 Data Flow Diagram (DFD) 19 .DEPARTMENTAL STORE MANAGEMENT SYSTEM S S a l e s h R / M e o p d o r t i f yS e a r c aS l ue p s p M i e r a n a l S P l a c e o r d e r f o r C u s t o m e e a r r c h / M o d i f y P r o d u c t C h e c k A v a i l a b l e S t o c k D e l i v e r y R e p o O r t r d P a y e r m e R e c e p t i o R P e a n i s t c e y m i p t e f o n t r C f o r p t o M a n S o ym s u s t S C u s t o D e a r t m e r e a g e m t e m e r m e r n t a l U n a v S a it l o a cb kl e e n t E m p l o y e e D e t a i l A t t e n R d ea cn oc re d P S e a r c a y h / A s l i p d d E mC p l le o r y k e e Fig 4.4 4.4.

3 Fragmented DFD A DFD that represent the system response to one event within a single process symbol is called DFD fragment. 4. End Users. The analyst usually creates DFD fragments on at a time. Each DFD fragment is a self-contained model showing how the system responds to a single event. focusing attention on just part of the system.DEPARTMENTAL STORE MANAGEMENT SYSTEM The traditional approach to information system development describes activities as processes carried out by or computer. Everyone working on a development project can see all aspects of the system working together at once with DFD. Data Flow Diagram 20 . external agents. A DFD fragment is created for each event in the event list (expanded into the event table). but the data flow diagram is the most commonly used process model. Each DFD fragment represents all processing for an event within single process symbol.4. and internal data stores. But the fragments show details of interactions between the process. processes. A graphical model that has proven to be quite valuable for modeling processes dependency diagram used in the Information Engineering approach and the workflow diagram used with business process reengineering. and data storage. management. Each DFD fragment shows only those data stores that are actually needed to respond to the event. A data flow diagram (DFD) is a graphical system model that shows all of the main requirements for an information system in one diagram: inputs and outputs. That is one reason for its popularity. The DFD is also easy to read because it is graphical model. and all information systems workers typically can read and interpret the DFD with minimal training. The data stores used on a DFD fragment represent entities on the ERD.

5 Data Flow Diagram 21 .DEPARTMENTAL STORE MANAGEMENT SYSTEM (Level-1) Fig 4.

6 Data Flow Diagram 22 .DEPARTMENTAL STORE MANAGEMENT SYSTEM (Level-2) Fig 4.

7 Data Flow Diagram 23 .DEPARTMENTAL STORE MANAGEMENT SYSTEM (Level 3) Fig 4.

8 4.DEPARTMENTAL STORE MANAGEMENT SYSTEM (Level 4) Fig 4.5 Structure Chart 24 .

9 Factoring of INPUT Module 25 .P ro d G S e t S t o c k u p p l i e r f r o m T r a n s a c t i o n P E a y t so l i p m p l o y e e D C e l i v e r y t o u s t o m e r Fig 4.P i a i n Pa lip y s B il l.DEPARTMENTAL STORE MANAGEMENT SYSTEM First Level Factoring: M Q ty d .

DEPARTMENTAL STORE MANAGEMENT SYSTEM G S e k d oc ta i l e t S t o c k u p p l i e r f r o Q ty .P ro m d St S u p p l i e r D e t a i l O r d e r U p d a t i n g S t o r e i n S t o c k Fig 4.10 Factoring Of TRANSFORM Module: 26 .

11 4.6 FLOW CHARTS Flow Chart For LOGIN : 27 .DEPARTMENTAL STORE MANAGEMENT SYSTEM T r a n s a c t i o n E id . A R t t e n d a n e c o r d c e p l o S y a e l ea r y B i l l t o P a y s l i p t o C a l c u l a C i ou sn t o m E e m r p l o y e e t d .n am e P ay l B il P ay B i ll s lip s lip S t o c k C G e t E m B i l l a l c u l a t i o I nn f o .P i d R O r d e r A v a i l a b i l i t y o f S t o c k d e t a i l e c o r d Fig 4.P i Q ty Q ty .

DEPARTMENTAL STORE MANAGEMENT SYSTEM Fig 4.12 Flow Chart for Add/Delete/Update Product Information: 28 .

13 Flow Chart for Add/Delete/Update Supplier Information: Start Add/Updat e/Delete Display Supplier Master Display Supplier Master Form Stop Form 29 Enter New Supplier Add to Database Details Update/Delete from Enter the Supplier to Update/Delete Database .DEPARTMENTAL STORE MANAGEMENT SYSTEM Fig 4.

DEPARTMENTAL STORE MANAGEMENT SYSTEM Fig 4.14 Flow Chart for Add/Delete/Update Employee Information: 30 .

15 Flow Chart for Add/Update/Delete Customer Master: Update/Delete from Enter the Customer to Update/Delete Database Add/Updat Displaye/Delete Master Customer Display Customer Master Start Form Stop Form 31 Enter New Customer Add to Database Details .DEPARTMENTAL STORE MANAGEMENT SYSTEM Start Display Employee Master Form Enter the Employee to Update/Delete Add/Updat e/Delete Enter New Employee Details Update/Delete from Database Add to Database Display Employee Master Form Stop Fig 4.

16 Flowchart for Add/Update/Delete Damages: 32 .DEPARTMENTAL STORE MANAGEMENT SYSTEM Fig 4.

DEPARTMENTAL STORE MANAGEMENT SYSTEM Start Display Damages Form Enter the Damages to Update/Delete Add/Updat e/Delete Enter New Damages Details Update/Delete from Database Add to Database Display Damages Form Stop Fig 4.7 MENU TREE 33 .17 4.

18 4.8 GANTT CHART 34 .DEPARTMENTAL STORE MANAGEMENT SYSTEM Fig 4.

19 35 .DEPARTMENTAL STORE MANAGEMENT SYSTEM Fig 4.

Employee Confirmation Employee 4.9 Event Table: NO 1. 9. 6. Order_Supl Supplier Customer Products Order_Supl Confirm Change confirmation Change confirmation Change confirmation Change confirmation Order_Supl Supplier Customer Products Order-Supl 36 . 2. Order_Cust Confirm Order_Cust 5. 8. 7. EVENT Add Supplier Details Add Customer Details Add Employee Details Entry for Customer Order Entry for Supplier Order Update Supplier Details Update Customer Details Update Product Details Update Supplier Order Details TRIGGER New Supplier Entry New Customer Entry New Employee Entry New Order Entry New Supplier Order entry Update Supplier Update Customer Update Product Update Supplier Order EVENT TABLE Supplier Customer ACTIVITY Make new Supplier entry Make new Customer entry Make new Employee entry Update Customer Order Entry Update Supplier Order Entry Update Supplier Update Customer Update Product Update Supplier Order RESPONSE Confirmation Confirmation DESTINATION Supplier Customer 3.DEPARTMENTAL STORE MANAGEMENT SYSTEM 4.

15. 17. 16. 13. 11. 14. Program List: 37 . Update Customer Order Details Update Employee Detail Delete Customer Detail Delete Supplier Detail Delete Employee Detail Delete Products Detail Generate Bill Reports Generate Salary Sheet Update Customer Order Update Employee Delete Customer Delete Supplier Delete Employee Delete Products Produce bill report Produce Salary Sheet Order_Cust Employee Customer Supplier Employee Products Order_Cust Salary Sheet Update Customer Order Update Employee Delete Customer Delete Supplier Delete Employee Delete Products Report Generation Pay slip Generation Change confirmation Change Confirmation Delete Confirmation Delete Confirmation Delete Confirmation Delete Confirmation Bill Reports Pay slip Order_Cust Employee Customer Supplier Employee Products Customer Salary Sheet 5.DEPARTMENTAL STORE MANAGEMENT SYSTEM 10. 12.

frm frmcustinfo. 2. 10.frm frmsearch.frm frmutensils.frm frmordercust. 8. 17.frm) frmsplash.frm frmtoys.frm frmfruitveg. 20. 11.frm frmmedecine. 15.frm frmWelcomeMDI.frm frmcustadd. 5.No. 19.frm frmemp.frm Description Displays the splash Screen Login the software by user id & password Displays the MDI form with different menus Displays form with customers information Displays form for adding the customer information Displays the form for adding customers orders Displays forms with employees information Displays the salary information for the employee Search a specific employee Contains the information about various products Displays the information about glossary Displays the information about hosiery Displays the information about medicines Displays the information about snacks Displays the information about toys Displays the information about utensils Displays the information about fruits & vegetables Displays the information about damaged products Displays the form for adding damaged products Displays the form with suppliers information Displays the form for adding suppliers information 38 . 7. 9.frm frmsupl.frm frmhosiery.frm frmsalary. 13. 3 4.frm frmgross. Program Caption Departmental Login Welcome…. 6. 18.DEPARTMENTAL STORE MANAGEMENT SYSTEM Sr.frm frmlogin. 12.frm frmproductsclo. Customer_Info Customer_Add Order_Customer Employee_Info Salary_Sheet Search Products Glossary Information Hosiery Information Medicine Information Snacks Information Toys Information Utensils Information Fruits & Vegetables Damages Add_Damages Supplier_Info Supplier_Add Program Name (.frm frmsnacks. 14. 1. 16.frm frmadddamages.. 21.frm frmdamages.frm frmsupl.

frm Displays the form for adding orders given to the supplier Displays the form for adding supplier orders Displays the form for adding suppliers payments Displays form with order given to the supplier Displays the About Us form 6. 24.frm frmpayadd. 23. 26.frm frmpayment.TABLE STRUCTURE: 39 .frm frmabout. Order to Supplier Purchases done by Company Add a supplier payment Order_Supplier About us frmaddsuporder. 25.frm frmordersup.DEPARTMENTAL STORE MANAGEMENT SYSTEM 22.

3. 5. Cust_name: This field stores the name of each employee. 4.DEPARTMENTAL STORE MANAGEMENT SYSTEM Branch Table: Sr. Fields Cust_Id Cust_name Address Phone_no Total_amt Balance Required(Y/N) Yes Yes Yes No No No Type Text Text Text Double Currency Currency Key Primary Key Description: • • • • • • Cust_Id: This field stores the Ids of each customer. This field gives the information about the actual sales of each Branch. Total_Amt: This column gives the total purchases of employees. 2 3. This field stores the name of the locations of each branch. Customer: Sr. 6. Address: This field gives the addresses of each customer. which is unique to each one. 1. 4. Branches have different branch ID. Phone_No: This column stores the phone numbers of employees. 5. 2. Balance: This field stores the balances remaining for the customers .No. This field gives the ID of the Branch Manager. 6. if any.No. Fields Branch_No Location Manager Emp_Id Target Sales Required(Y/N) Yes Yes Yes Yes Yes No Type Number Text Text Text Currency Currency Key Primary Key Description: • • • • • • Branch_No: Location: Manager: Emp_Id: Target: Sales: This field stores the IDs of the various branches located in different areas. 1. This field gives the information about target sale of each branch. This field contains the name of the managers of the branch. Employee: 40 .

Date of Birth Position Hire_Date Salary Bill_No Purchases Required(Y/N) Yes Yes Yes Yes Yes No Yes Yes Yes No No No Type Text Text Text Text Text Double Date/Time Text Date/Time Currency Text Currency Key Primary Key Foreign Key Description: • • • • • • • • • • • Emp_Id: This field stores the Ids of the each employee. 8. Position: This column stores the positions of each employee. Fields Emp_Id Ename Branch_Id Gender Address Phone_No.No. Bill_No: This field stores the order id of the employee. 9. 2. 6. Branch_Id: This field stores the branch id of the employee. 1. 4. 12. Address: This store the information of the employees addresses. 11.No. 3. Ename: This field stores the name of each employee. Phone no: This field stores the phone numbers of the employees.DEPARTMENTAL STORE MANAGEMENT SYSTEM Sr. which is also unique to each other. Salary: This column stores the salary of the employees. Hire Date: This field stores the hiring date of each employee. Fields Required(Y/N) Type Key 41 . 10. Supplier: Sr. Date of Birth: It stores the birthdates of each employee. Purchases: This field gives the information about the total purchases of the employee. 7. 5.

No. 3.No. 6. Size: This field gives the various sizes of clothes available. 5. Fields Required(Y/N) Type Key 42 . Sup_Id: This field gives the supplier Ids of the product who took the order. Quantity: This field stores the total quantities of each clothes. Clothes: Sr. 3. Fruits_Veg: Sr. 1. This column stores the phone numbers of supplier. 2. Sname: This field stores the name of each supplier Category: This field stores the category of each clothes whether it is dress materials. which is unique to each one. 5. 4. This field gives the addresses of each supplier. 7. Color: This field gives the various of clothes available. shirts or anything else. Fields Prod_Id Sup_Id Sname Category Quantity PayRate Size Color Required(Y/N) Yes Yes No Yes No No No No Type Text Text Text Text Double Currency Text Text Key Primary Key Foreign Key Description: • • • • • • • • Prod_Id: This field stores the product Ids of each product. schemes. PayRate: This field stores the price of each dress material. 4.DEPARTMENTAL STORE MANAGEMENT SYSTEM 1. Supp_Id Sname Address Phone_No Reasonable Yes Yes Yes No Yes Text Text Text Double Text Primary Key Description: • • • • • Supp_Id: Sname: Address: Phone No: Reasonable: This field stores the Ids of each supplier. products in a profitable price. This field stores the name of each supplier. This field just tells that whether the supplier provides us with reasonable discounts. 8. saris. 2.

Quantity: This field stores the total quantities of each glossary. 3. This field gives the supplier Ids of the product who took the order. Hosiery: Sr. 7. 4.DEPARTMENTAL STORE MANAGEMENT SYSTEM 1. Total_Amt: This field contains the total amount of grossary available. 5. This field stores the price of each vegetable and fruits. Grossary: Sr. This field tells whether the product is fruit or vegetable. 5. Fields Prod_Id Sup_Id Sname Category Quantity PayRate Total_Amt Required(Y/N) Yes Yes Yes Yes No No No Type Text Text Text Text Double Currency Currency Key Primary Key Foreign Key Description: • • • • • • • Prod_Id: Sup_Id: Sname: Category: This field stores the product Ids of each product. 6. Prod_Id Sup_Id Sname Category Type Quantity PayRate Yes Yes No Yes No No No Text Text Text Text Text Double Currency Primary Key Foreign Key Description • • • • • • • Prod_Id: Sup_Id: Sname: Category: Type: Quantity: PayRate: This field stores the product Ids of each product. This field gives the supplier Ids of the product who took the order. 2. Fields Required(Y/N) Type Key 43 . 2. 4. 7. 6. This field stores the name of each supplier This field stores the category of each glossary whether it is rice.No.No. 1. PayRate: This field stores the price of each glossary. This field stores the total quantities of each vegetable and fruits. This field stores the name of each supplier This field stores the category of each vegetable and fruits. 3. dal or anything else.

2. 4. 8. 3. This field stores the name of each supplier This field stores the category of each product whether it is soap. This field gives the supplier Ids of the product who took the order. This field stores the name of each supplier This field stores the category of each medicine. 2. shampoo or anything else. 4. This field stores the total quantities of each product. 7. This field gives the information about the expiry date of each medicine. This field stores the price of each product. 6.No. Fields Prod_Id Sup_Id Sname Item_Name Quantity Weight PayRate Expiry Required(Y/N) Yes Yes No Yes No Yes No No Type Text Text Text Text Double Text Currency Date/time Key Primary Key Foreign Key Description: • • • • • • • • Prodid: Suplid: Sname: Item_Name: Quantity: Weight: PayRate: Expiry Date: This field stores the product Ids of each product. This field gives the supplier Ids of the product who took the order. This field gives the net wt. This field stores the price of each product. 3. 5. Medicine: Sr. Snacks: 44 . 1. whether This field stores the total quantities of each product.DEPARTMENTAL STORE MANAGEMENT SYSTEM 1. 5. Prod_Id Sup_Id Sname Category Quantity PayRate Yes Yes No Yes No No Text Text Text Text Double Currency Primary Key Foreign Key Description: • • • • • • Prod_Id: Sup_Id: Sname: Category: Quantity: PayRate: This field stores the product Ids of each product. 6. brush. of the product.

Utensils: Sr. This field stores the name of each supplier This field stores the category of each snacks product whether it is wafer. 3. Sup_Id: This field gives the supplier Ids of the product who took the order.DEPARTMENTAL STORE MANAGEMENT SYSTEM Sr. This field stores the total quantities of each snacks product. 1. 5. 4.No. chocolate. 8. 6. 7.No. Fields Prod_Id Sup_Id Category Quantity PayRate Required(Y/N) Yes Yes Yes No No Type Text Text Text Double Currency Key Primary Key Foreign Key Description: • • • • • • Prod_Id: This field stores the product Ids of each product. Quantity: This field stores the total quantities of each toy. 4. Fields Required(Y/N) Type Key 45 . 1. This field stores the price of each product Toys: Sr. biscuits or anything else. 2.No. 2. This field gives the supplier Ids of the product who took the order. PayRate: This field stores the price of each toy. Sname: This field stores the name of each supplier Category: This field stores the category of each toy. Fields Prod_Id Sup_Id Sname Category Weight Quantity PayRate Expiry Required(Y/N) Yes Yes Yes No No Type Text Text Text Double Currency Key Primary Key Foreign Key Description: • • • • • • Prod_Id: Sup_Id: Sname: Category: Quantity: PayRate: This field stores the product Ids of each product. 3. 5.

This field stores the total quantities of each product. 4. This field stores the date of the order. 5. This field gives id of the customer who placed the order. Order_Customer: Sr. 2. 2. This field gives the amount paid by each customer. Order Customer Product: 46 . 1. This field stores the price of each product. Prod_Id Sup_Id Category Quantity PayRate Yes Yes Yes No No Text Text Text Double Currency Primary Key Foreign Key Description: • • • • • • Prod_Id: Sup_Id: Sname: Category: Quantity: PayRate: This field stores the product Ids of each product. pan. This field stores the total amount of purchase of the customers. 5. This field stores the balances remaining for the customers.DEPARTMENTAL STORE MANAGEMENT SYSTEM 1. This field gives the supplier Ids of the product who took the order. plates or anything else. Fields Orderid Custid Order_dt Paying_type Total_amt Balance Amt_paid Required(Y/N) Yes Yes Yes No Yes No No Type Text Text Date/Time Text Currency Currency Currency Key Primary Key Foreign Key Description: • • • • • • • Orderid: Custid: Order_dt: Paying_Type: Total Amt: Balance: Amt Paid: This field stores the order id for each customer. 4. 3. 3. This column gives the information about the paying type of each customer whether it is based on cash or cheque. 6.No. This field stores the name of each supplier This field stores the category of each product whether it is spoon. 7.

1. This field stores the total amount of purchase of the customers. This field gives id of the supplier to whom order is placed . 4. 5. 2. Fields Order_Id Sup_Id Order_dt Paying_type Total_amt Balance Amt_paid Required(Y/N) Yes Yes No Yes No No No Type Text Text Date/Time Text Currency Currency Currency Key Primary Key Foreign Key Description: • • • • • • • Order_Id: Sup_Id: Order_dt: Paying_type: Total_Amt: Balance: Amt_Paid: This field stores the order id for each supplier. This field stores the price of each product. Order Supplier Product: 47 . Order_supplier: Sr. This field stores the balances remaining for the customers. This field stores the information about those product ids for which customer placed the order. This column gives the information for the total quantity of products of each customer. 4. This column gives the information about the paying type of each customer whether it is based on cash or cheque. 1. 2. 6. This field stores the date of the order.DEPARTMENTAL STORE MANAGEMENT SYSTEM Sr. Fields Order_Id Prod_Id Quantity PayRate Required(Y/N) Yes Yes Yes Yes Type Text Yes Double Currency Key Foreign Key Foreign Key Description: • • • • Order_Id: Prod_Id: Quantity: PayRate: This field stores the order id for each customer. This field gives the amount paid by each customer. 3.No. 3. 7.No.

This field gives id of the supplier to whom we need to contact. This field gives id of the damaged product This column gives total quantity of the damaged products. 2. 4. Fields Required(Y/N) Type Key 48 . This field gives whether the damaged products are replaced or not Salary Sheet: Sr. 2. 1. 5.No. This field stores the price of each product.DEPARTMENTAL STORE MANAGEMENT SYSTEM Sr. 1. 6. 3. 3. Fields Cust_Id Sup_Id Prod_Id Quantity PayRate Replaced Required(Y/N) Yes Yes Yes No No Yes Type Text Text Text Double Currency Text Key Foreign Key Foreign Key Foreign Key Description: • • • • • • Cust_Id: Sup_Id: Prod_Id: Quantity: PayRate: Replaced: This field gives id of the customer who have reported damages. 4. Fields Order_Id Prod_Id Quantity PayRate Required(Y/N) Yes Yes Yes Yes Type Text Yes Double Currency Key Foreign Key Foreign Key Description: • • • • Order_Id: Prod_Id: Quantity: PayRate: This field stores the order id for each customer This field stores the information about those product ids for which customer placed the order. This field stores the price of each product.No. Damages: Sr. This column gives the information for the total quantity of products of each customer.No.

Ename Emp_ID Basic _Salary Dearness_Allowance Travelling_Allowance Medical_Allowance Overtime Bonus Providend_Fund Gross_Salary Service_Charge Income_Tax Net_Salary Yes Yes No No No No No No No No No No No Text Text Currency Currency Currency Currency Currency Currency Currency Currency Currency Text Currency Foreign Key Description: • • • • • • • • • • • • • Emp_Id: Ename: Basic_Salary: employees. 9. 11. 2. 7. 4. This field stores the bonus given to employee. REPORT LIST 49 . 7. If any. 13. 12. 5. This field stores the basic salary given to all This field stores the dearness allowance decided for the employees This field stores the traveling allowance decided for the employees. This field stores the overtime given to employee. 8. This field stores the income tax paid by the employee. which is also unique to each other. 3. This field stores the name of each employee. This field stores the amount for the Providend Fund decided for the employees. This field stores the medical allowance decided for the employees. This field stores the Gross Salary given to the employees. 6. This field store the Net Salary given to the employee. This field store the charges for the various services provided by the company. Dearness_Allowance: Travelling_Allowance: Medical_Allowance: Overtime: Bonus: Providend_Fund: Gross_Salary: Service_Charge: Income_Tax: Net_Salary: This field stores the Ids of the each employee.DEPARTMENTAL STORE MANAGEMENT SYSTEM 1. If any. 10.

DEPARTMENTAL STORE MANAGEMENT SYSTEM

The system includes the following reports:     Sales Report Purchase Report Salary Sheet Report Customer Bill Report

8. SYSTEM TESTING

50

DEPARTMENTAL STORE MANAGEMENT SYSTEM

Testing plays a critical role in quality assurance for software. Due to the limitations of the verification methods for the previous phases, design and requirements faults also appear in the code. Testing is used to detect these errors, in addition to the errors introduced during the coding phase. Testing is a dynamic method for verification and validation, where the system to be tested is executed and the behavior of the system is observed. Due to This, testing observes the failure of the system, from which the presence of faults can be deduced. However, separate activities have to be performed to identify the faults.

8.1Approaches: Black-Box Testing:
In the black-box testing, the internal logic of the system under testing is not considered and the test cases are decided from the specification or the requirements. It is often called functional testing. Equivalence class partitioning, boundary value analysis, and cause effecting graphing are examples of methods for selecting test cases for blackbox testing. State–based testing is another approach in which the system is modeled as a state machine and then this model is used to select test cases using some transition or path based coverage criteria. State–based testing can also be viewed as grey-box testing in that it often requires more information than just the requirements.

White-Box Testing:
In white-box testing, the test cases are decided entirely on the internal logic of the program or module being tested. The external specifications are not considered. Often a criterion is specified, but the procedure for selecting test case is left to the tester. The most common control flow-based criteria are statement coverage and branch coverage, and the common data flow-based criteria are all-defs and all-uses. Mutation testing is another approach for the white-box testing that creates mutants of the original program by changing the original program. The testing criterion is to kill all the mutants by having the mutant generate a different output from the original program.

8.2 System Test Document (STD)
System Overview:
51

DEPARTMENTAL STORE MANAGEMENT SYSTEM

The software system consists of a desktop application in which the local machine maintains various databases. The system consists of various interrelated pages. The interconnections of the pages and the links on the pages have to be tested for proper interfaces between them. The databases on the server system have to be checked for consistency on different input values entered at the client system. The two versions released have to be checked separately.

Test Approach:
 The model used to develop the software is the waterfall model. So the testing phase comes only once in the entire lifetime of the project. Therefore it has to be intensive and as thorough as possible.  First and foremost we have to check the hardware interfaces. While checking the visual interface the interconnection and the links have to be checked. This will be done by going through various links and checking if the desired pages open up.  This will be followed by testing the database business layer interface. Here the interactions between the validation and query scripts and the database have to be checked.  Next we check the GUI and business layer interfaces. Here the form validation and scripts acting on the form come into the picture.  The inventory triggers have to be checked for. This includes testing whether the triggers are activated on reaching minimum levels or not.  This will be succeeded by integration testing. The individual models are integrated and tested for proper interface. This will require 3 days.  System testing will focus on system integration.  User acceptance will focus on the testing by the user and then giving an approval of the system.

Features to be tested:
 The hardware has to be tested to check whether the standard output values expected are satisfied or not. The test cases involved in this are as follows 52

the form validation is done without any bugs in it. • By entering skeptical data. 8.3 TEST CASES: Case 1 (Interface): 53 . The database also has to be checked for maximum possible entries which it can accept and handle. The various test case involved are • By entering wrong and invalid values • By entering values on the boundary. The database on the server side should be checked for any inconsistencies.DEPARTMENTAL STORE MANAGEMENT SYSTEM  To check the machine speed. So it need not be checked by the developers and testers.e. is the lookout of the customer and is not an element to be considered for testing. The various test cases involved are as follows: By entering values which are repeated to make the database inconsistent.  The input fields have to be checked whether only valid values are being accepted i.  The machine speeds of the client machine.  The entered values are not allowed and are out of bounds     Features not to be tested:  The data inputs on the screen in the different forms are the sole interest and information only known to the customer.  The software interface testing is to be done next in this section. which may result into better speed of the software. Here we have to test the various links which provide the interfaces between different pages.  To check the links which are dependent on the data entered. The test cases involved in this are as follows:  To check links which are independent of the data entered.

DEPARTMENTAL STORE MANAGEMENT SYSTEM

Purpose:
To check links which are independent of the data entered and to check the links which are dependent on the data entered.

Inputs:
In case of independent links there would not be any inputs whereas in case of dependent links the fields, the value of which decides the links are to be entered. Example of dependent links is the form entered which is to be validated before accepting the information into the database. The data entered will be valid and invalid as well as on the boundary. Independent links are the ones in which the links are given on the screen and the pages to which they jump is prefixed and does not change based on any input.

Expected Outputs & Pass/Fail criteria:
In case of independent links the prefixed pages to which the links are pointing should be checked. If the links are functioning properly then the test is passed. In case of dependent links on entering the valid input the output should be generated. In case of invalid input an error message should be displayed. This will indicate whether the test has been passed or failed.

Test Procedure:
The required fields are entered and the links are clicked on and the results are observed and noted down. The valid input is entered and the results are verified. The invalid input is entered and the results are verified. The boundary conditions are also checked and verified.

Case 2 (Database): Purpose:
54

DEPARTMENTAL STORE MANAGEMENT SYSTEM

The purpose of this test case is to check the capability of the database. It will verify the amount of data that can be handled as well as determine the dependability of the data.

Inputs:
The inputs to the software will be data which can prove to be inconsistent and can damage the dependability of the software. The data entered will be in voluminous quantities so that the capability of the database can be tested.

Expected Outputs & Pass/Fail criteria:
In case of skeptical data, if the inputs given cause inconsistency to the database, the system will fail this test case. Even if 1 out of 100 inputs cause inconsistency then the system will fail to clear the test. In case of stressing the system, if the system is able to handle the number of entries as specified in the requirement document then the test will be passed by the system.

Test Procedure:
Enter the data in such a way that the inputs have same time slots allotted or same usernames allotted. If the database accepts those then the system fails there itself. The same process will be carried out in case of each input field to check for consistencies. The data will be then entered in large quantities. If the database is capable of handling it without losing any access time then the database will pass the test. 5% level of tolerance is acceptable.

9. CONCLUSION

55

DEPARTMENTAL STORE MANAGEMENT SYSTEM

Here we have tried to develop a system that will synchronize the data stored at various places to be maintained at a single location with proper accessibility and security. The system will store the various records of different products, distributors and various transactions in a uniform format. Effective management will be done to maintain minimum inventory levels of food and other essential commodities. The user will get critical information as unavailability of a certain product or expiry of some goods beforehand. User can also make any updates to previously entered information and also delete any obsolete data which is not required anymore. Thus, we tried to provide the store administrator with an easy way to access his data.

10. CODING CONVENTION

56

11.DEPARTMENTAL STORE MANAGEMENT SYSTEM Variable Name Convention: Every variable has being named according standard convention. Function Naming Convention: Every function has been named starting with corresponding name with underscore sign separating two records to maintain consistency. There is no number allowed at the beginning of each variable. FORM LAYOUTS 57 . Table Naming Convention: Every table has being named with underscore sign in between two words.

frm): 58 .DEPARTMENTAL STORE MANAGEMENT SYSTEM The Splash Screen (frmSplash.frm) The LOGIN Form (frmLogin.

frm) 59 .DEPARTMENTAL STORE MANAGEMENT SYSTEM Main Form (frmWelcomeMDI.

frm) 60 .DEPARTMENTAL STORE MANAGEMENT SYSTEM Customer Master Form (frmcustinfo.

frm) The Text Boxes Checks for validation of the value that is entered Here it checks whether the entered number is character or not 61 .DEPARTMENTAL STORE MANAGEMENT SYSTEM Form that Add A New Customer (frmcustadd.

DEPARTMENTAL STORE MANAGEMENT SYSTEM 62 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM 63 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM 64 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM 65 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM 66 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM 67 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM 68 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM 69 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM 70 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM About Us Form 71 .

DEPARTMENTAL STORE MANAGEMENT SYSTEM Data Report For Employees Salary sheet 72 .

CODE: 73 .DEPARTMENTAL STORE MANAGEMENT SYSTEM 12.

Caption = inti & "%" End Sub FORM: frmLogin.Value = 100 Then Timer1.frm 74 .DEPARTMENTAL STORE MANAGEMENT SYSTEM FORM : frmSplash.Enabled = False frmLogin.Value = ProgressBar1.frm Dim inti As Integer ‘*********************************************************************** Private Sub Form_KeyPress(KeyAscii As Integer) Unload Me End Sub '********** SETS THE TIMER EVENT FOR THE PROGRESSBAR ************** Private Sub Timer1_Timer() ProgressBar1.Value + 1 If ProgressBar1.Show End If inti = inti + 1 lblno.

ListIndex = 1 And txtPwd.DEPARTMENTAL STORE MANAGEMENT SYSTEM '***THIS FORM RELATES TO THE AUTHORISED USER ONLY*** '*********IT PROVIDES SECURITY TO THE USER********** Private Sub cmdcancel_Click() Unload Me End End Sub ‘*********************************************************************** Private Sub cmdOk_Click() If cbouser.Show ElseIf cbouser.Text = "gudiya" Then frmWelcomeMDI.ListIndex = 0 And txtPwd.frm 75 .Text = "rose" Then frmWelcomeMDI.Show Else MsgBox "Incorrect Password" End If End Sub FORM : frmcustinfo.

TextMatrix(X. 2) txtcid = MSFlexGrid1.locked = True txtcname. 6) End Sub ‘*********************************************************************** ‘** LOCKS ALL THE TEXTS BOXES SO THAT NO EDITION CAN BE DONE ** Public Sub locked() txtaddr.locked = True txtpur.TextMatrix(X. 4) txtpur = MSFlexGrid1.locked = True txtbalance. X As Integer Dim cnn1 As Connection Dim rs As New ADODB.Recordset Dim FLAG1 As Boolean Dim cnt As Integer Dim cur_record As Integer Dim r As String ‘*********************************************************************** Public Sub moves() txtcname = MSFlexGrid1. 1) txtaddr = MSFlexGrid1.TextMatrix(X. 3) txtph = MSFlexGrid1. 5) txtbalance = MSFlexGrid1.DEPARTMENTAL STORE MANAGEMENT SYSTEM '****** THIS FORM DISPLAYS ALL THE RECORDS ************ '******* PRESENT IN THE CUSTOMER DATABASE ********* '******* ALSO ALLOWS VARIOUS OPERATIONS TO BE ********* '********** PERFORMED ON THE RECORDS ***************** Dim r1 As Integer.locked = True txtcid.TextMatrix(X.TextMatrix(X.TextMatrix(X.locked = True txtph.locked = True End Sub '******** UNLOCKS ALL THE BOXES FOR FURTHER EDITION *********** 76 .

Show frmcustadd.locked = False txtph.Rows .locked = False txtbalance.Caption = "Customer Add" Exit Sub SaveErr: MsgBox Err.DEPARTMENTAL STORE MANAGEMENT SYSTEM Public Sub unlocked() txtaddr.Text = rs!Address txtbalance.Text = FormatCurrency(rs!Total_Purchase) End Sub ‘*********************************************************************** Private Sub cmdadd_Click() On Error GoTo SaveErr: Unload Me frmcustadd.Text = " Record " & X & " Of " & j End Sub *'****** DISPLAY RECORDS IN THE APPROPRIATE BOXES**************** Public Sub display() txtaddr.Description End Sub Private Sub cmdback_Click() Unload Me 77 .locked = False txtcid.locked = False End Sub ‘*********************************************************************** Public Sub setrecordcount() j = MSFlexGrid1.Text = rs!Cname txtph.2 txtrecord.locked = False txtcname.locked = False txtpur.Text = rs!Phone_no txtpur.Text = rs!Cust_Id txtcname.Text = FormatCurrency(rs!Balance) txtcid.

Visible = True cmdedit.DEPARTMENTAL STORE MANAGEMENT SYSTEM frmWelcomeMDI.Visible = False ' **** THINGS TO BE DISPLAYED IN THE LAYOUT ***** cmddelete.Visible = True cmdrefresh.Visible = True rs.Visible = True cmdadd.Visible = True cmdback.Visible = False cmdcancel.Visible = True cmdsearch.Show End Sub Private Sub cmdcancel_Click() locked rs.Open ' **** THINGS NOT TO BE DISPLAYED IN THE LAYOUT **** cmdupdate.Close End Sub ‘*********************************************************************** Private Sub cmdclose_Click() End End Sub Private Sub cmddelete_Click() 78 .

" .RowSel Do While i > 1 If Not . "DELETE RECORD" Else FLAG1 = False End If If FLAG1 = False Then s1 = MsgBox("Are You Sure You Want To Delete Record". You Can't Delete This Record. _ vbCritical.MoveNext If .RecordCount = 1 Then FLAG1 = True MsgBox "This Is Last Record.EOF Then .MovePrevious End If End If End If End With rs.MoveNext i=i-1 Loop i = MSFlexGrid1.EOF Then .RowSel .Close Exit Sub DeleteErr: MsgBox Err.Open With rs If . _ "DELETE RECORD") If s1 = vbYes Then i = MSFlexGrid1. vbQuestion + vbYesNo.".DEPARTMENTAL STORE MANAGEMENT SYSTEM On Error GoTo DeleteErr rs.Delete MsgBox "Record Is Successfully Deleted.Description End Sub Private Sub cmdedit_Click() 79 .

Visible = False cmdsearch.Visible = False cmdadd.Close End Sub ‘*********************************************************************** Private Sub cmdfirst_Click() On Error GoTo FirstErr X=1 moves setrecordcount Exit Sub FirstErr: MsgBox Err.Open '**** THINGS TO BE DISPLAYED IN THE LAYOUT **** cmdupdate.Visible = False cmdedit.Visible = False cmdback.Description End Sub 80 .Visible = True ' **** THINGS NOT TO BE DISPLAYED IN THE LAYOUT **** cmddelete.Visible = False rs.Visible = True cmdcancel.DEPARTMENTAL STORE MANAGEMENT SYSTEM unlocked rs.Visible = False cmdrefresh.

Close End Sub Private Sub cmdprevious_Click() On Error GoTo PreviousErr 81 .Description End Sub ‘*********************************************************************** Private Sub cmdrefresh_Click() rs.Requery rs.DEPARTMENTAL STORE MANAGEMENT SYSTEM Private Sub cmdLast_Click() On Error GoTo LastErr X = r1 moves setrecordcount Exit Sub LastErr: MsgBox Err.Description End Sub ‘*********************************************************************** Private Sub cmdnext_Click() On Error GoTo NextErr If (r1 > X) Then X=X+1 moves setrecordcount Else X=1 moves setrecordcount End If Exit Sub NextErr: MsgBox Err.Open MSFlexGrid1.Refresh rs.

Fields(1) = r Then MsgBox "Record Found" Call display End If rs.Open r = InputBox("Enter Customer's ID Or Customer's Name You Want To Search..EOF If rs.MoveNext Wend rs. _ "Get Information") rs.MoveFirst While Not rs.DEPARTMENTAL STORE MANAGEMENT SYSTEM If (r1 >= X) Then X=X-1 moves setrecordcount If X = 0 Then X = r1 moves setrecordcount End If End If Exit Sub PreviousErr: MsgBox Err.Description End Sub Private Sub cmdupdate_Click() On Error GoTo UpdateErr 82 .Close Exit Sub SearchErr: MsgBox Err..Description End Sub ‘*********************************************************************** Private Sub cmdsearch_Click() On Error GoTo SearchErr rs.?".Fields(0) = r Or rs.

'" & _ FormatCurrency(txtbalance.Text & "'.Text) & "'.'" & FormatCurrency(txtpur.Execute ("Insert into Customer values('" & txtcid. vbInformation Else r = MsgBox("Do YOU Want To Edit The Current Record?".Text & "'. _ vbQuestion + vbYesNo.Text & "'.'" & txtaddr.MoveNext i=i-1 Loop i = MSFlexGrid1.DEPARTMENTAL STORE MANAGEMENT SYSTEM locked If txtcid.Text & "'.EOF Then rs.Open i = MSFlexGrid1.Close End Sub Private Sub Form_Load() On Error GoTo FormErr 83 . "Data Edition") If r = vbYes Then cnn1.'" & _ txtcname.Text) & "')") ElseIf r = vbNo Then MsgBox "Modification Cancel" End If End If Exit Sub UpdateErr: MsgBox Err.RowSel X=i setrecordcount Call display rs.'" & _ txtph.RowSel Do While i > 1 If Not rs.Execute ("Delete from Customer where Cust_Id='" & txtcid & "'") cnn1.Text = "" Then MsgBox "There is no current record ".Description End Sub Private Sub MSFlexGrid1_Click() 'THE SELECTED RECORD IS DISPLAYED rs.

5) = FormatCurrency(rs!Total_Purchase) MSFlexGrid1. 2) = rs!Cname MSFlexGrid1. 3) = "Address" MSFlexGrid1. _ Data Source=supriya1" .Connection With cnn1 .MoveFirst Do While Not rs.Close r1 = MSFlexGrid1.Rows = MSFlexGrid1.Rows + 1 If Not rs.1.TextMatrix(i.TextMatrix(i. adLockOptimistic) i=1 '*** INCREASES THE COLUMN WIDTH *** For j = 1 To 6 Step 1 MSFlexGrid1. 1) = "Cust_Id" MSFlexGrid1. cnn1.TextMatrix(i. 6) = "Balance" '*** RECORDS ARE DISPLAYED IN THE GRID **** If Not rs. 6) = FormatCurrency(rs!Balance) i=i+1 MSFlexGrid1. 4) = "Phone_no" MSFlexGrid1. 5) = "Total_Purchase" MSFlexGrid1.EOF MSFlexGrid1.TextMatrix(i. adOpenDynamic.Open("select * from Customer".TextMatrix(0. 4) = rs!Phone_no MSFlexGrid1.EOF Then rs.MoveNext Loop rs. 2) = "Cust_name" MSFlexGrid1.DEPARTMENTAL STORE MANAGEMENT SYSTEM locked Set cnn1 = New ADODB.ColWidth(j) = 2000 Next j '*** COLUMN NAME IS DISPLAYED *** MSFlexGrid1.TextMatrix(0.Persist Security Info=False.2 X=1 84 .Open End With Call rs.Rows .ConnectionString = "Provider=MSDASQL.EOF Then rs.TextMatrix(0.TextMatrix(0.TextMatrix(0.TextMatrix(0. 1) = rs!Cust_Id MSFlexGrid1. 3) = rs!Address MSFlexGrid1.TextMatrix(i.TextMatrix(i.

frm '****** THIS FORM DEALS WITH ADDING A NEW CUSTOMER **** '*** IT ALSO CHECKS WHERTHER THE ENTERED ************* '************** VALUE IS VALID OR NOT **************** ‘********************************************************************* Private Sub cmdback_Click() Unload Me frmcustinfo.Persist Security Info=False.Open End With Call rs.Open("select * from Customer".Show End Sub ‘********************************************************************* Private Sub cmdclose_Click() Unload Me End Sub ‘******************************************************************** Private Sub Form_Load() Set cnn1 = New ADODB.Close End Sub Private Sub cmdsave_Click() On Error GoTo SaveErr 85 .DEPARTMENTAL STORE MANAGEMENT SYSTEM Exit Sub FormErr: MsgBox Err. cnn1.Description End Sub FORM: frmcustadd.ConnectionString = "Provider=MSDASQL. adOpenDynamic. adLockOptimistic) rs.Data Source=supriya1" .Connection With cnn1 .1.

Close Exit Sub SaveErr: MsgBox Err.Open rs.Text rs!Balance = FormatCurrency(txtbalance.Text) rs!Cust_Id = txtcid.Text rs!Cname = txtcname.DEPARTMENTAL STORE MANAGEMENT SYSTEM rs.Text rs!Phone_no = txtph.Text rs!Total_Purchase = FormatCurrency(txtpur.Description End Sub ‘*********************************************************************** Private Sub txtbalance_KeyPress(KeyAscii As Integer) If Not (KeyAscii >= 48 And KeyAscii <= 57 Or KeyAscii = 8) Then MsgBox "Please Enter The Numbers" KeyAscii = 0 End If End Sub Private Sub txtcname_KeyPress(KeyAscii As Integer) 86 .Update Else rs. _ vbYesNo + vbQuestion) If r = vbYes Then rs!Address = txtaddr.Text) MsgBox "Update Successfully" rs.AddNew r = MsgBox("Do You Want To SAVE The Changes To The Customer Database".CancelUpdate End If rs.

DEPARTMENTAL STORE MANAGEMENT SYSTEM If Not ((KeyAscii >= 97 And KeyAscii <= 122) Or (KeyAscii >= 65 And KeyAscii <= 91) Or KeyAscii = 8 Or KeyAscii = 32) Then MsgBox "Please Enter The Characters" KeyAscii = 0 End If End Sub ‘*********************************************************************** Private Sub txtph_KeyPress(KeyAscii As Integer) If Not (KeyAscii >= 48 And KeyAscii <= 57 Or KeyAscii = 8) Then MsgBox "Please Enter The Numbers" KeyAscii = 0 End If End Sub ‘*********************************************************************** Private Sub txttotal_KeyPress(KeyAscii As Integer) If Not (KeyAscii >= 48 And KeyAscii <= 57 Or KeyAscii = 8) Then MsgBox "Please Enter The Numbers" KeyAscii = 0 End If End Sub 87 .

and click on the Deploy button.DEPARTMENTAL STORE MANAGEMENT SYSTEM 13. Once the user has completed with the coding the application. The wizard will then take over and perform the rest of the deployment steps for you. a small working model with the required database was created and Installed on the Work Area for the respective Module. select the type of packaging as Standard Setup Package. 2) Select the Deployment method. You will see all the required files. In order to deploy any application. In this case. For making an exe file select make project name. it is ready to be deployed. it will be Folder.exe under the File menu. Implementation Procedure After the completion of each module. click on the Package button. To deploy your application. The Wizard will then take over and perform the rest of the packaging steps for you. and tested on multiple machines. 3) As per the requirements. The same procedure was repeated with the full system fill the end users were fully satisfied with the System. automatically being included. The same were implemented wherever possible and the updated copy of the Model was once again Installed and the same above procedure was repeated till the end user was satisfied sufficiently with the system. perform the following steps:1) Select the package you want to deploy. The Users were trained to use the system and their responses and suggestions for updations were noted. To Package your application perform the following steps: 1) Start the Package and Deployment Wizard. including the runtime files. the user can use the Package and Deployment Wizard Provided by Microsoft. 2) After selecting the administration module project. 88 . The prerequisite of deploying an application is packaging.

0 • • • Database Management System of Departmental Store Management System does not support the networking environment and hence. This system does not keep the details about customer’s discount & commission rate. Limitations of System: Any project development is always a little less well than what the user had on his mind. Every project that has been developed till date has never been a perfect one because as the user gains more acknowledge about the system. • Support for Networking in case of communication and data transfer between Front End is not included yet.DEPARTMENTAL STORE MANAGEMENT SYSTEM 14. Power failures and any hardware problem cause the system fail and you cannot keep any record of the transactions. 89 . user can work with only one window at the same time. he accepts that the system perform a little more than it is developed with requirement in the mind. there can be no centralization. Because of hardware problem there is possibility of losing data. • The System may not function properly under Lower Versions of Oracle 8.e. • This system is designed in SDI [Single Document Interface] user interface i.

90 . it is said that the latest release is an advanced version of the software system. c) Making the software platform independent. Scope of Future Enhancement For any system that is developing. there is always room for more development. b) More networking features.DEPARTMENTAL STORE MANAGEMENT SYSTEM 15. Whenever a change in existing software system is include and then release. Following are some of the feature that can be enhanced or include in the result generation system. d) Making the software version independent. • The system can be made compatible with different data base such as access. General additions to the software a) Data backup and recovery option.

MicroSoft Developer’s Network April 99 Edition (MSDN). Programming in Visual Basic By Julia Case Bradley. Anita C.0 Enterprise Edition. Software Engineering By Pressman DataBase System Concepts By Silberschatz. Sudarshan SQL the Complete Reference By Groff Weinberg Softwares Visual Basic 6. Bibliography References Mastering VB 6. Microsoft Access. 91 . Millspaugh An Integrated Approach to Software Engineering By Pankaj Jalote.DEPARTMENTAL STORE MANAGEMENT SYSTEM 16.0. Korth.

Sign up to vote on this title
UsefulNot useful