Implementation

UNIT 3 CASE STUDY: INVENTORY

CONTROL SYSTEM
Structure Page Nos.
3.0 Introduction 40
3.1 Objectives 40
3.2 Class Diagram 40
3.3 Object Diagram 41
3.4 Generalization and Association Diagram 42
3.5 Collaboration Diagram 44
3.6 Activity Diagram and Events 44
3.7 Use Case Diagram 48
3.8 Deployment Diagram 49
3.9 Summary 51

3.0 INTRODUCTION
Inventory control systems are used for managing the stocks of companies and big
distribution organisations. In this unit we will discuss about OOM for invention
control systems. We will cover class diagram design, object diagram different kind of
relationships, which include generalization, association and collaboration. We will
also discuss use case diagrams activities and events.

3.1 OBJECTIVES
After going through this unit, you should be able to:

• explain class diagram and object diagram of Inventory control System;

• describe generalization and Specialization of the system;
• describe collaboration diagram of the system;
• explain different activities and events of the systems, and
• explain deployment Diagram.

3.2 CLASS DIAGRAM

You know that a class is represented in a box like figure. Here we are taking the case
study of Inventory Control System.
Let us first set an idea of the Inventory Control System. It is the system in which you
can manage the stock of the products that a company sells. Basically, this system is
stock oriented where it makes sure that the quantity-in-stock does not reach the danger
level (Qty-ordered>Qty-in-stock).
In any system when we reach this level, we place a new order. To avoid this situation,
when in our system Qty-in-stock reaches a minimum level called the Reorder-level
then a new order is placed. Here, in this case study, you will see various diagrams.

40
 Case Study: Inventory
SUPPLIER CUSTOMER Control System
Supplier-id Customer-id
Supp-name Cust-name
Supp-address Cust-address
Supp-city Cust-city
Supp-state Cust-state
Supp-pincode Cust-pincode
Supp-status Cust-contact-no
Supp-Contact No1
Supp-phone 2 ADD
MODIFY
ADD DELETE
MODIFY VIEW
DELETE
VIEW

Figure 1: Class diagram represents the static structure of a System

You know that a class is represented in a box like Figure which can have at the most
three regions.

• Class Name
• List of Attributes
• List of Operations/Methods

PRODUCTS Class Name ORDER

Product-id Order-id
Name-of-product Attributes/properties Description No. of items
Category-id product-id order date
Description price
Qty-in-stock NEW ()
Danger-level EXISTING ()
Last-modification-date
Manufacturing-date

ADD
MODIFY Class Methods
DELETE
VIEW

INVOICE SALE

Invoice-no Receipt-no
Invoice-date Sale-of- sale
Customer-id Qty-sold
Supplier-id
Payment-status Detailed Item Sale ()
Daily Report Sale ()
Generate ()
Generate ()
View ()
View ()

Figure 2: Class diagram

3.3 OBJECT DIAGRAM

Object Diagram is an instance of a class. It describes the static structure of a system at
a particular time and are used to test the accuracy of classes.

41
Implementation
Generate
Enter

Product Details Report

Prod. No

PRODUCT
Bills of INVOICE
Material SUPPLIER

Invoice No.

Order by

by
EXISTING Cust Order- no
NEW
Code

Old CUSTOMER
New
Places ORDER
realise
an
Name
order
address details

Update
Identifies

details
Validation
Order Validate

Order
Order-no
Cost-no
Order Prod-no
received

Update Updates
Stock Files
Dispatch
Order
Qty-Stock
Order
Details

Figure 3: Object Diagram

3.4 GENERALIZATION AND ASSOCIATION

DIAGRAM
Generalisation: This is another name for inheritance, or an “is a” relationship. It
refers to a relationship between two classes where one class is a specialized version of
another.

42
 Case Study: Inventory
Super Type
Control System

Sub Type 1 Sub Type 2

CUSTOMER
Name: string

Credit ()

Regular Customer Customer

PRODUCT

New Product Existing Product

Figure 4: Generalisation of customer and product

Association: This represents static relationship between classes.

Roles represent the way the two classes see each other.

name
Class A Class B

1 role n role

ORDER CUSTOMER

Date-of order: date n 1 Customer details

Order-no
m
n
n

SUPPLIER

Supplier Details
m

Figure 5: Association of Order and customer

Aggregation: This denotes a strong ownership between class A, the whole, and class
B, and its part.
Hollow Diamond Simple Aggregation
Filled Diamond Strong Aggregation
PRODUCT INVOICE CUSTOMER

ORDER ORDER SUPPLIER

Figure 6: Aggregation
Ternary Association for Customer Supplier

CUSTOMER SUPPLIER

PRODUCT

Figure 7: Ternary association

43
Implementation
3.5 COLLABORATION DIAGRAM
This represents the interactions between objects as a series of sequenced messages.
Collaboration diagrams describe both the static structure and the dynamic behaviour
of a system.
Representation

Object: Class

1.2: [Condition]
1. Message Message
2. Message
3. Message
Object: Class Object: Class

Actor 2.3 [Condition]

Message

Object: Class

Figure 8 a: Collaboration diagram for inventory control system

: SUPPLIER

SUPPLIER
2.0 [SUPPLIER]
Invoice 3.0
1 places an
order [In Stock]

: ORDER : STOCK
Delivery new ()

New product 1
Customer [In order] 1.1

: PRODUCT

Figure 8 b: Collaboration diagram for the inventory control system

3.6 ACTIVITY DIAGRAM AND EVENTS

STATECHART DIAGRAM
This describes the dynamic behaviour of a system in response to external stimuli
• Basically, states are triggered by specific events.
Representation:

Initial state

State
Final state

