+---------------------+         +---------------------+
|   CategoryController|         |   SubCategoryController|
+---------------------+         +---------------------+
| - domainToken       |         | ...                 |
| + index()           |         |                     |
| + store()           |         |                     |
| + show()            |         |                     |
| + update()          |         |                     |
| + destroy()         |         |                     |
| + itemCategory()    |         |                     |
| + itemSubCategory() |         |                     |
+---------------------+         +---------------------+
           |                                 |
           |                                 |
           v                                 v
+---------------------+         +---------------------+
|      Category       |<>-------|    SubCategory      |
+---------------------+         +---------------------+
| - id                |         | - id                |
| - name              |         | - sub_category_name |
| - status            |         | - category_id       |
| - deleted_at        |         | - status            |
| ...                 |         | - deleted_at        |
+---------------------+         +---------------------+

Other controllers (not shown in detail):
- UnitController
- VendorController
- SizeController
- MaterialController
- MenuController
- SubmenuController
- ItemController
- TagsController
- ProcedureController

Helpers:
+---------------------+
|      Helpers        |
+---------------------+
| + getHistoryData()  |
+---------------------+

Notes:
- CategoryController uses Category and SubCategory models.
- Category has many SubCategory (one-to-many).
- All controllers extend Laravel's base Controller.
- Most controllers follow similar CRUD patterns.
- Authentication is handled via a token check in each controller.

This diagram gives you a structural overview. For a full system diagram, you would expand each controller and model similarly, showing their relationships and main methods. If you want a visual UML diagram, you can use tools like draw.io or Lucidchart to draw the above structure.+---------------------+         +---------------------+
|   CategoryController|         |   SubCategoryController|
+---------------------+         +---------------------+
| - domainToken       |         | ...                 |
| + index()           |         |                     |
| + store()           |         |                     |
| + show()            |         |                     |
| + update()          |         |                     |
| + destroy()         |         |                     |
| + itemCategory()    |         |                     |
| + itemSubCategory() |         |                     |
+---------------------+         +---------------------+
           |                                 |
           |                                 |
           v                                 v
+---------------------+         +---------------------+
|      Category       |<>-------|    SubCategory      |
+---------------------+         +---------------------+
| - id                |         | - id                |
| - name              |         | - sub_category_name |
| - status            |         | - category_id       |
| - deleted_at        |         | - status            |
| ...                 |         | - deleted_at        |
+---------------------+         +---------------------+

Other controllers (not shown in detail):
- UnitController
- VendorController
- SizeController
- MaterialController
- MenuController
- SubmenuController
- ItemController
- TagsController
- ProcedureController

Helpers:
+---------------------+
|      Helpers        |
+---------------------+
| + getHistoryData()  |
+---------------------+

Notes:
- CategoryController uses Category and SubCategory models.
- Category has many SubCategory (one-to-many).
- All controllers extend Laravel's base Controller.
- Most controllers follow similar CRUD patterns.
- Authentication is handled via a token check in each controller.

This diagram gives you a structural overview. For a full system diagram, you would expand each controller and model similarly, showing their relationships and main methods. If you want a visual UML diagram, you can use tools like draw.io or Lucidchart to draw the above structure.