Inventory Management System

Inventory Management System 216195BEIT30076
KADI SARVA VISHWAVIDYALAYA - UNIVERSITY

LDRP INSTITUTE OF TECHNOLOGY AND RESEARCH, GANDHINAGAR.
A Project
On
Online Inventory Management System
Subject:-Object Oriented Analysis And Design
Bachelors of Information Technology
4th Sem IT Department
Year -2017
Prepared By:- Mr. Smit Joshi (216195BEIT30076)
Guided By:-
Ms. Palak Parmar
Lecturer CE-IT Dept.
LDRP-ITR
Gandhinagar
1
LDRP ITR: I.T Dept.
CANDIDATE DECLARATION
I declare that my 4th semester report entered ONLINE INVENTORY MANAGEMENT is

my own work conducted under supervision of Ms. Palak Parmar
I Further declare that to the best of my knowledge the report for B.E 4th sem does not contain
part of the work which has submitted for the award of B.E degree either in this or any other
university without proper citation
Candidates sign: Submitted to:
Ms. Palak Parmar

Smit Joshi Faculty CE/IT Dept.
L.D.R.P-I.T.R, Gandhinagar .
2
LDRP ITR: I.T Dept.
CERTIFICATE
This is to certify that the project report entitled CUSTOMER RELATIONSHIP

MANAGEMENT is a beneficed report of the work carried out by Mr. Smit Joshi
(216195BEIT30076) under guidance and supervision for the partial fulfillment of degree of the
bachelor of Information Technology at LDRP Institute of Technology and Research-
Gandhinagar.
To the best of my knowledge and belief, this work embodies the work of candidates
themselves, has duly been completed, fulfils the requirement of the ordinance relating to the
bachelor degree of the university and is up to the standard in respect of content, presentation and
language for being referred to the examiner.
Ms. Palak Parmar Prof. Mehul Barot

Lecturer CE-IT Dept. Head of Department
Dept. of Info. Tech., Dept. of Info. Tech.,
LDRP-ITR,Gandhinagar, Gujarat LDRP-ITR,Gandhinagar, Gujarat
Signature and Name of supervisor Signature and Name of HOD
3
LDRP ITR: I.T Dept.
AKNOWLEDGMENT
Working in good environment and motivation enhance the quality of the work and we
get it from our college through our Object Oriented Analysis and development Project.
We have been permitted to take this golden opportunity under the expert guidance of
Ms. Palak Parmar from LDRP-ITR, Gandhinagar.
We are heartily thankful to her to make complete our project successfully. He has given
us his full experience and extra knowledge in practical field. We are also thankful to our head of
department Mr. Mehul Barot and all CE/IT staff to guide us.
Finally we thank all the people who had directly or indirectly help as to complete our
project.
Candidate name Enrollment no.
1. Smit Joshi 216195BEIT30076
4
LDRP ITR: I.T Dept.
Table of Contents
Title Page no
Abstract.
Tables
1. List of figures ..
2. List of tables.
Notations
Chapters
1. Introduction
1.1 Project Definition..
1.2 Project Description.
1.3 Purpose...
1.4 Scope.
2. System Requirements Study.
2.1 User Characteristics
2.2 Hardware and software Requirements..
3. Class Modeling..
3.1 Data dictionary for class
3.2 Class Diagram
4. State Modeling.
4.1 State Diagrams
5. Interaction Modeling..
5.1 Use case Diagrams..
5.2 Sequence Diagrams..
5.3 Activity Diagram
6. Component Diagram..
7. Collaboration Diagram..
8. Deployment Diagram..
9. Limitation and future Enhancement
10. References..
5
LDRP ITR: I.T Dept.
ABSTRACT
Inventory Management System is a computer-based system for

tracking inventory levels, orders, sales and deliveries. It can also be used in
the manufacturing industry to create a work order, bill of materials and other production-related
documents. Companies use inventory management software to avoid product overstock and
outages. It is a tool for organizing inventory data that before was generally stored in hard-copy
form or in spreadsheets.
6
LDRP ITR: I.T Dept.
TABLES
List of Figures:
Diagram
Class Diagram
State Diagram
Use case Diagram
Sequence Diagram
Activity Diagram
Collaboration Diagram
Development Model
List of Tables:
Sr.No. Table Description

