Contact:cdent@burningchrome.com
von Halle, B. (1996). Architecting in a virtual world. Database
Programming & Design (November 1996). Available at:
http://www.dbpd.com/vault/9611arch.htm
Comparison of traditional architect with the information architect to
highlight ways in which the profession can be clarified and
strengthened. The information architect needs legitimacy in the
enterprise where increasingly complex information environments are
making increased demands on information professionals. The role of the
information architect is to provie overarching structure and defintion
to information resources.
-=-=-
From an email to the 597 mailing list:
Date: Tue, 11 Sep 2001 17:30:52 -0500 (EST)
From: cdent@burningchrome.com
Cc: L597 <ejacob_597ia_fall01@majordomo.indiana.edu>
Subject: Re: von Halle
There's another side of the coin: In many organizations the info or
systems architect is not a defined role and frequently is assigned
sort of absently or by accident. Many times a senior management
official becomes the architect by default and does not have the
training or experience to bridge the gap between the "customer" and
the engineers. Or worse disregards both (I've been in that situation
many times).
While I disagree with von Halle's rather simplistic and
over-structured approach to the classes of problems she discusses, I
do agree that formalizing the role of the information architect in an
enterprise setting is a valuable and necessary task, for the reasons
you state: the long view.
My disagreement is with the strict attachment to deliverables as a
concept. To me they imply too much of an end point to any project, cast
things into an inflexible time structure. There is no such thing as an
end point. Any investment in process automation is a long term commitment.
See
Johnson, B. & Woolfolk, W. (1999). Counterintuitive Management of
Information Technology. _Business Horizons, 42_(2). 29-37.
(it's available in full text on EBSCO)
for a more maintenance oriented approach to informations systems
management. It also happens to be a very good read if you need a
refreshing perspective.
On Tue, 11 Sep 2001, stephen douglas rice wrote:
> An aspect of the von Halle article that I found interesting was the
> discussion of the jurisdiction of the architect and the engineer. The
> article notes that in traditional architecture, the architect has the
> final jurisdiction. No one is to change the design except the architect.
>
> Looking back on projects I have been involved with, engineers have made
> decisions without consulting the 'architect'. These decisions were
> usually made because of system constraints but they did have impact on the
> final product. I don't think the engineers are good at looking forward to
> the final product and instead look at the immediate problem they are faced
> with.
>
> I think it will take a major shift in thinking to get the engineers to
> request approval for changes and recognize the impact of their decisions
> on the final product.
Back to the Index