Thoughts on being a Solution Architect

What is a Solution Architect?

Web Dillies — Tue, 29 Apr 2008 16:00:29 GMT

Pretty good question. You can ask ten people and you will get ten answers, ten different answers. Tom

Software Architecture

Sunny Nagi — Thu, 01 May 2008 05:15:09 GMT

Software architecture has become one of the hottest topic in last year or so. I also moved into software

re: Thoughts on being a Solution Architect

Jon Kruger — Mon, 12 May 2008 02:45:57 GMT

Excellent post. I'm in the same role on my current project and I can relate to all of this stuff!

I think the part about still writing some code is really important. I've been on projects where things in the code base weren't designed the way they should be and then it slowed the whole project down. So if I'm responsible for the architecture side of things, it my job to be involved enough to make sure that that doesn't happen.

re: Thoughts on being a Solution Architect

Ross — Wed, 14 May 2008 10:05:49 GMT

A more basic question, how many architects do you know that get in there and cement bricks together when building a house. If you are still in the code, sorry, but I suggest you are a Developer rather than an architect. Architects take in the environment and align the requirements to that environment, looking after the people, the processes and the technology.

They need an understanding of the SDLC and the concepts but code - no way.

My two bits, happy to be hammered. I have just finished as Solution Architect on a large gateway project and if I had got involved in the code, I would have had 4 vendors on my tail. However, whenever there was an issue, I could usually identify the area and the vendor to resolve it.

relate it to buildings. EA design the town and the infrastructure. Solution Architects design the house plans and the tests for functionality, vendors and developers build to those plans and verify the functionality.

All fits neatly. Doesn't mean that the SA doesn't come and check how the project is hanging together.