Software Requirements Gathering Techniques

  • July 08, 2009 08 Jul'09

    Software requirements: Moving beyond use cases

    In this podcast, software development and requirements definition expert Ellen Gottesdiener describes when use cases are a good fit for software projects, when they are not, and what alternative approaches should be used.

  • July 08, 2009 08 Jul'09

    Mastering key requirements phases

    Consultant Robin F. Goldsmith describes the key phases in a successful software requirements process in this audiocast interview.

  • January 05, 2009 05 Jan'09

    Software development lifecycle (SDLC) trends 2009: Requirements, agile

    Read expert predictions on what's in store this year for software development lifecycle practices and who will best weather the economic storm.

  • November 12, 2008 12 Nov'08

    Business analysis skills you need for successful software requirements

    Business analysts must have certain skills and must understand the many software requirements techniques out there, says Barbara Carkenord, author of "Seven Steps to Mastering Business Analysis."

  • October 22, 2008 22 Oct'08

    Agile aims to bridge software requirements communications gap

    Agile software development bridges the software requirements communications gap by embracing flexibility and face-to-face communication rather than depending on documents to communicate, agile practitioners say.

  • October 20, 2008 20 Oct'08

    Simulation software a cure for hospital's requirements validation ills

    The M.D. Anderson Cancer Center relies on iRise's simulation software to validate software requirements with its stakeholders. The visual models eliminate misunderstandings between users and the development team.

  • August 20, 2008 20 Aug'08

    Requirements gathering resources, practices lacking at Fortune 500 companies

    Requirements gathering resources and best practices were found lacking at Fortune 500 companies, a recent study from Voke Inc. found. But if business analysts are equipped with the right tools and enough resources, businesses stand to benefit ...

  • June 27, 2008 27 Jun'08

    Teams turn to use cases, user stories to ease requirements gathering challenges

    The requirements gathering task remains complex and troubling, according to's 2008 Agile Trends survey. User stories are the technique of choice for Agile practitioners tackling this task, but use cases remain the most ...

  • May 12, 2008 12 May'08

    Book Review: Just Enough Requirements Management

    Alan M. Davis's Just Enough Requirements Management strikes at the heart of the problem of eliciting software requirements and helps to bridge the gap between development and business users' objectives.

  • April 11, 2008 11 Apr'08

    Software requirements sign-off essential for solid QA

    Not properly signing off on a software project's requirements limits the quality assurance (QA) team's ability to ensure that the software does as it's intended.

  • February 21, 2008 21 Feb'08

    Poor business requirements process leads to high project costs, study finds

    A recent IAG Consulting study finds that companies that have poor business requirements processes can expect to spend 49% more money and 39% more time on a project.

  • February 19, 2008 19 Feb'08

    Fun with UML

    Think UML can't be funny? Think again. Check out the recent winners of the International Software & Productivity Engineering Institute's UML joke contest.

  • October 08, 2007 08 Oct'07

    The importance of testing software requirements

    Bypassing requirements testing can lead to software that doesn't do what users expected, costly software changes and often project failure.

  • September 27, 2007 27 Sep'07

    Specifying IT: Key UML techniques in requirements

    The Unified Modeling Language (UML) can help communicate software requirements. Learn what its benefits are, how it complements natural languages and how the various UML diagrams work.

  • September 24, 2007 24 Sep'07

    The pros and cons of use case diagrams

    Putting too much into a use case diagram can often render the otherwise useful technique of use cases almost useless. Kevlin Henney recommends a more balanced and restrained approach in order to not lose readers in a myriad of bubbles and ...