1. User Users detail.
2. Employee Employees detail.
3. Order Orders detail.
4. Activity Info. About different activity.
5. Delivered Info. Delivered Item plane.
6. Payment Payment detail.
7. Invoice Invoice detail.
NOTATIONS
Activation :
Top Package::Actor1
Actor :
Top Package::Class1
Class :
Control Flow :
7
LDRP ITR: I.T Dept.
Decision :
Final State :
Generalization :
Initial State :
Final State :
System
System Boundary :
UseCase1
Use case :
8
LDRP ITR: I.T Dept.
CHAPTERS
9
LDRP ITR: I.T Dept.
CHAPTER 1
1.) INTRODUCTION
1.1 Project Summary:
Inventory Management Systems is a key instrument for businesses when tracking their
inventory.
Typically, Inventory Management Systems are used by firms that either sell a product or
manufacture a product for purposes of accounting for all the tangible goods that allow for
a sale of a finished product, or parts for making a product.
The size and volume of a firm help dictate whether or not a firm is in need of such a
system as they can be quite extensive and costly.
Large firms that have thousands of components must have a system in place for the
primary objective of tracking their assets.
There are three main reasons why an Inventory Management System is needed such as
timing/lead time, forecasting, and utilizing economies of scale.
The Inventory Management System is no different from any other information system in
that there are factors that make it successful.
These five critical components are hardware, software, data, procedures and people.
As these factors are discussed throughout the next several sections it becomes evident
that they are contingent upon one another, and frankly will not function efficiently
without the other.
1.2 Purpose:
Companies often use inventory management software to reduce their carrying costs.
The software is used to track products and parts as they are transported from a vendor to
a warehouse, between warehouses, and finally to a retail location or directly to a
customer.
Inventory management software is used for a variety of purposes, including:
Maintaining a balance between too much and too little inventory.

Tracking inventory as it is transported between locations.
Receiving items into a warehouse or other location.
Picking, packing and shipping items from a warehouse.
Keeping track of product sales and inventory levels.
Cutting down on product obsolesces and spoilage.
Avoiding missing out on sales due to out-of-stock situations.
10
LDRP ITR: I.T Dept.
1.3 Scope:
This project fulfills all the requirements of the Inventory management. This application
is very useful for the Inventory management to maintain the information of the
Inventories.
Inventory management software is made up of several key components, all
working together to create a cohesive inventory for many organizations' systems.
These features include:
We can also manage some important key points of inventory management system
as listed below.
Order Management.
Asset Tracking.
Service Management.
Product Identification.
Inventory Optimization.
1.4 System Description:
Manufacturers primarily use inventory management system to create work orders and
bills of materials.
This facilitates the manufacturing process by helping manufacturers efficiently assemble
the tools and parts they need to perform specific tasks.
For more complex manufacturing jobs, manufacturers can create multilevel work orders
and bills of materials, which have a timeline of processes that need to happen in the
proper order to build a final product.
Other work orders that can be created using inventory management system include
reverse work orders and auto work orders.
Manufacturers also use inventory management software for tracking assets, receiving
new inventory and additional tasks businesses in other industries use it for.
11
LDRP ITR: I.T Dept.
CHAPTER 2
2. SYSTEM REQUIREMENT STUDY
2.1 USER CHERECTERSTICS:
The main objectives of this system are as below:-
Registration
Through this function admin or employee can register a new member who joined the
system. Admin can enroll new employee. So using this system online most of work of the
Inventory management is reduced. It provides better performance than the current system.
Authentication
User is authenticated by entering user name and password. He/she must enter correct
user name and password to use this system.
Admin
In this functions Administrator are handle database. Admin is able to insert update or
delete details. Admin also can generate report of system. So this system is very flexible.
2.2 Software and Hardware Requirements:

SOFTWARE REQUIREMENTS:-
Platform
Windows Operating system
Software requirement
Visual Studio .Net 2010 Enterprise Edition
Database -SQL Server 2005 Enterprise Edition
Browser internet explorer or else
12
LDRP ITR: I.T Dept.
HARDWARE SPECIFICATIONS:-
Processor : Intel Pentium or more

Motherboard : Intel Chipset Motherboard.
Ram : 128 MB or more
Cache : 512 KB
Hard disk : 16 GB hard disk recommended
Disk Drive : 1.44MB Floppy Disk Drive
Monitor : 1024 x 720 Display
13
LDRP ITR: I.T Dept.
CHAPTER 3
3. CLASS MODELING:
CLASS DIAGRAM
-End1
*
-End2
*
Binary association :
Top Package::Class1
Class :
Generalization :
* 1
Aggregation :
3.1 DATA DICTIONARY FOR CLASS :

