This weekend has been very interesting, and not at all because I was at a beach festival in four days, drinking tequila, stayed up to 6am every day and did a bunch of different activities. But because during this weekend I could not stop thinking about use cases.
By the way this week’s topic is use cases.
https://media.giphy.com/media/5xtDarqlsEW6F7F14Fq/giphy.gif
We already talk lite about use cases in my other post “chapter 2 head first object-oriented analysis and design”. But you can not get enough of use cases, right?
A Use cases is a way to get information and requirements on a system or a already working system that need changes. Every use case has either one or more different scenarios that describe how a system integrate with it surrounding to a achieve a certain goal. For example, a use case often has a person (also know as a role) that wants to archive something, and then the use case is a map of how that person getting there and all the different scenarios the person will encounter on the way.
”A complete path through a use case, from the first step to the last, is called a scenario. Most use cases have several different scenarios, but they always share the same user goal ”
A use case does not contain a technical description but more of a description for the end user.
There you have a quick summery of a use case. As I said before you can read my other post if you want to learn more
REFERENCES
https://searchsoftwarequality.techtarget.com/definition/use-case
Olles blog 
