Visualising software architecture with the C4 model - Simon Brown, Agile on the Beach 2019

  Переглядів 403,676

Agile on the Beach

Agile on the Beach

День тому

In Simon Brown's talk at AOTB 2019 he explores the visual communication of software architecture based upon a decade of Simon’s experiences working with software development teams large and small across the globe.
He looks at what is commonplace today, the importance of creating a shared vocabulary, diagram notation, and the value of creating a lightweight model to describe your software system using the “C4 model”, which he created as a way to help software development teams describe and communicate software architecture, both during up-front design sessions and when retrospectively documenting an existing codebase.
It’s very likely that the majority of the software architecture diagrams you’ve seen are a confused mess of boxes and lines. Following the publication of the Manifesto for Agile Software Development in 2001, teams have abandoned UML, discarded the concept of modelling and instead place a heavy reliance on conversations centered around incoherent whiteboard diagrams or shallow “Marketecture” diagrams created with Visio. Moving fast and being Agile requires good communication, yet software development teams struggle with this fundamental skill. A good set of software architecture diagrams are priceless for aligning a team around a shared vision and for getting new-joiners productive fast.
Visit www.agileonthebeach.com for more information about the premier annual Agile conference.
BIOGRAPHY
Simon is an independent consultant specialising in software architecture, and the author of “Software Architecture for Developers” (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He is also the creator of the C4 software architecture model, which is a simple approach for creating maps of your code. Simon is a regular speaker at international software development conferences, travelling the world to help organisations visualise and document their software architecture.

КОМЕНТАРІ: 99
@kloudja
@kloudja Рік тому
One of the best presentations I've seen so far. Not boring at all. Not reading the power point slides. Simple bullet points. Amazing presentation. Interesting topic. Amazing content. Big applause to Simon Brown
@AlexandrePaivaBR
@AlexandrePaivaBR 2 місяці тому
Those are my words too. Excelent presentation.
@JazminMortimer
@JazminMortimer 3 роки тому
What a lovely presentation! Sat through the whole thing easily.
@archipeg
@archipeg 2 роки тому
We loved the C4 model, and this video helped us understand it in more detail, right from the author. We will soon be supporting C4 inside Archipeg, too. Seems to be a very promising metamodel for architecture. Thanks for this amazing video!
@twoencore
@twoencore Рік тому
Really enjoyed this. I found my self using old school UML to still describe an architecture. This video really helped refine my approach!
@dandoescode
@dandoescode 2 роки тому
Great presso! Amazing summary of C4 modelling and recommended best practices.
@quangninhus
@quangninhus 7 місяців тому
Exactly what I'm looking for. Thanks a lot
@MinhDangbui_Asopi
@MinhDangbui_Asopi 2 місяці тому
Still awesome in 2024! What a great presentation and explanation to break down such a complex ways of communication into simple process.
@SuperToughnut
@SuperToughnut 2 роки тому
Best video I have seen on drawing architecture diagrams. I'm glad I'm not the only one that looks at others diagrams and say "what"?
@thirudoddi8485
@thirudoddi8485 Рік тому
Nice Presentation! I always struggle what the Architect is trying to convey using the boxes and lines, a lot of hidden details even in a well organized (not documented) diagram. The Architectural diagrams are very valuable resources and C4 will definitely help to make the Architecture models self explanatory (hopefully)!
@mauricemakesmovies
@mauricemakesmovies Рік тому
Very clear presentation. Thanks for uploading this!
@jeromemohanan
@jeromemohanan 2 роки тому
Great Talk. Wonderful tool for High Level Abstraction. Paints the big picture very clearly.
@AMFLearning
@AMFLearning 7 місяців тому
nice mr simon brown, you are inspired us to create content about software architect for our college in UINSA, thanks a lot #amflearning #amflearningbydoing #amfedukasi #amfedukasiforeveryone
@josiahtobas9172
@josiahtobas9172 4 роки тому
Straight and to the point, great to see it's being taught to more people.
@DeepakAggarwal77
@DeepakAggarwal77 2 місяці тому
One of the best presentation not just in terms of delivery and content, but also impact🎉
@abdtubetv
@abdtubetv 4 роки тому
Great talk, straight to the point
@user-th5gq3ez8b
@user-th5gq3ez8b 8 місяців тому
so good presentation
@Krazness
@Krazness 2 роки тому
Excellent Presentation. Thank you
@roman_mf
@roman_mf Рік тому
This is awesome. Wish I saw this talk earlier!
@chiro5533
@chiro5533 2 роки тому
This teacher makes learning fun.
@myaccount09011975
@myaccount09011975 3 роки тому
Thanks Simon, great video.
@darkmift
@darkmift 2 роки тому
This really clears up amny things,thank you. I would very much like to see the diagram from the lecture.
@oscarsolis5969
@oscarsolis5969 4 роки тому
Interesting model. Great Talk
@wallyhall
@wallyhall 2 роки тому
I honestly think if universities around the world taught this first - and *then* UML - software teams (and engineering teams generally) would start to have saner (read: actually valuable) documentation within the next 10 years. After a decade-and-a-half of secular software engineering experience, I've only just discovered the C4 model. It's done more for my career than half of my formal education. Without hesitation I would say to anyone reading this: *start here*. Start with the C4 model. And stick with it until you have reason to break from it. And do your next employer/team a favour: pass this message on.
@nettion
@nettion 4 роки тому
Very good and straight forward intro to c4 thanks for sharing
@felipealmeida6091
@felipealmeida6091 2 роки тому
Watching in 2022 and this is amazing.
@illyam689
@illyam689 Місяць тому
Great! Excellent content and presentation skills!
@thingstodowithBASS
@thingstodowithBASS Рік тому
Great walkthrough!!
@AdnanHaider80
@AdnanHaider80 3 роки тому
Great. I must try this
@marcorutzen5351
@marcorutzen5351 Рік тому
Really great presentation!
@christianorduno6584
@christianorduno6584 Рік тому
LOVED!!!!!
@AliRezaTaleghaniIR
@AliRezaTaleghaniIR 3 роки тому
awesome speech! speaks a lot as itself... 1+
@cesarkohl
@cesarkohl Рік тому
Quite informative, thanks!
@rdogadin
@rdogadin 5 місяців тому
Great demo. You can also use Miro boards, if you don't want your sticky notes fall off.
@MinhYNguyen
@MinhYNguyen 2 роки тому
that's very useful video. Super thanks
@TheMegaMrMe
@TheMegaMrMe 2 роки тому
very good points. On the AWS example with icons, context is king. If you know the cloud, it makes sense and it is actually very helpful
@devops-sushi5534
@devops-sushi5534 Рік тому
Exactly my thought. Most of the whiteboard examples make sense for all ppl who were attending at the meetings as well?
@marcthomas9831
@marcthomas9831 2 роки тому
I used to be the person that you talk about "Just use a whiteboard" and use those diagrams to talk around. However, it doesn't hurt to have a simple, common notation. UML always felt too detailed and more applicable to application design rather than architecture.
@seshasaivenkat
@seshasaivenkat 3 роки тому
Simple ,Fantastic & Excellent
@musahassan5863
@musahassan5863 3 роки тому
Very helpful!
@andrewandrosow4797
@andrewandrosow4797 3 роки тому
Thanks! It`s a very interesting lection!
@GlennLewis
@GlennLewis Рік тому
Great talk... except... Where is the "workspace.dsl" file for this talk? That would be incredibly useful to have as a reference! Attempting to find a tutorial on writing this DSL file is extremely frustrating.
@sashakatwon4906
@sashakatwon4906 Рік тому
really cool, thnx!
@user-je1mx5zv4c
@user-je1mx5zv4c 2 роки тому
thanks!
@jorgetevez2122
@jorgetevez2122 3 роки тому
Thanks.
@lzap_rh
@lzap_rh Рік тому
UML is C++ of architecture design.
@MB-pt8hi
@MB-pt8hi 2 роки тому
What is Simon using for the presentation to get this zoom circle and give the rest of the screen a shadow?
@DeepakAggarwal77
@DeepakAggarwal77 2 місяці тому
This can be done using obs. I don't know though what Simon is using per se
@christians6843
@christians6843 3 роки тому
27:11 from my experience the hardest decision to be made when modelling C4. Both stories are very important, true and even necessary. Omitting kafka as a box: you don't see kafka needs to be deployed as a stand-alone thing. You don't see the dependencies at a glance. In some cases the diagram might get very complex, when many components talk to each other instead to a single box. Any suggestions?
@PaulSebastianM
@PaulSebastianM 3 роки тому
Yeah. Rearchitect.
@christians6843
@christians6843 3 роки тому
@@PaulSebastianM what does it mean?
@adelyawn
@adelyawn 3 роки тому
yeah, I also feel like C4 lacks a concept of a "proxy" for CDNs, event buses, proxy servers etc
@christians6843
@christians6843 3 роки тому
@@adelyawn indeed, thats what I mean. From a theoretical point of view its the same like when alice and bob communicate with each other. You could draw a line between them. It would be correct. You could also draw a line to some cloud in between or some routers etc (okay somehow out of scope C4). However, proxies, brokers etc are deployable units and a layer below alice and bob. If you draw a line between them you see the purpose better. Through the middleware, you see the architecture better, but the purpose is lost. As of you need both to understand the system, I tend to draw 1 line through all 3 entities to have the purpose and the high level architecture at a glance. Multiple diagrams or multiple lines with seperate descriptions would make more confusion in most cases imho. Do you have another approach?
@adelyawn
@adelyawn 3 роки тому
@@christians6843 don't have any approaches yet, but I'm 100% with you on this
@rosssoxa
@rosssoxa 3 роки тому
good themes
@sidekick3rida
@sidekick3rida Місяць тому
I use OmniGraffle mostly and it's perfectly fine.
@Japethify
@Japethify 4 роки тому
Interesting topic - definetly worth a try. Just one nitpick: Wouldn't it be better to call it C3 model because, as mentioned in the talk, one shouldn't do necessarily code diagrams? I feel C3 model would convey the idea more clearly. What do you think?
@rosey182
@rosey182 4 роки тому
or C3 +1
@aldosolorzano5734
@aldosolorzano5734 3 роки тому
@@rosey182 or C3++
@maskahleo
@maskahleo 3 роки тому
@@aldosolorzano5734 or just C++
@MaximilianBerkmann
@MaximilianBerkmann 3 роки тому
AFAIK Calling it C3 would lead to more confusion with the already existing C3 tool (which you probably know if you've done Exploratory Data Analysis and visualisations). SC3 might or SC2 might have been more accurate for the model IMO.
@christians6843
@christians6843 3 роки тому
Code diagrams are great. But usually you should do them on demand and if possible auto-generated. Also, giving the component level diagrams you should be able to determine the code artifacts quickly. So yes, level 4 in C4 is only some set of recommendations. But it also borrows UML or other helpful notations on that level, instead of reinventing the wheel. That also means, I'd explicitly label such a diagram as "c4 code diagram", even though it might be UML. Just to make its relationship with the other diagrams obvious.
@warrenstrife4818
@warrenstrife4818 11 місяців тому
what's the advantage of using C4 over uml ?
@AlexeyPirogov
@AlexeyPirogov Рік тому
AWS diagrams are excellent for Deployment Diagrams. You immediately see AZs, regions which are extremely important to understand limitations (e.g. SPOF). I don't think C4 is good for Deployment diagram. At least with PlantUml, where alignment options are quite limited.
@jerylcook1708
@jerylcook1708 Рік тому
through level 4 in the trash :) lol....i remember long long time ago...we use to use a tool to autogenerate "class diagrams"..i don't think that is a thing now days.
@user-ok9cm9nv6c
@user-ok9cm9nv6c Рік тому
One major problem is that his software-architectural floorplan diagram is actually brilliant.
@shawnmccool1622
@shawnmccool1622 Рік тому
Nice talk, but the conference template is an unfortunate waste of screen real estate.
@teminoah2960
@teminoah2960 4 роки тому
what a rare intelligence
@willgumm
@willgumm 4 роки тому
Great stuff - time to get rid of Visio - great comment ...
@anytcl
@anytcl 9 місяців тому
C4 model Context = System (but Context is fine too) Container = Component Component = Module Code = Code I guess the weird naming, is to be able to call it C4 instead of SCMC
@Jonathan-od5xc
@Jonathan-od5xc 2 роки тому
So C3
@DodaGarcia
@DodaGarcia 2 роки тому
Whoa Martin Freeman is looking great these days
@reshmatamrakarful
@reshmatamrakarful 2 роки тому
34:37
@andreferreira.86
@andreferreira.86 3 роки тому
For those who came to learn about the C4 model, just jump to 9:30. Before that he's just mocking someone else's diagram...
@simonbrown4821
@simonbrown4821 2 роки тому
That "mocking" serves an important lesson in what not to do - it wouldn't be included otherwise.
@C3Cooper
@C3Cooper 3 роки тому
Simon took his argument one step too far and is very incorrect when he referenced the AWS/Azure symbol diagrams as pointless. Those diagrams are very useful summary to practitioners that are fluent in the symbology. If you're not fluent in the symbols, you're not the right audience. The symbology diagrams would compliment an L3 diagram and provide a helpful, service specific summary. Audience targeting is a fundamental rule in a communications - know your audience and label your diagramming accordingly. It is not always a choice between A -or- B.
@simonbrown4821
@simonbrown4821 2 роки тому
My experience suggests that the number of people fluent in the various AWS/Azure icons is actually quite small ... especially with the rate that AWS releases new services. That's why I recommend "icons supplement text, not replace it". Here's a blog post I wrote about cloud architecture diagrams: dev.to/simonbrown/cloud-architecture-diagrams-3pbm
@nextlifeonearth
@nextlifeonearth 4 роки тому
Just an FYI: Acronyms by definition are pronounce-able abbreviations. Just say abbreviation if you mean abbreviation. (sure, "up for debate" wise arses can go speak their gibberish while other people try to maintain a consistent, comprehensible language where all words with individual meanings don't just become synonyms of one another)
@namaste3089
@namaste3089 4 роки тому
I think you searched for English grammar architecture and ended up in Agile Modeling, since the only thing that you could point out from the talking was his use of the word Acronyms...
@nextlifeonearth
@nextlifeonearth 4 роки тому
@@namaste3089 It's worth saying. Software modelling is more of the same, little to say about that hasn't been said already.
@ShpanMan
@ShpanMan 3 роки тому
Am I crazy or did he end up basically with the same diagram structure as all the previous teams... There was really nothing special in his approach other than layering which is not a new concept.
@sdrbox
@sdrbox 3 роки тому
No, he explained very well why use c4 model, that's the key of the video.
@adithyakiransekar
@adithyakiransekar Рік тому
Exactly, nothing new here. Just separated each layer out to its own diagram
@therealdrag0
@therealdrag0 Рік тому
Yep. I listened at 2x speed and still skipped through it manually. Not much here.
@vitorassissantos4302
@vitorassissantos4302 Рік тому
The key concept here is that it's not supposed to be innovative, but to help clean up the mind mapping mess that drive people insane while trying to use those previous innovative approaches. It's about the abstractions made throughout the process (he emphasized the term "abstraction first" in the video), not the final result.
@sharbelokzan9673
@sharbelokzan9673 5 місяців тому
unfortunately yes, I was excited at first but got disappointed at the end. If those teams in the workshop he mentioned used C4 they will end up rating each other's diagrams as 7/10. I don't see a concrete representation of the "abstraction" here.
@gyawimovement9164
@gyawimovement9164 3 роки тому
The bite-sized throat bacteriologically flash because move disappointedly rot excluding a loving helicopter. protective, insidious use
@sthex4640
@sthex4640 Рік тому
This can't get any more dishonest. Examples for bad modelling carefully chosen to include obvious works in progress, general ideas or helicopter views, with crossed out names, written on wrinkled paper. You spent no time to try to explain those, yet you've spent quite a bit to explain what you have modeled in C4, even though it was supposed to be so clear. And you've done multiple levels of presentation of your design and did not compare those to any other techniques. Absolutely nothing new here, just promoting old design under a new name.
@tsss5271
@tsss5271 Рік тому
You were very late in coming to the point and you were explaining things which were not relevent
@LogicPhalanx
@LogicPhalanx 2 роки тому
Knowfa Mallity. Did nobody get the joke?
A Philosophy of Software Design | John Ousterhout | Talks at Google
1:01:40
Talks at Google
Переглядів 461 тис.
Voloshyn - ЗУСИЛЛЯ (прем'єра треку 2024)
06:17
VOLOSHYN
Переглядів 638 тис.
skibidi toilet 73 (part 2)
04:15
DaFuq!?Boom!
Переглядів 29 млн
Помилка,  яку зробило військове керівництво 🙄
01:00
Радіо Байрактар
Переглядів 444 тис.
Денис Цветцих - C4 model на практике
45:48
Flow — конференция про системный и бизнес-анализ
Переглядів 793
Google system design interview: Design Spotify (with ex-Google EM)
42:13
IGotAnOffer: Engineering
Переглядів 944 тис.
C4 models as code - Simon Brown - NDC Oslo 2023
1:00:02
NDC Conferences
Переглядів 21 тис.
Simon Brown - The lost art of software design
41:08
Agile meets Architecture
Переглядів 10 тис.
C4 models as code - Simon Brown - NDC Porto 2023
54:26
NDC Conferences
Переглядів 3,3 тис.
Making Architecture Matter - Martin Fowler Keynote
14:04
O'Reilly
Переглядів 331 тис.
Diagrams as code 2.0 • Simon Brown • Devoxx Poland 2022
32:54
Devoxx Poland
Переглядів 6 тис.
How to "think" (and design) like a Software Architect at Silicon Valley Code Camp 2019
1:12:57
Airpods’un Gizli Özelliği mi var?
0:14
Safak Novruz
Переглядів 861 тис.
Игровой ноутбук за 100тр в МВИДЕО
0:58
KOLBIN REVIEW
Переглядів 398 тис.
How Neuralink Works 🧠
0:28
Zack D. Films
Переглядів 25 млн
Клавиатура vs геймпад vs руль
0:47
Balance
Переглядів 878 тис.
Which Phone Unlock Code Will You Choose? 🤔️
0:12
Game9bit
Переглядів 6 млн
Портативная PS 5 🎮 #ps5 #expressly
0:22
ExpresSLY Shorts
Переглядів 216 тис.