What Is A Use Case

COURSE OVERVIEW

Business Use Cases Help You Manage Complexity. Use Case Models are well suited to build a product backlog. They are the ideal tool to identify, clarify, and organize functional software requirements for a digital solution.

Use Cases define the interactions between people and technology. As a business user of IT solutions, a Use Case enables you to talk to technologists about your IT business needs in a manner they can understand. As a technical professional, a Use Case enables you to talk about technology to the business community without using technical jargon.

Write Use Cases for Lean and Agile Environments

Lean Use Cases are becoming the de facto standard for defining and communicating functional requirements in Lean and Agile environments. Applying the Lean philosophy of waste reduction to the Use Case concept creates a powerful tool for communication to and within a Lean or Agile Software Development team.

User Stories and other forms of textual requirements often lack context making room for ambiguity. Use Case Models, however, provide this context and are easily understandable by all stakeholders, including customers, users and managers, not just developers and testers.

Writing a Lean Use Case is a skill that anyone in an organization can easily acquire. Learning how to write and manage Lean Use Cases at varying levels of detail is a major step in getting your IT applications to do what you want them to do. Knowing why you need a Lean Use Case, when to create one (especially in a lean environment), and where to put what information is critical to creating high-quality functional requirements.

You Will Learn How to Make Use Cases Work in a Lean / Agile Setting

This exercise and example-rich business analysis training course explains the who, what, when, where, how and why of Lean Use Case models. Learn how to make Use Cases fit in the overall process of Lean and Agile software development by starting small with just enough detail at every point in the Agile development process.

To easily discover Use Cases, we include a section on Event-Response Analysis, Vision Statement Analysis, and Example- or Scenario-based Use Case Identification.

After finishing this course, you will be able to write high-quality Use Cases defining actors, pre-conditions, post-conditions, main paths, alternate paths, and exception paths.



DISCLAIMER: We designed this course specifically for people responsible for writing non-technical (Business-oriented) Use Cases from the User perspective. The course does not address the creation or use of System-level Use Cases. System Use Cases are at a much lower level of detail and usually a tool for technical professionals (developers, software engineers, testers, etc.) to help them create the design for a new technology solution. Developers who want to understand Use Cases that are codable will not find anything at that level of detail in this course. You have been warned. Thank you for taking this into consideration before buying this course.

#usecase #businessanalyst #businessanalysis #requirements #softwaredeveloper #softwaredevelopment #agile #sdm

[allanrabindran]

Thank you so much sir. I appreciate your work, time and effort to produce such an impeccable audio visual. Great work

[Jinkellytv]

This is great. So simply and thoroughly explained. Very helpful!

[nibhaswarup]

That was really helpful, also crisp and clear ! Thank you :)

[shinimannan]

Thanks a lot for explaining the concept using a simple and easy to follow contextual example.

[pranishshrestha]

Thanks for the video. I had been actually making usecases in my requirements list and I was wondering how to draw one.

[guilhermerodrigues]

Thank you very much! It was a very concise presentation. You summarised it very well!

[kok]

you are just very good. i got it for the very 1st time. teaching method is the best

[MohammadAliAr-Ramini]

Thank you so much for this video, it was so useful

[sumitbhujel]

This is so so so amazing. Thanks a lot

[mobindaraie]

Couldn't be better. Fantastic overview.

[PiumalMahawasala]

thank you ! Was helpful to understand clearly! :)

[waqasgondal]

The video is very useful for,
Rating: 10/10

you can have a look at it:

1. i push the ON button
2. the phone display the Android symbol
3. the phone display the lock screen
4. i enter my security key
5. the phone display the missed call's in motification bar
6. i press the notification
7. the phone display my Buddy name (Which want's to reach me)
8. i press the call button to make contact

Thanks!

[pragyasharma]

very effective video in short timeframe..

[yourworld]

Thanks for this video, very helpful and informative and cleared my doubts

[haymiworku]

tnx it is good example for me also intersting

[nezarfadle]

Brilliant explanation .. Thumbs up ^_^

Thank you for the video, it was clean and precise

[srinivassiddarth]

Thanks. You made it look simple and easy.

[manishagrawal]

Immensely easy to understand. thank you very much.

I may be little late to the party to ask a query, but anyways, I'll ask, let's see if I get lucky to see a reply.

I want to know how to draw a cross-functional diagram for a new mobile app which involves more than one actor and have different roles to play, an example would be an app for food ordering from nearby restaurants.

The actors - the app owner, restaurant owners, restaurant staff, delivery boy and general user

I am stuck in the very first step as what level of detail we can show in the chart. Next, when I started to build the chart I was trying to put the first step of User registering from the app. Here, all the actors require to register, so how do I show his? Do I make a separate box for register for each actor or one box. If I draw only one box, then in which swim lane that box will be.

Can you can help me to get started here.

[sk]

i thought use case defines interaction between actor and the system? not between 2 actors. can someone please clarify?