{"id":3548,"date":"2022-02-10T13:11:03","date_gmt":"2022-02-10T05:11:03","guid":{"rendered":"https:\/\/blog.visual-paradigm.com\/pl\/?p=3548"},"modified":"2022-04-22T09:40:21","modified_gmt":"2022-04-22T01:40:21","slug":"use-case-diagram-a-notation-guide","status":"publish","type":"post","link":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/","title":{"rendered":"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie"},"content":{"rendered":"<p><span>Diagram przypadk\u00f3w u\u017cycia to diagram UML (Unified Modeling Language) s\u0142u\u017c\u0105cy do pozyskiwania wymaga\u0144.\u00a0Diagramy przypadk\u00f3w u\u017cycia zapewniaj\u0105 graficzny przegl\u0105d cel\u00f3w (modelowanych przez przypadki u\u017cycia), kt\u00f3re u\u017cytkownicy (reprezentowani przez aktor\u00f3w) chc\u0105 osi\u0105gn\u0105\u0107 za pomoc\u0105 systemu.\u00a0Przypadki u\u017cycia na diagramie przypadk\u00f3w u\u017cycia mo\u017cna zorganizowa\u0107 i uporz\u0105dkowa\u0107 zgodnie z ich istotno\u015bci\u0105, poziomem abstrakcji i wp\u0142ywem na u\u017cytkownika.\u00a0Mo\u017cna je \u0142\u0105czy\u0107, aby pokaza\u0107 ich zale\u017cno\u015bci, uwzgl\u0119dni\u0107, rozszerzy\u0107, relacje pokoleniowe.<\/span><\/p>\n<p><span>Przypadek u\u017cycia opisuje konkretny cel biznesowy, kt\u00f3ry ma spe\u0142nia\u0107 budowany system.\u00a0Graficznie jest to owal o nazwie, kt\u00f3ra wygl\u0105da na prost\u0105, ale jest najcz\u0119\u015bciej u\u017cywanym narz\u0119dziem do zarz\u0105dzania celami biznesowymi lub celami projektu.<\/span><\/p>\n<h3><span id=\"Use_Case_Diagram_Notation_Summary\"><span>Podsumowanie notacji diagramu przypadk\u00f3w u\u017cycia<\/span><\/span><\/h3>\n<table>\n<tbody>\n<tr>\n<td colspan=\"2\"><strong><span>Opis notacji<\/span><\/strong><\/td>\n<td><strong><span>Reprezentacja wizualna<\/span><\/strong><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><strong><span>Aktor<\/span><\/strong><\/p>\n<ul>\n<li><span>Kto\u015b wchodzi w interakcj\u0119 z przypadkiem u\u017cycia (funkcj\u0105 systemu).<\/span><\/li>\n<li><span>Nazwany rzeczownikiem.<\/span><\/li>\n<li><span>Aktor odgrywa rol\u0119 w biznesie<\/span><\/li>\n<li><span>Podobny do koncepcji u\u017cytkownika, ale u\u017cytkownik mo\u017ce odgrywa\u0107 r\u00f3\u017cne role<\/span><\/li>\n<li><span>Na przyk\u0142ad:<\/span>\n<ul>\n<li><span>Prof.\u00a0mo\u017ce by\u0107 instruktorem, a tak\u017ce badaczem<\/span><\/li>\n<li><span>odgrywa 2 role w dw\u00f3ch systemach<\/span><\/li>\n<\/ul>\n<\/li>\n<li><span>Aktor wyzwala przypadki u\u017cycia.<\/span><\/li>\n<li><span>Aktor ponosi odpowiedzialno\u015b\u0107 wobec systemu (wej\u015bcia), a aktor ma oczekiwania wobec systemu (wyj\u015bcia).<\/span><\/li>\n<\/ul>\n<\/td>\n<td><span>\u200b<\/span><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-4373\" src=\"https:\/\/blog.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/15\/2022\/02\/use-case-diagram-notation-actor.png\" alt=\"Notacja diagramu przypadk\u00f3w u\u017cycia: aktor\" width=\"31\" height=\"73\" \/><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><strong><span>Przypadek u\u017cycia<\/span><\/strong><\/p>\n<ul>\n<li><span>Funkcja systemu (proces \u2013 zautomatyzowana lub r\u0119czna)<\/span><\/li>\n<li><span>Nazwany przez czasownik + rzeczownik (lub fraz\u0119 rzeczownika).<\/span><\/li>\n<li><span>czyli zr\u00f3b co\u015b<\/span><\/li>\n<li><span>Ka\u017cdy aktor musi by\u0107 po\u0142\u0105czony z przypadkiem u\u017cycia, podczas gdy niekt\u00f3re przypadki u\u017cycia mog\u0105 nie by\u0107 po\u0142\u0105czone z aktorami.<\/span><\/li>\n<\/ul>\n<\/td>\n<td><span>\u200b<\/span><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-4379\" src=\"https:\/\/blog.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/15\/2022\/02\/use-case-diagram-notation-use-case.png\" alt=\"Notacja diagramu przypadk\u00f3w u\u017cycia: przypadek u\u017cycia\" width=\"81\" height=\"41\" \/><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><strong><span>Link do stowarzyszenia<\/span><\/strong><\/p>\n<ul>\n<li><span>Uczestnictwo aktora w przypadku u\u017cycia jest pokazane przez po\u0142\u0105czenie aktora z przypadkiem u\u017cycia za pomoc\u0105 sta\u0142ego \u0142\u0105cza.<\/span><\/li>\n<li><span>Aktorzy mog\u0105 by\u0107 po\u0142\u0105czeni z przypadkami u\u017cycia za pomoc\u0105 skojarze\u0144, co oznacza, \u017ce \u200b\u200baktor i przypadek u\u017cycia komunikuj\u0105 si\u0119 ze sob\u0105 za pomoc\u0105 komunikat\u00f3w.<\/span><\/li>\n<\/ul>\n<\/td>\n<td><span>\u200b<\/span><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-4374\" src=\"https:\/\/blog.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/15\/2022\/02\/use-case-diagram-notation-association-link.png\" alt=\"Notacja diagramu przypadk\u00f3w u\u017cycia: Powi\u0105zanie\" width=\"145\" height=\"1\" \/><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><strong><span>Granica systemu<\/span><\/strong><\/p>\n<ul>\n<li><span>Granica systemu to potencjalnie ca\u0142y system okre\u015blony w dokumencie wymaga\u0144.<\/span><\/li>\n<li><span>W przypadku du\u017cych i z\u0142o\u017conych system\u00f3w ka\u017cdy modu\u0142 mo\u017ce stanowi\u0107 granic\u0119 systemu.<\/span><\/li>\n<li><span>Na przyk\u0142ad w przypadku systemu ERP dla organizacji ka\u017cdy z modu\u0142\u00f3w takich jak kadry, p\u0142ace, ksi\u0119gowo\u015b\u0107 itp.<\/span><\/li>\n<li><span>mo\u017ce tworzy\u0107 granic\u0119 systemu dla przypadk\u00f3w u\u017cycia specyficznych dla ka\u017cdej z tych funkcji biznesowych.<\/span><\/li>\n<li><span>Ca\u0142y system mo\u017ce obejmowa\u0107 wszystkie te modu\u0142y, przedstawiaj\u0105c og\u00f3ln\u0105 granic\u0119 systemu<\/span><\/li>\n<\/ul>\n<\/td>\n<td><span>\u200b<\/span><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-4378\" src=\"https:\/\/blog.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/15\/2022\/02\/use-case-diagram-notation-system.png\" alt=\"Notacja diagramu przypadk\u00f3w u\u017cycia: System\" width=\"200\" height=\"280\" \/><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><strong><span>Rozszerza<\/span><\/strong><\/p>\n<ul>\n<li><span>Wskazuje, \u017ce\u00a0 przypadek u\u017cycia\u00a0<\/span><strong><span>\u201eNieprawid\u0142owe has\u0142o\u201d<\/span><\/strong><span>\u00a0\u00a0mo\u017ce obejmowa\u0107 (z zastrze\u017ceniem okre\u015blenia w rozszerzeniu) zachowanie okre\u015blone przez podstawowy przypadek u\u017cycia\u00a0\u00a0<\/span><strong><span>\u201eKonto logowania\u201d<\/span><\/strong><span>\u00a0.<\/span><\/li>\n<li><span>Przedstawia strza\u0142k\u0105 skierowan\u0105 z lini\u0105 przerywan\u0105.\u00a0Ko\u0144c\u00f3wka grotu strza\u0142ki wskazuje podstawowy przypadek u\u017cycia, a podrz\u0119dny przypadek u\u017cycia jest po\u0142\u0105czony u podstawy strza\u0142ki.<\/span><\/li>\n<li><span>Stereotyp \u201e&lt;&lt;rozszerza&gt;&gt;\u201d identyfikuje si\u0119 jako zwi\u0105zek rozszerzony<\/span><\/li>\n<\/ul>\n<\/td>\n<td><span>\u200b<\/span><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-4375\" src=\"https:\/\/blog.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/15\/2022\/02\/use-case-diagram-notation-extend-300x43.png\" alt=\"Notacja diagramu przypadk\u00f3w u\u017cycia: Rozszerz\" width=\"300\" height=\"43\" \/><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><strong><span>W\u0142\u0105cza\u0107<\/span><\/strong><\/p>\n<ul>\n<li><span>Gdy przypadek u\u017cycia jest przedstawiony jako korzystaj\u0105cy z funkcjonalno\u015bci innego przypadku u\u017cycia, relacja mi\u0119dzy przypadkami u\u017cycia jest nazywana jako relacja include lub uses.<\/span><\/li>\n<li><span>Przypadek u\u017cycia obejmuje funkcjonalno\u015b\u0107 opisan\u0105 w innym przypadku u\u017cycia jako cz\u0119\u015b\u0107 jego przep\u0142ywu proces\u00f3w biznesowych.<\/span><\/li>\n<li><span>Relacja u\u017cywa z podstawowego przypadku u\u017cycia do podrz\u0119dnego przypadku u\u017cycia wskazuje, \u017ce wyst\u0105pienie podstawowego przypadku u\u017cycia b\u0119dzie zawiera\u0107 zachowanie okre\u015blone w podrz\u0119dnym przypadku u\u017cycia.<\/span><\/li>\n<li><span>Relacja zawierania jest przedstawiona za pomoc\u0105 skierowanej strza\u0142ki z lini\u0105 przerywan\u0105.\u00a0Ko\u0144c\u00f3wka grotu strza\u0142ki wskazuje podrz\u0119dny przypadek u\u017cycia i nadrz\u0119dny przypadek u\u017cycia po\u0142\u0105czony u podstawy strza\u0142ki.<\/span><\/li>\n<li><span>Stereotyp \u201e&lt;&lt;include&gt;&gt;\u201d identyfikuje relacj\u0119 jako relacj\u0119 obejmuj\u0105c\u0105.<\/span><\/li>\n<\/ul>\n<\/td>\n<td><span>\u200b<\/span><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-4377\" src=\"https:\/\/blog.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/15\/2022\/02\/use-case-diagram-notation-include-300x37.png\" alt=\"Notacja diagramu przypadk\u00f3w u\u017cycia: uwzgl\u0119dnij\" width=\"300\" height=\"37\" \/><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><strong><span>Uog\u00f3lnienie<\/span><\/strong><\/p>\n<ul>\n<li><span>Relacja uog\u00f3lnienia to relacja rodzic-dziecko mi\u0119dzy przypadkami u\u017cycia.<\/span><\/li>\n<li><span>Potomny przypadek u\u017cycia jest rozszerzeniem nadrz\u0119dnego przypadku u\u017cycia.<\/span><\/li>\n<li><span>Generalizacja jest pokazana jako skierowana strza\u0142ka z tr\u00f3jk\u0105tnym grotem strza\u0142ki.<\/span><\/li>\n<li><span>Przypadek u\u017cycia dziecka jest po\u0142\u0105czony u podstawy strza\u0142ki.\u00a0Ko\u0144c\u00f3wka strza\u0142ki jest po\u0142\u0105czona z nadrz\u0119dnym przypadkiem u\u017cycia.<\/span><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span id=\"Use_Case_Diagram_Vehicle_Sales_Systems\"><span>Diagram przypadk\u00f3w u\u017cycia \u2013 systemy sprzeda\u017cy pojazd\u00f3w<\/span><\/span><\/h2>\n<p><span>Poni\u017cszy rysunek przedstawia przyk\u0142adowy diagram przypadk\u00f3w u\u017cycia dla systemu pojazdu.\u00a0Jak wida\u0107, nawet system tak du\u017cy jak system sprzeda\u017cy pojazd\u00f3w zawiera nie wi\u0119cej ni\u017c 10 przypadk\u00f3w u\u017cycia!\u00a0Na tym polega pi\u0119kno modelowania przypadk\u00f3w u\u017cycia.<\/span><\/p>\n<p><span>Model przypadk\u00f3w u\u017cycia pokazuje r\u00f3wnie\u017c u\u017cycie extend i include.\u00a0Poza tym istniej\u0105 powi\u0105zania, kt\u00f3re \u0142\u0105cz\u0105 aktor\u00f3w i przypadki u\u017cycia.<\/span><\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blog.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/15\/2022\/02\/13-use-case-diagram-example-vehicle-sales-systems.png\" alt=\"Przyk\u0142ad diagramu przypadk\u00f3w u\u017cycia \u2014 systemy sprzeda\u017cy pojazd\u00f3w\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A use case diagram is a Unified Modeling Language (UML) diagram for requirements elicitation. Use case diagrams provide a graphical overview of the goals (modeled by use cases) that users (represented by actors) want to achieve by using the system. Use cases in a use case diagram can be organized and arranged according to their relevance, level of abstraction, and impact on the user. They can be linked to show their dependencies, include, extend, generation relationships.<\/p>\n","protected":false},"author":1,"featured_media":3559,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[36],"tags":[],"class_list":["post-3548","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uml","loop-entry","clr"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.3 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie - Visual Paradigm Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie - Visual Paradigm Blog\" \/>\n<meta property=\"og:description\" content=\"A use case diagram is a Unified Modeling Language (UML) diagram for requirements elicitation. Use case diagrams provide a graphical overview of the goals (modeled by use cases) that users (represented by actors) want to achieve by using the system. Use cases in a use case diagram can be organized and arranged according to their relevance, level of abstraction, and impact on the user. They can be linked to show their dependencies, include, extend, generation relationships.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-02-10T05:11:03+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-04-22T01:40:21+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png\" \/>\n<meta name=\"author\" content=\"Admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png\" \/>\n<meta name=\"twitter:label1\" content=\"Napisane przez\" \/>\n\t<meta name=\"twitter:data1\" content=\"Admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/\",\"url\":\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/\",\"name\":\"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie - Visual Paradigm Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png\",\"datePublished\":\"2022-02-10T05:11:03+00:00\",\"dateModified\":\"2022-04-22T01:40:21+00:00\",\"author\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/#\/schema\/person\/a649c442f11a53040710ddec750926c6\"},\"breadcrumb\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#primaryimage\",\"url\":\"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png\",\"contentUrl\":\"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png\",\"width\":\"913\",\"height\":\"417\",\"caption\":\"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/blog.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/#\/schema\/person\/a649c442f11a53040710ddec750926c6\",\"name\":\"Admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/6b756c36f5e9132f6067fb4d22bef2e3?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/6b756c36f5e9132f6067fb4d22bef2e3?s=96&d=mm&r=g\",\"caption\":\"Admin\"},\"url\":\"https:\/\/blog.visual-paradigm.com\/pl\/author\/vpadminuser\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie - Visual Paradigm Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/","og_locale":"pl_PL","og_type":"article","og_title":"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie - Visual Paradigm Blog","og_description":"A use case diagram is a Unified Modeling Language (UML) diagram for requirements elicitation. Use case diagrams provide a graphical overview of the goals (modeled by use cases) that users (represented by actors) want to achieve by using the system. Use cases in a use case diagram can be organized and arranged according to their relevance, level of abstraction, and impact on the user. They can be linked to show their dependencies, include, extend, generation relationships.","og_url":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/","og_site_name":"Visual Paradigm Blog","article_published_time":"2022-02-10T05:11:03+00:00","article_modified_time":"2022-04-22T01:40:21+00:00","og_image":[{"url":"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png","type":"","width":"","height":""}],"author":"Admin","twitter_card":"summary_large_image","twitter_image":"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png","twitter_misc":{"Napisane przez":"Admin","Szacowany czas czytania":"5 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/","url":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/","name":"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie - Visual Paradigm Blog","isPartOf":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#primaryimage"},"image":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#primaryimage"},"thumbnailUrl":"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png","datePublished":"2022-02-10T05:11:03+00:00","dateModified":"2022-04-22T01:40:21+00:00","author":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/#\/schema\/person\/a649c442f11a53040710ddec750926c6"},"breadcrumb":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/"]}]},{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#primaryimage","url":"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png","contentUrl":"https:\/\/cdn-images.visual-paradigm.com\/guide\/uml\/what-is-use-case-diagram\/13-use-case-diagram-example-vehicle-sales-systems.png","width":"913","height":"417","caption":"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie"},{"@type":"BreadcrumbList","@id":"https:\/\/blog.visual-paradigm.com\/pl\/use-case-diagram-a-notation-guide\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Diagram Przypadk\u00f3w U\u017cycia \u2014 Przewodnik Po Zapisie"}]},{"@type":"WebSite","@id":"https:\/\/blog.visual-paradigm.com\/pl\/#website","url":"https:\/\/blog.visual-paradigm.com\/pl\/","name":"Visual Paradigm Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Person","@id":"https:\/\/blog.visual-paradigm.com\/pl\/#\/schema\/person\/a649c442f11a53040710ddec750926c6","name":"Admin","image":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/blog.visual-paradigm.com\/pl\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/6b756c36f5e9132f6067fb4d22bef2e3?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6b756c36f5e9132f6067fb4d22bef2e3?s=96&d=mm&r=g","caption":"Admin"},"url":"https:\/\/blog.visual-paradigm.com\/pl\/author\/vpadminuser\/"}]}},"modified_by":"vpmiku","_links":{"self":[{"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/posts\/3548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/comments?post=3548"}],"version-history":[{"count":4,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/posts\/3548\/revisions"}],"predecessor-version":[{"id":8245,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/posts\/3548\/revisions\/8245"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media\/3559"}],"wp:attachment":[{"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=3548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/categories?post=3548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/tags?post=3548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}