“What architects do I require in my organization?”, “What architect could I be?”. Two different questions. One from a customer, the other from a colleague or job applicant. Both questions are related: They both assume (in a way) a clear distinct separation of the architecture domain into roles. Based on job titles, advertisements and function-descriptions there are dozens of architecture-roles used in the field: information architects, enterprise architects, solution architects, software architects… and so on, and so on. You most likely have a feeling about their supposed meaning and responsibilities, just like I do.
Structuring (a forest of) architecture-roles
4 september 2016