requirements

31 Mar 2011 - 10:33am
0
Terms:
kabe001
2010

Persona Driven Use Cases

Does anyone have good examples for persona driven use cases or use scenarios? Ideally formats, data elements, etc. that should be included.

thanks.

7 Sep 2010 - 6:00am
0
1 year ago
2 replies
Terms:
Jan Dittrich
2010

Simplifying Needs and Requirements Description

I am thinking about a way which is easy-top-apply for  turning (user) research into Requirements, Needs and Goals – so the prerequisites for the actual design process.

4 Nov 2009 - 12:06pm
0
2 years ago
1 reply
Terms:
j.scot
2008

Serena Prototype Composer?

Some guys at work are exploring this... I'm curious if any of you
guys have ever used it?

5 Oct 2009 - 2:13pm
0
2 years ago
1 reply
Terms:
Siegy Adler
2009

Identifying Stakeholder Requirements

Here’s my take on a key first step in the development of any
functional spec – the identification of stakeholder requirements.

Let's start by defining the term 'stakeholder'. A stakeholder can
be anyone who has an interest in the successful completion of a
project. This may include the individual(s) authorizing the project
as well as the folks who will actually be using the application. Once
you have identified the stakeholders, at a minimum, you'll need to
get answers to the following questions:

1.

23 May 2008 - 5:33pm
0
3 years ago
5 replies
Terms:
Luke Bishop
2008

query: mobile functionality trends

Hi All,

Im curious if anyone has come across any recent research or trend projections regarding the future of mobile phone form / functionality / IxD, as a result of nano-technologies impacting the industry.
Sorta along the lines of what Nokia is projecting in 5-7 years with Morph.
Apologies if this is already an ancient line of discussion here...

cheers!
- Luke

----please consider whether it is necessary to print this email----

19 May 2008 - 8:24pm
0
3 years ago
3 replies
Terms:
Todd Moy
2007

Users' ability to predict features they "need"

Hi all,

I'm looking for some information about users' ability to predict the
features that they need. In the past, I've heard the statement "people are
poor predictors of the features they need." I tend to agree with this
argument, especially since I encounter cases where clients feel they "need"
blogs, forums or whatever without first analyzing the goals of their users.

What I can't recall is if there are studies that support or refute this
argument.

27 Mar 2008 - 11:21am
0
1 year ago
5 replies
Terms:
Jeff Axup
2006

Use Case / Requirements Management Tools

Hi Everyone,

My company is currently looking into tools to manage use cases and
requirements.

Since these terms can mean a wide variety of things I'll give an example of
how we're using them:

*Requirement:* The product should be secure and protect the safety and
privacy of the user.
*Use Case:* The user logs on to the system.
*Sub-use case/scenario:* The user has mistyped their password while logging
in.
*Associated features: *Login screen, password security feedback, lost
password functionality, error feedback system.
*Associated users/actors: *Child, parent, administrator

We are developi

13 Dec 2004 - 11:27am
0
7 years ago
13 replies
Terms:
Dave Malouf
2005

Software for requirements management

Hey there folks,

What are people using (especially for in-house types) for requirements
management throughout the entire product management lifecycle:
1. input channels and research capture
2. concept capture
3. requirements definition
4. design docs
5. technical docs
6. QC test scripts
7. launch, rollout, marketing plans

Something that deals w/ workflow and lifecycle management
Has strong permissioning
Well designed (something I would WANT to use)
Understands that software requires a designer (sheesh!)
works well on pc and mac

-- dave

Syndicate content Get the feed