INDEX

1. Introduction
1.1. Objectives
1.2. Purpose
1.3. Advantage
1.4. Disadvantage
1.5. Software Requirement
1.6. Hardware Requirement

2. System Design

2.1 Modules
2.2 Data Flow Diagram
2.3 Database table
2.4 E-R Diagram
2.5 Float Chart

3. System implementation

4. Output

5. Conclusion
6. Bibliography
 CONDIDATE DECLATION

I hereby declare that the presented in the report entitled ‘STORE MANAGEMENT
SYSTEM’ in java for the fulfilment of requirement for the award of the degree of
MASTER OF COMPURT APPLICATION, submitted the department of Computer
Science, Kanya Gurukul Campus Dehradun(Second campus of Gurukul Kangri
Vishwavidyalaya, Haridwar), is an authentic record of my work carried out under the
guidance of Dr. Praveena Chaturvedi(Associate Professor) Department of Computer
Science ,Kanya Gurukul Campus Dehradun.

The matter embodied in this report has not been submitted by me for the award of any
other degree/examination.

(NUTAN SINGH)

MCA 4TH Semester

KGC,Dhradun

This is to certify that the above statement made by the candidate is correct to the best of
my knowledge.

Dr. Praveena Chaturvedi

Dept. Of Computer Science,

Kanya Gurukul campus, Dehradun(India).

 ACKNOWLEDGEMENT

I would like to express my profound gratitude and thanks to respected Dr. Praveena
Chaturvedi(Associate Professor) for her immense support, valuable guidance and
advices during the preparation of this seminar. She helped nurse this project from idea
of stage to the record. I tried my maximum to make this seminar according to her
suggestion and direction.
I am also thankful to Dr. Nipur Singh who never hesitated to extend her helping hand
whenever required during the seminar. I also extend my sincere thanks to Dr. Neena
Gupta and Dr. Heman Pathak, for support and also making available the computer
resources. I particularly want to acknowledge Dr. Bhavna Arora for her continuous help
and support.

Date: NUTAN SINGH

MCA 4th sem
 ABSTRACT

Project Title: Stores Management System

The system creates a web based manufacturing system that enables a

manufacturing industry to schedule its manufacturing operations based on the daily
update of sales from its dealers. Once the sales figures of items for the past week are
entered by the dealers over the internet along with the orders for the next delivery, the
schedule for the next week’s production will be drawn up. A report of the required raw
materials or parts will be drawn up with the product requirements over the internet &
asked to quote their rates.

Once the rates are quoted, the order will be placed with the required delivery schedules.
Once the parts the parts are supplied the stocks will be updated. Then a production plan
will be drawn up taking the bill of materials into consideration. Once the production
plan is approved, the stock will be updated when the material is issued. Once the
finished products are available the delivery schedules will be drawn up based on the
orders placed by the Dealers. The stocks with the dealers will also be maintained.

The Benefits of the Stores Management System is

 It is used as an intranet Application.

  Providing High-Security.

 Easy Business Solutions

INTRODUCTION

1. Introduction

Stores are required for the following purposes :-

1. Capital works
2. Operation and Maintenances Works
3. Other Commercial activities like hiring equipment etc..,

The ‘Stores Management System’ is targeted to automate the almost all of the processes
mentioned above to reduce the clerical labor of the staff working in Stores both
technical and as well as Accounts departments using the software Industry’s latest
technologies and cost effective tools there by providing the better control to the
management by avoiding manual errors etc..,

In this project modules under study are Material Issues module, Reports module.

Material Issues module deals with the Issues functionality of the application. It mainly
contains two operations namely Material issues i.e. Issues issued to works based on field
requisitions and Inter stores issues i.e. material issues to other stores based on inter store
requisitions. For these two operations, we have to issue the gate passes for both types of
operations.
Reports module deals with the Reports provided by the application. This module
contains various reports namely Monthly SRB Report, Monthly SIB Report, Monthly
Section Wise Issues Reports, Priced Ledger, Monthly Stores Abstract, Monthly Work
Order wise Details and Monthly Stock Report.
1.1. Objectives
Departmental Store Management (DSM) system provides businesses with the ability to
computerize, systematize and correlate retail information. Where cash registers,
including complex register systems, have limited information collection capacity, DSM
systems can gather, store and return detailed reports on inventory trends and customer
information. Additionally, DSM systems more easily integrate with numerous sales and
ordering systems, including mail or online ordering systems used in conjunction with in-
person sales.

1.2. Purpose

