Software Design

Dynamic Surge & Split Fare Architecture

Use Case Diagrams · made in Skemio

Use case diagram for Surge Pricing and Split Fare systems featuring Primary Rider, Co-Rider, and Pricing Engine actors connected to fare calculations.
Use case diagram for Surge Pricing and Split Fare systems featuring Primary Rider, Co-Rider, and Pricing Engine actors connected to fare calculations.
Open it in SkemioMake your own

What it shows

  • Surge multiplier recalculated dynamically using supply-demand ratio per h3 cell
  • Split fare flow operates as an extension of the primary ride settlement
  • Secondary riders must confirm splits before billing engine locks the trip

The takeaway

Surge calculation is an immutable input to quote generation; fare splitting is a payment extension.

More use case diagrams