use case

A use case (or set of use cases) has these characteristics:

• Organizes functional requirements
• Models the goals of system/actor (user) interactions
• Records paths (called scenarios) from trigger events to goals
• Describes one main flow of events (also called a basic course of action), and possibly other ones, called exceptional flows of events (also called alternate courses of action)
• Is multi-level, so that one use case can use the functionality of another one.

Use cases can be employed during several stages of software development, such as planning system requirements, validating design, testing software, and creating an outline for online help and user manuals.

Getting started with use case methodology

To explore how use case is used in the enterprise, here are some additional resources for learning about use case methodology:

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

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.

Five use case traps to avoid: Employing use cases during software requirements analysis helps you improve your chances of developing software that truly meets their needs. But there are traps you should avoid, says expert Karl E. Wiegers.

Learn more about Use cases and misuse cases

Do you have something to add to this definition? Let us know. Send your comments to techterms@whatis.com

More resources from around the web: - Alastair Cockburn offers a tutorial on use case. - The Use Case Zone examines the methodology in more detail.

FILE EXTENSION AND FILE FORMAT LIST File Extension and File Format List: A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #

RELATED CONTENT Requirements practices evolving, but organizations still struggle Requirements elicitation causes software development teams' some of their toughest problem today, according to a Tech Target survey. Defining report requirements with use cases This tip offers a new and interesting way to go about defining and reporting requirements for use cases. How requirements use cases facilitate the SDLC Learn software use case processes and techniques that result in better application requirements in this tip. Takeaways are use case diagrams and user...

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary build tool  (SearchSoftwareQuality.com) A build tool is a programming utility that automates a software build task, such as ensuring that the proper source code files are compiled and that... development environment  (SearchSoftwareQuality.com) In computer program and software product development, the development environment is the set of processes and programming tools used to create the...