Professional Documents
Culture Documents
Case Study To Inventory Control Management
Case Study To Inventory Control Management
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:
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
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
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 ()
41
Implementation
Generate
Enter
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
42
Case Study: Inventory
Super Type
Control System
CUSTOMER
Name: string
Credit ()
PRODUCT
name
Class A Class B
1 role n role
ORDER CUSTOMER
SUPPLIER
Supplier Details
m
Figure 6: Aggregation
Ternary Association for Customer Supplier
CUSTOMER SUPPLIER
PRODUCT
Object: Class
1.2: [Condition]
1. Message Message
2. Message
3. Message
Object: Class Object: Class
Object: Class
: 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
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
Synchronization
Splitting of Control
Demand Occurred
[Valid demand]
[Valid]
Check
QTY-in-stock
Cancel Demand
Reverse Order
Demand Occurred
Payment Made
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
Cancel
Do: cancel the
Order
Generate
Do: Generate
Update Bills of Material
Do: Update (BOM)
Inventory Status
File
46
Case Study: Inventory
<<uses>> Control System
Place an Generate
Order INVOICE
<<extends>> <<extends>>
<<uses>> <<uses>>
Place an
Order
Validate Check
the order Qty-in-stock
Invalid
1.2
2.0 Order Check
Reorder
Display
level
error Msg
2.1 Reject
the Order
4.0 5.0
Inventory File
Generate Update
Bills of Inventory
Material Status
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
• 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
SUB DIAGRAM
INVENTORY
CONTROL SYSTEM
Place an Order
Place an
Order
Generate
INVOICE
48
USER INTERFACE Case Study: Inventory
Control System
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 To
Qty-in-stock Order Qty View
Generate Bills of
Material entry Report Run Button
Generate Invoice
Voucher Invoice
Press Card
Button
Generate Inventory
Status Report Press Report
Button
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
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>>
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
• Collaboration diagram
• Activity diagram
• State diagram
• Dataflow diagram
51