I've been talking through the role profile for software architects recently and I'm going to publish a revised version soon. In the meantime, I thought that it's worth clarifying exactly who the profile is aimed at. Although there might not be a common definition of "architecture", there is agreement that there are different scales of architecture. For example, you might have architecture at an application level, at a software system level or at an enterprise level.
Put simply; the role profile is aimed at those of us taking responsibility for the architecture of a bespoke software development, which I've summarised as follows.
Essentially, the scope of the role is the software and the infrastructure on which that software runs upon, which my experience suggests is what people mean by "software architect" or "technical architect" (i.e. they are aggregate terms). What do you think?
Simon is an independent consultant specializing in software architecture, and the author of Software Architecture for Developers (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He’s also the creator of the C4 software architecture model and the founder of Structurizr, which is a collection of open source and commercial tooling to help software teams visualise, document and explore their software architecture.