Heres 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:
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...
----please consider whether it is necessary to print this email----
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
My company is currently looking into tools to manage use cases and
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
*Associated features: *Login screen, password security feedback, lost
password functionality, error feedback system.
*Associated users/actors: *Child, parent, administrator
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