How fatimaalmurtadha/healthcaresystem works
Project Type and Purpose
• This is a console-based, C#/.NET monolithic application for managing healthcare users, patients, personnel, appointments, journals, and permissions. It demonstrates OOP principles in a student practice project.
Main Logical Layers (Components)
a. Presentation Layer (Console UI)
• Program.cs: startup, main menu loop
• AppointmentMenu.cs: appointment-specific console menus
• RequestRegistration.cs: registration UI
b. Business Logic Layer
• SystemLogic.cs: orchestrates user workflows (login, registration, requests)
• MainAdmin.cs / LocalAdminPerm.cs: admin logic for permissions and regions
• Personnel.cs / Patient.cs: role-specific operations
c. Domain Model
• Entities and interfaces:
• IUser.cs, User.cs (if exists), Patient.cs, Personnel.cs, MainAdmin.cs
• Appointment.cs (or Appointments.cs), Journal.cs, Permissions.cs
d. Data Access Layer (Repositories)
• UserDataManager.cs, JournalDataManager.cs, AppointmentStorage.cs, PermissionsDataManager.cs
• These classes implement CRUD against plain-text files (Users.txt, Journals.txt, Appointments.txt, Permissions.txt, etc.)
e. Storage
• Flat files under project root: Users.txt, Journals.txt, Appointments.txt, Permissions.txt, Personnel.txt, Users_log.txt
• AdminPermissions.txt, other metadata text files
Relationships & Interactions
• UI components invoke methods on SystemLogic.
• SystemLogic delegates to role-specific classes (Patient, Personnel, Admin).
• Each role class uses one or more DataManager classes to read/write data.
• DataManager classes perform file I/O and return domain entities or collections.
• Domain entities (Appointment, Journal, User, Permission) carry business data through the layers.
• Optionally, SystemLogic logs key events to Users_log.txt via UserDataManager.
Architectural Patterns & Principles
• Layered Architecture: clear separation between UI, business logic, domain model, and data access.
• Repository Pattern: DataManager classes abstract persistence behind CRUD methods.
• Single Responsibility: each class has one main focus (e.g., AppointmentStorage only handles appointment persistence).
• Dependency‐inversion: interfaces (IUser) decouple code from concrete implementations.
Technologies & Frameworks
• .NET 8.0 SDK, C# 11
• Console Application (command-line interface)
• File-based persistence (no external DB)
Final Checklist
• UI → SystemLogic → Role Classes → Data Managers → Storage.
• Optional: annotate key use cases (e.g., “Request Appointment” path) on the side.