Admin: This Class Contains the Information of administrator details.
Attributes: ID, Admin name, admin e-mail id.
Member: This class contains the information about the member.
Attributes: ID, Name, Address, Age, Email-id, contact no., joining date, Position.
User: This class contains information about the user.
Attributes: ID, Name, Password, E-mail, Contact, Gender, Age.
Order: This class contains information about Order.
Attributes: Order no., Time stamp, payment, Description, Shipment status.
Invoice: this class contains invoice information.
14
LDRP ITR: I.T Dept.
Attributes: Invoice id, Member id, Order Id, Payment, Date, Time Stamp.
Stock: This table contain information about stock.
Attributes: Stock, Name, Status.
3.2 CLASS DIAGRAM:
A class is a set of objects that share a common structure and common behavior
(the same attributes, operations, relationships and semantics).
A class is an abstraction o real-world items. When these items exist in the real
world they are instances of the class and are referred to as objects
The attribute and operation sections of the class box can be suppressed to
Reduce detail in an overview. Suppressing a section makes no statement
Absence of attributes or operations, but drawing an empty section explicitly states
that there are no elements in that part.
15
LDRP ITR: I.T Dept.
CLASS DIAGRAM :
ADMIN
PRODUCT
ID
PRICE
NAME
STOCK
CONTACT
DISCRIPTION
TRACK OREDER
MANAGE SYSTEM DILIVARY
INVENTORY SYSTEM
ID
NAME
LOCATION
CONTACT
ADMINISTRATION
CUSTOMER
CASIER
STOCK KEEPER
INVOTORY MANAGER
CASIER
ID ID
NAME NAME
CONTACT CONTACT
ADDRESS
ORDER DETAIL
TRACK ORDER
PRODUCT
RECIVE PAYMENT MANAGE OREDER
MANAGE STOCK
TRACK ORDER
16
LDRP ITR: I.T Dept.
CHAPTER 4
4. STATE MODELING:
STATE MODEL
State :
Final State :
Initial State :
Transition :
Valuable technique for modelling behaviors that can be described in terms of:
States
Events
Transitions
17
LDRP ITR: I.T Dept.
STATE MODEL:
RE-ORDER PRODUCTS
IN INVOTORY CHECK
INVONTORY
start
CHECK QUANTITY
PRODUCT MISSING
OUT FOR
quantity checked
DELIVERY
check again delivery
CHECK QUALITY
PRODUCT SEND AT PRODUCT
DEPATURE SITE DELIVERED
TAKE ORDER
quality checked product ordered invoiceing
stop
18
LDRP ITR: I.T Dept.
CHAPTER 5
5. Interaction modeling:
5.1 USE CASE DIAGRAM
The requirements of a system can be captured by Use Case Diagrams. They are modelled
to capture the intended behavior of the system. Use Cases interact with human or actors that use
the system to accomplish some work. They define a set of sequence of actions that a system
performs to yield an observable result of value to an actor. An actor represents a role that a
human, a hardware device or another system plays with a system.
Use Cases are used to come to a common understanding with the systems end users and
the domain experts. They help in validating the systems architecture and its evolution process.
After a thorough understanding of the requirements of the system the use cases are modelled
following the steps mentioned below: -
Identify the actors that interact with the system.

Organize actors according to their roles.
Identify the primary ways in which an actor interacts with the system elements.
Organize these behaviors as use cases.
19
LDRP ITR: I.T Dept.
USE CASE DIAGRAM:
Inventory Management System
Genrate Order
Payment
Createdby Trial
Vers ion
Createdby Trial
Vers ion
Createdby Trial
Vers ion
cashier Invoice
Createdby Trial
Vers ion
Createdby Trial
Vers ion
Createdby Trial
Vers ion
Createdby Trial
Vers ion
Createdby Trial
Vers ion
View Shipment Status Coustomer

Createdby Trial
Vers ion
Admin
Createdby Trial
Vers ion
Autentication
Createdby Trial
Vers ion
Createdby Trial
Vers ion
Stock keeper Manage Stock
Order Shipment
20
LDRP ITR: I.T Dept.
5.2 SEQUENCE DIAGRAM:
A sequence diagram is an interaction diagrams that shows how objects operate with one
another and in what order. It is a construct of a message sequence chart.
A sequence diagram shows object interactions arranged in time sequence.

