4. High-Level Design 4.1. System Architecture Overview What to include: Architecture Model: Present a high-level diagram (e.g., layered architecture, client-server architecture, or microservices architecture). Indicate how different components of the system (patient management, billing, appointments, etc.) interact with each other. Key Components: Include an overview of the main system components such as the user interface (UI), application logic, database, external systems, and APIs. Deployment Strategy: Discuss whether the system is deployed on-premises, in the cloud (AWS, Azure, etc.), or hybrid, and why that choice is optimal for the hospital's needs. Example: You can use a 3-tier architecture (Presentation layer, Logic layer, and Data layer), explaining how the hospital staff interacts with the user interface, how the logic layer handles business processes (like patient registration), and how the data layer manages the database. 4.2. Functional Design What to include: System Use Cases: Describe the primary functionalities of the system (e.g., patient registration, appointment scheduling, billing). Use a Use Case Diagram to visually represent these. Workflow Diagrams: Create flowcharts or activity diagrams for the major processes, such as the patient admission workflow, appointment scheduling process, or billing cycle. Feature Description: Provide a detailed breakdown of core functionalities, describing the expected behaviour of each feature/module. Ensure you tie each function back to the user needs or requirements. Example: For patient management, explain the flow from when a patient enters their details to when they're admitted, and the data that gets captured in the process. 4.3. Non-Functional Requirements What to include: Performance Requirements: Define expected response times, system throughput, and the number of concurrent users the system should handle. For example, the HMS should handle 500 concurrent users with a response time of