Architecture type definitions

re: Architecture type definitions

Panagiotis Kanavos, SQL Server MVP — Mon, 10 Oct 2005 23:59:04 GMT

What is then the definition of the Software Architect? I heard the term mentioned at a summit two weeks ago ;)

re: Architecture type definitions

Graham Chastney — Thu, 03 Nov 2005 19:36:46 GMT

Nice post. I'm not sure though that I would split the definitions the way that you have or give the names that you have. I think the problem is with the definition of a solution architect and an infrastructure architect. In a sense there is a suggestion from the names that the infrastructure architect doesn't deliver any solutions and that's clearly not the case. Speaking as someone who is clearly within the Infrastructure Architect camp (from your definition) it facinates me that the Infrastructure Architect is always put last, almost like it's a hierarchy, again something that is clear not true.

re: Architecture type definitions

Ekrem Aksoy — Tue, 13 Dec 2005 14:38:03 GMT

To me, these definitons are necessary to distinguish roles in such a software organization. However, as a "solution architect", I'd such moments to decide the strategical extension for projects. I mean, although we can say where an architect's point of view is, we should care of his/her context. Thus, instead of defining the boundaries, we should focus on architectural body of knowledge. It has to be canonical such that we all can apply to several layers of abstraction

re: Architecture type definitions

Gary Varga — Tue, 13 Dec 2005 14:47:12 GMT

I don't see it as a hierarchy, or if there is one, the Solution Architect (SA) is at the bottom of the tree. Not because they are any less skilled but because the SA works on projects (or programmes at most) which build upon the work of the other two. It has a clear period for each project (ignore deadline slippage etc) i.e. a beginning and an end.

The Infrastructure Architect (IA) role appears to be an attempt to make the use of computing as close to utility usage as is reasonably possible e.g. delivers a new machine that plugs into a network that allows access to all that a user needs (and no more). It is a neverending (and thankless?) task.

The Enterprise Architect (EA) tends to define future changes to match current requirements or new ways to deliver them. These changes may be to process, tools or roles. This role is again continuous, like the IA.

Basically, the EA is responsible for defining the future direction of the provision of tools (i.e. manual or automated systems) to support the needs of the business. The IA provides the technical platform (including COTS) for the business to utilise. Whilst the SA is responsible for providing a specific tools to the business to perform specific tasks.

As for a Software Architect - this really is split between the EA and the SA. Both do Software Architect duties but at a different level. The SA relies on architectural decisions made by the EA and the IA.

This is my view as an SA.

The various hats of an architect...

Ali Pasha's WebLog... — Wed, 15 Feb 2006 04:41:57 GMT

One of the most heated debates out there is that of the definition of an architect. In my view, what...

Architecture this, architecture that ...

Panagiotis Kanavos' Weblog — Thu, 16 Feb 2006 19:13:14 GMT

Διάβασα πρόσφατα το άρθρο "What is a software architecture?" στο τελευταίο τεύχος του Rational Ezine....

Links on Architecture

Paulo Sousa — Tue, 14 Mar 2006 17:51:33 GMT

original post on October 26th, 2005
Just some links for future reference:

Enterprise Architecture,...

What is Architecture - Part 2

Arno Nel on Web Development, Web 2.0 and Sharepoint — Fri, 28 Apr 2006 08:38:48 GMT

In this post&nbsp;i asked what Architecture is. Michael Platt, in this post, describes 3 Architect Roles,...

What is Architecture - Part 2

Arno Nel — Fri, 28 Apr 2006 08:38:58 GMT

In this post&nbsp;i asked what Architecture is. Michael Platt, in this post, describes 3 Architect Roles,...

Architect Personas

simonguest.com — Mon, 16 Oct 2006 01:42:11 GMT

I’ve sat through many architect events over the past few years and one thing that always strikes