What's the difference between Enterprise Architect , Software/Solution Architect and a Dev Senior?
I was discussing with some friends and I got to the conclusion that in the Software area Architects are divided into **Enterprise Architect** and **Software/Solution Architect**.

**Enterprise Architect** => It is the IT professional more connected to the business, usually specializing in one industry vertical. It, we want a broad knowledge of processes, methods and platforms, both business and IT. He must be the right arm of the CxO level, when we speak in the strategic definition of IT. Therefore, we are reducing the scope for large corporations, where there is space for this type of structure and business impact.

**Software/Solution Architect** = Design decisions and organization of software components that are part of the system are autonomous decisions of the developer, you can take good PATTERNS development and architecture, is guided by the solution architect / software, is based on his own luggage training with knowledge of UML, patterns, frameworks, etc. .. Many developers are expert software architects and not make much sense to have this separation in some cases. Think about SCRUM, which defines all of the Development Team as DEVELOPERS! A fine example!

I wanted to confirm this conclusion. That's OK?

If this is correct, I see no separation between a **Developer** and a **Software/Solution Architect**. To me all developer should know make decisions of the code he are building, know which technology to use, the appropriate place to put some class or another component. Summarizing every developer should be a Software Architect, otherwise I do not think he is a developer and I see no reason for being called Software Architect.

What you guys think?
What's the difference between Enterprise Architect , Software/Solution Architect and a Dev Senior?
===

I was discussing with some friends and I got to the conclusion that in the Software area Architects are divided into **Enterprise Architect** and **Software/Solution Architect**.

**Enterprise Architect** => It is the IT professional more connected to the business, usually specializing in one industry vertical. It, we want a broad knowledge of processes, methods and platforms, both business and IT. He must be the right arm of the CxO level, when we speak in the strategic definition of IT. Therefore, we are reducing the scope for large corporations, where there is space for this type of structure and business impact.

**Software/Solution Architect** = Design decisions and organization of software components that are part of the system are autonomous decisions of the developer, you can take good PATTERNS development and architecture, is guided by the solution architect / software, is based on his own luggage training with knowledge of UML, patterns, frameworks, etc. .. Many developers are expert software architects and not make much sense to have this separation in some cases. Think about SCRUM, which defines all of the Development Team as DEVELOPERS! A fine example!

I wanted to confirm this conclusion. That's OK?

If this is correct, I see no separation between a **Developer** and a **Software/Solution Architect**. To me all developer should know make decisions of the code he are building, know which technology to use, the appropriate place to put some class or another component. Summarizing every developer should be a Software Architect, otherwise I do not think he is a developer and I see no reason for being called Software Architect.

What you guys think?