Visualise, document and explore your software architecture
$20.00
Minimum price
$25.00
Suggested price

Visualise, document and explore your software architecture

Software Architecture for Developers - Volume 2
  • 20,226

    Readers

  • 193

    Pages

  • English

  • PDF

  • EPUB

  • MOBI

  • WEB

About the Book

This book focusses on the visual communication and documentation of software architecture, based upon a collection of ideas and techniques that thousands of people across the world have found useful. The core of this is my C4 software architecture model and the software guidebook. You'll also find discussion about notation, the various uses for diagrams, the value of creating a model and tooling.

This book was formerly called "The Art of Visualising Software Architecture", and now additionally includes information about documentation.

About the Author

Simon Brown
Simon Brown

Simon is an independent software development consultant specializing in software architecture; specifically technical leadership, communication, and lightweight, pragmatic approaches to software architecture. Simon is the author of "Software Architecture for Developers", a developer-friendly guide to software architecture, technical leadership, the balance with agility and communicating software architecture with sketches, diagrams, and models. He is also the creator of the C4 model and the founder of Structurizr, a collection of tooling to help teams visualise, document and explore their software architecture.

Bundles that include this book

Software Architecture for Developers: Volumes 1 & 2 - Technical leadership and communication
2 Books
$50.00
Suggested Price
$25.00
Bundle Price

