SIGIA-L Mail Archives: RE: SIGIA-L: notations
RE: SIGIA-L: notations
From: Lisa Chan (lisa.chan_at_av.com)
Date: Tue Jul 11 2000 - 12:42:13 EDT
If October is too late to discuss notation methods...maybe mini-groups can
form at various locations to discuss with whomever(of course we can take
over the local diner to discuss or get someone to get facilities set up?)
the frustrations and the triumphs of notation systems. I agree with Chuck
and I think others would as well that there are so many overlaps in IA work
with other disciplines.
Things that could be discussed/"action items list":
-basics of what everyone does
-overview of existing notation schemas(who's got a summary of this?)
-how we can grab all the best practices, create some kind of methodology
-try it in practice
-discuss again what worked/what didn't work.
-hash out the different layers of information that various groups require
from our deliverables
<add to this list and we can forward this to those who want to lead
mini-groups in local areas, even if we can't get official facilities, maybe
we can take over a local diner/Denny's to discuss these topics>
Thanks,
Lisa
-----Original Message-----
From: chuck.lutz_at_telelogic.com [mailto:chuck.lutz_at_telelogic.com]
Sent: Tuesday, July 11, 2000 7:31 AM
To: sigia-l_at_asis.org
Subject: RE: SIGIA-L: conventions
Augh!
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.
Chuck
-----Original Message-----
From: Matt LaLiberte [mailto:mlaliberte_at_flywire.com]
Sent: Tuesday, July 11, 2000 8:39 AM
To: sigia-l_at_asis.org
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?
Matt LaLiberte
Flywire
www.flywire.com
T 603.430.3700 x153
F 603.430.3766
This archive was generated by hypermail 2.1.2
: Sun Nov 23 2003 - 22:54:20 EST
|
