About This Architecture

Burger Quick's inventory control system uses a UML use case diagram to map four distinct user roles—Administrator, Purchasing Manager, Kitchen Chief, and Supplier—against 13 core system functions. The diagram shows how each actor interacts with use cases like product management, purchase registration, stock tracking, and inventory alerts, with include and extend relationships clarifying dependencies between operations. This architecture demonstrates role-based access control and separation of concerns, ensuring that purchasing, kitchen, and administrative teams work within their assigned responsibilities. Fork this diagram on Diagrams.so to customize actor roles, add new use cases, or adapt it for your restaurant or retail inventory workflow.

People also ask

How do you design a UML use case diagram for a restaurant inventory management system with multiple user roles?

This diagram models four actors—Administrator, Encargado de Compras, Jefe de Cocina, and Proveedor—each with distinct use cases. The Administrator manages products, providers, users, and reports; the Purchasing Manager handles purchase registration and stock entry; the Kitchen Chief registers stock exits and losses; and the Supplier participates in purchase registration. Include and extend relatio