Simon Guest posted an entry on “Architect Personas” in which he identifies three different personas in software architecture:
- Enterprise Architect – Strategic Architect, Chief Architect, Business Architect
- Solutions Architect – Application Architect, Data Architect, Integration Architect
- Infrastructure Architect – Technology Architect, Systems Architect
I thought this was quite an interesting concept and I also enjoyed one of the comments made by Mitchell Land regarding the Solutions Architect. He says:
“I think you can create another triangle solely for the Solutions area in which you have Software Architect, Data Architect and, perhaps, Integration Architect. Some people are more accomplished in one area over the others. The individual who is accomplished in all three is a true Solutions Architect”
I agree with this statement but also believe that the titles data architect, application architect, and integration architect are a bit misleading. My belief is that these titles are created just to categorize somebody as senior in their particular area of software development. If these category of software developers are titled architects it creates confusion for those who do not understand a solutions, enterprise, or infrastructure architects role. They may say things like “aren‘t software architects just a senior developer”.
I had a conversation recently in which it was brought up that the use of the architect title is perceived to equal a lead or senior software developer. The interesting part was after discussing this back and forth we thought it may be helpful to describe the lead and senior level developers. These are roles which are greatly needed within organizations for more granular domain recognition and team mentoring. By doing so we may get a better distinction between a lead or senior software developer and a software architect.
