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 recieve a request for a shift swap
5. User should be able to accept or decline a shift swap

Non-Functional Requirements:

Low latency -> possible shifts should be retrieved as fast as possible

High availability -> Swap shift should be possible at any time

Scalability -> Across an organization different departments and roles should be able to simultaneously use the system without impacting other areas

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...