The user adds a product to their shopping cart.A user goes to the website and browses through the product catalog.A use case for this project might be something like this: It’s typically written as a sequence of steps, each representing a different action the user takes.įor example, let’s say you’re designing a new e-commerce website. Like a user story, a use case describes how a user will interact with a system to achieve a goal but on a slightly more granular level. What is a use case?Įxplaining how a user will interact with a system is a must if you’re going to a) get buy-in from stakeholders and b) create something the user wants to use.
Let’s take a closer look at what a use case is and how it can help you. It’s typically used in software development as part of the functional requirements document/plan, but use case scenarios aren’t just for developers. And the best way to validate a project to stakeholders (and make sure your creation is a hit) is to show them why and how the intended audience will use it.Ī use case scenario describes how a user might interact with a system to achieve a goal. Whether working on an app or setting up a sandwich shop, your project needs a reason for existing.