The purpose of this document is to describe all external requirements for mobile task
manager. It also describes the interfaces for the system.
1.3. Advantage
Web Based or Mobile DSM: Our works on Mobile, Tab and PC system you can use one
or more than one Platform. It works in both online and offline.
DSM Works Offline: DSM works online but when internet down than you can
continue your selling. DSM will automatically resynchronize with other terminals & up-
to-date back-up.
Online Store: Open an Online Store and quickly get your product online with just one
click. No need to be web expert.
Mobile Friendly: You can operate and see details of shop in your mobile phone.
Domain and Hosting: Bring your own domain to ensure to match your Shop.
Inventory Control: See stock on hand, get notification when stock is low.
Customer History: Keep all your customer information in one place. It keeps customer
purchase history.
Customizable Reporting: Build your own reports and quick see the store. Reports like
inventory, sells, end of day. You can even see the reports from mobile phone.
Add-Ons: You can integrate multiple data in one database it’s synchronize
automatically.
Multi-Outlet: You can open new outlet using same database. You can add more than
one user just a click.

1.4. Disadvantage
User’s view of the problem
The user’s problem is that his branches and their associated systems function
Independently thus creating difficulties in keeping track of any changes made to the
local Databases. Therefore a system is needed that will be able to make changes
Instantaneously in a synchronized manner. This will mean that a distributed application
should be introduced which will be needed to send objects from one application to
another by
Summoning a single application program of object methods located in Another
program. In so doing, it will be easy to monitor the progress of the company and
employees.
Methodology
the requirement where analyzed from the developer’s point of view. I was using Asail
Methodology. I had begun the analysis by looking at the possible challenges that will be
encountered and Alternative solutions that could be implemented. System
implementation will be carried out Using Bootstrap, CSS 3, Jquery, Ajax, PHP 7,
MySQL, and framework: Codeigniter 3, which are the open source applications.

1.5. Software Requirements

Operating System : Windows 2000 Professional
Web Server : Apache Tomcat Web Server
Database : XAMPP
Programming Language : Java
1.6. Hardware requirements
SERVER:
Processor : Pentium IV
Speed : 1.7 GHz
Memory Capacity : 1 GB
Hard Disk Capacity : 80 GB
Monitor Make : acer
Client:
Processor : Pentium IV
Speed : 1.7 GHz
Memory Capacity : 256 MB
Hard Disk Capacity : 20 GB
Monitor Make : acer
2. SYSTEM DESIGN
Before developing a system we have to design our system like how Use case of our
System. Data Flow Diagram (DFD) provides a view of how the system or business
flows that able to increase the efficiency and effectiveness to achieve system objectives.
Entity Relationship Diagram (ERD) will tell us about our database. We can know our
system structure when we will design it and that is State transaction diagram showing
entities that interact with this system and the last one Gantt charts it’s illustrate the start
and finish dates of the terminal elements and summary elements of a project.
2.1. MODULES
This project mainly deals with two modules- reports modules and material issued
modules.
Material issues modules
It deals with the application specific functionalities. Two main material issues are-
issues aroused when the work is allocated according to field requisitions and issues
which are related to inter-store works. For both these operations, the gate passes will
have to be issued.
Reports modules
In this, we basically deal with the reports that will be generated by the application.
Reports are the actual result of a particular process and are basically generated on a
monthly basis. The reports which are basically includes in the module are SIB report,
SRB report, issues report of respective sessions, stores abstract, Ledger report, details of
work orders and stock reports.
2.2. DFD (DATA FLOW DIAGRAM)
We usually begin withdrawing a context diagram, a simple representation of the whole
system. To elaborate further from that, we drill down to a level 1 diagram with
additional information about the major functions of the system.
2.2.1. Context diagram (Level 0 DFD) :

2.2.2. Level 1 DFD :

2.3. E-R DIAGRAM
Entity-relationship (ER) diagram, a graphical representation of entities and their
relationships to each other, typically used in computing in regard to the organization of
data within databases or Information systems. An entity is a piece of data-an object or
concept about which data is stored

2.4. Database Description:

2.4.1.User

Field Data type Constraint

Userid Varchar2 (50) Primary key
Password Varchar2 (50)
Fname Varchar2 (50)
Lname Varchar2 (50)
Initials Varchar2 (50)
Designation Varchar2 (20)
Job Varchar2 (20)
Store_code Number (10) Foreign key
Timestamp Varchar2 (100)
Macaddress Varchar2 (100)

2.4.2.Designation

Field Data type Constraint

Designation Number (10) Primary key
Short_name Varchar2(20)
Full_name Varchar2(50)

2.4.3.Organization

Field Data type Constraint

Organisationid Varchar2 (10) Primary key
Org_short_name Varchar2 (50)
Org_full_name Varchar2 (200)
Address Varchar2 (100)
Street Varchar2 (100)
City Varchar2 (100)
Phone Varchar2 (50)
url Varchar2 (50)
2.4.4.Log table

Field Data type Constraint

Userid Varchar2(50) Foreign key
Appname Varchar2(50)
Operation Varchar2(100)
Date Date

2.4.5.Issues

Field Data type Constraint

