[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-655730-105":59,"doc-detail-655730-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","the-c4-model-for-visualising-software-architecture","The C4 model for visualising software architecture","","The C4 model for visualising software architecture explains a practical approach to visual communication and documentation for software systems. It frames the problem of teams discarding diagrams and struggling to communicate architecture, then presents lightweight ideas and techniques centered on the author’s “C4 model”. The book emphasizes clarity, semantics, and diagramming practices that help teams ask questions, align understanding, and design software complexity to be communicated effectively.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":30,"@type":76,"position":81},"https://docshare.wps.com/document/technology/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/the-c4-model-for-visualising-software-architecture/655730/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/the-c4-model-for-visualising-software-architecture/655730.png","ImageObject",300,407,{"name":92,"@type":93},"dbqoiu","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-25",true,{"@type":102,"interactionType":103,"userInteractionCount":39},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"Why does the book focus on visual communication of software architecture?","Question",{"text":112,"@type":113},"It argues that software design should be communicated clearly, yet teams increasingly reduce or abandon diagrams and documentation, leaving understanding incomplete.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"What is the core contribution discussed in the book?",{"text":117,"@type":113},"The book centers on the author’s “C4 model” for visualising software architecture using lightweight ideas and techniques.",{"name":119,"@type":110,"acceptedAnswer":120},"What issue does the author highlight about modern software development teams?",{"text":121,"@type":113},"The author describes a “failure to communicate,” where even with agile, testing, continuous delivery, and cloud practices, teams still miss effective architectural communication.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},655730,1793029565,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":29,"category_name":30,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":39,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":139,"language":140,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":67,"update_tm":144,"read_time":145},3985747862462,"https://ap-avatar.wpscdn.com/davatar_3d24733baf745e90a7e4bdd5f77d97b2","The C4 model for visualising software architecture  \nSimon Brown  \nThis book is available at [https://leanpub.com/visualising-software-architecture](https://leanpub.com/visualising-software-architecture)[ ](https://leanpub.com/visualising-software-architecture)[This version was published on 2025-11-19](This version was published on 2025-11-19)  \nThis is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do.  \n© 2015-2025 Simon Brown  \nFor Kirstie, Matthew and Oliver  \nContents  \n1. About the book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1  \n2. About the author ..................................... 3  \n3. We have a failure to communicate ........................... 4  \n3.1 What happened to SSADM, RUP, UML, etc? .................. 4  \n3.2 A lightweight approach .............................. 5  \n3.3 Draw one or more diagrams ........................... 6  \n3.4 Where do we start? ................................. 7  \n3.5 Some examples ................................... 8  \n3.6 Common problems ................................. 18  \n3.7 The hidden assumptions of diagrams ...................... 19  \n1. About the book  \nI graduated from university in 1996, a time when CASE and modeling tools were popular and in common use. I remember attending a training course about the Unified Modeling Language and the SELECT tooling soon after I started my professional career. A number of the projects I worked on made extensive use of tools like SELECT and Rational Rose for diagramming and documenting the design of software systems. With buggy user interfacesand ugly diagrams, the tooling may not have been brilliant back then, but it was still very useful if used in a pragmatic way.  \nI’m very much a visual person. I like being able to visualise a problem before trying to find a solution. Describe a business process to me, and I’ll sketch up a summary of it. Talk tome about a business problem, and I’m likely to draw a high-level domain model. Visualising the problem is a way for me to ask questions and figure out whether I’ve understood what you’re saying. I also like sketching out solutions to problems, again because it’s a great way to get everything out into the open in a way that other people can understand quickly.  \nBut then something happened somewhere during the early 2000s, probably as a result of the Manifesto for Agile Software Development that had been published a few years beforehand. The way teams built software started to change, with things like diagramming and documentation being thrown away alongside big design up front. I remember seeing numerous software development teams reducing the quantity of diagrams and documentation they were creating. In fact, I was often the only person on the team who really understood UML well enough to create diagrams with it.  \nFast-forward to the present day, and creating software architecture diagrams seems to be something of a lost art. I’ve been running software architecture training courses for a number of years, part of which is a simple architecture kata where groups of people are asked to design a software solution and draw some architecture diagrams to describe it. Over 10,000 people and 􀀘 40 countries later, I have gigabytes of anecdotal photo evidence-the majority of the diagrams use an ad hoc “boxes and arrows” notation with no clear notation or semantics. Designing software is where the complexity should be, not communicating it.  \nThis book focuses on the visual communication and documentation of software architecture. I’ve seen a number of debates over the years about whether software development is an art, a craft, or an engineering discipline. Although I think it should be an engineering discipline, I believe we’re a ","cbCaiq8fwkbYM4dQ","https://ap.wps.com/l/cbCaiq8fwkbYM4dQ","pdf",5206158,23,"English","# About the book\n## About the author\n## We have a failure to communicate\n### What happened to SSADM, RUP, UML, etc?\n### A lightweight approach\n### Draw one or more diagrams\n### Where do we start?\n### Some examples\n### Common problems\n### The hidden assumptions of diagrams","[{\"question\":\"Why does the book focus on visual communication of software architecture?\",\"answer\":\"It argues that software design should be communicated clearly, yet teams increasingly reduce or abandon diagrams and documentation, leaving understanding incomplete.\"},{\"question\":\"What is the core contribution discussed in the book?\",\"answer\":\"The book centers on the author’s “C4 model” for visualising software architecture using lightweight ideas and techniques.\"},{\"question\":\"What issue does the author highlight about modern software development teams?\",\"answer\":\"The author describes a “failure to communicate,” where even with agile, testing, continuous delivery, and cloud practices, teams still miss effective architectural communication.\"}]","The C4 model for visualising software architecture | PDF",1792963504,58]