Program Code : BCA

Course Code : CS-76

Course Title : PROJECT

Project Title :

Enrolment No. :

Name :

Address :

Date :

Signature

1

Project Proposal

The following project proposal includes: -

Title of the Project Introduction and objectives of the Project Project Category (RDBMS/OOPS/Networking/Java/Internet (Web

designing etc.)/AI/Multimedia etc. Tools/Platform, Hardware and Software requirement Specifications A complete structure of the Program: -

o Analysis (DFDs, ER Diagrams etc.)o Number of modules and their descriptiono Data Structures (Tables etc.) for all the modules o Process Logic of each module(Input of the Project)o Types of report generation(Output of the Project)

Security Scope of future application

TITLE OF THE PROJECT

Automation of working of a Departmental Store.

INTRODUCTION AND OBJECTIVES OF THE PROJECT

The project is developed to automate the working of a Departmental Store having wide range of products from toiletries to decorative pieces etc.

All the products are to be distributed to the respective outlets (in the Departmental Store) depending on the inventory and the requirement raised from the particular department.

The warehouse department keeps record of goods in stock.The gatekeeper does the gate entry of the vehicles carrying the products.Sale of any product will directly debit the quantity of goods from the amount of stockwith the front shop inventory, along with the details of the counter selling it and the details of the goods being sold, the time of sale etc. The system will ask for authorization and only then anything will be sold or exchanged. If a customer is paying by credit card then the details of the

2

credit card are taken down. Generation of bill is done the very moment a customer pays. The Departmental Store requires the automation of the complete system, which includes:-

1. Product Section2. Customer Section3. Supplier Section4. Warehouse Section5. Account Section (Only Form Design)

1.Product Section

1. Product Details2. Requirement of the Product

2.Customer Section

1. Customer Details2. Customer Order3. Bill

3.Supplier Section

1. Supplier Details2. Damaged Goods3. Purchased Goods

4.Warehouse Section

1. Gate Entry2. Details of the products in warehouse3. Requirement of the products in warehouse4. Gate Pass

5.Account Section

1. Group Creation2. Ledger Creation3. Journal4. Voucher Details5. Debit/Credit Note

3

PROJECT CATEGORY

The project category is RDBMS.The project will be made using Visual Basic 6.0 as the front end and Oracle8i as the back end.

TOOL/PLATFORM, HARDWARE AND SOFTWARE REQUIREMENTS

This software is a database application. The tools used for developing

the projects are as follows:

Visual Basic 6.0 (Visual Basic)

Oracle 8.0

Reasons for using these tools:

Visual Basic:

Microsoft Visual Basic is the quickest and easiest way to create

applications for Microsoft Windows Operating System. The VB

programming system allows us to create attractive and useful

applications. VB has a powerful help support for the programmers. The

help files contain complete information and assistance for a topic. Thus

programmers find it easy for the projects, on which they are working

and can also refer to the examples given with the help.

VB makes us more productive by providing appropriate tools for the

different aspects of GUI development. The objects like text box, list box,

picture box, labels can easily be drawn thus helps in easy interface

designing. And after designing the interface we make this interface

interact with the user by writing code that responds to events that occur

in the interface.

4

ORACLE 8.0

Oracle 8.0 is a Relational database Management System

product. It offers capabilities of both relational and object oriented

database system. In general objects can be defined as reusable

software codes which are location independent and perform a specific

task on any application environment with little or no change to the

codes.

SQL is used to access the data within the Oracle. It contains a set of

commands, which make it very easy to maintain the database. It has for

sub parts DDL, DML, DCL, and TCL. DDL includes the commands,

which allows us to create objects and to manipulate the structure of the

objects. DML includes the commands to manipulate the information

stored in a database. DCL includes the commands for controlling the

data access and TCL includes the commands for controlling the

transactions like commit and rollback.

The database server or backend is used to manage the database tables

optimally among multiple clients who concurrently request the server for

the same data. It also enforces Data Integrity across all client

application and controls database access and other security

requirements.

Tool/Platform: Windows 98/2000/xp/vista

Hardware Requirements: 16 MB RAM, 486 or Pentium 1, 500 MB Hard Disk

Software Requirements: Oracle, VB

5

A COMPLETE STRUCTURE OF THE PROGRAM

There are five modules. These are: -

1.Product Section Module2.Customer Section Module3.Supplier Section Module4.Warehouse Section Module5.Account Section Module (Only Form Design)

The project opens with the main MDI form. All the sections form the part of the menu bar, which is further divided into sub-menus.

The Product Section

It consists of two forms: -

1. Product Details2. Requirement of the Product

Product Details The Product ID will be auto generated. The user will enter all the product details such as Product Name, Unit of Measurement, Quantity on Hand, Reorder Level Quantity, Rate, Supplier ID. On entering the Supplier ID, the Supplier Name will automatically appear. All the product details will be added and stored in a table (database). The user can modify the details by clicking on the Modify Button. The user can also delete the details of a particular product by clicking the Delete Button. The Save Button will be used to add new records in the database or modify existing records. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

Requirement of the Product

When the products will fall short, the requirement form will be generated. This form will enable the user to enter all the requirement details of a product. When the details will be entered, it will then automatically pass to the Warehouse. The Requirement ID will be auto-generated. The user will have to enter the Requirement Date. On entering the Product ID- the

6

Product Name, Quantity on Hand, Reorder Level Quantity, Supplier ID and the Supplier Name will be automatically entered. The user will have to enter the Quantity Required. . All the requirement details will be added and stored in a table (database). The Next Button will be used to enter multiple product requirements for one particular Requirement ID. The Save Button will be used to add new records in the database. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

The Customer Section

It consists of three forms: -

1. Customer Details2. Customer Order3. Bill/Cash Memo

Customer Details

It is necessary for the company to maintain complete details of the customer. The Customer ID will be auto generated, while the user will have to enter all the other details like Customer Name, Customer Address, City, State, Pin Code, Contact No 1, Contact No 2, Due Limit, Due Amount. The Due Limit and Due Amount will be automatically updated whenever a Customer will buy or pay the amount. The user can modify the customer details by clicking on the Modify Button. The user can also delete the details of a particular customer by clicking the Delete Button. The Save Button will be used to add new records in the database or modify existing records. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

Customer Order

When a Customer wants an item, which is not currently in stock then the operator, will generate this form. Order No will be automatically generated and Order Date will be the current date but it can be modified. The operator will enter supply date. The user will enter the Customer ID. The Customer Name will be generated according to the Customer ID. The user will enter The Product ID. The Product Name, Unit, Rate will automatically appear. The user will enter Quantity. The Sub Total will be generated accordingly. The Next Button will enable the user to enter details of multiple products. The Save Button will be used to add new

7

records in the database. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

Bill/Cash Memo

When a Customer will purchase any goods from the store then the Bill will be raised. The Bill will have two types of payment modes. The Bill No. will be auto-generated. The user will enter the Customer ID and accordingly the Customer Name will appear. Then the user will enter the product details. The Sub Total and the Total will be generated accordingly. The Next Button will be used to enter details of multiple products. On entering the Less amount, the Final will be generated. The Save Button will be used to add new records in the database. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

The Supplier Section

It consists of three forms: -

1. Supplier Details2. Damaged Goods3. Purchased Goods

Supplier Details

It is necessary for the company to maintain complete details of its Suppliers. The Supplier ID will be auto generated, while the user will have to enter all the other details like Supplier Name, Address, City, State, Pin Code, Contact No1, Contact No 2, Pending Amount. The user can modify the customer details by clicking on the Modify Button. The user can also delete the details of a particular customer by clicking the Delete Button. The Save Button will be used to add new records in the database or modify existing records. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

Damaged Goods Form

When goods are old dated or damaged then they will have to be returned to the Supplier. The user will enter Damaged Goods Voucher No., Damaged Goods Voucher Date. The he will enter the details of the damaged product. On entering the Product ID, its Name, Supplier Id,

8

Supplier Name , Unit and Rate will automatically appear. The user will have to enter the Quantity, Mfd. Date and Remarks. The Sub Total will automatically appear on entering the Quantity. Similarly the Total will be generated. The Next Button will be used to enter details of multiple products. The Save Button will be used to add new records in the database. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

Purchased Goods

When the Supplier will send goods to the warehouse then the Purchased Goods Form will be raised. The Purchase No. will be auto-generated. The user will have to enter Purchase Date, Supplier ID. The Supplier Name will automatically appear on entering the Supplier ID. The user will enter all the details of the purchased products. The Product Name, Unit, Rate will automatically appear on entering the Product ID. The Sub Total and Total will be automatically generated on entering the Quantity. The Final amount will automatically appear on entering the Less Amount. The Next Button will be used to enter details of multiple products. The Save Button will be used to add new records in the database. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

The Warehouse Section

It consists of four forms: -

1. Gate Entry2. Details of the products in warehouse3. Requirement of the products in warehouse4. Gate Pass

Gate Entry

When the products will arrive at the warehouse stores gate, Gate Entry will be done. This form will enable the gatekeeper to enter the details regarding goods like Gate Entry No.(auto generated), Gate Entry Date (auto generated), Gate Entry Time, Bill No., Supplier ID, Vehicle No., Driver Name. The Supplier Name will automatically appear on entering the Supplier ID. The gatekeeper will also have to enter the product details like Product ID, Quantity as per Bill, Actual Quantity, Remarks. The Product Name and Unit will automatically appear on entering the Product ID. The Next Button will be used to enter details of multiple products.

9

The Save Button will be used to add new records in the database. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

Product of Warehouse Details

It is necessary for the company to maintain the details of products in warehouse. The user will have to enter the Rack No., Product ID, Rate, Quantity on Hand, Reorder Level Quantity. The Product Name, Unit, Supplier Id, Supplier Name will automatically appear on entering the product ID. The Save Button will be used to add new records in the database. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

Requirement of the product of warehouse

When the products will fall short, the requirement form will be generated. The user will have to enter all the requirement details of the product. The Requirement ID will be auto-generated. The user will enter Requirement Date, Product ID, Rack No., Quantity on Hand, Reorder Level Quantity and the Quantity Required. The Product Name, Supplier ID, Supplier Name will automatically appear on entering the Product ID. The Next Button will be used to enter details of multiple products. The Save Button will be used to add new records in the database. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

Gate Pass

When the material will be dispatched, it will be received at the gate along with a copy of MRS. The operator will have to prepare a Gate Pass before dispatching goods. The Gate Pass No. and Gate Pass Date will be auto generated. The user will have to enter the MRS No., Vehicle No., Driver Name. The Product Name, Unit will automatically appear on entering the Product ID. The user will have to enter the Quantity and Remarks. The Next Button will be used to enter details of multiple products. The Save Button will be used to add new records in the database. The Refresh Button will be used to clear all fields in the form. The Exit Button will take the user to the main MDI Form.

10

ANALYSIS

E R Diagram

11

Customer PurchaseProduct in Store

Payment

Sold Goods Purchased Goods

Damaged Goods

Supplied as per demand

Account

Update

Warehouse Supplier

Stored

Returned

Returned

Sends Goods

Sends Bill

Update

0 Level DFD

Select Product

Bill Products

12

Customer Buys Product

Departmental Store

Supplies Goods

Payment of Purchased goods

Supplier

13

Level 1 DFD

Product DetailsCustomer Details

Details Details

Select Product

Places order

Requirement

Bill Requirement ofProduct

Bill Database Order Details

Customer Order

Account

Database Pay

Products

Details

Damaged Supplier Details Goods

ProductDetails (WH)

RequirementOf Product

Details

Customer Buys Product

Product in Store

Order

Supplier

Supply Goods

Warehouse

Update

Account

PurchaseGoods

Return Damaged Goods

Payment

14

Details PurchasedGoods

Damaged Goods

15

Level 2 DFD

Product DetailsCustomer Details

Details Details

Select Product

Places order

Requirement

Bill Requirement ofProduct

Bill Database Order Details

Customer Order Supplier DetailsPay

Account

Database

Gate Entry

Details

ProductDetails (WH)

Dmg.Requirement

Goods Of Product

Customer Buys Product

Product in Store

Order

Supplier

Supply Goods

Warehouse

Update

Account

PurchaseGoods

Return Damaged Goods

Payment

Gate Pass

Gate Entry

16

DetailsDetails Details

Purchased Gate Pass Goods Damaged Goods

17

DATABASE OF THE PROJECT

Product Section

Product Details TableFIELD NAME DATA TYPE DESCRIPTIONprod_id Varchar2(8) Product IDprod_name Varchar2(20) Product Nameprod_unit Varchar2(10) Unit of Measurementqty_on_hand Number(10,2) Quantity on Handqty_reorder Number(10,2) Reorder Level

Quantityrate Number(10,2) Ratesupp_id Varchar2(8) Supplier ID

Requirement of the Product TableFIELD NAME DATA TYPE DESCRIPTIONprod_id Varchar2(8) Product IDqty_on_hand Number(10,2) Quantity on Handqty_reorder Number(10,2) Reorder Level

Quantitysupp_id Varchar2(8) Supplier IDqty_req Number(10,2) Quantity Requiredreq_id Varchar2(8) Requirement IDreq_date Date Requirement Date

Customer Section

Customer Details TableFIELD NAME DATA TYPE DESCRIPTIONcus_id Varchar2(8) Customer IDcus_name Varchar2(25) Customer Namecus_add Varchar2(30) Customer Addresscus_city Varchar2(25) Citycus_state Varchar2(25) Statecus_pin Number(6) Pin Codecus_cont1 Number(15) Contact No.1cus_cont2 Number(15) Contact No.2cus_due_limit Number(10,2) Due Limitcus_due_amount Number(10,2) Due Amount

18

Customer Order Details

Table1FIELD NAME DATA TYPE DESCRIPTIONord_no Varchar2(8) Order No.ord_date Date Order Datesupp_date Date Supply Datecus_id Varchar2(8) Customer IDtotal_amount Number(10,2) Total Amount

Table2FIELD NAME DATA TYPE DESCRIPTIONord_no Varchar2(8) Order No.ord_date Date Order Dateprod_id Varchar2(8) Product IDprod_qty Number(10,2) Quantity

Bill/Cash Memo

Table1FIELD NAME DATA TYPE DESCRIPTIONbill_no Varchar2(8) Bill No.bill_date Date Bill Datecus_id Varchar2(8) Customer IDpayment_mode Varchar2(4) Payment Modeless Number(10,2) Less Amounttotal_amount Number(10,2) Total Amount

Table2FIELD NAME DATA TYPE DESCRIPTIONbill_no Varchar2(8) Bill No.bill_date Date Bill Dateprod_id Varchar2(8) Product IDprod_qty Number(10,2) Quantity

Supplier Section

Supplier Details TableFIELD NAME DATA TYPE DESCRIPTIONsupp_id Varchar2(8) Supplier IDsupp_name Varchar2(25) Supplier Namesupp_add Varchar2(30) Supplier Address

19

supp_city Varchar2(25) Citysupp_state Varchar2(25) Statesupp_pin Number(6) Pin Codesupp_cont1 Number(15) Contact No.1supp_cont2 Number(15) Contact No.2supp_pending_amt Number(10,2) Pending Amount

Damaged Goods

Table1FIELD NAME DATA TYPE DESCRIPTIONdamgoods_vh_no Varchar2(8) Dmg. Goods Voucher

No.damgoods_vh_date Date Dmg. Goods Voucher

Datetotal_amount Number(10,2) Total Amount

Table2FIELD NAME DATA TYPE DESCRIPTIONdamgoods_vh_no Varchar2(8) Dmg. Goods Voucher

No.damgoods_vh_date Date Dmg. Goods Voucher

Dateprod_id Varchar2(8) Product IDprod_qty Number(10,2) Quantitysupp_id Varchar2(8) Supplier IDmfd_date Date Mfd. Dateremarks Varchar2(30) Remarks

Purchased Goods

Table1FIELD NAME DATA TYPE DESCRIPTIONpur_no Varchar2(8) Purchase No.pur_date Date Purchase Datesupp_id Varchar2(8) Supplier IDLess Number(10,2) Less Amounttotal_amount Number(10,2) Total Amount

Table2FIELD NAME DATA TYPE DESCRIPTIONpur_no Varchar2(8) Purchase No.

20

pur_date Date Purchase Dateprod_id Varchar2(8) Product IDprod_qty Number(10,2) Quantity

Warehouse Section

Gate Entry

Table1FIELD NAME DATA TYPE DESCRIPTIONge_no Varchar2(8) Gate Entry No.ge_date Date Gate Entry Datege_time Date Gate Entry Timebill_no Varchar2(8) Bill No.veh_no Varchar2(20) Vehicle No.drv_name Varchar2(20) Driver Namesupp_id Varchar2(8) Supplier ID

Table2FIELD NAME DATA TYPE DESCRIPTIONge_no Varchar2(8) Gate Entry No.ge_date Date Gate Entry Dateprod_id Varchar2(8) Product IDqty_bill Number(10,2) Quantity on Billact_qty Number(10,2) Actual Quantityremarks Varchar2(30) Remarks

Product Details (Warehouse)

TableFIELD NAME DATA TYPE DESCRIPTIONprod_id Varchar2(8) Product IDrack_no Varchar2(10) Rack No.qty_on_hand Number(10,2) Quantity on Handqty_reorder Number(10,2) Reorder Level

Quantityrate Number(10,2) Ratesupp_id Varchar2(8) Supplier ID

21

Requirement of the Product (Warehouse)

FIELD NAME DATA TYPE DESCRIPTIONprod_id Varchar2(8) Product IDrack_no Varchar2(10) Rack No.qty_on_hand Number(10,2) Quantity on Handqty_reorder Number(10,2) Reorder Level

Quantitysupp_id Varchar2(8) Supplier IDqty_req Number(10,2) Quantity Requiredreq_id Varchar2(8) Requirement IDreq_date Date Requirement Date

Gate Pass

Table1FIELD NAME DATA TYPE DESCRIPTIONgp_no Varchar2(8) Gate Pass No.gp_date Date Gate Pass Datemrs_no Varchar2(10) Goods Dispatch No.veh_no Varchar2(20) Vehicle No.drv_name Varchar2(20) Driver Name

Table2FIELD NAME DATA TYPE DESCRIPTIONgp_no Varchar2(8) Gate Pass No.gp_date Date Gate Pass Dateprod_id Varchar2(8) Product IDqty Number(10,2) Quantity

TYPES OF REPORT GENERATION

A number of reports will be generated like: -

1. Product Details Report2. Product Requirement Report3. Product Requirement Report (Warehouse)4. Customer Details Report5. Customer Order Report6. Supplier Details Report

22

7. Damaged Goods Report8. Purchased Goods Report9. Product Details Report (Warehouse)10.(10) Sales Report11.(11) Dispatched Goods Report

More relevant reports will be generated as the project progresses.

VALIDATION CHECKS

1. The user will be prompted to enter complete details in any form.2. The user cannot modify any auto-generated number or data.3. The user cannot enter alphabetic data in a numeric data field.4. The user will have to enter date in the correct format.

Is there any client for this project?

No. there is no client for this project. This Software is my individual effort and work in Stand Alone environment with all the functionalities.

Security

Any Computer based system project that manages valuable information about various transactions need to be protected against improper individuals or hackers that can perform illegal penetration into the system. The various security measures need to be implemented in a project system. In order to protect sensitive content and provide secure mode of data transmission, strong security measures must be implemented through the system. Hackers who attempt to penetrate systems for sport; disgruntled employees who attempt to penetrate for revenge; dishonest individuals who attempt to penetrate gain can be avoided by providing proper Security Measures.

The following security measures are considered in this project.1) User Level Authentication2) Restricted Menu access

23

SCOPE OF FUTURE APPLICATION

The following application can be used to automate the working of any kind of store, factory, warehouse and industry with slight modifications. The application will enable to monitor the working and also proper management of any similar kind of system.

24