Requirements

Gathering and documenting software requirements is a discipline that has been approached in many different ways over the years. Detailed analysis and design documentation, feature lists, use cases, user stories, prototypes are all approaches I've seen and/or used.

I'm not sure that any of these is the "best" approach.

What I believe is more important than any requirements technique are 3 things:

• Requirements need to be simple, clear and concise
  
• It's important to get requirements from the right people
• Requirements will change