A PROJECT REPORT ON “Inventory Management System” Carried out for “SigmaSoft Solutions Pvt. Ltd.” Address: C1/201, Saudamini Complex, Bhusari Colony, Pune (Maharashtra) Phone: (+91)992-261-8823 Submitted To Marathwada Mitra Mandal’s College Of Engineering, Karvenagar, Pune 411052 In Partial fulfilment of M.C.A. Degree in Engineering Faculty Savitribai Phule Pune University Pune 411 007
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
A PROJECT REPORT
ON“Inventory Management System”
Carried out for“SigmaSoft Solutions Pvt. Ltd.”
Address:
C1/201, Saudamini Complex,Bhusari Colony, Pune (Maharashtra)Phone: (+91)992-261-8823
Submitted ToMarathwada Mitra Mandal’s College Of Engineering,
Karvenagar, Pune 411052
In Partial fulfilment of M.C.A. Degree in Engineering Faculty
Savitribai Phule Pune UniversityPune 411 007
Submitted By:
Prasad KeluskarPankaj Gore
2014-2015
A
PROJECT REPORT ON
“Inventory Management System”
For
“Beyond Imagination”
In Partial fulfilment of Master of Computer Application Degree in Engineering Faculty
By
Prasad KeluskarPankaj Gore
MCA- III SEM- VI2014-2015
Submitted To
Savitribai Phule Pune UniversityPune-411 007
Marathwada Mitra Mandal’s College Of Engineering,Karvenagar, Pune 411052
A
CERTIFICATE
This is to certify that Mr.Prasad Keluskar of M.C.A. (Engineering Faculty 2008 Course) has completed his Industrial Project in Semester VI during academic year 2014-2015 in partial fulfilment of the M.C.A. Course.
This is to certify that Mr.Pankaj Gore of M.C.A. (Engineering Faculty 2008 Course) has completed his Industrial Project in Semester VI during academic year 2014-2015 in partial fulfilment of the M.C.A. Course.
3. Company Name & Address :- C1/201, Saudamini Complex, Bhusari Colony, Pune (Maharashtra)
Phone: (+91)992-261-8823
4. Guide From Industry :- Mr.Gaurav Joshi.
5. Guide From Department :- Mrs.Swapna Kolhatkar.
6. Title of Project :- “Inventory Management System”.
7. Project work is :- Along with others in industry.
8. Actual Duration for Project :- 6 months.
I hereby declare that above project work has been completed by me under the guidance of internal as well as external guide.
I hereby declare that this project work is my original work and it has not been submitted elsewhere as project report by me or anyone.
Place - Pune Signature
Date – 30/5/2015 Prasad Keluskar
M.C.A Department
Marathwada Mitra Mandal College Of Engineering.
Self – Declaration of Project by the student
1. Name of Student :- Pankaj Gore.
2. Roll No. :- 16
3. Company Name & Address :- C1/201, Saudamini Complex, Bhusari Colony, Pune (Maharashtra)
Phone: (+91)992-261-8823
4. Guide From Industry :- Mr.Gaurav Joshi.
5. Guide From Department :- Mrs.Swapna Kolhatkar.
6. Title of Project :- “Inventory Management System”.
7. Project work is :- Along with others in industry.
8. Actual Duration for Project :- 6 months.
I hereby declare that above project work has been completed by me under the guidance of internal as well as external guide.
I hereby declare that this project work is my original work and it has not been submitted elsewhere as project report by me or anyone.
Place - Pune Signature
Date – 30/5/2015 Pankaj Gore
I undersigned hereby declare that the project report entitled
“INVENTORY MANAGEMENT SYSTEM” is developed for SIGMA SOFT SOLUTIONS ,Written and submitted by me in partial fulfilment of the requirement for the award of the degree of Master of Computer application is my original work .The empirical findings in this report are based on the data collected by us through discussion with the customer.
I understand that, any such copying is liable of punishment to us in the way University authorities deem fit.
Place -Pune Yours Faithfully
Date – 30/5/2015 Prasad Keluskar
DECLARATION
I undersigned hereby declare that the project report entitled
“INVENTORY MANAGEMENT SYSTEM” is developed for SIGMA SOFT SOLUTIONS ,Written and submitted by me in partial fulfilment of the requirement for the award of the degree of Master of Computer application is my original work .The empirical findings in this report are based on the data collected by us through discussion with the customer.
I understand that, any such copying is liable of punishment to us in the way University authorities deem fit.
Place – Pune Yours Faithfully
Date -30/5/2015 Pankaj Gore
DECLARATION
ACKNOWLDGEMENT
Industrial training is the phase of the activity during my study in which I am
expected to expand my creative thinking ability and to get the training of how to work in
industry and how all works are undertaken in the industry. It was a great pleasure
working on this project.
It is with a profound sense of gratitude that we express our sincere thanks to all
those who helped us to develop this project. A successful project is result of good team
work which contain not only people who put in their logic and hard work but also who
guide them.
We would especially like to thank Principal Dr. S.M.Deshpande and MCA
Head of Department Prof. Mr. Atul Naik for giving us the prospect to do this course
and thereby the project.
We are really thankful to Mrs. Swapna Kolhatkar our Project Guide for their
exemplary patience, valuable timely assistance and motivation all through the way. Their
dedication in poring through source code and struggling through complex explanations
inspired us to make this project work better.
It is a delight to work with such talented people.
Without their complete support and willing co-operation, this would have not
been possible. We are grateful to Mr. Gaurav Joshi for permitting us to work on this
project.
Last but not least I am also thankful to all my friends who supported me to
completing my project.
Prasad Keluskar ---------------------
Pankaj Gore -----------------------
Table Of Contents
Sr. No CONTENT PAGE NO
Preliminary Investigation1 Introduction 12 Company Profile 23 Existing System 34 Project Scope 45 Description of Technology
5.1 JAVAFX 55.2 MySQL Server 6
6 Hardware and Software Requirement 7System Analysis
7 Gantt Chart 228 Proposed System 239 Module Description 2410 Stakeholders 2711 Fact Finding Technique 2812 Feasibility Study 3013 System UML
13.1 Class Diagram 3313.2 Use Case 3413.3 ERD 3513.4 Sequence Diagram
13.4.1 sequence diagram for customer 3613.4.2 sequence diagram for supplier 37
Operation System: windows 7/8/8.1 And Android 3.0 and later
Browser: Any JavaScript enabled browser
Software Requirements:
User Interface: Scene builder
Integrated Development Environment (IDE) :Eclipse
JDK 1.8
Front End: Java
Backend Tool: MySQL
SystemAnalysis
Gantt Chart
Project Planning Phase
Proposed System
After studying the above requirements we will propose to build a desktop based
application which is mainly developed using JAVAFX and MySQL.
High Level System functionality:
This system will be mainly divided in to two sections as below:
Admin section
Operations section.
1.1. Admin Section:This section will allow user to perform admin level activities. The
important activities can be done within admin section will be listed as below:
Maintain stock.
Maintain product.
Maintain report
Expenses.
Profit and loss statements.
Recovery
1.2. Operations Section:This section will allow user to perform daily operations (normal user
level activities)
Selling products.
Billings.
Access utilities.
Module Description
The modules involved are:
Admin
Supplier
Vendor
Employee
Customer
Payment
Bill
Stock detail
Add Item
Bank detail
Admin:
Who handle the whole system and create a new user login credential as well as
manage all reports.
Supplier:
The person who buy good from company and supplied to shop.
Maintain the record like:
Supplier detail
Supplier order
Vendor:
The person who buy good from shop and sell them to other.
Maintain the record like:
Vendor detail
Vendor order
Employee:
The persons who works for company.
Maintain the record like:
Employee detail
Employee attendance
Customer:
The person who actually buy a good from shop.
Maintain the record like:
Customer detail
Customer order
Customer bill
Payment:
Maintain the record like:
Payment mode like cash, cheque both for sale and purchase.
Bill:
Maintain the record like:
Generation of bill for customer, supplier, vendor.
Stock detail:
Maintain the record like:
product detail
Add Item:
Maintain the record like:
Supplier detail
Supplier order
Bank Detail:
Maintain the record like:
Category such as supplier /vendor/owner and their a/c no, type, IFSC code,
branch and bank.
STAKEHOLDERS
Primary source of information for system requirement is the various stakeholder of
the new system.
Stakeholder are all people who have an interest in successful implementation of the
system.
Stakeholder are categories into one of the three group.
USER
Those who actually use the system on daily bases.
CLIENT
Those who pay for and own the system.
TECHNICAL STAFF
The people who must insure that the system operates in computing
environment of the organization.
OWNER -
He manages private data entries like bills amount of retrieveatio
purchasing order.
COUNTER -
Enters a Stock and selling entries as well as retrieveatio report
checks the availability of stock.
Fact finding technique
We study system and collect facts and all relevant information. When facts expressed
in quantitative form then known as data. The success of any project is depended upon the
accuracy of available data. Accurate information can be collected with help of certain
methods/ techniques. These specific methods for finding information of the system are
termed as fact finding techniques. Interview, Questionnaire, Documentation and
Observations are the different fact finding techniques used by the analyst. The analyst
may use more than one technique for investigation.
No system details will left out.
Right problems are identified.
Repetitive work is avoided.
Wrong and incomplete details are not to be collected.
There are,
a. Interview.
b. Questionnaires
c. Documentations.
d. Observations
Interview:
We used this technique for collect the information from individual or from group.
It is better to learn from practice rather than books. In interview a discussion include
formal and informal thing about project.
Questionnaires:
Questionnaires may be used as supplement to interviews. Questionnaires can be
considered as a structured interview form. We asked them following set of questions to
our client for understand the project need and requirement.
Q.1) Name of the company: --------------- Date: --
Q.2) Basic information about item:
(a) What are the inventory items your company have?
(b) Is there serial no. for item?
(c) What is the item category?
(d) What is the unit of measurement used?
(e) Does your item come with expiry date?
Q.3) is there return policy?
Q.4) how do you keep the track stock and cost information of the items?
Q.5) who managed system?
Q.6) what privilege for employee?
Q.7) do you used a computerized inventory system before?
Q.8) any other information?
Documentation:
Believing record other than people, thus a good system analyst always gets
information from related system is published in the sources like newspapers, magazines,
journals, documents etc. This record review helps the analyst to get valuable information
about the system and the organization.
Observation:
We observed the other fact finding techniques, in this method the analyst himself
visits the organization and observes and understand the flow of documents, working of
the existing system, the users of the system etc. For this method to be adopted it takes an
analyst to perform this job as he knows which points should be noticed and highlighted.
In analyst may observe the unwanted things as well and simply cause delay in the
development of the new system
Feasibility study
An important outcome of the preliminary investigation is determined that the
system requested is feasible. Our hands on experience on all shades of expertise dealing
with project management give us a cutting edge advantage to prepare a realistic
feasibility study which will give our clients a true picture of constraints associated with a
project in terms of time, money, technology and operational aspects that will impact a
user’s need analysis and assessment of project. Our feasibility gives a complete
overview and the detailed view important for the sponsors before deciding to undertake a
project or otherwise. We understand that the laid down criteria are based on the
limitations and dynamics of every organization’s own set of conditions. So we have a
detailed review of conditions leaving no area unattended. Our feasibility will not let the
decision makers feel short of information. We cover every aspect under the following
four main categories.
Technical feasibility:
We evaluated their business situation and consider various technical options and
issues to make sure that a bug free, secure and efficient services is proposed. We
examined all eventualities to make an agile solution with your present and future needs
in mind. We make strive to keep you ahead of your competition and adopt a proactive
approach to apprise you of upcoming technical challenges. The most important aspect of
our study objectives is to make sure that there are no production barriers and there are
minimum external dependence in the proposed solution. The system integrates
technically with available add-ons.
Financial feasibility:
Our experts carry out economic analysis for evaluating the effectiveness of a
proposed solution against the existing solution and all other available options, giving due
consideration to limitations and constraints of our clients. In other words we provide a
snapshot of cost/benefits analysis. Our process determines the immediate and projected
benefits and savings that are expected from a proposed system and compare them with
the immediate and the projected costs. Obviously the benefits must outweigh the costs to
make it a viable solution, which makes a business sense.
Operational feasibility:
Under this category of service we conduct a study to analysis and determine
whether your business need can be fulfilled by using a proposed solution. The result of
our operational feasibility Study will clearly outline that the solution proposed for your
business is operationally workable and conveniently solves your problems under
consideration after the proposal is implemented. This is sometimes referred to as
‘Feasibility Evaluations’. We would precisely describe how the system will interact with
the systems and persons around. Our feasibility report would provide results of interest
to all stakeholders
Timeline feasibility:
It is important to understand that a need must be fulfilled when it has to be. Some
otherwise feasible and highly desirable projects can become non-feasible due to very
restrictive timeline constraints. This fact makes it imperative that milestones are clearly
linked to the timeline and projects are well conceived with safe unforeseen margins. We
make sure that we strictly follow what has been stated above.
System UMLDiagram
Class Diagram: A class diagram is an illustration of the relationships and source code
dependencies among classes in the Unified Modeling Language (UML). In this context, a class defines the methods and variables in an object, which is a specific entity in a program or the unit of code representing that entity.
Fig: 13.1 Class diagram for Inventory management system
Use Case:A use case diagram is a graphic depiction of the interactions among the elements
of a system. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements.
Fig: 13.2 Use diagram for Inventory management system
Entity Relationship Diagram (ERD):ERDs show entities in a database and relationships between tables within
that database. It is essential to have ER-Diagrams if you want to create a good database design. The diagrams help focus on how the database actually works
Fig: 13.3 ERD diagram for Inventory management system
Sequence Diagram:A Sequence diagram is an interaction diagram that shows how
processes operate with one another and what is their order. It is a construct of a Message Sequence Chart. A sequence diagram shows object interactions arranged in time sequence.
Fig: 13.4.1 sequence diagram for Customer
Sequence Diagram:
Fig: 13.4.2 sequence diagram for Supplier
Sequence Diagram:
Fig: 13.4.3 sequence diagram for Admin
Collaboration Diagram:
Like sequence diagrams, collaboration diagrams are also interaction diagrams. Collaboration diagrams convey the same information as sequence diagrams, but focus on object roles instead of the times that messages are sent. In a sequence diagram, object roles are the vertices and messages are the connecting links.
Fig: 13.5 Collaboration diagram for Inventory management system
Activity Diagram:Activity diagrams are graphical representations of workflows of
stepwise activities and actions with support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams are intended to model both computational and organizational processes.
Fig: 13.6.1 Activity diagram for Customer
Activity Diagram:
Fig: 13.6.2 Activity diagram for Supplier
Activity Diagram:
Fig: 13.6.3 Activity diagram for Admin
State Chart Diagram:Objects have behaviours and states. The state of an object depends on its
current activity or condition. A state chart diagram shows the possible states of the object and the transitions that cause a change in state.
Fig: 13.7 State chart diagram for Inventory management system
Object Diagram:An object diagram in the Unified Modeling Language (UML), is a diagram that
shows a complete or partial view of the structure of a modeled system at a specific time.
Fig: 13.8 Object diagram for Inventory management system
Timing Diagram:Timing diagrams are used to show interactions when a primary purpose
of the diagram is to reason about time. Timing diagrams focus on conditions changing within and among Lifelines along a linear time axis.
Fig: 13.9 Timing diagram for Inventory management system
Component Diagram:I n the Unified Modeling Language, a component diagram depicts how
components are wired together to form larger components and or software systems. They are used to illustrate the structure of arbitrarily complex systems.
Fig: 13.10 Component diagram for Inventory management system
Interaction Overview Diagram:Interaction diagrams are models that describe how a group of objects
collaborate in some behaviour typically a single use-case. The diagrams show a number of example objects and the messages that are passed between these objects within the use-case.
Fig: 13.11 Interaction Overview diagram for Inventory management system
Deployment Diagram:A deployment diagram in the Unified Modeling Language models the
physical deployment of artefacts on nodes.
Fig: 13.12 Deployment diagram for Inventory management system
Admin
Package DiagramA package diagram in the Unified Modeling Language depicts the
dependencies between the packages that make up a model.
Fig: 13.13 Package diagram for Inventory management system
System Design
Module Hierarchy
Employee maintenance
Product maintenance
Customer maintenance
Expense
Reports
Billings
Add/update/delete
Data Dictionary
A data dictionary is a central storehouse of information of about the system’s
data. An analyst uses data dictionary to collect, document and organize specific fact
about system, including the contents of data flow, data stores, entities and process
Name: Customer table
Purpose: Stored customer detail.
Sr.No Field
Name
Type Size Constrain
t
Description
1 Cust_id int 10 Primary key Customer id
2 Cust_name varchar 40 Not null Customer name
3 Cust_contact int 10 Not null Customer no
4 Cust_gender Varchar 8 Not null Customer sex
Name: Employee table
Purpose: Stored employee detail.
Sr.N
o
Field Name Type Size Constraint Descriptio
n1 Emp_id int 10 Primary key Employee id
2 Emp_fullname varchar 40 Not null Employee full
name
3 Emp_contact int 10 Not null Employee no
4 Emp_salary Float 5 Not null Employee
salary
5 Emp_dob Date 3bytes Not null Employee date
of birth
6 Emp_joining Date 3bytes Not null Employee
joining date
7 Emp_picture byte 200 Not null Employee
profile picture
8 Emp_gender varchar 8 Not null Employee sex
9 Emp_address Varchar 100 Not null Employee
address
10 Emp_email Varchar 50 Not null Employee
email address
11 Emp_designatio
n
Varchar 20 Not null Employee post
Name: Supplier table
Purpose: Stored supplier detail.
Sr.N
o
Field Name Type Size Constrain
t
Description
1 Sup_id int 10 Primary key Supplier id
2 Sup_name varchar 40 Not null Supplier name
3 Sup_contact int 10 Not null Supplier no
4 Sup_email Varchar 30 Not null Supplier email
address
5 Product_name Varchar 40 Not null Product name
6 Product_Descrip Varchar 100 Not null Product detail
7 Sup_company Varchar 30 Not null Supplier company
8 Product_price Float 10 Not null Product price
9 Quantity Int 10 Not null Product quantity
10 Tax Float 5 Not null All tax
11 Amount Float 10 Not null Total amount
12 Discount Float 5 Not null Discount on
product
Name: Vendor table
Purpose: Stored vendor detail.
Sr.N
o
Field
Name
Type Size Constrain
t
Description
1 Ven_id int 10 Primary key Vendor id
2 Ven_name varchar 40 Not null Vendor name
3 ven_contact int 10 Not null Vendor no
4 Ven_email Varchar 30 Not null Vendor email
address
5 Product_name Varchar 40 Not null Product name
6 Product_price Float 10 Not null Product price
7 Quantity Int 10 Not null Product quantity
8 Tax Float 5 Not null All tax
9 Amount Float 10 Not null Total amount
10 Discount Float 5 Not null Discount on
product
Name: Bank detail table.
Purpose: Stored bank detail.
Sr.No Field
Name
Type Size Constrain
t
Description
1 Acc_no int 10 Primary key Account no
2 Ban_name varchar 40 Not null Bank name
3 Sup_id Int 10 Foreign key Supplier id
4 Emp_id Int 10 Foreign key Employee id
5 Ven_id Int 10 Foreign key Vendor id
6 Information Varchar 30 Not null Extra information
7 Acc_type Varchar 40 Not null Account type
8 IFSC_code Int 8 Not null Bank
identification
code
9 Ban_branch Varchar 20 Not null Bank branch
name
Name: Stock table
Purpose: Stored stock detail.
Sr.No Field
Name
Type Size Constrain
t
Description
1 St_id Int 10 Primary key Stock id
2 St_date Date 3bytes Not null Stock date
3 pro_name varchar 40 Not null Product name
4 Information
Varchar
30 Not null Extra
information
5 Pro_type Varchar 40 Not null Product type
6 Pro_price Float 10 Not null Product price
7 Quantity Int 8 Not null Total quantity
8 Amount Int 20 Not null Total amount
Name: Invoice table
Purpose: Stored invoice detail.
Sr.No Field Name Type Size Constrain
t
Description
1 Invoice_id Int 10 Primary key Invoice id
2 Cust_id Int 10 Foreign key Customer id
3 Sup_id Int 10 Foreign key Supplier id
4 Ven_id Int 10 Foreign key Vendor id
5 Date Date 3bytes Not null Invoice date
6 Pro_name
Varchar
30 Not null Product name
7 Pro_quantity Varchar 40 Not null Product quantity
8 Pro_price Float 10 Not null Product price
9 Tax Float 8 Not null All tax
10 Discount Float 6 Not null Product
discount
11 Total_amount Float 10 Not null Final amount
Name: Payment table
Purpose: Stored payment detail.
Sr.No Field Name Type Size Constraint Description1 Pay_id Int 10 Primary key Payment id
2 Emp_id Int 10 Foreign key Employee id
3 Sup_id Int 10 Foreign key Supplier id
4 Ven_id Int 10 Foreign key Vendor id
5 Pay_name varchar 40 Not null Pay for
6 Pay_date Date 3bytes Not null Payment date
7 Amount Float 10 Not null Total amount
6 Start_date Date 3bytes Not null Payment from
7 End_date Date 3bytes Not null Payment to
8 Tax Float 6 Not null All tax
Name: Admin table
Purpose: Stored admin detail.
Sr.N
o
Field
Name
Type Size Constrain
t
Description
1 User_id Varchar 20 Primary key User name
2 Password Varchar 20 Not null User password
3 C_password Varchar 20 Not null Confirm password
Screen Layout
Home Page :
Login Screen:
LogIn Screen :
Supplier Detail :
Employee Information :
Customer Detail :
Vendor Detail :
Main Screen:
ValidationVendor :
Add Item :
REPORTEmployee Detail :
Vendor detail :
Employee Operator Manager0
0.51
1.52
2.53
3.54
4.55
4.3
2.5
3.5
2.4
4.4
1.8
1 1 1
Employee Detailwork extra hour Series 3
33%
13%18%
37%
Sales For Vendor
1st Qtr2nd Qtr3rd Qtr4th Qtr
Purchase Detail :
Invoice :
23%
20%
17%
40%
Purchase Item From Suplier
1st Qtr2nd Qtr3rd Qtr4th Qtr
System
Implementation
Test Procedure and Implementation
Test case id: - tc_01
Test case 1:- Login Form
Description:Admin or Users enter valid username and password. Log in values are mapped in
database table to check id and password is ok. If entry exist then login process will be successful.
Test
Case
Step
Description
Test Data Expected Result
Actual Result Status
01 Open log in window .enter user name & password
Valid user name & password
Valid user name & password and welcome screen appear
Successfully log in page and display menu page
Pass
02 Select user name and press enter
From list Error message Password field not empty
Pass
03 Enter password and
Press enter
No input Error message User field not empty
Pass
04 Enter user name and password and
Press enter
Raj12 Error message Password must be greater than 8 character
pass
Test case id: - tc_02
Test case 1:- New User Form
Description:Admin create a user name and password for a new user.
Test
Case
Step
Description
Test Data Actual Result Status
01 Enter user name Valid user name User name available Pass
02 Enter pass word 2123 Password minimum 8 digit
Pass
03 Enter confirm password
23434 Password not match Pass
04 Enter user name and password and
Press enter
Raj12 Password or user name invalid
pass
05 All field empty and press create button
No input Error message Pass
Test case id: - tc_03
Test case 1:- Employee Form
Description:Admin enter the employee detail
Test
Case
Step
Description
Test Data Actual Result Status
01 Enter employee full name
Input number only character allow Pass
02 Enter address Input special character
only alpha numeric value allow
Pass
03 Enter contact no Enter 1213 Must be 10 digit no Pass