ERD Flowcharts and other documentation
summary
A call‑for‑papers example maps three actors — speaker attendee organizer — into a context data‑flow diagram that shows eight inputs and outputs; drilling down isolates processes (submit, vote, select, view) and a flowchart for voting enforces rules (CFP open, block self‑voting, validate then store). Mockups reveal required fields (speaker photo, vote count) that drive an ER diagram with event→sessions→votes relationships and composite keys, plus runnable BDD tests to lock API contracts; diagrams and mockups can be produced in a day with a diagramming tool and a UML book.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:17What It's Not About
- 0:45What It Is About
- 1:15Anna Filina
- 1:40Why No Diagrams?
- 4:08Not Always Boring
- 4:32The Real Problem
- 5:24Use Case
- 7:08Data Flow Diagram
- 12:06Common Mistakes
- 14:22Flowchart
- 16:12Mockups
- 17:24ER Diagram
- 19:56Behat
- 22:18Source Comments
- 25:56Manual
- 26:38Application Complexity
- 27:01Security Requirements
- 27:40Financial Impact
- 28:25Team Size
- 29:27Team Proximity
- 30:09Developer Level
- 30:46Good Documentation
- 33:28Takeaways
related talks
39mDiagrams as Code 2.0
01mJacqui Reed at DDD Europe 2025
43mC4 models as code
15mDraw me a software or the art of diagrams that stick in the mind
42mThe C4 model for visualising software architecture
50mDesign Patterns for Software Diagramming
41mDesign Patterns for Software Diagramming
01h 00mDescribing and Documenting Your Architecture