What consequences does this mindset bring about?
- Architecture is not a tangible artefact, but a social construct. (See note below.)
- Architecture cannot be created directly, but is the result of other activities (i.e. planning, designing, building and sustaining a system).
- The team creates the architecture through interaction. Someone called an architect doesn’t create the architecture by drawing diagrams for the team.
- Someone called an architect could promote the shared understanding of a system through conversations with fellow team members and potentially creating supporting artefacts.
- Someone called an architect may well contribute to making significant design decisions (sometimes called architecture in the sense of a system’s significant design decisions).
Note: I didn’t come up with the notion of “architecture as a social construct” myself. But then again, I don’t seem to be able to find a single source, so I probably mashed up some ideas from the sources on architecture I mentioned before and the notion of “software as a social construct”.
2013-11-24: Added note on “architecture as a social construct”.