aspose file tools*
The moose likes Agile and Other Processes and the fly likes Solution Architect   Vs   Technical Architect Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Solution Architect   Vs   Technical Architect" Watch "Solution Architect   Vs   Technical Architect" New topic
Author

Solution Architect Vs Technical Architect

kri shan
Ranch Hand

Joined: Apr 08, 2004
Posts: 1372
How the responsibilities(requirements gathering, Modelling(DB Modelling & UML Modelling)) differs Solution Architect & Technical Architect ?
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
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.


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
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).


A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Chris Nappin
Ranch Hand

Joined: Aug 04, 2005
Posts: 36
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.


Technical Architect, SCJP, SCWCD
Rajah Nagur
Ranch Hand

Joined: Nov 06, 2002
Posts: 239
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


You can't wake a person who is <b><i>pretending</i></b> to be asleep.<br />Like what <b>"it"</b> does not like - <i> Gurdjieff </i>
Kishore Dandu
Ranch Hand

Joined: Jul 10, 2001
Posts: 1934
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.


Kishore
SCJP, blog
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Solution Architect Vs Technical Architect