{"id":3481,"date":"2022-02-09T17:13:56","date_gmt":"2022-02-09T09:13:56","guid":{"rendered":"https:\/\/blog.visual-paradigm.com\/pl\/?p=3481"},"modified":"2022-11-25T17:29:16","modified_gmt":"2022-11-25T09:29:16","slug":"include-and-extend-use-cases","status":"publish","type":"post","link":"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/","title":{"rendered":"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d"},"content":{"rendered":"

Przypadek\u00a0<\/span>u\u017cycia<\/span><\/a>\u00a0opisuje, w jaki spos\u00f3b u\u017cytkownik u\u017cywa systemu do osi\u0105gni\u0119cia okre\u015blonego celu.\u00a0Diagram przypadk\u00f3w u\u017cycia sk\u0142ada si\u0119 z systemu, powi\u0105zanych przypadk\u00f3w u\u017cycia i aktor\u00f3w i \u0142\u0105czy je ze sob\u0105 w celu wizualizacji: co jest opisywane?\u00a0(\u00a0<\/span>system<\/span><\/strong>\u00a0), kto korzysta z systemu?\u00a0(\u00a0<\/span>aktorzy<\/span><\/strong>\u00a0) i co aktorzy chc\u0105 osi\u0105gn\u0105\u0107?\u00a0(\u00a0<\/span>przypadki u\u017cycia<\/span><\/strong>\u00a0), a zatem przypadki u\u017cycia pomagaj\u0105 zapewni\u0107 opracowanie w\u0142a\u015bciwego systemu poprzez uchwycenie wymaga\u0144 z punktu widzenia u\u017cytkownika.<\/span><\/p>\n

\"Szablon<\/h3>\n

Strukturyzacja przypadk\u00f3w u\u017cycia<\/span><\/span><\/h2>\n

Relacje przypadk\u00f3w u\u017cycia modeluj\u0105 zale\u017cno\u015bci mi\u0119dzy przypadkami u\u017cycia w modelu interakcji systemu.\u00a0Chocia\u017c niezale\u017cne przypadki u\u017cycia mog\u0105 odpowiednio reprezentowa\u0107 prostsze systemy.\u00a0Jednak w celu przedstawienia z\u0142o\u017conych lub du\u017cych system\u00f3w mo\u017ce by\u0107 konieczne skonstruowanie z\u0142o\u017conych przypadk\u00f3w u\u017cycia za pomoc\u0105 zale\u017cno\u015bci mi\u0119dzy przypadkami u\u017cycia.\u00a0Ustanawianie relacji mi\u0119dzy przypadkami u\u017cycia umo\u017cliwia ponowne wykorzystanie przypadk\u00f3w u\u017cycia, kt\u00f3re musz\u0105 by\u0107 definiowane w k\u00f3\u0142ko, co zmniejsza wysi\u0142ek programist\u00f3w.<\/span><\/p>\n

UML definiuje trzy stereotypy strukturyzowania powi\u0105za\u0144 przypadk\u00f3w u\u017cycia.<\/span><\/p>\n

Co to jest przypadek u\u017cycia <<Uwzgl\u0119dnij>>?<\/span><\/span><\/h3>\n

Rozszerzaj\u0105cy si\u0119 przypadek u\u017cycia jest w rzeczywisto\u015bci alternatywnym przebiegiem podstawowego przypadku u\u017cycia.\u00a0Przypadek u\u017cycia <<rozszerz>> osi\u0105ga to poprzez koncepcyjne wstawienie dodatkowych sekwencji dzia\u0142a\u0144 do podstawowej sekwencji przypadk\u00f3w u\u017cycia.<\/span><\/p>\n

Czas na u\u017cycie relacji <<include>> nast\u0119puje po uko\u0144czeniu pierwszego opisu wszystkich g\u0142\u00f3wnych przypadk\u00f3w u\u017cycia.\u00a0Mo\u017cesz teraz przyjrze\u0107 si\u0119 Przypadkom U\u017cycia i zidentyfikowa\u0107 typowe sekwencje interakcji u\u017cytkownika z systemem.<\/span><\/p>\n

    \n
  • Kiedy przypadek u\u017cycia jest przedstawiony jako wykorzystuj\u0105cy funkcjonalno\u015b\u0107 innego przypadku u\u017cycia, zwi\u0105zek mi\u0119dzy przypadkami u\u017cycia jest nazywany relacj\u0105 w\u0142\u0105czania lub u\u017cywania.<\/span><\/li>\n
  • Przypadek u\u017cycia obejmuje funkcjonalno\u015b\u0107 opisan\u0105 w innym przypadku u\u017cycia jako cz\u0119\u015b\u0107 przep\u0142ywu proces\u00f3w biznesowych.<\/span><\/li>\n
  • Relacja u\u017cycia od podstawowego przypadku u\u017cycia do potomnego przypadku u\u017cycia wskazuje, \u017ce instancja podstawowego przypadku u\u017cycia b\u0119dzie zawiera\u0107 zachowanie okre\u015blone w potomnym przypadku u\u017cycia.<\/span><\/li>\n
  • Relacja obejmuj\u0105ca jest przedstawiona za pomoc\u0105 skierowanej strza\u0142ki z lini\u0105 kropkowan\u0105.\u00a0Ko\u0144c\u00f3wka grotu strza\u0142ki wskazuje na potomny przypadek u\u017cycia i nadrz\u0119dny przypadek u\u017cycia po\u0142\u0105czony u podstawy strza\u0142ki.<\/span><\/li>\n
  • Stereotyp \u201e<<include>>\u201d identyfikuje relacj\u0119 jako relacj\u0119 obejmuj\u0105c\u0105.<\/span><\/li>\n<\/ul>\n

    Przyk\u0142ad przypadku u\u017cycia \u2014 uwzgl\u0119dnij zwi\u0105zek<\/span><\/span><\/h3>\n

    Relacja do\u0142\u0105czania dodaje dodatkowe funkcje, kt\u00f3re nie zosta\u0142y okre\u015blone w podstawowym przypadku u\u017cycia.\u00a0Relacja <<Include>> jest u\u017cywana do w\u0142\u0105czania typowego zachowania z uwzgl\u0119dnionego przypadku u\u017cycia do podstawowego przypadku u\u017cycia w celu wspierania ponownego wykorzystania typowego zachowania.<\/span><\/p>\n

    \"Notacja<\/p>\n

    Co to jest przypadek u\u017cycia <<Rozszerz>>?<\/span><\/strong><\/span><\/h3>\n

    \"Notacja<\/p>\n

      \n
    • Wskazuje, \u017ce\u00a0 przypadek u\u017cycia\u00a0<\/span>\u201eNieprawid\u0142owe has\u0142o\u201d<\/span><\/strong>\u00a0\u00a0mo\u017ce obejmowa\u0107 (pod warunkiem okre\u015blonym w rozszerzeniu) zachowanie okre\u015blone przez podstawowy przypadek u\u017cycia\u00a0\u00a0<\/span>\u201eKonto logowania\u201d<\/span><\/strong>\u00a0.<\/span><\/li>\n
    • Przedstawi\u0107 za pomoc\u0105 skierowanej strza\u0142ki z lini\u0105 przerywan\u0105.\u00a0Ko\u0144c\u00f3wka grotu wskazuje na podstawowy przypadek u\u017cycia, a potomny przypadek u\u017cycia jest po\u0142\u0105czony u podstawy strza\u0142ki.<\/span><\/li>\n
    • Stereotyp \u201e<<rozszerza si\u0119>>\u201d identyfikuje zwi\u0105zek rozszerzaj\u0105cy si\u0119<\/span><\/li>\n<\/ul>\n

      Rozszerz zwi\u0105zek<\/span><\/span><\/h4>\n

      Relacje rozszerzaj\u0105ce s\u0105 wa\u017cne, poniewa\u017c przedstawiaj\u0105 opcjonalne funkcje lub zachowanie systemu.\u00a0Relacja <<extend>> s\u0142u\u017cy do uwzgl\u0119dnienia opcjonalnego zachowania z rozszerzaj\u0105cego si\u0119 przypadku u\u017cycia w rozszerzonym przypadku u\u017cycia.\u00a0W powy\u017cszym przyk\u0142adzie wyst\u0119puje z\u0142\u0105cze rozszerzaj\u0105ce z punktem rozszerzenia \u201eNieprawid\u0142owe has\u0142o\u201d.<\/span><\/p>\n

      Abstrakcyjny i uog\u00f3lniony przypadek u\u017cycia<\/span><\/span><\/h3>\n

      Og\u00f3lny przypadek u\u017cycia jest abstrakcyjny.\u00a0Nie mo\u017cna utworzy\u0107 instancji, poniewa\u017c zawiera niepe\u0142ne informacje.\u00a0Tytu\u0142 abstrakcyjnego przypadku u\u017cycia jest zaznaczony kursyw\u0105.<\/span><\/p>\n

      \"Notacja<\/p>\n

      Przyk\u0142ad diagramu przypadk\u00f3w u\u017cycia<\/span><\/span><\/h2>\n

      Ten przyk\u0142ad diagramu przypadk\u00f3w u\u017cycia przedstawia model kilku biznesowych przypadk\u00f3w u\u017cycia (cel\u00f3w), kt\u00f3re reprezentuj\u0105 interakcj\u0119 mi\u0119dzy restauracj\u0105 (systemem biznesowym) a jej kluczowymi interesariuszami (uczestnikami biznesowymi i pracownikami biznesowymi).\u00a0Po zidentyfikowaniu podstawowych przypadk\u00f3w u\u017cycia w pierwszej rundzie ci\u0119\u0107, by\u0107 mo\u017ce uda nam si\u0119 dalej budowa\u0107 te przypadki u\u017cycia z \u201erozszerzeniem\u201d i \u201ew\u0142\u0105czeniem\u201d przypadk\u00f3w u\u017cycia w drugiej rundzie rewizji.<\/span><\/p>\n

      \"Diagram<\/p>\n","protected":false},"excerpt":{"rendered":"

      Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.<\/p>\n","protected":false},"author":1,"featured_media":3608,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[36],"tags":[],"class_list":["post-3481","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uml","loop-entry","clr"],"yoast_head":"\nPrzypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d - Visual Paradigm Blog<\/title>\n<meta name=\"description\" content=\"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.\" \/>\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\/include-and-extend-use-cases\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d - Visual Paradigm Blog\" \/>\n<meta property=\"og:description\" content=\"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-02-09T09:13:56+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-11-25T09:29:16+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\" \/>\n<meta name=\"author\" content=\"Admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.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\/include-and-extend-use-cases\/\",\"url\":\"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/\",\"name\":\"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d - Visual Paradigm Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\",\"datePublished\":\"2022-02-09T09:13:56+00:00\",\"dateModified\":\"2022-11-25T09:29:16+00:00\",\"author\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/#\/schema\/person\/a649c442f11a53040710ddec750926c6\"},\"description\":\"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#primaryimage\",\"url\":\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\",\"contentUrl\":\"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png\",\"width\":\"733\",\"height\":\"656\",\"caption\":\"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d\"}]},{\"@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":"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d - Visual Paradigm Blog","description":"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.","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\/include-and-extend-use-cases\/","og_locale":"pl_PL","og_type":"article","og_title":"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d - Visual Paradigm Blog","og_description":"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.","og_url":"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/","og_site_name":"Visual Paradigm Blog","article_published_time":"2022-02-09T09:13:56+00:00","article_modified_time":"2022-11-25T09:29:16+00:00","og_image":[{"url":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png","type":"","width":"","height":""}],"author":"Admin","twitter_card":"summary_large_image","twitter_image":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.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\/include-and-extend-use-cases\/","url":"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/","name":"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d - Visual Paradigm Blog","isPartOf":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#primaryimage"},"image":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#primaryimage"},"thumbnailUrl":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png","datePublished":"2022-02-09T09:13:56+00:00","dateModified":"2022-11-25T09:29:16+00:00","author":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/#\/schema\/person\/a649c442f11a53040710ddec750926c6"},"description":"Use case relationships model the dependencies between use cases in the interaction model of the system. Although, independent use cases can adequately represent simpler systems. However, in order to represent complex or large systems, we may need to construct complex use cases with the help of dependencies between use cases. Establishing relationships between use cases allows reuse of those use cases that need to be defined over and over again, which reduces developer effort.","breadcrumb":{"@id":"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/"]}]},{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#primaryimage","url":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png","contentUrl":"https:\/\/circle.visual-paradigm.com\/wp-content\/uploads\/2017\/08\/Use-Case-Diagram-Include-and-Extend-Use-Cases.png","width":"733","height":"656","caption":"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d"},{"@type":"BreadcrumbList","@id":"https:\/\/blog.visual-paradigm.com\/pl\/include-and-extend-use-cases\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Przypadki U\u017cycia \u201eUwzgl\u0119dnij\u201d I \u201eRozszerz\u201d"}]},{"@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\/3481","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=3481"}],"version-history":[{"count":6,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/posts\/3481\/revisions"}],"predecessor-version":[{"id":10331,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/posts\/3481\/revisions\/10331"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media\/3608"}],"wp:attachment":[{"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=3481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/categories?post=3481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/tags?post=3481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}