Gathering Software Requirements Use Cases
- June 03, 2011
In part one of this two-part interview with EBG Consulting's Ellen Gottesdiener, we learn about techniques used to elicit requirements and hear about the differences between Agile and traditional requirements elicitation.
- March 22, 2011
Requirements management continues to be a challenge to software development organizations, but tool vendors are working to address those challenges. In this interview with Forrester analyst Mary Gerush, we hear about five important ALM trends in ...
- April 15, 2010
Eliciting software requirements is a human-intensive activity, and any process requiring user input is never a walk in the park. Learn techniques that can help project leaders make the right choices in eliciting and then analyzing requirements needs.
- November 16, 2009
Requirements elicitation is software development teams' toughest problem today, reveals a TechTarget survey. Most teams rely on use cases and requirements management tools to get requirements right. Agile and lean development practices are also ...
- November 01, 2007
It's tempting to consider use case diagrams as context diagrams because they do show context. But having one diagram for both will result in an unreadable cloud of bubbles.
- October 08, 2007
Milan Kratochvil, author of UML Xtra Light, explores the future of classical system use cases, Ivar Jacobson's business use cases and user queries.
- September 24, 2007
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 ...
- July 18, 2007
Ideally use cases capture the functional requirements of a system in terms of identifiable and testable goals. The trick is writing and documenting them so that they offer value not just for requirements gathering but also for software design and ...