It depicts the objects and classes involved in the scenario and the sequence of messages
exchanged between the objects needed to carry out the functionality of the scenario.
Sequence diagrams are typically associated with use case realizations in the Logical View
of the system under development.
This allows the specification of simple runtime scenarios in a graphical manner.
SEQUENCE DIAGRAM:
Coustomer Inventory Management System Authentication
login
login
Authentication
Authentication
Show Order
view Items
Order Details
Check Stock
Order
Stock Status
Order Shipment
view Sipment Status
Shipment status
Shipment Detail
Manage Stock
Recive Payment
Payment
Manage User
Invoice
21
LDRP ITR: I.T Dept.
5.3 ACTIVITY DIAGRAM:

An activity diagrams essentially a flowchart showing flow of flow of control from activity to
activity. We use activity diagram to model the diagram aspects of a system. For the most part
this involves modelling the sequential (and possibly concurrent) steps in a computational
process. With an activity diagram, you can also model the flow of an object as move from state
to state at a different points in the flow of control activity diagram may stand alone to visualize,
specify, construct and document the dynamics of a society of objects, or they may be use to
model the flow of control of an operation.
Basic Notations for Activity Diagram:
Initial node: The filled in circle is the starting point of the diagram. An initial node isnt
required although it does make it significantly easier to read the diagram.
Activity final node: The filled circle with a border is the ending point. An activity
diagram can have zero or more activity final nodes.
Activity: The rounded rectangles represent activities that occur.
Flow/edge: The arrows on the diagram. Although there is a subtle difference between
flows and edges we have never seen a practical purpose for the difference although we
have no doubt one exists. Well use the term flow.
Fork: A black bar with one flow going into it and several leaving it. This denotes the
beginning of parallel activity.
Join: A black bar with several flows entering it and one leaving it. All flows going into
the join must reach it before processing may continue. This denotes the end of parallel
processing.
22
LDRP ITR: I.T Dept.
Condition: Text such as [Incorrect Form] on a flow, defining a guard which must
evaluate to true in order to traverse the node.
Decision: A diamond with one flow entering and several leaving. The flows leaving
include conditions although some modelers will not indicate the conditions if it is
obvious
ACTIVITY DIAGRAM:
Decision :
Control Flow :
Final State :
Initial State :
State :
Action state :
Fork line :
Join line :
23
LDRP ITR: I.T Dept.
ACTIVITY DIAGRAM:
1. ACTIVITY DIAGRAM FOR COUSTOMER:
Register
login
Order
Manage Account
Invoice
Feedback
No
payment
Yes
shipment status
Logout
24
LDRP ITR: I.T Dept.
2). ACTIVITY MODEL FOR ADMINISTRATIOR:
Register
login
Manage order
Manage Account
Manage Stock Manage
Finanace
Recive payments
No
Stock
Yes
Shipment status
Logout
25
LDRP ITR: I.T Dept.
CHAPTER 6
6. COMPONENT DIAGRAM:
A component diagram describes the organization and wiring of the physical
components in a system. Component diagrams are often drawn to help model implementation
details and double-check that every aspect of the system's required functions is covered by
planned development. In the first version of UML, components included in these diagrams were
physical: documents, database table, files, and executables, all physical elements with a location.
In the world of UML 2, these components are less physical and more conceptual stand-alone
design elements such as a business process that provides or requires interfaces to interact with
other constructs in the system. The physical elements described in UML 1, like files and
documents, are now referred to as artifacts. A UML 2 component may contain multiple physical
artifacts if they naturally belong together.
NOTATIONS:
Component:
Interface:
Dependencies:
Port:
26
LDRP ITR: I.T Dept.
6. COMPONENT DIAGRAM:
27
LDRP ITR: I.T Dept.
CHAPTER 7
7. COLLABORATION DIAGRAM:
A collaboration diagram, also called a communication diagram or interaction diagram, is an
illustration of the relationships and interactions among software objects in the Unified Modeling
Language (UML). The concept is more than a decade old although it has been refined as
modeling paradigms have evolved.
NOTATIONS:
Objects :
Multi-object :
Association role:
Delegation:
Constraint:
Note :
28
LDRP ITR: I.T Dept.
7. COLLABORATION DIAGRAM:
29
LDRP ITR: I.T Dept.
CHAPTER 8
8. DEPLOYMENT DIAGRAM:
Deployment diagram is a structure diagram which shows architecture of the system
as deployment (distribution) of software artifacts to deployment targets. Artifacts represent
concrete elements in the physical world that are the result of a development process.
NOTATIONS:
Package:
Objects:
Component:
Interfaces:
Data flow:
Constraint:
30
LDRP ITR: I.T Dept.
8. DEPLOYMENT DIAGRAM:
31
LDRP ITR: I.T Dept.
CHAPTER 9
9.1 Limitations:
Software or application can be error free but never be failure free i.e. software of
application can be syntactically correct but semantically it can have some shortcomings.
Failure is not only concerned with the syntax error of our program, but is also concerned
with our logical error or requirement omission.
Requirement itself is an ever changing entity, in turn, software or developed application

