Virtual Restaurant Simulator

Model a working restaurant, staff, menus, orders and inventory, and keep it maintainable as new staff types get added, instead of collapsing into one giant switch statement.

A 14-class architecture using multi-level inheritance, abstract base classes and virtual methods, so each staff role defines its own behaviour through one shared interface. Adding a role means adding a class, not editing the code that already works.

Inventory, menu and order data persist to three separate files and reload on start, so a session can be saved and resumed. Input validation handles case-insensitive matching, stock caps and low-stock alerts, so malformed input cannot crash it.

A command-line simulation that runs a full restaurant cycle and stays easy to extend. The project where I learned to think in class boundaries and polymorphism.