Class Diagram

Best used for a single bounded context, not a codebase.

• Format.puml
• Length38 lines
• Includesnone

The source

38 lines of PlantUML, and needs nothing beyond the bundled engine. Copy it, or open the template inside Gnomon and render it as it is.

@startuml

title Class Diagram

abstract class Animal {
  - name: String
  - age: int
  + getName(): String
  + makeSound(): void
}

class Dog extends Animal {
  - breed: String
  + fetch(): void
  + makeSound(): void
}

class Cat extends Animal {
  - indoor: boolean
  + scratch(): void
  + makeSound(): void
}

interface Trainable {
  + train(): void
}

Dog ..|> Trainable

class Owner {
  - name: String
  - pets: List<Animal>
  + addPet(animal: Animal): void
}

Owner "1" *-- "0..*" Animal : owns

@enduml

Others in UML and standard diagrams

• Sequence DiagramThe highest-value diagram in this list. Time runs down; participants across.
• Activity / Flow DiagramEarns its place when there are real branches and joins.
• Use Case DiagramActor-to-goal. Dated, but still the clearest way to show scope boundaries.
• State DiagramForces the awkward questions about duplicate and out-of-order events.
• ER DiagramCardinality is the part people get wrong. Write it explicitly.
• Mind MapFor structuring thinking, not for documenting a system.
• Gantt ChartPlans, not architecture, but it renders from text, so it diffs in review.
• JSON VisualizationVisualises a JSON payload: handy in an API design review.
• Work Breakdown StructureWork breakdown. Useful for scoping a piece of delivery.