[Sigia-l] Sigia-l Digest, Vol 41, Issue 22

[Lee Hsieh]

One approach is to define high level goals users want to achieve and then break each down into tasks users must perform to achieve those goals.  From there you can define features/functionality that the system must support for each task.  You can augment this approach with workflow/taskflow, hub&spoke diagrams.

Lee

sigia-l-request at asis.org wrote:
> 
> Message: 1
> Date: Wed, 27 Feb 2008 07:46:56 -0500
> From: Susan Rice <ratdog99 at hotmail.com>
> Subject: [Sigia-l] Interesting & Effective Requirements Gathering
> 	Techniques?
> To: <sigia-l at asis.org>
> Message-ID: <BAY103-W1380FF78CF0275A60F1758C41A0 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> I'm looking for interesting techniques for the requirements gathering of internal applications... specifically ones that involve levels of participatory design (our users are in-house and will participate as cross functional team members). We'll be conducting traditional JAD sessions and paper prototyping, but I'm interested in other ideas that have been effective and possibly even "fun." Thanks!~Susan Rice
> User Experience Lead for Strategic Applications
> VistaPrint
>