Learning Guide

Software requirements gathering techniques

 


Requirements gathering is an essential part of software development. However, the process can be difficult. To help you, we've assembled a detailed guide of the best methods for facilitating the

    Requires Free Membership to View

requirements gathering process. Not merely a collection of links, our guide has detailed descriptions to help you maneuver.

We value your input. As always, if you know of an article, tip, tool or method that should be included, send me an e-mail with the information and I'll be happy to add it. – Jennette Mullaney, assistant editor.

 

TABLE OF CONTENTS
   Prototyping
   Storyboards
   Modeling
   State transition diagrams
   Use cases
   Tools
   Other Useful Resources

 

  Prototyping  

[Return to Table of Contents]
Prototypes range from the simple to the elaborate. But whether it's a paper sketch or an interactive digital design, a prototype should aid stakeholders and developers in anticipating requirements for a product.

 

  Storyboards  

[Return to Table of Contents]
Storyboards help developers visualize the sequence and interconnectedness of their work. They allow for a "big picture" approach that may be very useful in requirements gathering.

 

  Modeling  

[Return to Table of Contents]
A model can be made according to Unified Modeling Language (UML) or according to domain-specific modeling. Or, models can consist of stick figures on a whiteboard. All of these methods have their advantages and disadvantages. Use these links to figure out what method is right for you.

 

  State transition diagrams  

[Return to Table of Contents]
State transition diagrams allow developers and users to see how a program might behave. This anticipation of events is useful when discussing requirements.

  • State-transition diagrams: This article explains what state transitions are and why they are important. Also included are a series of questions for testing state-transition diagrams.
  • Automating state transitions: The Microsoft Developer's Network state transitions within Visual Studio. Code examples aid the reader.
  • Visual Requirements: There is a section devoted to state transition diagrams in this article on diagrams in software development. The author provides a clear perspective on state diagrams and the necessary part they play among the other diagrams. (PDF)
  • State transition diagrams: The language of this white paper is technical, so beginners may be put off. However, the paper achieves what it sets out to do, and that is to define the syntax and semantics of state transition diagrams. (PDF)

 

  Use cases  

[Return to Table of Contents]

Use cases are created to capture functional requirements in the software development lifecycle.

 

  Tools  

[Return to Table of Contents]
Here are some tools that may prove useful in the requirements gathering process.

 

  Other useful resources  

[Return to Table of Contents]

 

Expert advice on software requirements

Do you have a question about software requirements gathering? Our requirements expert Betty Luedke may have the answer. Read advice she has given or submit your own questions.



 

Send in your suggestions
Are there other topics you'd like to see learning guides on? Send assistant editor Jennette Mullaney an e-mail at jmullaney@techtarget.com and let her know what they are.

This was first published in February 2007

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: