Software Requirements Gathering Techniques
- July 08, 2009
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
Consultant Robin F. Goldsmith describes the key phases in a successful software requirements process in this audiocast interview.
- January 05, 2009
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
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
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
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
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
The requirements gathering task remains complex and troubling, according to SearchSoftwareQuality.com'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
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
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
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
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
Bypassing requirements testing can lead to software that doesn't do what users expected, costly software changes and often project failure.
- September 27, 2007
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
Modeling should not be considered something that's done only after requirements have been gathered. Use them throughout the requirements process to elicit and clarify requirements.