SIGIA-L Mail Archives: RE: SIGIA-L: IA Deliverables
RE: SIGIA-L: IA Deliverables
From: Gent, Andrew (Andrew.Gent_at_compaq.com)
Date: Thu Mar 01 2001 - 09:06:04 EST
Richard,
It is probably too late, since you already are working on the site map
etc... but there are four additional documents, or parts of documents, that
I normally include as deliverables of any IA project:
Requirements
I am surprised how many projects survive (or don't) without a written set of
requirements. Completeness is not possible, but capturing and documenting
50-80% is essential. This document is used as a check to make sure the
client buys off on the set of requirements that we design to and, usually,
their priority. (Note, some clients push back on this, but for my own sake I
consider it essential.)
Assumptions
I usually include this in the requirements document, but sometimes we call
it out separately to make sure they are visible. They articulate any
assumptions about the environment, the users, or expected tradeoffs (e.g.
reliability is more important than additional features, must accommodate
browsers down to version n.n, users are experienced in x, y, and z, etc.)
Metrics
Sometimes included as part of the usability guidelines or requirements. The
metrics define a minimum set of goals the resulting system must meet to be
considered a success. We don't use metrics as a measurement of our meeting
our commitments (i.e. being paid). We use signoff on the project documents
and deliverabels for that. But we do use metrics to measure the minimal
"success" of the project overall; that is, whether we have met the intended
business goal.
Design Principles
Again, these are sometimes included in the requirements, but I like to call
them out. These are the high-level, often unstated, principles that drive
all aspects of the design. I like to keep them short; a page at most,
preferably a bulleted list, which has been as short as three bullets. These
are the core principles behind all decisions in the design and the
implementation. I keep them short so that every member of the team can
memorize them and we are all working from the same context.
Andrew Gent
Information Architect
Compaq Global Services
603 884-7475
-----Original Message-----
From: Oppedisano, Richard M
[mailto:richard.m.oppedisano_at_bankofamerica.com]
Sent: Thursday, March 01, 2001 8:41 AM
To: sigia-l_at_asis.org
Subject: SIGIA-L: IA Deliverables
Good morning all:
I am working on establishing basline deliverables for software application
information architecture. So far, I have identified and completed the
following deliverables:
site map
wireframes
usability guidelines
What else should I cover?
Please help,
Rick O.
===========================================================================
List archives are available at:
http://www.listquest.com/computers/tier2/computer_misc.html
--------------------------------------------------------------------------
To subscribe or unsubscribe, send mail to majordomo_at_asis.org with the
appropriate command from the list below in the body of the message:
subscribe sigia-l
subscribe sigia-l-digest
unsubscribe sigia-l
unsubscribe sigia-l-digest
===========================================================================
List archives are available at:
http://www.listquest.com/computers/tier2/computer_misc.html
--------------------------------------------------------------------------
To subscribe or unsubscribe, send mail to majordomo_at_asis.org with the
appropriate command from the list below in the body of the message:
subscribe sigia-l
subscribe sigia-l-digest
unsubscribe sigia-l
unsubscribe sigia-l-digest
This archive was generated by hypermail 2.1.2
: Sun Nov 23 2003 - 22:54:34 EST
|