{"id":2510,"date":"2015-04-28T19:06:53","date_gmt":"2015-04-28T19:06:53","guid":{"rendered":"http:\/\/blog.soton.ac.uk\/smallworld\/?p=2510"},"modified":"2015-04-28T22:08:48","modified_gmt":"2015-04-28T22:08:48","slug":"the-differences-between-a-scenario-and-a-use-case","status":"publish","type":"post","link":"https:\/\/blog.soton.ac.uk\/smallworld\/2015\/04\/28\/the-differences-between-a-scenario-and-a-use-case\/","title":{"rendered":"The differences between a scenario and a use case"},"content":{"rendered":"<p>Use cases are a technique for capturing the functional requirements of system.<br \/>\nUse cases work by describing the typical interactions between the users of<br \/>\na system and the system itself, providing a narrative of how a system is used.<\/p>\n<p>Rather than describe use cases head-on, I find it easier to sneak up on them<br \/>\nfrom behind and start by describing scenarios. <strong>A scenario is a sequence<br \/>\nof steps describing an interaction between a system and a user.<\/strong> So if<br \/>\nwe have a Web-based on-line store, we might have a Buy and Product scenario that<br \/>\nwould say like this:<\/p>\n<p><em>The customer browses the catalog and adds desired items to the shopping basket.<\/em><br \/>\n<em> When the customer wishes to pay, the customer describes the shipping and credit<\/em><br \/>\n<em> card information and confirms the sale. The system checks the authorization on<\/em><br \/>\n<em> the credit card and confirms the sale both immediately and with a follow-up email.<\/em><\/p>\n<p>This scenario is one thing that can happen. However, the credit card authorization<br \/>\nmight fail, and this would be a separate scenario. In another case, you may have<br \/>\na regular customer for whom you don&#8217;t need capture the shipping and credit card<br \/>\ninformation, and this is a third scenario.<\/p>\n<p>All these scenario are different yet similar. The essence of their similarity is that<br \/>\nin all these three scenarios. the user has the same goal: to buy a product. The user<br \/>\ndoesn&#8217;t always succeed, but the goal remains. This user goal is the key to user cases:<br \/>\n<strong>A use case is a set of scenarios tied together by a common user goal <\/strong>(Fowler, 2004)<strong>.\u00a0<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2515\" src=\"http:\/\/blog.soton.ac.uk\/smallworld\/files\/2015\/04\/scenario-diagram.png\" alt=\"scenario diagram\" width=\"917\" height=\"433\" srcset=\"https:\/\/blog.soton.ac.uk\/smallworld\/files\/2015\/04\/scenario-diagram.png 917w, https:\/\/blog.soton.ac.uk\/smallworld\/files\/2015\/04\/scenario-diagram-300x142.png 300w, https:\/\/blog.soton.ac.uk\/smallworld\/files\/2015\/04\/scenario-diagram-500x236.png 500w\" sizes=\"auto, (max-width: 917px) 100vw, 917px\" \/><\/p>\n<p>http:\/\/www.inf.unibz.it\/~ryzhikov\/HCI\/hci_02.pdf<\/p>\n<p><strong>References:\u00a0<\/strong><\/p>\n<p>Fowler, M 2004, UML Distilled : A Brief Guide To The Standard Object Modeling Language \/ Martin Fowler ; [Forewords By Cris Kobryn &#8230; [Et Al.]], n.p.: Boston : Addison-Wesley, c2004., University of Southampton Library Catalogue, EBSCOhost, viewed 28 April 2015.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Use cases are a technique for capturing the functional requirements of system. Use cases work by describing the typical interactions between the users of a system and the system itself, providing a narrative of how a system is used. Rather &hellip; <a href=\"https:\/\/blog.soton.ac.uk\/smallworld\/2015\/04\/28\/the-differences-between-a-scenario-and-a-use-case\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":97423,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8883],"tags":[8898,975479],"class_list":["post-2510","post","type-post","status-publish","format-standard","hentry","category-related-academic-work","tag-scenario","tag-user-cases"],"_links":{"self":[{"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/posts\/2510","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/users\/97423"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/comments?post=2510"}],"version-history":[{"count":6,"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/posts\/2510\/revisions"}],"predecessor-version":[{"id":2530,"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/posts\/2510\/revisions\/2530"}],"wp:attachment":[{"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/media?parent=2510"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/categories?post=2510"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/smallworld\/wp-json\/wp\/v2\/tags?post=2510"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}