How sansukumar22j24-hash/doctorappoimtmentsystem works
This is a small console-based doctor appointment example. The user enters symptoms and a doctor type; Main creates a patient, selects a general or special doctor, books an appointment, and displays the fee and appointment ID. Doctor holds appointment data and a patient reference, and reads the patient’s symptoms when booking. The graph reflects the shown code; it does not infer behavior from the empty README.
Main entry points: Main.java Main workflow · Doctor.java Doctor base · DoctorInterface.java Doctor contract · Patient.java Patient state
Components 10
Console workflow
- Main workflow
Main.java
Appointment domain
- Patient state
Patient.java - Patient contract
PatientInterface.java - Doctor base
Doctor.java - Doctor contract
DoctorInterface.java - General doctor
GeneralDoctor.java - General contract
GeneralDoctorInterface.java - Special doctor
SpecialDoctor.java - Special contract
SpecialDoctorInterface.java
Other components
- Console user
Connections 13
- Console user → Main workflow: enters details
Main.java - Main workflow → Patient state: creates and updates
Main.java - Main workflow → General doctor: creates or selects
Main.java - Main workflow → Special doctor: creates or selects
Main.java - Main workflow → Doctor contract: books and reads details
Main.java - Main workflow → Patient state: stores doctor reference
Main.java - Doctor base → Patient contract: reads symptoms
Doctor.java - General doctor → Doctor base: extends
GeneralDoctor.java - Special doctor → Doctor base: extends
SpecialDoctor.java - Patient state → Patient contract: implements
Patient.java - Doctor base → Doctor contract: implements
Doctor.java - General contract → Doctor contract: extends
GeneralDoctorInterface.java - Special contract → Doctor contract: extends
SpecialDoctorInterface.java