Show me a diagram with arrow

Objective:

In this assignment, you will demonstrate your understanding of object$-$oriented design by creating a class diagram for a Hospital Management System based on the scenario provided. You are required to identify the key classes, their relationships, attributes, and methods. Additionally, you will submit a written explanation of your design choices and assumptions.

Scenario: Hospital Management System

A hospital needs to develop a system to manage its patients, doctors, staff members, and medical appointments. The system will track patient details, doctor assignments, and the hospital staff's activities.

Patients have a unique ID$,$ name, contact information, medical history, and a list of treatments they have received. Each patient is assigned a primary doctor but can have multiple appointments with different doctors.

Doctors have a unique ID$,$ name, contact information, and a medical specialization $($e$.$g$.,$ cardiologist, neurologist$).$ A doctor can treat multiple patients, but a patient can only have one primary doctor at a time.

Staff Members $($including nurses and administrative staff$)$ have a unique ID$,$ name, role, and work schedule. Nurses assist doctors with patient care, while administrative staff handle admissions and appointment scheduling.

Appointments track the date, time, and reason for a patient's visit, and are linked to both the patient and doctor.

Treatments record the details of medical procedures and their associated costs.

Your task is to design a class diagram representing this system, including relationships between the main entities and a clear indication of the attributes and methods relevant to each class.

Assignment Requirements:

Class Diagram

Design a class diagram that represents the Hospital Management System.

Your class diagram should include:

Classes for the key entities $($e$.$g$.,$ Patient, Doctor, Staff, Appointment, Treatment$).$Attributes and methods for each class.Relationships between the classes $($e$.$g$.,$ associations, inheritance$).$Multiplicities where applicable $($e$.$g$.,$ one$-$to$-$many, many$-$to$-$many$).$

Written Explanation

Along with the class diagram, provide a $1-2$ page written explanation that includes:

A brief description of each class and its purpose in the system.

A justification for the relationships between the classes.

A discussion of any assumptions or additional features you included in your design.

Deliverables:

Class Diagram: Submit a clear, well$-$structured class diagram using a UML tool $($e$.$g$.,$ Lucidchart, Visual Paradigm, draw.io$)$ or a neatly drawn version. Save it as a PDF or image file.

Written Explanation: Provide a separate document $($PDF or Word$)$ explaining your design and decisions.

Evaluation Criteria:

Identification of Key Classes: The diagram correctly represents the main entities in the system.

Attributes and Methods: The inclusion of relevant attributes and methods for each class.

Relationships and Multiplicities: Proper use of associations, inheritance, and multiplicities between classes.

Design Clarity: The class diagram is well$-$structured and easy to understand.

Justification of Design: The written explanation clearly justifies the design choices and relationships between classes.