What does software architecture mean and how does it differ from application architecture or systems architecture? Who is a software architect? Those are common questions amongst software or systems developers, and I’ve been on the receiving end many times. At other times I’ve introduced myself as a software security architect, before being asked, “I hope you’re not one of those people who just draw blocks on slides?”. So just what is software architecture and what do software architects do?
In his brilliantly written and free book or article (at least the web version) titled Technical Leadership and The Balance with Agility, Simon Brown, does a great job of describing the role, discipline, and practice of software architecture in systems development.
Here are a few teasers from the book:
All architecture is design but not all design is architecture.
Architecture represents the significant design decisions that shape a system, where significance is measured by cost of change
Becoming a software architect isn’t something that simply happens overnight or with a promotion. It’s a role, not a rank.
Software architecture is about the significant design decisions, where significance is measured by cost of change.
Subscribe
