STAR Method: (Situation – Task – Action – Result)

Software DesignSectionUML diagrams and new project design New Project Designsoftware designstarting a design Use Case Diagramsumlactors and goals Class Diagramsumltypes and relationships Sequence Diagramsumlinteractions over time Activity Diagramsumlworkflows Python DesignSectionPython architecture diagrams Module Dependency Diagrampython diagramsimports between modules Pipeline Diagrampython diagramsdata flow stages Schema Diagrampython diagramsdata model Software Design Diagramssoftware designSoftware design diagrams are visual tools used during the analysis and design phases of the Software…

This section is about communicating design: explaining what you built and why, and drawing the structure of a system so others can review it. The STAR method below gives a structure for describing past engineering work; the two child sections cover software design diagrams and Python-specific architecture diagrams.

Overview

The STAR method is a structured workflow used to clearly explain professional experience by breaking an answer into four logical parts: Situation, Task, Action, and Result.

STAR Workflow

  1. Situation (Context) - Analysis

    Key question: What was happening?

  2. Task (Responsibility) - Design

    Key question: What was I responsible for?

  3. Action (Execution) - Implementation

    Key question: What did I do to solve the problem?

  4. Result (Outcome) - Testing

    Key question: What was the outcome?

Database scaling strategies compared: vertical scaling, read replicas, and sharding
Video Thumbnail

Strategies to Scale Database

Video Thumbnail

System Design - Dianna Yau

Video Thumbnail

Snowflake System Design

Browse by Area

How systems get drawn before they get built — the diagrams, and what each one is for.

AI Systems (6)

Reference architectures at scale: agent orchestration, self-hosted inference, and LLM evaluation platforms.

Database Design (6)

Context and data-flow diagrams, entity relationships, and schema design.

Software Design (5)

UML in the parts that earn their keep — class, sequence and activity diagrams.

Python Design (3)

Why Python is module-first, and the module, pipeline and schema diagrams that follow from it.

1. How the pieces fit

Design communication STAR narrative situation, task, action, result Software design diagrams use case, class, sequence, activity Python design diagrams modules, pipelines, schemas Reviewable designs and clear write-ups

A STAR answer explains the story of a piece of work; diagrams explain the system itself. In a design review or interview, the two support each other: the situation and task set the requirements, a context or use-case diagram shows scope, class and sequence diagrams show the solution, and the result section reports measurable outcomes.

2. Which diagram to use

QuestionDiagramSection
Who uses the system and for what?Use case diagramSoftware design
What are the main types and relationships?Class diagramSoftware design
In what order do components interact?Sequence diagramSoftware design
What is the workflow, including branches?Activity diagramSoftware design
How do modules depend on each other?Module dependency diagramPython design
How does data move through stages?Pipeline diagramPython design
What tables and columns exist?Schema diagramPython design

Draw the fewest diagrams that answer the reviewer's questions, and keep each one at a single level of abstraction.