Here is a possible use case diagram for the described application: Use Case Diagram: Actors: User: represents any user of the application who can search for restaurants. Restaurant owner: represents a restaurant owner who can add information about their restaurant. Administrator: represents an administrator who can verify or reject restaurant owners. Use Cases: Search restaurants: this represents the user's ability to search for restaurants using the application. Sort results by price: this represents the user's ability to sort search results by price. Sort results by distance: this represents the user's ability to sort search results by distance. Add restaurant information: this represents the restaurant owner's ability to add information about their restaurant. Contact restaurant: this represents the user's ability to contact a restaurant using the contact information provided by the restaurant owner. View menu: this represents the user's ability to view the menu for a restaurant. Verify restaurant owner: this represents the administrator's ability to verify a restaurant owner. Reject restaurant owner: this represents the administrator's ability to reject a restaurant owner. Send verification email: this represents the administrator's ability to send a verification email to a restaurant owner. Send rejection email: this represents the administrator's ability to send a rejection email to a restaurant owner. Register user: this represents the user's ability to register with the application. Relationships: A user can search restaurants and view the results. A user can sort the search results by price or distance. A restaurant owner can add information about their restaurant. A user can contact a restaurant or view the menu using the information provided by the restaurant