Table of Contents

  •  
    • About the book
    • About the author
  • I Visualise
    • 1. We have a failure to communicate
      • 1.1 What happened to SSADM, RUP, UML, etc?
      • 1.2 A lightweight approach
      • 1.3 Moving fast requires good communication
      • 1.4 Draw one or more diagrams
      • 1.5 Where do we start?
      • 1.6 Some examples
      • 1.7 Common problems
      • 1.8 The hidden assumptions of diagrams
    • 2. A shared vocabulary
      • 2.1 Common abstractions over a common notation
      • 2.2 Static structure
      • 2.3 Components vs code?
      • 2.4 Modules and subsystems?
      • 2.5 Microservices?
      • 2.6 Serverless?
      • 2.7 Platforms, frameworks and libraries?
      • 2.8 Create your own shared vocabulary
    • 3. The C4 model
      • 3.1 Hierarchical maps of your code
    • 4. Level 1: System Context diagram
      • 4.1 Intent
      • 4.2 Structure
      • 4.3 Elements
      • 4.4 Interactions
      • 4.5 Motivation
      • 4.6 Audience
      • 4.7 Required or optional?
    • 5. Level 2: Container diagram
      • 5.1 Intent
      • 5.2 Structure
      • 5.3 Elements
      • 5.4 Interactions
      • 5.5 Motivation
      • 5.6 Audience
      • 5.7 Required or optional?
    • 6. Level 3: Component diagram
      • 6.1 Intent
      • 6.2 Structure
      • 6.3 Elements
      • 6.4 Interactions
      • 6.5 Motivation
      • 6.6 Audience
      • 6.7 Required or optional?
    • 7. Level 4: Code-level diagrams
      • 7.1 Intent
      • 7.2 Structure
      • 7.3 Motivation
      • 7.4 Audience
      • 7.5 Required or optional?
    • 8. Notation
      • 8.1 Titles
      • 8.2 Keys and legends
      • 8.3 Elements
      • 8.4 Lines
      • 8.5 Layout
      • 8.6 Orientation
      • 8.7 Acronyms
      • 8.8 Quality attributes
      • 8.9 Diagram scope
      • 8.10 Listen for questions
    • 9. Diagrams must reflect reality
      • 9.1 The model-code gap
      • 9.2 Technology details on diagrams
      • 9.3 Would you code it that way?
    • 10. Other diagrams
      • 10.1 Architectural view models
      • 10.2 System Landscape
      • 10.3 User interface mockups and wireframes
      • 10.4 Business process and workflow
      • 10.5 Domain model
      • 10.6 Runtime and behaviour
      • 10.7 Infrastructure
      • 10.8 Deployment
      • 10.9 And more
  • II Document
    • 11. Software documentation as a guidebook
      • 11.1 The code doesn’t tell the whole story
      • 11.2 Our duty to deliver documentation
      • 11.3 Lightweight, supplementary documentation
      • 11.4 1. Maps
      • 11.5 2. Sights
      • 11.6 3. History and culture
      • 11.7 4. Practical information
      • 11.8 Describe what you can’t get from the code
      • 11.9 Product vs project documentation
      • 11.10 Keeping documentation up to date
      • 11.11 Documentation length
    • 12. Context
      • 12.1 Intent
      • 12.2 Structure
      • 12.3 Motivation
      • 12.4 Audience
      • 12.5 Required
    • 13. Functional Overview
      • 13.1 Intent
      • 13.2 Structure
      • 13.3 Motivation
      • 13.4 Audience
      • 13.5 Required
    • 14. Quality Attributes
      • 14.1 Intent
      • 14.2 Structure
      • 14.3 Motivation
      • 14.4 Audience
      • 14.5 Required
    • 15. Constraints
      • 15.1 Intent
      • 15.2 Structure
      • 15.3 Motivation
      • 15.4 Audience
      • 15.5 Required
    • 16. Principles
      • 16.1 Intent
      • 16.2 Structure
      • 16.3 Motivation
      • 16.4 Audience
      • 16.5 Required
    • 17. Software Architecture
      • 17.1 Intent
      • 17.2 Structure
      • 17.3 Motivation
      • 17.4 Audience
      • 17.5 Required
    • 18. Code
      • 18.1 Intent
      • 18.2 Structure
      • 18.3 Motivation
      • 18.4 Audience
      • 18.5 Required
    • 19. Data
      • 19.1 Intent
      • 19.2 Structure
      • 19.3 Motivation
      • 19.4 Audience
      • 19.5 Required
    • 20. Infrastructure Architecture
      • 20.1 Intent
      • 20.2 Structure
      • 20.3 Motivation
      • 20.4 Audience
      • 20.5 Required
    • 21. Deployment
      • 21.1 Intent
      • 21.2 Structure
      • 21.3 Motivation
      • 21.4 Audience
      • 21.5 Required
    • 22. Operation and Support
      • 22.1 Intent
      • 22.2 Structure
      • 22.3 Motivation
      • 22.4 Audience
      • 22.5 Required
    • 23. Development Environment
      • 23.1 Intent
      • 23.2 Structure
      • 23.3 Motivation
      • 23.4 Audience
      • 23.5 Required
    • 24. Decision Log
      • 24.1 Intent
      • 24.2 Structure
      • 24.3 Motivation
      • 24.4 Audience
      • 24.5 Required
  • III Tooling
    • 25. Sketches, diagrams, models and tooling
      • 25.1 Sketches
      • 25.2 Diagrams
      • 25.3 Models
      • 25.4 Reverse-engineering the software architecture model
      • 25.5 Architecture description languages
      • 25.6 Structurizr
      • 25.7 Minimise the model-code gap
    • 26. The C4 model with other notations and tools
      • 26.1 Boxes and lines
      • 26.2 UML (with a modeling tool)
      • 26.3 UML (with PlantUML)
    • 27. Exploring your software architecture model
      • 27.1 Static structure
      • 27.2 Dependency maps
      • 27.3 Component size or complexity
      • 27.4 Other ways to explore
    • 28. Appendix A: Financial Risk System
      • 28.1 Background
      • 28.2 Functional Requirements
      • 28.3 Non-functional Requirements
  • Notes

Authors have earned$10,098,681writing, publishing and selling on Leanpub, earning 80% royalties while saving up to 25 million pounds of CO2 and up to 46,000 trees.

Learn more about writing on Leanpub

The Leanpub 45-day 100% Happiness Guarantee

Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

