How to Write a Use Case

A use case is a powerful business analysis technique that analyzes the functional requirements for a software application and get everyone on the same page about what the software needs to do to meet the business needs.

DOWNLOAD THE USE CASE TEMPLATE (it's free):

As a business user,  you’ll be able to write use cases even if you don’t understand or want to use the technical jargon. In fact, as you’ll learn in the video, they can help you ask smart questions about the tech even if you don’t really understand the tech and clearly communicate what you want the software system to do. This is what business analysts call the functional requirements.

And if you are more technically inclined, this technique helps you communicate with your business users about technology without using “tech speak” - i.e. getting to the "what" of the functional requirements and avoiding getting too detailed into the technical or system requirements.

Use cases are an incredibly powerful functional requirements analysis technique – and I hope you find this tutorial useful in applying use cases in your analytical work today.

DOWNLOAD THE USE CASE TEMPLATE (it's free):

WATCH THESE VIDEOS NEXT:

User Stories vs. Use Cases

How to Analyze a Business Process:

View the Full-Text Transcript Here:

00:00 How to Write a Use Case
00:41 Why Should You Write a Use Case
2:00 What is a Use Case?
3:24 What is in a Use Case?
9:05 What if I Don't Know Tech?

[OshadhiVindhyani]

Dear Laura, you have no idea how this video helping me. I was stuck at the design phase lost in all the requirements and all the tech details. Thank you so much for this valuable content.

[bambynaa]

You are so helpful Laura, thank you! The BRIDGING THE GAP videos are such a knowledgeable resource.

[Channelabc]

I have watched so many videos, and this is is the only one with such a great explanation! Thank you!!!! All the other videos get stuck in the description of what UC diagram is, but they don't show how to create it.

[abrahaminikori]

Always a valuable time spent watching BRIDGING THE GAP videos

[mikemott]

I was writing Use Cases before they were cool. Your presentation was a great explanation of the tool. We wrote them in workshops with the customer, technical lead, and facilitator. Our first step would be a brainstorming session to identify the Use Cases. They had to be named noun-verb as you said in the video. Once we had the list, we would go through the process of filling out the Use Case Form. When that task was complete, the technical team decomposed the system using Sequence Diagrams to lay out the top-level system design. The test team used them to begin writing their top-level test plans.
This material would be used to put together the project plan. They are indeed a very powerful tool.

[efarias]

Dear Laura - Timeless video, thank you. It helped me to setup a BAU service specifically to replace aged PCs connected to laboratory instruments at the University of Newcastle.

[nielsreyngoud]

Laura, thank you for this clear explanation! Working on user stories and use cases for a project right now and this is really helpful!

[michelereid]

Thank you so much Laura. Wow! What a difference an alternative perspective can make?!

[agustinlawtaro]

The best explanation of how to write a use case. Thanks!

[dickwooden]

Laura- these videos are for all types of businesses and professionals. They are easier to follow, practical in use, and increase engagement for improved productivity.

[salesforcereasun]

Again you put the ABCs in writing a use case. 😁 You make it seem so doable. I love you style of teaching. By describing the players as actors gives you allot of creative space.
Thanks again

[ibraheemahmad]

I am a newbie and the ping pong makes a lot of sense. You also made me get the Clare difference between use case and user story. Thank you so much. You are building the gap.

[casandra_]

Thank you Laura. You are so right. I finally found my role after listening to you. I love systems and I love Python programming. You are right about the non tech speak. As I am learning Python, we are always told to leave comments and write code that is readable and to give descriptive meaningful names. So, even in coding the human interaction and basic understanding is still true.

[duinneacha]

Liked the video and your clear explanation of this subject - thanks!

[essiemw]

Wow, l love this.... This is more clear

[ctjanney]

great, clear explanation. Thank you.

[planorarmadesign]

Very helpful explanation of use cases. It made sense, as I imagined the use case perspective is sitting above both the user and system to document the "ping pong" between them, whereas user stories are written as if I was sitting in the chair of the user to document interaction from his/her perspective primarily. In a way, the difference between describing via 3rd person omniscient vs. first person singular.

[weedosutra]

Thank you, Laura! You have explained it so well!

[anasdawood]

This is a very helpful video. Thank you for clarifying all these points in such a simple way.

[AlexanderPauls]

Laura, thank you very much! Such a great explanation