{"id":3878,"date":"2021-01-15T12:52:17","date_gmt":"2021-01-15T11:52:17","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=3878"},"modified":"2025-02-04T08:21:10","modified_gmt":"2025-02-04T07:21:10","slug":"usecase","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/usecase\/","title":{"rendered":"Use Case"},"content":{"rendered":"<p><a href=\"https:\/\/en.wikipedia.org\/wiki\/Use_case\">Use Cases<\/a> are used to describe scenarios in which users and other stakeholders interact with the system. <a href=\"https:\/\/en.wikipedia.org\/wiki\/Use_case\">Use Cases<\/a> are a good method for describing functional requirements and dynamic behavior of the system. Many non-functional requirements can also be discovered during the analysis.<\/p>\n<p>In order not to forget any essential <a href=\"https:\/\/en.wikipedia.org\/wiki\/Use_case\">Use Cases<\/a> during the requirements analysis, it has proven useful to analyze the Product life cycle and the single-unit life cycle and to define the stakeholder needs as well as central use cases.<\/p>\n<p>Translated with www.DeepL.com\/Translator (free version)<\/p>\n<h3>Product life cycle<\/h3>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone wp-image-693 size-large\" src=\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/product_life_cycle-1024x292.png\" alt=\"\" width=\"648\" height=\"185\" srcset=\"https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/product_life_cycle-1024x292.png 1024w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/product_life_cycle-300x86.png 300w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/product_life_cycle-768x219.png 768w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/product_life_cycle.png 1421w\" sizes=\"(max-width: 648px) 100vw, 648px\" \/><\/p>\n<h3>Single-unit life cycle<\/h3>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone wp-image-694 size-large\" src=\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/unit_life_cycle-1024x311.png\" alt=\"\" width=\"648\" height=\"197\" srcset=\"https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/unit_life_cycle-1024x311.png 1024w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/unit_life_cycle-300x91.png 300w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/unit_life_cycle-768x233.png 768w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/unit_life_cycle.png 1498w\" sizes=\"(max-width: 648px) 100vw, 648px\" \/><\/p>\n<h3>Description of a Use Case<\/h3>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-3927\" src=\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2021\/01\/Use_Case_Template.png\" alt=\"\" width=\"526\" height=\"777\" srcset=\"https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2021\/01\/Use_Case_Template.png 526w, https:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2021\/01\/Use_Case_Template-203x300.png 203w\" sizes=\"(max-width: 526px) 100vw, 526px\" \/><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2021\/01\/Business-Use-Case-Description.pdf\">Download Template for Business Use Case Description<\/a><\/p>\n<h2>Use-Case-driven Design<\/h2>\n<ul>\n<li>Scenario-based, natural language, non-technical<\/li>\n<li>Use Cases can be used for &#8230;\n<ul>\n<li>Requirements documentation<\/li>\n<li>Test scenario specifications<\/li>\n<li>User manuals<\/li>\n<\/ul>\n<\/li>\n<li>Use Case scanarions lead to better Quality Attributes (QA), aka non-functional requirements (NFRs)<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"Use Cases are used to describe scenarios in which users and other stakeholders interact with the system. Use Cases are a good method for describing functional requirements and dynamic behavior of the system. Many non-functional requirements can also be discovered during the analysis. In order not to forget any essential Use Cases during the requirements&hellip;","protected":false},"author":3,"featured_media":4156,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[4],"tags":[],"translation":{"provider":"WPGlobus","version":"2.10.10","language":"en","enabled_languages":["de","en"],"languages":{"de":{"title":true,"content":true,"excerpt":false},"en":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/3878"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=3878"}],"version-history":[{"count":11,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/3878\/revisions"}],"predecessor-version":[{"id":4896,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/3878\/revisions\/4896"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/4156"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=3878"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=3878"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=3878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}