How reviverkid/smartdoctorappointmentsystem works
Main Components
• Presentation Layer: This is represented by the various Activities (MainActivity, SplashScreen, LoginActivity, DoctorMainActivity, PatientMainActivity, etc.), Fragments (DoctorFragments and PatientFragments), and UI Adapters that provide the user interface and handle user interactions.
• Business Logic / Controller Layer: Although not explicitly separated via packages, check the Java classes (such as the ReusableFunctionsAndObjects or DataRetrievalClass sub-packages) that handle core logic, data processing, and decision-making. This layer coordinates between the UI and data components.
• Data Layer & External Services: The project relies on Firebase (for authentication, real-time database, notifications) and perhaps Retrofit for network calls. Additionally, integration with Google Services (as seen in the google-services.json file) should be a part of this layer.
• External Libraries & UI Frameworks: Technologies like Glide for image handling and Material Design components should be represented as part of the supportive infrastructure that enhances the UI and performance.
Relationships and Interactions Between Components
• How the Presentation Layer interacts with the Business Logic/Controller layer (e.g., through Activities invoking helper classes and functions).
• How the adapters and fragments are used by Activities to render data retrieved from backend services.
Architectural Patterns and Design Principles
• Modularity by showing how different user roles (doctor, patient, admin) are managed via separate dashboards and flows.
Detailed Elements
• Each block/component should have a clear label (e.g., “Doctor Dashboard”, “Patient Appointment Management”).
• UI triggers -> Business logic controllers.
• Business logic -> Data retrieval/storage APIs.
• Push notifications directed from Firebase to device-level notification services.
• Android client components (Activities, Fragments)
• External services (Firebase, Google Services)
• Utility classes/adapters that bridge data and UI.