ERD, Flowcharts and Other Documentation
summary
Diagrams prove useful by showing concrete decisions not vague topics: an ERD maps tables and composite keys, a data‑flow diagram forces matching inputs and outputs (this example yields eight external I/O), flowcharts capture validation logic, mockups become screenshots, and a small conference management application for the Kung Fu CFP is designed, exported to a real database and used in production. Tools named are Asta for diagrams and Balsamic for wireframes; the process uncovers missing fields and prevents black holes.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:15Anna Filina
- 2:35Not Always Boring
- 3:15The Real Problem
- 4:36Use Case
- 5:36ER Diagram
- 9:37Data Flow Diagram
- 15:37Common Mistakes
- 18:59Flowchart
- 21:46Mockups
- 22:45Function Reference
- 25:35Source Comments
- 29:55Manual
- 33:25Security Requirements Foo
- 33:54Financial Impact
- 34:26Team Size
- 35:36Good Documentation
- 37:35Next Steps
related talks
49mFrom Doodles to Dashboards, Data Flows, and Docs
07mCan software developers draw pictures?
34mDiagram as Code - Decoding Architectural Diagrams
01h 00mC4 models as code
01h 00mVisualise, document and explore your software architecture
39mBuilding Architecture Diagrams the Red Hat way
57mVisualise, document and explore your software architecture
34mDocumentation Thinking Beyond the Docs: Lessons from Decision-Facing Technical Writing