Requirements

Functional Requirements:

1. User should be able to login and view their shifts
2. service should get only shifts that are of same kind as user
3. user should be able to send a Swap request once alt shift is chosen
4. User should be able to receive a request for a shift swap
5. User should be able to accept or decline a shift swap

Non-Functional Requirements:

Low latency -> response time per request should not exceed 200ms

High availability -> system should have an 99.9% uptime so that last minute swap shifts such as an employee calling in sick can be handled

Scalability -> For single location with a large amount of shift workers such as a hospital ~1000 employees and ~ 300 shift workers and 15 different departments so 20 different groups of workers making requests should not affect the system -> load balancing across departments. within departments the system should be able to handle multiple requests for the same shift

API Design

Define the APIs expected from the system...

High-Level Design

Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram. If unfamiliar with the tool, describe your design to the AI and ask it to generate a starter diagram...

Detailed Component Design

Deep dive into 2-3 key components. Explain how they work, how they scale, and any relevant algorithms or data structures. Consider drawing detailed diagrams to enhance your explanation...