SIGIA-L Mail Archives: RE: SIGIA-L: conventions
RE: SIGIA-L: conventions
Date: Tue Jul 11 2000 - 10:31:03 EDT
The notation dragon strikes again!
I've been too swamped the past several days to review the recent
"notation" etc. thread, but I'm hoping to do that soon. I want to
ask a few questions about some of the things discussed in order to
get a better feel for what is to be notated.
One question that comes to mind - someone mentioned that notation
still would be unable to capture the "meaning" of the website/pages
to the user. Could someone elaborate on this?
Seems to me that maybe we're looking for more than one notation.
One notation could show abstract architecture, and another could
show its "mapping" to implementation elements. As an example of the
latter, I doubt it would be necessary to document an actual entry
in a pulldown menu if there was a standard notational element that
"stood for" this.
On another topic: I did start to re-comb past SIGIA-L posts and I'm
finding "striking" similarities between IA "problems" and those
encountered in more general s/w design/engineering. This might
be grist for the "body of knowledge" idea I discussed in a post
on 28 June.
From: Matt LaLiberte [mailto:mlaliberte_at_flywire.com]
Sent: Tuesday, July 11, 2000 8:39 AM
Subject: SIGIA-L: conventions
Our company is just starting to integrate IA into its SOP, and we're feeling
some growing pains. What conventionas exist for documenting an IA? Are there
standard means of identifying links, graphics, pulldowns, and so forth?
Ideally, we would like to standardize our visual displays of client IAs so
all team members can understand what we're refering to- can anyone assist us
or point us in the right direction?
T 603.430.3700 x153
This archive was generated by hypermail 2.1.2
: Sun Nov 23 2003 - 22:54:20 EST