Activity Diagram for Inventory Management System

Here is the final activity diagram for the Inventory Management System:

The video explanation for the final activity diagram for the Inventory Management System is as follows:

Video Transcript

As part of the final activity diagram, we can see that an inventory manager starts the activity logs in. He also checks if his user ID passwords are all correct. If not, a notification is sent to the admin and the flow ends there. This means that he is not able to log in successfully on successful login, he goes to his views, his profile dashboard checks for notifications, and if he has any notification that any product is below threshold level, he goes ahead and places an order. If there is no notification for any product below threshold level, the flow ends there.

 When the inventory manager places an order, it triggers a notification via the notification service to the supplier. The supplier views the order checks. If the product is available, he takes a decision and based on the decision, he decides whether to manufacture the product or not. If it is available, he forks two activities which are namely sense stock and race. Invoice sent. Stock communicates back to the inventory manager and the inventory manager receives the stock checks for quality. If it is good, he adds it back to the stock and the admin is notified if the quality is bad. As part of the decision, he returns the stock back to the supplier and the supplier receives the return stock and the flow ends. As part of the raise invoice which the supplier did, an invoice object is created and remains in the status unpaid, and the stock is added to the inventory admin. When he receives the stock and he gets a confirmation that the stock is added to the inventory, he views the invoice and pays the supplier. When he pays the supplier, the invoice object which was created by the supplier, which was in an unpaid state, gets updated to paid state and the activity finally ends. One point to note, the flow can even end if the stock which the supplier sent did not get added to the inventory. As well, as you can see here in this one point to note is there are a set of activities which are done only by the supplier or few only by the admin, and few are restricted to the inventory manager. So these sets of activities which can be grouped to a particular actor or a particular party, are called partitions. Here all these activities are partitioned with these rectangles boundary lines representing the partitions for admin, inventory Manager supplier Notification Service this represents the final activity diagram which are partitioned between the actors.

Video Recap

• 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.