RE: Looking 4 resources: Software development cycle / Software Usability

["Steve Hudson" <steve -at- wright -dot- com -dot- au>]

Your key role in the dev process is the development of thorough use cases in
the initial planning stage, these then get turned into functional specs
which you maintain change control over with the product manager, then whilst
the coders are running amuck you wander around and gather their charts and
notes to compile into the technical spec.

The help system /user guide becomes trivial as you also work off the
functional spec. The initial prototype is barely a skeleton, which you flesh
out as each dialog is realised.

There are some examples of these documents on the HATT site, under Files
then Skeletons

http://groups.yahoo.com/group/HATT


Steve Hudson
Principal Technical Writer
Wright Technologies (Aus)
steve -at- wright -dot- com -dot- au
(612) 9518-1822
The best way to predict the future... is to create it!



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

A landmark hotel, one of America's most beautiful cities, and 
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe.  http://ieeepcs.org/2001/

  +++  Miramo -- Database/XML publishing automation.  See us at  +++
  +++  Seybold SFO, Sept. 25-27, in the Adobe Partners Pavilion  +++
  +++ More info: http://www.axialinfo.com  http://www.miramo.com +++

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.