Scenario:

Imagine your team has been tasked with developing a new online food ordering system for a local restaurant chain. This system should allow users to browse the menu, make selections, customize orders $($e$.$g$.,$ingredient preferences$),$submit orders, and make payments. The system should also support user account creation and management, order history tracking, and basic loyalty program features.

Actors: These are the external entities that interact with the system being modeled. Actors can be individuals, other systems, or even hardware devices.

Use Cases: These represent the specific functionalities or actions that the system can perform. Each use case describes a particular interaction between an actor and the system.

Relationships: Use cases can have relationships with other use cases or actors. The main relationships in a use case diagram are:

Association: It represents a communication link between an actor and a use case.

Generalization: It shows that one use case is a specialized version of another use case.

Include: It indicates that one use case includes the functionality of another use case.

Extend: It represents optional or alternative functionality that can be added to a use case.

System Boundary: This is a box that encloses all the use cases and actors, representing the scope of the system being modeled.

Notation: Use case diagrams use specific symbols to represent actors, use cases, and relationships. Actors are typically represented by stick figures, use cases by ovals, and relationships by arrows.

use the scenario above to fill in the coresponding components