• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • paul wheaton
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Tim Holloway
  • Carey Brown
  • salvin francis

Solution Architect Vs Technical Architect

 
Ranch Hand
Posts: 1490
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How the responsibilities(requirements gathering, Modelling(DB Modelling & UML Modelling)) differs Solution Architect & Technical Architect ?
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Job titles are just words. They don't necessarily mean anything and when they do, they likely mean two different things between two different companies or even two different projects.

Having said that, I'd wager that a "solution architect" role would tend more towards the overall solution while the "technical architect" role would tend more towards a specific part of the overall solution.
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've only run across the TA job title with a vendor. There it was a senior developer who thoroughly knew the guts of the system AND could be trusted with high level design and architecture decisions. In other words, a nearly impossible assignment on a product developed over many years by dozens of people all over the world and customized nearly beyond recognition by the customer (us).
 
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The only times I've come accross those job titles, a "TA" was more junior than an "SA".

A Solution Architect looks after things from a higher level, possibly overseeing a programme of projects rather than just the one. They could also be involved in a lot more than simply software development, for example hardware, 3rd party software, business process re-engineering and anything that makes up the overall "solution" that a customer has purchased.

A Technical Architect has a lower-level focus, and typically deals with the Software (and possibly hardware) issues on one project (or product line).

Having said that "Architect" is probably one of the vaugest job titles in the Industry and in practice means very little.
 
Ranch Hand
Posts: 239
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree with above opinions and views.

Solution Architect has higher responsibility, more experienced, good domain knowledge, responsible for more than one projects. His main reponsibility would be to streamline different techologies used in different projects, foucs on reducing costs and finding a better/cheap solution.
His mantra would be to reduce costs and improve revenue for the account he is responsible for.

He is assisted by few Business stakeholders, Techincal architects etc

---Just my thoughts
 
Ranch Hand
Posts: 1934
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Rajah Nagur:
I agree with above opinions and views.

He is assisted by few Business stakeholders, Techincal architects etc

---Just my thoughts



It is not always the case. Depending on the entity you are working lot of these jobs fall with different hierarchies and responsibilities.
 
Villains always have antidotes. They're funny that way. Here's an antidote disquised as a tiny ad:
professionally read, modify and write PDF files from Java
https://products.aspose.com/pdf/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!