Visualise, Document and Explore Your Software Architecture

Visualise, Document and Explore Your Software Architecture

GOTO Conferences via YouTube Direct link

Think about the target audience

8 of 25

8 of 25

Think about the target audience

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Visualise, Document and Explore Your Software Architecture

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Introduction
  2. 2 Selected highlights
  3. 3 Moving fast in the same direction requires good communication
  4. 4 Why is there a separation between the logical and development views?
  5. 5 the architecture diagrams don't match the code
  6. 6 A common set of abstractions is more important than a common notation
  7. 7 The abstractions must reflect the technology
  8. 8 Think about the target audience
  9. 9 C4 is not a design process
  10. 10 retrospectively drawing diagrams
  11. 11 What is a "component"?
  12. 12 The code is the embodiment of the architecture
  13. 13 Is the architecture in the code?
  14. 14 Architecture description languages
  15. 15 Create an architecture description language using code
  16. 16 "Component Finder"
  17. 17 Working software comprehensive documentation
  18. 18 The code doesn't tell the whole story
  19. 19 Tribal knowledge
  20. 20 Product project
  21. 21 Microsoft Word?
  22. 22 Documentation should describe what the code doesn't
  23. 23 Tactics for better teams
  24. 24 The 1990's called and they want their tools back.
  25. 25 Do you have a ubiquitous language to describe your software?

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.