Gathering Software Requirements Use Cases

Email Alerts

Register now to receive news, tips and more, delivered to your inbox.
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
  • Business analysis and requirements elicitation: Interview with Ellen Gottesdiener -- Part one

    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. 

  • Trends in ALM: Requirements management tools

    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 requ... 

  • Requirements practices evolving, but organizations still struggle

    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 helpi... 

  • From use case diagrams to context diagrams

    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. 

  • UML made Jacobson's use cases state of the art. What's next?

    Milan Kratochvil, author of UML Xtra Light, explores the future of classical system use cases, Ivar Jacobson's business use cases and user queries. 

  • 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 microscopic... 

  • How to document use cases

    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 tes... 

  • use case diagram

    A use case diagram is a graphic depiction of the interactions among the elements of a system. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. 

  • user acceptance testing (UAT)

    In software development, user acceptance testing (UAT) - also called beta testing, application testing, and end user testing - is a phase of software development in which the software is tested in the "real world" by the intended audience. 

  • use case

    A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. 

  • HCI (human-computer interaction)

    HCI (human-computer interaction) is the study of how people interact with computers and to what extent computers are or are not developed for successful interaction with human beings. 

About Gathering Software Requirements Use Cases

Use cases and misuse cases are modeling tools used to document software requirements. Use cases are structured in a way in which a user story or scenario is described as a user, defined by the role he plays, performs a scenario. The story would describe what should happen when the software product is used. A misuse case, in contrast, names something that should not happen, which may lead to additional requirements that can be expressed as use cases. Misuse cases help in identifying security risks to the system.