Loading low-level design…

Design CricInfo - Low-Level Design | OneNoughtOne

00:00:00

Design CricInfo

Advanced

Design an object-oriented cricket scoring and information system (CricInfo) that supports player and team management, match scheduling (T20/ODI/Test), ball-by-ball score recording, real-time scorecard generation, and aggregated player statistics.

Each delivery (Ball) captures runs, extras (wide, no-ball, bye, leg-bye), dismissal type (bowled, caught, LBW, run-out, etc.), and involved players. Overs track legal deliveries (6 per over, extras don't count). Innings end on all-out or overs exhausted. Batting and bowling scorecards are maintained per innings with strike rate, economy, and other derived metrics.

Core Use Cases

Manage players

Create teams

Create teams, add squad, set Playing XI and captain

Schedule match

Schedule a match (T20/ODI/Test) between two teams at a venue

Record toss

Record toss winner and BAT/BOWL decision

Record ball-by-ball

Core operation: record each delivery with runs, extras, wickets, dismissal type

Live scorecard

View current score, batting/bowling scorecards in real-time

Innings management

Start/end innings, track overs, detect all-out / overs-complete

Player statistics

Aggregate batting and bowling stats across matches

Match result

Determine and record match result (win by runs / wickets)

Constraints

Each over has exactly 6 legal deliveries (wides and no-balls are re-bowled)
Innings ends when all-out (10 wickets) or overs exhausted (T20: 20, ODI: 50)
A bowler cannot bowl consecutive overs
Playing XI must have exactly 11 players
Score can never go negative

Assumptions

In-memory storage (no database)
Single-threaded (concurrency is a follow-up)
Limited format support (T20 and ODI primarily; Test is simplified)
No DLS method for rain-affected matches
Commentary is a simple string per ball (no rich media)

In Scope

Player, Team, and Match modelling
Ball-by-ball recording with all delivery types
Batting and Bowling scorecards per innings
Over tracking (legal balls, wides, no-balls)
Innings lifecycle (start, ball-by-ball, end)
Aggregated player career statistics
Match status lifecycle

Out of Scope

DLS method for rain-affected matches
Live video streaming
Fantasy points calculation
Umpire decision review system (DRS)
Tournament / series management
Wagon wheel and pitch map visualisations

Approach Guide(Click to expand each section)

Before diving into code, clarify the use cases and edge cases. Understanding the problem deeply leads to better class design.

List Core Use Cases

Identify the primary actions users will perform. For a parking lot: park vehicle, exit vehicle, check availability. Each becomes a method.

Identify Actors

Who interacts with the system? Customers, admins, automated systems? Each actor type may need different interfaces.

Clarify Constraints

What are the limits? Max vehicles, supported vehicle types, payment methods. Constraints drive your data structures.

Ask About Edge Cases

What happens on overflow? Concurrent access? Payment failures? Thinking about edge cases reveals hidden complexity.

Follow-up Questions(Questions an interviewer might ask)

💡 Draw UML class diagrams, sequence diagrams, or any design visualizations. Submit from the Code tab.

Loading canvas...

Loading LLD design...

00:00:00

Design CricInfo

Advanced

Core Use Cases

Manage players

Create teams

Create teams, add squad, set Playing XI and captain

Schedule match

Schedule a match (T20/ODI/Test) between two teams at a venue

Record toss

Record toss winner and BAT/BOWL decision

Record ball-by-ball

Core operation: record each delivery with runs, extras, wickets, dismissal type

Live scorecard

View current score, batting/bowling scorecards in real-time

Innings management

Start/end innings, track overs, detect all-out / overs-complete

Player statistics

Aggregate batting and bowling stats across matches

Match result

Determine and record match result (win by runs / wickets)

Constraints

Each over has exactly 6 legal deliveries (wides and no-balls are re-bowled)
Innings ends when all-out (10 wickets) or overs exhausted (T20: 20, ODI: 50)
A bowler cannot bowl consecutive overs
Playing XI must have exactly 11 players
Score can never go negative

Assumptions

In-memory storage (no database)
Single-threaded (concurrency is a follow-up)
Limited format support (T20 and ODI primarily; Test is simplified)
No DLS method for rain-affected matches
Commentary is a simple string per ball (no rich media)

In Scope

Player, Team, and Match modelling
Ball-by-ball recording with all delivery types
Batting and Bowling scorecards per innings
Over tracking (legal balls, wides, no-balls)
Innings lifecycle (start, ball-by-ball, end)
Aggregated player career statistics
Match status lifecycle

Out of Scope

DLS method for rain-affected matches
Live video streaming
Fantasy points calculation
Umpire decision review system (DRS)
Tournament / series management
Wagon wheel and pitch map visualisations

Approach Guide(Click to expand each section)

Before diving into code, clarify the use cases and edge cases. Understanding the problem deeply leads to better class design.

List Core Use Cases

Identify the primary actions users will perform. For a parking lot: park vehicle, exit vehicle, check availability. Each becomes a method.

Identify Actors

Who interacts with the system? Customers, admins, automated systems? Each actor type may need different interfaces.

Clarify Constraints

What are the limits? Max vehicles, supported vehicle types, payment methods. Constraints drive your data structures.

Ask About Edge Cases

What happens on overflow? Concurrent access? Payment failures? Thinking about edge cases reveals hidden complexity.

Follow-up Questions(Questions an interviewer might ask)

💡 Draw UML class diagrams, sequence diagrams, or any design visualizations. Submit from the Code tab.

Loading canvas...

Design CricInfo

Core Use Cases

Constraints

Assumptions

In Scope

Out of Scope

Approach Guide(Click to expand each section)

Follow-up Questions(Questions an interviewer might ask)

Explore the full editorial.

Sign in to view submissions

Design CricInfo

Core Use Cases

Constraints

Assumptions

In Scope

Out of Scope

Approach Guide(Click to expand each section)

Follow-up Questions(Questions an interviewer might ask)

Explore the full editorial.

Sign in to view submissions

Design CricInfo

Core Use Cases

Constraints

Assumptions

In Scope

Out of Scope

Approach Guide(Click to expand each section)

Gather Requirements~3 min

Identify Classes & Entities~4 min

Define Relationships~3 min

Apply Design Patterns~4 min

Apply SOLID Principles~3 min

Code Organization~2 min

Follow-up Questions(Questions an interviewer might ask)

1How would you implement a live commentary feed with Observer pattern?

2How would you add tournament / series management (IPL, World Cup)?

3How would you implement the DLS method for rain-interrupted matches?

4How would you support real-time push notifications for score updates?

5How would you add wagon wheel and pitch map visualisations?

Key Topics

Asked At

Explore the full editorial.

Sign in to view submissions

Design CricInfo

Core Use Cases

Constraints

Assumptions

In Scope

Out of Scope

Approach Guide(Click to expand each section)

Gather Requirements~3 min

Identify Classes & Entities~4 min

Define Relationships~3 min

Apply Design Patterns~4 min

Apply SOLID Principles~3 min

Code Organization~2 min

Follow-up Questions(Questions an interviewer might ask)

1How would you implement a live commentary feed with Observer pattern?

2How would you add tournament / series management (IPL, World Cup)?

3How would you implement the DLS method for rain-interrupted matches?

4How would you support real-time push notifications for score updates?

5How would you add wagon wheel and pitch map visualisations?

Key Topics

Asked At

Explore the full editorial.

Sign in to view submissions