{"id":1685,"date":"2026-02-25T10:44:50","date_gmt":"2026-02-25T10:44:50","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/"},"modified":"2026-02-25T10:44:50","modified_gmt":"2026-02-25T10:44:50","slug":"identifying-actors-use-case-scenarios","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/","title":{"rendered":"Identifying Actors and Scenarios in Real Projects"},"content":{"rendered":"<p>When I first worked on a healthcare system, I spent days drawing use cases\u2014only to realize we\u2019d missed a critical external system: the national patient registry. It wasn\u2019t just a missing detail; it was a failure to ask the right questions about who or what interacts with the system. That moment taught me: identifying use case actors isn\u2019t about guessing. It\u2019s about listening to your system\u2019s environment.<\/p>\n<p>Use case actors are the lifelines of functional modeling. They\u2019re not just users. They\u2019re any entity\u2014people, systems, or devices\u2014that initiates or receives behavior from your system. If you skip this step, your use cases will miss key interactions, and your software will be built on assumptions, not requirements.<\/p>\n<p>What you\u2019ll learn here is how to spot these actors reliably in real projects, avoid common traps, and turn user needs into clear, actionable use case scenarios. You\u2019ll walk away with a repeatable process, not just theory.<\/p>\n<h2>Start with the Right Questions: The First Step to Finding Use Case Actors<\/h2>\n<p>Don\u2019t start by drawing boxes. Start by asking: who or what uses this system\u2014or is affected by it?<\/p>\n<p>Begin with the system boundary. Define the scope first. Then ask who or what crosses that boundary to trigger behavior.<\/p>\n<p>Here\u2019s a simple but powerful checklist to guide you:<\/p>\n<ul>\n<li>Who performs actions like login, submit, or approve?<\/li>\n<li>Who receives outputs like reports, alerts, or confirmations?<\/li>\n<li>Is there an external system that sends data or expects a response?<\/li>\n<li>Does any device or service interact automatically (e.g., IoT sensor, payment gateway)?<\/li>\n<\/ul>\n<p>These questions shift focus from \u201cwhat can the system do\u201d to \u201cwho has a stake in it?\u201d<\/p>\n<h3>Real-World Example: Online Grocery Ordering<\/h3>\n<p>Let\u2019s say you&#8217;re modeling a grocery delivery app. You might start with these actors:<\/p>\n<ul>\n<li><strong>Customer<\/strong>: places orders, views inventory.<\/li>\n<li><strong>Delivery Driver<\/strong>: receives pickup instructions, updates delivery status.<\/li>\n<li><strong>Payment Gateway<\/strong>: processes credit card charges.<\/li>\n<li><strong>Inventory System<\/strong>: updates stock levels after an order is confirmed.<\/li>\n<\/ul>\n<p>See how the <em>Payment Gateway<\/em> isn\u2019t a user. It\u2019s an external system that interacts with your app. Yet if you miss it during initial modeling, your payment process will be incomplete.<\/p>\n<h2>Common Pitfalls in Identifying Actors in UML<\/h2>\n<p>Even experienced modelers stumble here. Let\u2019s break down the top three:<\/p>\n<h3>1. Confusing Actors with Roles<\/h3>\n<p>Not every role in a business process is a use case actor. A \u201cManager\u201d might be a role, but if they don\u2019t initiate or receive behavior from the system, they\u2019re not an actor.<\/p>\n<p>Ask: Does this role trigger or receive an action from the system? If not, it\u2019s likely a participant in a scenario, not an actor.<\/p>\n<h3>2. Overlooking External Systems<\/h3>\n<p>Many beginners focus only on people. But systems\u2014like a weather API, a bank\u2019s fraud detection system, or a CRM\u2014often drive behavior.<\/p>\n<p>Tip: When reviewing requirements, watch for phrases like \u201cintegrated with,\u201d \u201cconnected to,\u201d or \u201csends data to.\u201d These signal potential actors.<\/p>\n<h3>3. Treating Use Cases as Actors<\/h3>\n<p>Use cases are actions: \u201cPlace Order,\u201d \u201cCancel Payment.\u201d They don\u2019t initiate behavior\u2014they\u2019re performed by actors.<\/p>\n<p>Don\u2019t confuse: <em>Customer places order<\/em>. The actor is <em>Customer<\/em>, the use case is <em>Place Order<\/em>.<\/p>\n<h2>Step-by-Step Guide to Derive Use Cases from Requirements<\/h2>\n<p>Use case actors are the trigger. Use cases are the response. Here\u2019s how to turn stakeholder needs into real use cases.<\/p>\n<ol>\n<li><strong>Identify all actors<\/strong>: Use the checklist above. Write each down.<\/li>\n<li><strong>For each actor, ask: \u201cWhat do they need from the system?\u201d<\/strong> Focus on goals.<\/li>\n<li><strong>Group similar needs<\/strong>: Two users might both need to \u201cview their orders,\u201d but if the data or permissions differ, they may have different use cases.<\/li>\n<li><strong>Phrase use cases as goals<\/strong>: Start with a verb. \u201cPay for order,\u201d \u201cCancel reservation,\u201d \u201cReceive confirmation email.\u201d<\/li>\n<li><strong>Validate with stakeholders<\/strong>: Run the list past users or domain experts. If they say \u201cThat\u2019s not what I do,\u201d refine the use case.<\/li>\n<\/ol>\n<h3>Example: Refining a Use Case from a Requirement<\/h3>\n<p>Requirement: \u201cThe system must allow customers to change their delivery address.\u201d<\/p>\n<p>Step 1: Actor is <em>Customer<\/em>.<\/p>\n<p>Step 2: What do they need? To update their delivery address.<\/p>\n<p>Step 3: Phrase it: <strong>Update Delivery Address<\/strong>.<\/p>\n<p>Step 4: Ask: Does this cover all scenarios? What if the address is invalid? What if the user has no saved addresses? That\u2019s where sub-steps and exceptions come in later.<\/p>\n<h2>Practical Tips for Beginner Use Case Scenarios<\/h2>\n<p>Use case scenarios are the narrative behind the diagram. They\u2019re not just a list\u2014they\u2019re stories of how the system behaves in real contexts.<\/p>\n<p>A common mistake is writing overly technical or vague descriptions. Instead, use the <strong>Actor + Goal + Action<\/strong> pattern:<\/p>\n<ul>\n<li><strong>Customer<\/strong> wants to <strong>update their delivery address<\/strong>, so they <strong>select the profile menu, choose \u201cEdit Address,\u201d enter new details, and confirm<\/strong>.<\/li>\n<\/ul>\n<p>Keep scenarios short, specific, and goal-driven. Avoid details like \u201cclick the blue button\u201d\u2014focus on intent, not interface elements.<\/p>\n<p>Here\u2019s how to make your beginner use case scenarios more effective:<\/p>\n<ul>\n<li><strong>Start with the actor\u2019s goal<\/strong>: \u201cI want to cancel a reservation.\u201d<\/li>\n<li><strong>Use active voice<\/strong>: \u201cUser clicks \u2018Cancel\u2019\u201d not \u201cCancellation is processed.\u201d<\/li>\n<li><strong>Include key variations<\/strong>: What if the reservation is already past the cancellation deadline?<\/li>\n<li><strong>Use natural language<\/strong>: Avoid technical jargon unless necessary.<\/li>\n<\/ul>\n<h2>How to Find Use Cases: A Reality Check<\/h2>\n<p>Let\u2019s be clear: you won\u2019t get it perfect on the first try. The goal isn\u2019t perfection\u2014it\u2019s clarity and coverage.<\/p>\n<p>Here\u2019s a table summarizing how to approach each step:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Step<\/th>\n<th>Action<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td>1. Spot stakeholders<\/td>\n<td>List every person, system, or device interacting with your app<\/td>\n<td>Ensures no key interactions are missed<\/td>\n<\/tr>\n<tr>\n<td>2. Ask \u201cWhat do they want?\u201d<\/td>\n<td>Focus on the user\u2019s goal, not the feature<\/td>\n<td>Aligns use cases with real needs<\/td>\n<\/tr>\n<tr>\n<td>3. Avoid overloading<\/td>\n<td>Split large use cases (e.g., \u201cManage Order\u201d) into smaller ones<\/td>\n<td>Improves readability and testability<\/td>\n<\/tr>\n<tr>\n<td>4. Review for completeness<\/td>\n<td>Check if every actor has at least one interaction<\/td>\n<td>Prevents missing critical flows<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Remember: the goal of use case modeling isn\u2019t to draw a perfect diagram. It\u2019s to uncover what the system <strong>must do<\/strong>\u2014and who it\u2019s for.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How to find use cases when requirements are vague?<\/h3>\n<p>Start by identifying actors. If a requirement says \u201cthe system handles orders,\u201d ask: \u201cWho places these orders? Who receives confirmation? Who processes payment?\u201d Each answer points to a potential use case. Use phrases like \u201cX needs to\u2026\u201d or \u201cY expects\u2026\u201d to uncover hidden goals.<\/p>\n<h3>How to identify actors in UML when multiple users share the same role?<\/h3>\n<p>Group them under one actor if they perform the same actions with the same permissions. For example, \u201cCashier\u201d and \u201cManager\u201d in a store app might both handle returns. But if managers can approve more than $100 refunds and cashiers can\u2019t, they should be separate actors with different use cases.<\/p>\n<h3>What\u2019s the best way to write use case scenarios for beginners?<\/h3>\n<p>Use the \u201cActor + Goal + Action\u201d format. Keep it simple. Describe the main success scenario (happy path), then add alternate paths like invalid input or system failure. Use natural language\u2014aim for clarity, not jargon.<\/p>\n<h3>Can an actor be a system or a device?<\/h3>\n<p>Absolutely. External systems like a payment processor, weather API, or a sensor device are valid actors. They initiate or receive behavior. Example: \u201cPayment Gateway\u201d sends confirmation; \u201cIoT Thermostat\u201d triggers a home automation event.<\/p>\n<h3>Why do use case actors matter for software design?<\/h3>\n<p>They define the system\u2019s boundaries. Without clear actors, your use cases may not cover all stakeholder needs. This leads to missing features, incorrect assumptions, and costly rework later. Use case actors help align design with real-world behavior.<\/p>\n<h3>How often should you revisit use case actors during development?<\/h3>\n<p>Revisit them early and often. As the project evolves, new actors may emerge\u2014like a third-party audit system or a new device interface. Review use cases during sprint planning or after stakeholder feedback to ensure nothing has changed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I first worked on a healthcare system, I spent days drawing use cases\u2014only to realize we\u2019d missed a critical external system: the national patient registry. It wasn\u2019t just a missing detail; it was a failure to ask the right questions about who or what interacts with the system. That moment taught me: identifying use [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1683,"menu_order":1,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1685","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Use Case Actors: How to Find Use Cases in UML<\/title>\n<meta name=\"description\" content=\"Learn how to identify actors and derive beginner use case scenarios in real projects. Practical steps, techniques, and real-world examples for mastering use case actors in UML diagrams.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Use Case Actors: How to Find Use Cases in UML\" \/>\n<meta property=\"og:description\" content=\"Learn how to identify actors and derive beginner use case scenarios in real projects. Practical steps, techniques, and real-world examples for mastering use case actors in UML diagrams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/\",\"name\":\"Use Case Actors: How to Find Use Cases in UML\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:44:50+00:00\",\"description\":\"Learn how to identify actors and derive beginner use case scenarios in real projects. Practical steps, techniques, and real-world examples for mastering use case actors in UML diagrams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"UML Basics: Diagrams for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Exploring Use Case Diagrams for Requirements\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Identifying Actors and Scenarios in Real Projects\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Use Case Actors: How to Find Use Cases in UML","description":"Learn how to identify actors and derive beginner use case scenarios in real projects. Practical steps, techniques, and real-world examples for mastering use case actors in UML diagrams.","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:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/","og_locale":"pl_PL","og_type":"article","og_title":"Use Case Actors: How to Find Use Cases in UML","og_description":"Learn how to identify actors and derive beginner use case scenarios in real projects. Practical steps, techniques, and real-world examples for mastering use case actors in UML diagrams.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"7 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/","name":"Use Case Actors: How to Find Use Cases in UML","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:44:50+00:00","description":"Learn how to identify actors and derive beginner use case scenarios in real projects. Practical steps, techniques, and real-world examples for mastering use case actors in UML diagrams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/identifying-actors-use-case-scenarios\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"UML Basics: Diagrams for Beginners","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Exploring Use Case Diagrams for Requirements","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/"},{"@type":"ListItem","position":4,"name":"Identifying Actors and Scenarios in Real Projects"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1685","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1685\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1683"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=1685"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=1685"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}