LLDsystem_design~12 mins

Class identification (ParkingLot, Floor, Spot, Vehicle) in LLD - Architecture Diagram

Choose your learning style9 modes available

Learn Why Deep Arch Practice Challenge Design Recall Scale

System Overview - Class identification (ParkingLot, Floor, Spot, Vehicle)

This system models a parking lot with multiple floors and parking spots. It manages vehicles entering and leaving, assigning spots based on availability and type. The key requirement is to efficiently track spot occupancy and vehicle location.

Architecture Diagram

User
  |
  v
ParkingLot
  |
  v
Floor(s)
  |
  v
Spot(s) <--> Vehicle(s)

Components

User

actor

Person who parks or retrieves vehicles

ParkingLot

class

Manages floors and overall parking operations

Floor

class

Represents a single floor with multiple parking spots

Spot

class

Represents a parking spot that can be occupied by a vehicle

Vehicle

class

Represents a vehicle that needs parking

Request Flow - 6 Hops

User → ParkingLot

ParkingLot → Floor

Floor → Spot

Spot → Floor

Floor → ParkingLot

ParkingLot → User

Failure Scenario

Component Fails:Spot

Impact:Spot incorrectly marked as available or occupied, causing parking conflicts or failures

Mitigation:Implement spot status validation and periodic synchronization with sensors or manual checks

Architecture Quiz - 3 Questions

Test your understanding

Which class is responsible for managing multiple floors in the parking system?

ASpot

BParkingLot

CFloor

DVehicle

Design Principle

This design uses clear class responsibilities to separate concerns: ParkingLot manages floors, Floor manages spots, and Spot manages vehicle occupancy. This modular approach simplifies maintenance and scaling.