event/action

Activity Diagram
This illustrates the dynamic nature of a system by modeling the flow of control from
activity to activity, or you can say operation on some class that results in a change in
the state of the system.

44
 Case Study: Inventory
• Basically, this shows the workflow model, or business process and the internal
Control System
operation

: Class

Activity

Activity

: Class

Figure 9: Activity flow

Synchronization and Splitting of Control

• A short heavy bar with two transitions entering it represents a synchronization
of Control.
• Splitting of Control that creates multiple states.

Synchronization
Splitting of Control

Demand Occurred
[Valid demand]
[Valid]

Check
QTY-in-stock
Cancel Demand

Validate the Order Place the Order

[Rush order] [else]

Reverse Order

Overnight Delivery Regular Delivery

Demand Occurred

Payment Made

Figure 10: Activity diagram

Events
Actions taken in Inventory Control System:
1) Order is placed by the CUSTOMER
2) Order is received by the SUPPLIER
3) Checking of Quantity-in-Stock and Reorder-level
4) Checking of Inventory Status
5) Generating Bills of Material

45
Implementation 6) Generating the INVOICE VOUCHER
7) Updating Inventory Status File

Do:
Validation
Main screen Do: Verify the
Do: display Select Place the Order Order
Customer/Supplier
Order

Order Rejected
Order
OK
Sector the
Order

Rejected Order Do: check

Do: reject the min. Qty-in-stock
Order

Cancel
Do: cancel the
Order

Min Qty >qty-in-stock

Reorder Level
Display Do: Display Bad Generation Do:
Do: finish process Message Generate
INVOICE

Generate
Do: Generate
Update Bills of Material
Do: Update (BOM)
Inventory Status
File

Figure 11: State diagram

46
 Case Study: Inventory
<<uses>> Control System
Place an Generate
Order INVOICE

<<extends>> <<extends>>
<<uses>> <<uses>>

Update Inventory Invoice of the

Generate Invoice of an item item for Supplier
Status File for Customer
Receipt

Receipt of an item Receipt for

for Customer Supplier

Place an
Order

<<uses>> <<uses>> <<uses>>

Validate Check
the order Qty-in-stock

Figure 12: Adding details

Data Flow Diagram for System

Order details Order Master File

Places 1.0 Check 1.0

CUSTOMER
demand Validation Order
Places an Validate the
order order

Invalid
1.2
2.0 Order Check
Reorder
Display
level
error Msg

8.0 2.0 trans details

Validated ROL
Transaction File
Generate Valid ROL
OK Qty-in-stock
Invoice & Qty-in-
Voucher stock

2.1 Reject
the Order
4.0 5.0
Inventory File
Generate Update
Bills of Inventory
Material Status

Figure 13: Data flow diagram

47
Implementation
3.7 USE CASE DIAGRAM
A “uses” relationship indicates that the use case is needed by another in order to
perform a task

• An “extends” relationship indicates alternative options under a certain use case.

• Use case diagrams model the functionality of a system using actors and use
cases.

• Use cases are services or functions provided by the system to its users.

Use Case

Use Case

(Actor)

Use Case

Figure 14: Use Case diagram

For Inventory Control System the initial design is:

SUB DIAGRAM
INVENTORY
CONTROL SYSTEM
Place an Order

Place an
Order

<<uses>> <<uses>> <<uses>>

Generate
INVOICE

Update Generate Generate

Inventory INVOICE BOM
Status File
Actor
(Customer) Update
Inventory
Status File
Generate
BOM

Figure 15: Initial design of the Inventory Control system

48
USER INTERFACE Case Study: Inventory
Control System

Run Program Interactive Display Power on

Load Standard Program

Operate
enter
Display Display Supplier
Menu Screen button Screen Run entries
do: show Customer Do: show supplier are set
Select

Run
Set supplier & Customer code
Program

Display
Order Screen Set upon Order
do: show order details

HOLD

60 Sec
without
input

Setup

Set Set Set

Qty-in-stock Order Qty Program

Set Set To
Qty-in-stock Order Qty View

Generating report mode

Generate Bills of
Material entry Report Run Button

Generate Invoice
Voucher Invoice
Press Card
Button

Generate Inventory
Status Report Press Report
Button

Figure 16: User interface

3.8 DEPLOYMENT DIAGRAM

Deployment diagram: This shows the hardware for your system, the software that is
installed on that hardware, and the middleware that is used to connect the machines to
one another.

49
Implementation
• Deployment diagrams depicts the physical resources in a system including
nodes, components and connections, where a node is a physical resource that
executes code components.

Node

Component

Figure 17: Deployment

Web Server
<<JDBC>>
<<Device>>
INVENTORY CUSTOMER DB Server
CONTROL JDBC
SYSTEM Inventory DB
<<databases>>
<<JSPs>> SUPPLIER

{order=order}
PRODUCTS

<<Deployment
Space.>>
Placing of Order

Execution: thread
Nested
Transaction: True

<<EJBs>>
Servlets

Inventory Control
Series
<<Web Services>>

Web Server

<<JDBC>> <<Device>>
Inventory :App” Server
Control War <<JDBC>>
: EJB Container Inventory
DB
customes. ear
supplier. ear
product. ear
order..xml
<<deployment space>>

Inventory gmt. jar

Figure 18: Deployment diagram

50
 Case Study: Inventory
3.9 SUMMARY Control System

In this unit different diagram are design to represent OOM of inventory control
system. These diagrams are:

• Class diagram

• Object diagram

• Generalization and association

• Collaboration diagram

• Activity diagram

• State diagram

• Dataflow diagram

• Use case diagram

• Use Interface and Deployment Diagram.

51