In the next video, you will get an overview of the Inventory Management System that you are going to design using different UML diagrams.
In the previous video, you got an overview of the Inventory Management System which you will be designing while learning different UML diagrams. It is similar to normal inventory management systems where an Inventory Manager keeps track of available stock. Whenever there is a requirement for new goods, he places an order, which is supplied by a Supplier. This whole system is maintained by an Admin. All these different actors interact with each other by sending notifications to each other via a Notification Service.
Before we understand about each of those UML diagrams, it would be easier if you could understand it with an example. We'll take an example of an inventory management system where I am managing my inventory and I have a bunch of goods in my stock, and if I run out of stock, I manage it and I try to procure it more from a supplier. So in this this case, let's have the role players who will be there. Let's say I have an inventory manager, who keeps checking stocks and then places an order whenever I run out of stock. And then whenever there is an order placed, I have a supplie, who supplies goods to me so that my inventory is replenished and managing in the whole software system to manage everything. Say I have an admin, who would be involved in paying the supplier and managing everybody who has more of an admin privileges. And the way each of these person is communicating between themselves, it is maybe through a notification system, what we can call it as notification service. With these players in this inventory management system, let's try to understand each of the UML diagrams.
An example of a class diagram for inventory management system is used to explain the system
The inventory manager checks stock levels and places orders when stock runs out
A supplier provides goods to replenish the inventory
An admin manages payments and has administrative privileges
Communication between the players happens through a notification service
The segment explains each UML diagram in the context of this example
The segment does not refer to a class diagram for college management system
The segment only pertains to the inventory management class diagram.