UML Diagram for Inventory Management System are
as follows:
Class Diagram
●
●
●
●
●
●
The system user class is inherited by all other user classes (admin, supplier, inventory
manager) and contains common attributes and methods.
The system manager class has a composition of the address and a one-to-many
relationship with the notification service, represented using an association class.
Each user class has relationships with other classes. Admin and supplier have a one-tomany relationship and are connected through an invoice class and a transaction class.
The order class contains all the details of an order and is commonly shared between the
inventory manager and supplier classes.
Admin can assign tasks to inventory managers, and the relationship between the task
and inventory manager is that the inventory manager completes those tasks.
There are multiple levels of relationships between the classes.
Use Case Diagram
● Admin has use cases such as login, logout, manage supplier, update profile, check
notifications, view invoices and pay supplier.
● Inventory Manager has use cases similar to Admin but also has specific use cases like
place order, view order, manage order, and manage stock.
● Supplier has use cases related to check notifications, view invoices, raise invoice, send
stock, and receive or return stock.
● Notification Service is related to only one use case which is to send a notification.
Activity Diagram
●
●
●
●
●
●
An inventory manager logs in and checks their user ID and password. If the login is
successful, the inventory manager checks their profile dashboard for notifications of
products below threshold levels.
If there are any, the inventory manager places an order, which triggers a notification to
the supplier.
The supplier checks if the product is available and decides whether to manufacture it or
not.
If the product is available, the supplier sends an invoice and stock to the inventory
manager.
The inventory manager checks the quality of the stock and adds it to the inventory.
The supplier creates an invoice object in an unpaid state, which the inventory manager
pays later.
●
●
The flow can end if the stock is not added to the inventory.
The activities are partitioned between the inventory manager, supplier, admin, and
notification service.