See full terms

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers), EPUB (for phones and tablets) and MOBI (for Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses! Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks. Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. It really is that easy.

Learn more about writing on Leanpub

Top Books

  1. #1

    C++20

    Rainer Grimm

    C++20 is the next big C++ standard after C++11. As C++11 did it, C++20 changes the way we program modern C++. This change is, in particular, due to the big four of C++20: ranges, coroutines, concepts, and modules.

    The book is almost daily updated. These incremental updates ease my interaction with the proofreaders.

  2. #2

    A Guide to Artificial Intelligence in Healthcare

    Dr. Bertalan Mesko

    Can we stay human in the age of A.I.?  To go even further, can we grow in humanity, can we shape a more humane, more equitable and sustainable healthcare? This e-book aims to prepare healthcare and medical professionals for the era of human-machine collaboration. Read our guide to understanding, anticipating and controlling artificial intelligence.

  3. #3

    Atomic Kotlin

    Bruce Eckel and Svetlana Isakova

    For both beginning and experienced programmers! From the author of the multi-award-winning Thinking in C++ and Thinking in Java together with a member of the Kotlin language team comes a book that breaks the concepts into small, easy-to-digest "atoms," along with exercises supported by hints and solutions directly inside IntelliJ IDEA!

  4. #4

    Introducing EventStorming

    Alberto Brandolini

    The deepest tutorial and explanation about EventStorming, straight from the inventor.

  5. #5

    C++ Best Practices

    Jason Turner

    Level up your C++, get the tools working for you, eliminate common problems, and move on to more exciting things!

  6. #6

    Ansible for DevOps

    Jeff Geerling

    Ansible is a simple, but powerful, server and configuration management tool. Learn to use Ansible effectively, whether you manage one server—or thousands.

  7. #7

    Everyday Rails - RSpecによるRailsテスト入門

    Junichi Ito (伊藤淳一), AKIMOTO Toshiharu, 魚振江, and Aaron Sumner

    RSpecを使ってRailsアプリケーションに信頼性の高いテストを書く実践的なアドバイスを提供します。詳細で丁寧な説明は本書のオリジナルコンテンツです。また、説明には実際に動かせるサンプルアプリケーションも使用します。本書は2017年版にアップデートされ、RSpec 3.6やRails 5.1といった新しい環境に対応しています！さあ、自信をもってテストできるようになりましょう！

  8. #8

    The Hundred-Page Machine Learning Book

    Andriy Burkov

    Everything you really need to know in Machine Learning in a hundred pages.

  9. #9

    Composing Software

    Eric Elliott

    All software design is composition: the act of breaking complex problems down into smaller problems and composing those solutions. Most developers have a limited understanding of compositional techniques. It's time for that to change.

  10. #10

Top Bundles

  1. #1

    Software Architecture for Developers: Volumes 1 & 2 - Technical leadership and communication

    2 Books

    "Software Architecture for Developers" is a practical and pragmatic guide to modern, lightweight software architecture, specifically aimed at developers. You'll learn:The essence of software architecture.Why the software architecture role should include coding, coaching and collaboration.The things that you really need to think about before...
  2. #2

    All the Books of The Medical Futurist

    6 Books

    We put together the most popular books from The Medical Futurist to provide a clear picture about the major trends shaping the future of medicine and healthcare. Digital health technologies, artificial intelligence, the future of 20 medical specialties, big pharma, data privacy, digital health investments and how technology giants such as Amazon...
  3. #3

    Cisco CCNA 200-301 Complet

    4 Books

    Ce lot comprend les quatre volumes du guide préparation à l'examen de certification Cisco CCNA 200-301.
  4. #4

    Linux Administration Complet

    4 Books

    Ce lot comprend les quatre volumes du Guide Linux Administration :Linux Administration, Volume 1, Administration fondamentale : Guide pratique de préparation aux examens de certification LPIC 1, Linux Essentials, RHCSA et LFCS. Administration fondamentale. Introduction à Linux. Le Shell. Traitement du texte. Arborescence de fichiers. Sécurité...
  5. #5

    Learn Git, Bash, and Terraform the Hard Way

    3 Books

    Learn Git, Bash and Terraform using the Hard Way method.These technologies are essential tools in the DevOps armoury. These books walk you through their features and subtleties in a simple, gradual way that reinforces learning rather than baffling you with theory.
  6. #6

    PowerShell

    3 Books

    Buy every PowerShell book from Adam Bertram at a 20% discount!
  7. #7

    Software Architecture and Beautiful APIs

    2 Books

    There is no better way to learn how to design good APIs than to look at many existing examples, complementing the Software Architecture theory on API design.
  8. #8

    9 Books-Bundle: Shut Up and Code!

    9 Books

    "Shut up and code." Laughter in the audience. The hacker had just plugged in his notebook and started sharing his screen to present his super-smart Python script. "Shut up and code" The letters written in a white literal coding font on black background was the hackers' home screen background mantra. At the time, I was a first-year computer...
  9. #9

    CCDE Practical Studies (All labs)

    3 Books

    CCDE lab
  10. #10

    Modern C++ by Nicolai Josuttis

    2 Books

Publish Early, Publish Often

  • Path
  • There are many paths, but the one you're on right now on Leanpub is:
  • › Visualising-software-architecture

Leanpub is copyright © 2010-2021 Ruboss Technology Corp. All rights reserved.