Sib_slno Varchar2 (20) Primary key
Sib_number Varchar2 (20)
Date Date
Receiving_section Number (10)
Receivers_name Varchar2 (150)
Receivers_designatio
Varchar2 (50)
n
Tda Varchar2 (20)
Work_order_number Varchar2(100)
Remarks Varchar2 (100)
Store_id Varchar2(20)
Userid Varchar2(50) Foreign key
Timestamp Timestamp
Macadderess Varchar2(50)
Reqno Varchar2(100)
Reqdate Date
Work_order_date Date
Scheme Number(10)
2.4.6.Issues-items
Field Data type Constraint
Sib_slno Varchar2 (20) Primary key
Item_id Varchar2 (20)
Quantity Number (10)
Price Number (10)
Userid Varchar2 (20) Foreign key
Timestamp Timestamp
Macadress Varchar2 (20)
Reqno Varchar2(20)
Reqdate Date
Flag Varchar2(20)

2.4.7.Issues_corr

Field Data type Constraint

Sib_slno Varchar2 (20) Primary key
Sib_number Varchar2 (20)
Date Date
Receiving_section Number (10)
Recievies_name Varchar2 (150)
Receivers_designatio
Varchar2(50)
n
Tda Varchar2 (20)
Work_order_number Varchar2(100)
Remarks Varchar2 (1000)
Store_id Varchar2(20)
Userid Varchar2 (50) Foreign key
Timestamp Timestamp
Macaddress Varchar2 (50)
Reqno Varchar2(100)
Reqdate Date
Work_order_date Date
Scheme Number (10)
E_userid Varchar2(50)
E_timestamp Timestamp
E_macadress Varchar2(50)

2.4.8.Item

Field Data type Constraint

Item_id Varchar2 (20) Primary key
Item_name Varchar2 (200)
Min_stock Number (10)
Max_stock Number (10)
Units Varchar2 (50)
Bin_card Varchar2 (100)
Qty Double
Ledger_folio Varchar2(300)
Major_head Varchar2(10)
Submajor_head Varchar2(10)
Minor_head Varhcar2(10)
Storage Varchar2 (10)

2.4.9.item_new

Field Data type Constraint

Item_id Varchar2 (20) Primary key
Item_name Varchar2 (200)
Min_stock Number (10)
Max_stock Number (10)
Units Varchar2 (50)
Bin_card Varchar2 (100)
Qty Double
Ledger_folio Varchar2(300)
Major_head Varchar2(10)
Submajor_head Varchar2(10)
Minor_head Varhcar2(10)
Storage Varchar2 (10)

2.4.10.item_old

Field Data type Constraint

Item_id Varchar2 (20) Primary key
Item_name Varchar2 (200)
Min_stock Number (10)
Max_stock Number (10)
Units Varchar2 (50)
Bin_card Varchar2 (100)
Qty Double
Ledger_folio Varchar2(300)
Major_head Varchar2(10)
Submajor_head Varchar2(10)
Minor_head Varhcar2(10)
Storage Varchar2 (10)

2.4.11.item_new

Field Data type Constraint

Item_id_new Varchar2 (20) Primary key
Item_id_old Varchar2 (20) Foreign key
Ledger folio Varchar2 (15)
Units Varchar2 (100)
Name Varchar2 (20)
Stork Number (15,5)
Price Number (20,2)
Value Number (25,2)
Account Varchar2(20)
Mhead Varchar2(5)
Smhead Varhcar2(5)

2.4.12.item_types

Field Data type Constraint

Type_id Varchar2 (20)
Type_name Varchar2 (20) Foreign key

2.4.13.Updates

Field Data type Constraint

Storied Varchar2 (20) Primary key
Client_time Timestamp
Server_time Varchar2(20)
Hwaddress Varchar2(20)
Userid Varchar2(50) Foreign key
2.5. E-R DIAGRAM-
Entity-relationship (ER) diagram, a graphical representation of entities and their
relationships to each other, typically used in computing in regard to the organization of
data within databases or Information systems. An entity is a piece of data-an object or
concept about which data is stored.
2.6. FLOAT CHART
3. SOFTWARE IMPLEMENTATION
3.1. CODE PROJECT

3.2. MY ACCOUNT
3.3. ADD EMPLOYEE

3.4. STORE
3.5. SELLS
4. OUTPUT

4.1. HOME

4.2. STORE-
1. SUPPLYER

2. BRAND
3. CATAGORIES

4. UNIT
5. RMA
6. SELLS

7. EMPLOYEE
 5. Conclusion

Our project is only a humble venture to satisfy the needs in an Institution.

Several user friendly coding have also adopted. This package shall prove to be
a powerful package in satisfying all the requirements of the organization.
The objective of software planning is to provide a frame work that enables the manger
to make reasonable estimates made within a limited time frame at the beginning of the
software project

6. Bibliography
1) http://www.javaworld.com/javaworld/jw-01-1998/jw-01-bookreview.html
2) Database Programming with JDBC and Java by O'Reilly
3) Head First Java 2nd Edition
4) http://www.jdbc-tutorial.com/
5) Java and Software Design Concepts by A Press
.