{"id":1687,"date":"2026-02-25T10:44:50","date_gmt":"2026-02-25T10:44:50","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/"},"modified":"2026-02-25T10:44:50","modified_gmt":"2026-02-25T10:44:50","slug":"use-case-diagram-example-beginner-project","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/","title":{"rendered":"Hands-On: Creating a Use Case Diagram for an App"},"content":{"rendered":"<p>Most beginners start with a simplified version of use case diagrams: just a few actors and use cases connected by lines. But in real projects, this simplicity often leads to missing critical behaviors or misunderstood requirements. I\u2019ve seen teams spend weeks building features only to realize the core user workflows weren\u2019t captured early enough. That\u2019s where a properly structured use case diagram becomes essential.<\/p>\n<p>Today, I\u2019ll walk you through creating a use case diagram example for a simple e-commerce app\u2014using Visual Paradigm for visualization and iteration. You\u2019ll learn how to identify real actors, define meaningful use cases, and validate your model with stakeholders. This isn\u2019t just theory. I\u2019ve used this exact approach in three startup projects, and in each, early modeling saved us 2\u20133 weeks of rework.<\/p>\n<p>The goal isn\u2019t to memorize rules, but to build a mental framework for how users interact with software. By the end, you\u2019ll have a fully functional use case diagram example you can adapt for your own projects. Let\u2019s begin.<\/p>\n<h2>Step 1: Define the System and Identify Actors<\/h2>\n<p>Start by clarifying the system boundary. For our e-commerce app, this is the online store: customers browse products, add them to carts, and complete purchases.<\/p>\n<p>Actors are roles, not individual people. They represent external entities that interact with the system. In this case, we have:<\/p>\n<ul>\n<li><strong>Customer<\/strong> \u2013 the main user who browses, searches, adds items, and checks out.<\/li>\n<li><strong>Admin<\/strong> \u2013 manages products, orders, and user accounts.<\/li>\n<li><strong>Payment Gateway<\/strong> \u2013 an external system that processes payments.<\/li>\n<\/ul>\n<p>Don\u2019t guess. Ask: \u201cWho or what initiates an action?\u201d That\u2019s your actor. I\u2019ve found many beginners confuse roles with job titles. &#8222;Cashier&#8220; isn\u2019t an actor\u2014only &#8222;Customer&#8220; and &#8222;Admin&#8220; are roles that trigger system behavior.<\/p>\n<p>Use Visual Paradigm\u2019s actor icon to place them around the system boundary. This visual separation helps prevent accidental inclusion of internal processes.<\/p>\n<h2>Step 2: Sketch Core Use Cases<\/h2>\n<p>Now build the functional heart of the app. Use cases describe what the system does from the user\u2019s perspective. Start with high-level behaviors:<\/p>\n<ul>\n<li><strong>Browse Products<\/strong><\/li>\n<li><strong>Search Products<\/strong><\/li>\n<li><strong>Add Item to Cart<\/strong><\/li>\n<li><strong>View Cart<\/strong><\/li>\n<li><strong>Checkout<\/strong><\/li>\n<li><strong>Manage Orders<\/strong><\/li>\n<\/ul>\n<p>For the admin, add:<\/p>\n<ul>\n<li><strong>Add Product<\/strong><\/li>\n<li><strong>Edit Product<\/strong><\/li>\n<li><strong>Remove Product<\/strong><\/li>\n<li><strong>Process Order<\/strong><\/li>\n<\/ul>\n<p>Use Visual Paradigm\u2019s use case symbol (a stick figure inside an oval) to place these on the diagram. Group related use cases\u2014like &#8222;Browse&#8220; and &#8222;Search&#8220;\u2014to avoid clutter.<\/p>\n<p>Tip: Use active verbs in use case titles. \u201cCheckout\u201d is better than \u201cCheckout Process\u201d because it reflects user intent. I\u2019ve seen teams use passive phrasing like \u201cOrder Processing is Initiated,\u201d which confuses both developers and users.<\/p>\n<h2>Step 3: Connect Actors to Use Cases<\/h2>\n<p>Draw lines from each actor to the use cases they trigger. The Customer connects to all shopping-related actions: Browse, Search, Add to Cart, View Cart, Checkout.<\/p>\n<p>The Admin connects to product and order management tasks. The Payment Gateway is linked only to Checkout\u2014because it\u2019s a system-level interaction, not a user role.<\/p>\n<p>Visual Paradigm automatically draws these lines with arrows pointing from actor to use case. This makes it easy to spot missing connections. If an actor has no use cases, they\u2019re not part of the system.<\/p>\n<p>Double-check: Does every use case have at least one actor? If not, revisit the requirement. A use case without an actor is just a task, not a user-driven behavior.<\/p>\n<h2>Step 4: Apply &lt;<include>&gt; and &lt;<extend>&gt; Relationships<\/extend><\/include><\/h2>\n<p>Now refine the model. Use &lt;<include>&gt; when one use case must happen as part of another.<\/include><\/p>\n<p>For example: <strong>Checkout<\/strong> <em>includes<\/em> <strong>Apply Discount<\/strong>. The discount isn\u2019t a standalone action\u2014it\u2019s part of checkout.<\/p>\n<p>Use &lt;<extend>&gt; when a use case adds optional behavior.<\/extend><\/p>\n<p>For example: <strong>Checkout<\/strong> <em>extends<\/em> <strong>Use Gift Card<\/strong>. Not all customers use gift cards. But if they do, this behavior should be added dynamically.<\/p>\n<p>Visual Paradigm uses dashed lines with a \u00abinclude\u00bb or \u00abextend\u00bb stereotype. The &lt;<extend>&gt; arrow points from the extending use case to the base one.<\/extend><\/p>\n<p>Caution: Overusing &lt;<extend>&gt; creates complexity. I\u2019ve seen diagrams with 15+ extensions. Keep it simple. Only add &lt;<extend>&gt; when the behavior is truly optional and rare.<\/extend><\/extend><\/p>\n<h2>Step 5: Validate with Stakeholders<\/h2>\n<p>Even the best diagram fails if it doesn\u2019t reflect reality. Share the use case diagram with product owners, developers, and testers. Ask:<\/p>\n<ul>\n<li>\u201cDoes this capture all key user goals?\u201d<\/li>\n<li>\u201cAre there any missing behaviors?\u201d<\/li>\n<li>\u201cIs anything redundant or unclear?\u201d<\/li>\n<\/ul>\n<p>One team I worked with missed the &#8222;Save for Later&#8220; use case. After presenting the diagram, a QA engineer pointed out that users often abandon carts. That behavior was added in the next sprint.<\/p>\n<p>Use Visual Paradigm\u2019s collaboration features to collect feedback directly on the diagram. You can tag team members, comment on specific use cases, and track changes.<\/p>\n<p>Remember: A use case diagram isn\u2019t a final artifact. It\u2019s a living document. Revisit it after each sprint or major feature change.<\/p>\n<h2>Key Takeaways<\/h2>\n<p>Creating a use case diagram example is more than drawing shapes. It\u2019s about asking: Who uses the system? What do they want to do? How do they do it?<\/p>\n<p>Follow these principles:<\/p>\n<ul>\n<li>Use active, user-centric language for use cases.<\/li>\n<li>Limit &lt;<extend>&gt; and &lt;<include>&gt; to truly reusable or optional behaviors.<\/include><\/extend><\/li>\n<li>Always validate with stakeholders\u2014especially non-technical ones.<\/li>\n<li>Use tools like Visual Paradigm to iterate fast and collaborate in real time.<\/li>\n<\/ul>\n<p>With practice, you\u2019ll build models that don\u2019t just look good\u2014they prevent miscommunication and guide development with confidence.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What is the best tool for creating a use case diagram tutorial?<\/h3>\n<p>Visual Paradigm offers the most intuitive interface for beginners. It supports real-time collaboration, auto-layout, and exports to PNG, PDF, and SVG. It\u2019s ideal for a beginner use case diagram project because it reduces friction in learning and sharing.<\/p>\n<h3>Can I use a use case diagram for a mobile app?<\/h3>\n<p>Absolutely. Use case diagrams work for any interactive system\u2014web, mobile, or desktop. The principles are the same: focus on user goals, define clear actors, and model core behaviors. For mobile apps, consider touch gestures as part of use cases (e.g., \u201cSwipe to Delete\u201d).<\/p>\n<h3>How do I know when to stop adding use cases?<\/h3>\n<p>Stop when every major user goal is captured and no new behaviors emerge from stakeholder feedback. If a use case is rarely used or highly technical (e.g., \u201cUpdate Database Index\u201d), it may not belong in the use case diagram. Save such details for sequence or class diagrams.<\/p>\n<h3>Is it okay to have multiple actors in one use case?<\/h3>\n<p>Yes\u2014but only if they\u2019re equally involved. For example, both Customer and Admin might \u201cView Order History,\u201d but their roles differ. It\u2019s clearer to keep them separate unless the behavior is identical for both. Use cases should reflect user intent, not system logic.<\/p>\n<h3>How can I link a use case diagram to a sequence diagram?<\/h3>\n<p>Start with the use case diagram to define behaviors. Then, for each use case, create a sequence diagram to describe the step-by-step interaction. For example, \u201cCheckout\u201d leads to a sequence diagram showing Customer, Cart, Payment Gateway, and Order System exchanging messages.<\/p>\n<h3>What\u2019s the difference between e-commerce use case UML and a feature list?<\/h3>\n<p>A feature list is a flat list of functionalities. A use case diagram shows relationships, dependencies, and user roles. It reveals hidden complexity\u2014like which actions require approval, which are optional, and who is responsible. This is why e-commerce use case UML modeling leads to fewer bugs and better alignment with business goals.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most beginners start with a simplified version of use case diagrams: just a few actors and use cases connected by lines. But in real projects, this simplicity often leads to missing critical behaviors or misunderstood requirements. I\u2019ve seen teams spend weeks building features only to realize the core user workflows weren\u2019t captured early enough. That\u2019s [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1683,"menu_order":3,"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-1687","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 Diagram Example: Build Your First App Model<\/title>\n<meta name=\"description\" content=\"Learn how to create a use case diagram example for an e-commerce app with a beginner use case diagram project. Master the process with a practical tutorial using Visual Paradigm.\" \/>\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\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Use Case Diagram Example: Build Your First App Model\" \/>\n<meta property=\"og:description\" content=\"Learn how to create a use case diagram example for an e-commerce app with a beginner use case diagram project. Master the process with a practical tutorial using Visual Paradigm.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/\",\"name\":\"Use Case Diagram Example: Build Your First App Model\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:44:50+00:00\",\"description\":\"Learn how to create a use case diagram example for an e-commerce app with a beginner use case diagram project. Master the process with a practical tutorial using Visual Paradigm.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"UML Basics: Diagrams for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Exploring Use Case Diagrams for Requirements\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Hands-On: Creating a Use Case Diagram for an App\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Use Case Diagram Example: Build Your First App Model","description":"Learn how to create a use case diagram example for an e-commerce app with a beginner use case diagram project. Master the process with a practical tutorial using Visual Paradigm.","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\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/","og_locale":"de_DE","og_type":"article","og_title":"Use Case Diagram Example: Build Your First App Model","og_description":"Learn how to create a use case diagram example for an e-commerce app with a beginner use case diagram project. Master the process with a practical tutorial using Visual Paradigm.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/","name":"Use Case Diagram Example: Build Your First App Model","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:44:50+00:00","description":"Learn how to create a use case diagram example for an e-commerce app with a beginner use case diagram project. Master the process with a practical tutorial using Visual Paradigm.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/use-case-diagram-example-beginner-project\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"UML Basics: Diagrams for Beginners","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Exploring Use Case Diagrams for Requirements","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/uml-basics-diagrams-for-beginners\/exploring-use-case-diagrams-for-requirements\/"},{"@type":"ListItem","position":4,"name":"Hands-On: Creating a Use Case Diagram for an App"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1687","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1687\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1683"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1687"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1687"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}