A

PROJECT REPORT ON
“INVENTORY MANAGEMENT SYSTEM”

Submitted in partial fulfillment of requirement of

PROJECT for academic year 2009-10.

Submitted by
MALEWADKAR PRANAV P.
(Roll. No. 33)

Guided By
PROF. DEEPALI CHAVAN

Department of Computer Engineering

PCT’s Parshvanath College of Engineering
University of Mumbai
(2009-2010)
 Department of Computer Engineering,
Parshvanath Charitable Trust’s
Parshvanath College of Engineering
Kasarvadavali, G. B. Road, Thane.

CERTIFICATE

This is to certify that

MALEWADKAR PRANAV P.
(Roll. No. 51)

has successfully completed the project work (Sem. VI) entitled “INVENTORY
MANAGEMENT SYSTEM” for the partial fulfillment of requirement of PROJECT for
the academic year 2009 - 2010.

______________ _______________ _____________

Internal Examiner External Examiner (Head of Department,

Computer Engineering)
 ACKNOWLEDGEMENT

I would like to thank our guide Prof. DEEPALI CHAVAN who greatly
inspired us for the project and for her valuable guidance and suggestions for
enhancing and clarifying the material at hand.

I would also like to thank Prof. S. M. TORASKAR, Head of Computer

Engineering Department, and other professors of the department who directly or
indirectly are of great help to us.

MALEWADKAR PRANAV P.
PROBLEM DEFINITION:-
Construct the design elements for a Inventory Management System that can
be used to manage the inventory for an organization. The system offers
techniques for inventory control and stock keeping. Suppliers are the primary
source of stock and supply the purchases of the organization.

The Inventory clerk checks the shipping details for each Purchase Order and
valid shipments are forwarded to the Inspector and invalid returned to the
supplier. The clerk also checks for low inventory or stock and creates the
appropriate purchase order for restocking.

The Inspector checks the shipment for quality issues by comparing the
shipment with a strict quality criteria. Shipments which meet the criteria are
added to the Accepted items list and those which do not pass are added to the
defective items list and returned to the supplier.
Data flow Diagram:

The functional model consists if multiple data flow diagrams which specify the
meaning of operations & constraints. A data flow diagram is a graph showing the
flow of data values from their sources in objects through processes that transform
them to their destinations in other objects. A data flow diagram does not show
control information such as the time at which processes are executed or decision
among alternate data paths, this information belongs to the dynamic model. A
data flow diagram does not show the organization of values into objects, this
information belongs to the object model.

A data flow diagram contains processes that transform data, data flows that move
data, actor objects that produce & consume data & data store objects that store
data passively. The data flow diagram shows the sequence of transformations
performed as well as the external values & objects the affect the computation.

Elements of Data Flow Diagram are:

 Processes
 Data Flows
 Actors
 Data Stores
 Nested Data Flow Diagrams
 Control Flows
 Specifying Operations
DFD Level 0 : Inventory Management System.

Solution:

In this DFD the whole system can be represented as input processing and output.

The Inputs are:

1. Supplier submits landing bill

2. PD gives bill details
3. Inspector Generates Report
4. Inventory Clerk checks Inventory
5. SR clerk creates a purchase order.

The outputs are:

1. Notices of Defective items, Shipment errors.

2. Purchase order
DFD Level 1 : Inventory Management System.

In this level the system is exposed with more processing details.

The processes that need to be carried out are –

1) Placing Order
2) Review Shipment and Update inventory.

The information is gathered from data stores like Inventory Items, Purchase Details etc
State Diagram
State diagrams (also called as State Chart Diagrams or State Transition Diagram)
are used to help the developer better understand any complex/ unusual
functionalities or business behavior of entire system, or a sub – system, or even a
single object in a system. This is done with the help of Behavior elements.

A state diagram shows a state machine. An activity diagram is a special case of a

state diagram in which all or most of the states are activity states & all or most of
the transitions are triggered by completion of activities in source state. As both
activity & state diagrams are useful in modeling the lifetime of an object. An
activity diagram shows flow of control from state to state.

Elements of State Diagrams:

 Initial States
 State
 Transition
 History States
 Final States
State Diagram:
Use Case Diagram
Use Cases represents typical sets of scenarios that help to structure, relate &
understand the essential requirements. A Use Case Diagram is a diagram that help
system analyst to discoverthe requirements of the target system from the user’s
perspective. Use Case Diagram can be used to describe the functionality of a
system in a horizontal way.

Use CaseDiagram:
 Describes the behavior of a system from a user’s state point.
 Provides functional description of a system & its major processes.
 Provides graphic description of the users of a system & what kinds of
interactions to expect within that system.
 Displays the details of the processes that occur within the system.

Use Case Diagram helps in:-

 Communicating with clients.
 Generating new use cases.
 Discovering new features(requirements).
Use Case Diagram : Inventory Management System.
Class Diagram

The first step in analyzing the requirements is to construct an object model. The
object model shows the static data structure of the real world system 7 organizes
it into workable pieces. The object model describes real world object classes &
their relationship to each other.

Information for the object model comes from the problem statement, Expert
knowledge of the application domain, & general knowledge of the real world.
Object model diagrams promote communication between computer professional
& application domain experts.
Class diagram : Inventory Management System.
Sequence Diagram

A sequence diagram depicts the sequence of actions that occur in a

system. The invocation of methods in each object & the order in which
the invocation occurs is captured in a sequence digram. This makes the
sequence diagram a very useful tool to easily represent the dynamic
behavior of a system.

A sequence diagram is two dimensional in nature. On the horizontal

axis, it shows the life of the object that it represents, while on the
vertical axis, it shows the sequence of the creation or invocation of
these objects.

Sequence diagram are typically used to model:

 Usage Scenarios.
 The Logic of Methods.
 The Logic of Services.
Sequence Diagram : Inventory Management System.

Sequence diagram for Purchasing Order

Collaboration Diagram

A collaboration diagram is interaction diagram that emphasizes the structural

organization of the objects that send & receives messages. Graphically, a
sequence diagram is a collection of the vertices & arcs. A collaboration diagram is
very between a symbol diagram & a sequence diagram. It describes a specific the
course of the scenarios. Collaboration diagram express similar information as in
sequence diagram, but shown in different way.

A distinguishing feature of a collaboration diagram is that it shows the objects &

their association with other objects in the system apart from how they interact
with each other. The association between objects is not represented in a
Sequence diagram.
Collaboration Diagram : Inventory Management System.