is also dynamic entity they cant remain static throughout its lifetime.
When requirements change, older requirement may become shortcoming or lack of newly
identified requirement may also become an important drawback of our system. Finally
conclusion is, every software or application possesses some type of deficiency.
Our developed system is, also not an exception in this case, having mentioned the
limitation.
Application has not messaging facility.
Application is not useful when new requirements arrive; changes according to the
requirements are acceptable.
Application required some management through manpower.
9.2 Future Enhancement:

Software or application is continuously changing entity. Software or application should
be reflected with new features whenever new requirements emerge.
Evolution and Enhancement are big phases in any softwares or application lifecycle. We
have to project towards some newly emerged and previously ignored functionality in
way to enhance the system.
Once system is implemented and installed into its essential environment, we have to
examine newly emerging requirements, misinterpretation of older requirements, impact
due to omission of some important requirements, and failure of some features
Try to remove all above limitation from our project.
SMS Facilities can be added in the application which is not provided in

the application.
Online Payment Facilities can be added in our application in future.
32
LDRP ITR: I.T Dept.
CHAPTER 10
References:
The Ultimate VB.NET and ASP.NET Code Book

By- Karl Moore
ASP.NET Web Developers Guide.

By- Syngress Press
ASP.NET Unshielded
By- Stephen Walther
Microsoft .Net framework 2.0 Web based client development

By- Glenn Johnson and Tenny Northrup
WEBSITES:-
www.google.com
www.codeproject.com
www.startvndotnet.com
www.wikipedia.com
www.asp.net
msdn2.microsoft.com
33
LDRP ITR: I.T Dept.

Inventory Management System

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Inventory Management System

Caricato da

Copyright:

Formati disponibili

Inventory Management System 216195BEIT30076

KADI SARVA VISHWAVIDYALAYA - UNIVERSITY

4th Sem IT Department

Prepared By:- Mr. Smit Joshi (216195BEIT30076)

I declare that my 4th semester report entered ONLINE INVENTORY MANAGEMENT is

Candidates sign: Submitted to:

Ms. Palak Parmar

This is to certify that the project report entitled CUSTOMER RELATIONSHIP

Ms. Palak Parmar Prof. Mehul Barot

Signature and Name of supervisor Signature and Name of HOD

Ms. Palak Parmar from LDRP-ITR, Gandhinagar.

Candidate name Enrollment no.

1. Smit Joshi 216195BEIT30076

Inventory Management System is a computer-based system for

Sr.No. Table Description

Maintaining a balance between too much and too little inventory.

1.4 System Description:

2. SYSTEM REQUIREMENT STUDY

2.1 USER CHERECTERSTICS:

The main objectives of this system are as below:-

2.2 Software and Hardware Requirements:

Visual Studio .Net 2010 Enterprise Edition

Database -SQL Server 2005 Enterprise Edition

Browser internet explorer or else

Processor : Intel Pentium or more

3.1 DATA DICTIONARY FOR CLASS :

Invoice: this class contains invoice information.

3.2 CLASS DIAGRAM:

MANAGE SYSTEM DILIVARY

5.1 USE CASE DIAGRAM

Identify the actors that interact with the system.

USE CASE DIAGRAM:

Inventory Management System

View Shipment Status Coustomer

Stock keeper Manage Stock

5.2 SEQUENCE DIAGRAM:

A sequence diagram shows object interactions arranged in time sequence.

Coustomer Inventory Management System Authentication

5.3 ACTIVITY DIAGRAM:

Basic Notations for Activity Diagram:

Activity: The rounded rectangles represent activities that occur.

2). ACTIVITY MODEL FOR ADMINISTRATIOR:

Requirement itself is an ever changing entity, in turn, software or developed application

Application has not messaging facility.

Application required some management through manpower.

9.2 Future Enhancement:

SMS Facilities can be added in the application which is not provided in

Online Payment Facilities can be added in our application in future.

The Ultimate VB.NET and ASP.NET Code Book

ASP.NET Web Developers Guide.

Microsoft .Net framework 2.0 Web based client development

Potrebbero piacerti anche