| - Be very mindful of the "level of recursion" you are trying to express - i.e. how many trees to include when it should be a forest. - Look into the C4 model - that is great for expressing architecture. - Have a Miro board with multiple versions and working charts. - Make at least one that reflects the full process, and one chart that reflects the relationships between components. - Keep it simple, and avoid creating DoD style monstrosities. if you find yourself in that situation it means either you are mixing up recursion levels, or are not very clear on the purpose of the chart and the audience. - Boxes and arrows are enough - I personally have benefited from UML style charts, others hate them. - Domain Driven Design and Event Storming style maps are also very clear way to express things. - Most importantly - remember that an architecture is not a static thing, but a living, changing and ever-evolving thing. Like a garden. |