Home > Software requirements gathering techniques
Learning Guide:
EMAIL THIS

Software requirements gathering techniques

15 Feb 2007 | SearchSoftwareQuality.com

Software quality news and advice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


[IMAGE] 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 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][TABLE]

[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. [TABLE]

[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. [TABLE]

[Return to Table of Conten


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Software requirements techniques (Prototyping, Storyboards, Modeling, State transitions)
Quality assurance (QA) and testing's role in requirements
Agile software development tutorial: Agile requirements gathering
Reporter's Notebook: Jack Vaughan on agile methodology
Pros and cons of requirements-based software testing
How to avoid requirements creep
Making requirements walkthroughs more effective (and fun)
Software development lifecycle (SDLC) trends 2009: Requirements, agile
Using proactive test design methods to catch requirements issues early
Is a requirements freeze in a software project a bad idea?
Requirements elicitation: Workshops vs. apprentice-style analysis

Software requirements tools
Blueprint rolls out Requirements Center 2010
Borland releases requirements definition simulation tool for teams
New requirements definition tools focus on chronic flaws
Agile software development tutorial: Agile requirements gathering
Simulation software a cure for hospital's requirements validation ills
Requirements tools that empower business analysts
How to choose the right requirements tool
Requirements gathering resources, practices lacking at Fortune 500 companies
Workbench helps get your software requirements house in order
Tools of the Agile trade

Use cases and misuse cases
Requirements use cases tutorial: Advanced formats, test case comparisons
Use cases for software requirements tutorial: Strengths, flaws, formats
Writing a software requirements specification (SRS) for a portal app
Agile software development tutorial: Agile requirements gathering
Pros and cons of requirements-based software testing
How to avoid requirements creep
Template for requirements use cases
Top 10 software requirements tips
Use cases and SRS for requirements gathering
Use cases: Who writes them, what data do you include?

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
requirements analysis  (SearchSoftwareQuality.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


ts]
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. [TABLE]

[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. [TABLE]

[Return to Table of Contents]

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

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

[Return to Table of Contents]

[TABLE]

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.






Software Quality Testing - Research and White Papers
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2006 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts