Use cases tool

Below, are examples of three use cases with increasing levels of complexity. For our purposes we have defined them as Simple, Middleweight and Heavyweight use case for doing the laundry.

In each of these types of uses cases you will see that:. Skip to main content. Improving the User Experience. Use Cases A use case is a written description of how users will perform tasks on your website. Benefits of Use Cases Use cases add value because they help explain how the system should behave and in the process, they also help brainstorm what could go wrong.

Welcome to the Reimagined HHS. Creating Cross-Channel Experiences. User-Centered Design Process Map. Creating a User-Centered Approach in Government. Related Resources Creating Wireframes. Defensive Design for the Web: How to improve error messages, help, forms, and other Related Categories Interaction Design. Format your use cases and connectors formatting tools: Shape and line format solid, gradient, transparency, etc , font style, rotatable shapes, shape alignment and distribution, embed image and URL, etc.

Try it yourself. You will see for yourself that it is everything we say it is, or perhaps more. We use cookies to offer you a better experience. By visiting our website, you agree to the use of cookies as described in our Cookie Policy. Explore Visual Designer. Flipbook Maker New. Chart Maker. Form Builder. Background Remover. Diagram Creator. Photo Book Maker New. Collage Maker. Spreadsheet Editor. Data Widgets. This is what allows us to get at the software requirements.

What is included in a use case? You can take notes if you want, but you can also download our template. There should also be a link below this video. You want to start with a name , and just like with a business process, you want that name to be verb-noun. Next is a brief description , and one of the things I really like to include in my brief description is a sentence that really gets clear about the scope.

The actors : who are the users, or the roles, or the types of actors that might use the system? Multiple people can fill that role with the system. Are you a purchaser?

Are you an administrator? Are you a reporter? Something like that. Preconditions : what must be true before the use case starts? This, again, is a very system-level. What can the system know to be true before the use case starts? Then, you get into the basic flow , and I like to think of the basic flow like ping pong. The user does one thing, the system does another thing.

Ping pong. User, user, user, user, user, user. It really dials you into, as a businessperson, what the system is doing to support you and what those requirements actually are of the system that you might not see otherwise. User, user, user, user. You want the requirements. Not how the system is doing all that.