> Architecture is the relationships between systems I find that somewhat limited. A part of architecture “can be” the relationship between systems. As with any

> Architecture is the relationships between systems I find that somewhat limited. A part of architecture “can be” the relationship between systems. As with anything expressing relationships, representing them using diagrams is helpful. Given the textual nature of our tools, storage and change systems, I like the idea that a diagram is based on code. However, it’s no panacea, as future maintainers still need to understand and learn the syntax and rules of that diagramming code. Can code and diagram changes be automated? I suggest no. I prefer to think that software architecture is the set of decisions made about how to implement the functional and non-functional requirements of a project.