[Sigia-l] IA system components - add to the list!

[Boniface Lau]

> From: sigia-l-admin at asis.org [mailto:sigia-l-admin at asis.org]On
> Behalf Of Arno Reichenauer
>
> "Boniface Lau" wrote:
>
> > IA stands for Information Architecture. Shouldn't there be a
> > component called “architecture"?
>
> Hm, I’m talking about what parts of a working interactive system
> an IA can contribute, i.e., very down-to-earch things like the
> navigation structure, or the content which will be part of the
> website. What would architecture include in that context?

How about the architecture itself? Creating/maintaining a non-trivial
interactive system without paying attention to its architecture will
cause the system to deteriorate or even collapse. Is system
architecture a very down-to-earth thing? I would think so. In fact,
non-attention to the architecture will likely bring the system
crushing down to earth.


[...]
> Why can’t we first of all just collect what each one of us is
> contributing to a working website or intranet and then use the sum
> of it as a starting point not for defining IA but for defining IA
> methodology, i.e. the process you have to go through to obtain these
> contributions?

If I understand you correctly, what you call "IA methodology" is
really a process for drawing information architects' contributions
into the development of various web site components. It is a misnomer
to call that IA methodology.


> The definition of IA itself would then be just a collateral result
> of this.

I think you meant collective when you said collateral. But the
collective result of your so called "IA methodology" is a web site,
not an information architecture.


> And everybody could then just choose the components he feels fine
> with, i.e. could specialize on specific parts of the sum of IA
> components?

Unfortunately, many people still equate site components (navigation,
searching, labeling, etc.) with information architecture. That reminds
me of a magic trick. Audience see a handkerchief that seems to be
covering something. They noticed the protruding corners. But as they
try to grab on to a corner, the handkerchief collapsed and the
audience found nothing but the handkerchief. Whatever beneath has
escaped.

Information architecture influences site components like the
"protruding corners". But equating site components with information
architecture will miss the real information architecture.


Boniface