Skip to main content
PreparationZone Logo
PrepZone

Design Tic-Tac-Toe

Board, win detection, and two-player loop.

Pass checkpoint below

Read these first

Why this matters

  • 3×3 board; two players X and O
  • Scope — what "Board" covers inside Tic-Tac-Toe and what it does not
  • Scope — what "Win check" covers inside Tic-Tac-Toe and what it does not
  • Scope — what "Player turn" covers inside Tic-Tac-Toe and what it does not
  • Games and architecture patterns signal staff+ depth.
Waiting
InProgress
Finished
Turn-based games map cleanly to State pattern — one handler per game phase.

CampusOS context

CampusOS is the fictional smart-campus platform used across this track. Treat this module as a real product slice:

Context

  • Belongs to CampusOS — same naming and design vocabulary as parking, library, and booking modules
  • Scope is one JVM — persistence is in-memory or behind a repository interface
  • Goal is a class diagram + core Java that an interviewer can follow in 35–45 minutes
  • Extension paragraph at the end links to System Design when scale exceeds one process

Requirements snapshot

Functional requirements

  • 3×3 board; two players X and O
  • Detect win on row, column, or diagonal
  • Detect draw when board full
  • Reject illegal moves (occupied cell, wrong turn)

Non-functional requirements

  • Single JVM, in-process design for this LLD article
  • Core flows testable with in-memory repositories
  • Extension points for new rules without editing central god classes
  • Clear public API on facade/service layer
  • CampusOS extension links to System Design when scale demands distribution

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 6 sections

  • Overview
  • Requirements
  • Board
  • Win check
  • Player turn
  • CampusOS extension

Test yourself

Answer these before moving on — recall is what makes it stick.