{"id":1111,"date":"2026-02-25T10:36:00","date_gmt":"2026-02-25T10:36:00","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/"},"modified":"2026-02-25T10:36:00","modified_gmt":"2026-02-25T10:36:00","slug":"user-story-relationships-epics-dependencies-traceability","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/","title":{"rendered":"Story Relationships: Epics, Dependencies, and Traces"},"content":{"rendered":"<p>Stories don\u2019t exist in isolation\u2014they connect, depend, and trace back to bigger goals. The real power of user stories unfolds when you understand how they relate.<\/p>\n<p>I\u2019ve seen teams build entire features without realizing their stories were disconnected from the product vision. That\u2019s why modeling relationships isn\u2019t just about diagrams\u2014it\u2019s about clarity, alignment, and accountability.<\/p>\n<p>By the end of this chapter, you\u2019ll be able to organize stories using epics, map dependencies with confidence, and create traceability diagrams that tell a coherent story from idea to delivery.<\/p>\n<h2>Understanding User Story Hierarchy<\/h2>\n<p>Not every story is created equal. Some are broad, strategic, and long-term\u2014others are precise, tactical, and sprint-ready. That\u2019s where hierarchy comes in.<\/p>\n<p>At the top is the <strong>epic<\/strong>\u2014a large body of work that captures a major user goal or business capability. Think: \u201cEnable secure login with multi-factor authentication.\u201d<\/p>\n<p>Below it are <strong>features<\/strong>, which break down epics into deliverable chunks. For example: \u201cAllow users to set up a one-time password via email.\u201d<\/p>\n<p>Finally, <strong>user stories<\/strong> are the smallest units: \u201cAs a user, I want to receive a 6-digit OTP via email so I can verify my identity.\u201d<\/p>\n<h3>The Power of the Epic<\/h3>\n<p>Epics are not just labels\u2014they\u2019re containers for related stories. They help product owners prioritize at scale, create roadmap themes, and align teams around shared objectives.<\/p>\n<p>A common mistake is treating epics as if they\u2019re stories. Never commit to delivering an epic in a sprint. Instead, use epics to group stories that share a purpose.<\/p>\n<h3>How to Build a User Story Hierarchy<\/h3>\n<ol>\n<li><strong>Start with the business outcome<\/strong>: Ask, \u201cWhat problem are we solving?\u201d This becomes your epic.<\/li>\n<li><strong>Break it into features<\/strong>: Identify major deliverables. Each feature should be a logical phase of the epic.<\/li>\n<li><strong>Write stories for each feature<\/strong>: Focus on one user, one action, one benefit. Use the \u201cAs a\u2026 I want\u2026 so that\u2026\u201d format.<\/li>\n<li><strong>Link stories to the epic<\/strong>: Use traceability tools or labels (e.g., Epic ID: #LOGIN-001).<\/li>\n<\/ol>\n<p>Let\u2019s say you\u2019re building a payment system. The epic is \u201cSupport recurring billing.\u201d The feature: \u201cAllow users to set up monthly auto-pay.\u201d The story: \u201cAs a subscriber, I want to schedule a monthly payment so I don\u2019t miss my renewal.\u201d<\/p>\n<p>This hierarchy keeps your backlog focused and your planning transparent.<\/p>\n<h2>Mapping Dependencies Between Stories<\/h2>\n<p>Not all stories can be built independently. Some require inputs from others. These are <strong>dependencies<\/strong>, and ignoring them leads to blocked sprints, wasted effort, and confusion.<\/p>\n<p>There are three main types:<\/p>\n<ul>\n<li><strong>Upstream dependency<\/strong>: Story A must be completed before Story B can begin.<\/li>\n<li><strong>Downstream dependency<\/strong>: Story B depends on Story A\u2019s output.<\/li>\n<li><strong>Parallel dependency<\/strong>: Two stories must be completed before a third can start (e.g., both a profile and payment setup are needed before checkout).<\/li>\n<\/ul>\n<h3>When Dependencies Are a Red Flag<\/h3>\n<p>If you see too many dependencies, ask: \u201cIs this a sign of poor decomposition?\u201d A well-sliced story should be self-contained.<\/p>\n<p>But when dependencies are unavoidable\u2014like in integrations or system-level changes\u2014document them clearly.<\/p>\n<h3>Tools for Dependency Mapping<\/h3>\n<p>Use simple dependency graphs or visual modeling tools to map relationships. In Visual Paradigm, you can:<\/p>\n<ul>\n<li>Draw <strong>dependency arrows<\/strong> from Story A to Story B.<\/li>\n<li>Label arrows with constraints (e.g., \u201cMust complete before,\u201d \u201cData required from\u201d).<\/li>\n<li>Use color codes: red = blocking, yellow = high risk, green = independent.<\/li>\n<\/ul>\n<p>For example:<\/p>\n<pre><code>Story: Create User Profile (ID: U-001) \u2192 Story: Enable Payment Gateway (ID: P-002)\n<\/code><\/pre>\n<p>This shows that the payment gateway can\u2019t be integrated until the user profile exists.<\/p>\n<h2>Establishing Traceability with Diagrams<\/h2>\n<p>Traceability is about answering: \u201cWhere did this story come from? Where does it go?\u201d It\u2019s not just compliance\u2014it\u2019s transparency.<\/p>\n<p><strong>Traceability diagrams<\/strong> connect user stories back to their source\u2014epics, business goals, or even regulatory requirements.<\/p>\n<p>They help you:<\/p>\n<ul>\n<li>Verify that work aligns with strategy.<\/li>\n<li>Explain decisions in retrospectives.<\/li>\n<li>Support audits and compliance.<\/li>\n<\/ul>\n<h3>How to Build a Traceability Diagram<\/h3>\n<p>Start with the epic or business goal at the top. Draw lines to its features, then to the individual user stories.<\/p>\n<p>On the reverse side, link stories to acceptance criteria and test cases. This forms a bidirectional map.<\/p>\n<h3>Real Example: Healthcare Portal<\/h3>\n<p>Consider a story: \u201cAs a patient, I want to view my medical history so I can track my treatment.\u201d<\/p>\n<p>Traceability path:<\/p>\n<ol>\n<li>Epic: \u201cProvide patient access to health records\u201d<\/li>\n<li>Feature: \u201cDisplay past appointments and test results\u201d<\/li>\n<li>Story: \u201cView medical history\u201d<\/li>\n<li>Acceptance Criteria: \u201cDisplay records from the last 2 years\u201d<\/li>\n<li>Test Case: \u201cVerify data retrieval for user ID 12345\u201d<\/li>\n<\/ol>\n<p>Now, if a stakeholder asks why a feature was delayed, you can point to this chain and show the impact.<\/p>\n<h3>Best Practices for Traceability Diagrams<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Practice<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td>Use unique IDs for every artifact<\/td>\n<td>Enables precise linking across tools.<\/td>\n<\/tr>\n<tr>\n<td>Review traceability in sprint planning<\/td>\n<td>Prevents stories from being \u201clost\u201d in the backlog.<\/td>\n<\/tr>\n<tr>\n<td>Keep diagrams updated as stories evolve<\/td>\n<td>Outdated maps mislead teams.<\/td>\n<\/tr>\n<tr>\n<td>Share diagrams with stakeholders<\/td>\n<td>Builds trust and reduces rework.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with good intentions, teams fall into traps:<\/p>\n<ul>\n<li><strong>Over-architecting relationships<\/strong>: Not every story needs a dependency or traceability link. Focus on what\u2019s critical.<\/li>\n<li><strong>Letting diagrams become static<\/strong>: A traceability diagram that\u2019s never updated becomes clutter. Treat it as living documentation.<\/li>\n<li><strong>Ignoring dependency risks<\/strong>: A story blocked by another may not show up in velocity. Track dependencies in sprint reviews.<\/li>\n<\/ul>\n<p>My rule: If a story can\u2019t be tested, deployed, or validated without another story, call it out. Use dependency tags in your backlog.<\/p>\n<h2>Integrating Relationships into Your Workflow<\/h2>\n<p>Don\u2019t wait until planning to think about relationships. Build them in from the start.<\/p>\n<p>Here\u2019s how to embed them:<\/p>\n<ol>\n<li><strong>During backlog refinement<\/strong>: Review epics, identify features, and assign stories.<\/li>\n<li><strong>During sprint planning<\/strong>: Identify dependencies and adjust sprint goals.<\/li>\n<li><strong>Throughout the sprint<\/strong>: Update dependency status in daily standups.<\/li>\n<li><strong>In retrospectives<\/strong>: Evaluate which dependencies caused delays and why.<\/li>\n<\/ol>\n<p>Use visual tools like Kanban boards or digital whiteboards. Color-code stories: green (independent), yellow (pending input), red (blocked).<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I decide if a story belongs in an epic?<\/h3>\n<p>Ask: \u201cDoes this story contribute to a larger user goal or business capability?\u201d If yes, it likely belongs under an epic. If it\u2019s a standalone feature like \u201cReset password,\u201d it may not need one.<\/p>\n<h3>Can a user story have multiple dependencies?<\/h3>\n<p>Yes\u2014but it\u2019s a red flag. If a story depends on three others, ask: \u201cCan this be split or redesigned to reduce coupling?\u201d High dependency counts often signal poor decomposition.<\/p>\n<h3>Do I need traceability diagrams for every story?<\/h3>\n<p>No. Focus traceability on high-impact, regulated, or complex stories. For example, financial, medical, or compliance-related features benefit most.<\/p>\n<h3>How do I maintain traceability in large teams?<\/h3>\n<p>Use a shared model (like Visual Paradigm) with role-based access. Assign ownership: one person maintains the epic \u2192 feature \u2192 story map. Update it during refinement.<\/p>\n<h3>What\u2019s the difference between dependency and overlap?<\/h3>\n<p>Dependency means one story relies on another\u2019s output. Overlap means two stories share resources (e.g., same database), but either can proceed independently. Use dependencies to manage sequencing.<\/p>\n<h3>Should I link acceptance criteria in traceability diagrams?<\/h3>\n<p>Yes\u2014especially for regulated domains. A traceability diagram should show: Epic \u2192 Feature \u2192 Story \u2192 Acceptance Criteria \u2192 Test Case. This ensures no step is skipped.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Stories don\u2019t exist in isolation\u2014they connect, depend, and trace back to bigger goals. The real power of user stories unfolds when you understand how they relate. I\u2019ve seen teams build entire features without realizing their stories were disconnected from the product vision. That\u2019s why modeling relationships isn\u2019t just about diagrams\u2014it\u2019s about clarity, alignment, and accountability. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1109,"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-1111","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>User Story Relationships: Epics, Dependencies, Traces<\/title>\n<meta name=\"description\" content=\"Master user story relationships with practical techniques for hierarchy, dependencies, and traceability diagrams. Improve Agile planning and delivery with real-world modeling guidance.\" \/>\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\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Relationships: Epics, Dependencies, Traces\" \/>\n<meta property=\"og:description\" content=\"Master user story relationships with practical techniques for hierarchy, dependencies, and traceability diagrams. Improve Agile planning and delivery with real-world modeling guidance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/\",\"name\":\"User Story Relationships: Epics, Dependencies, Traces\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:36:00+00:00\",\"description\":\"Master user story relationships with practical techniques for hierarchy, dependencies, and traceability diagrams. Improve Agile planning and delivery with real-world modeling guidance.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Visualizing and Modeling User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Story Relationships: Epics, Dependencies, and Traces\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Story Relationships: Epics, Dependencies, Traces","description":"Master user story relationships with practical techniques for hierarchy, dependencies, and traceability diagrams. Improve Agile planning and delivery with real-world modeling guidance.","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\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/","og_locale":"id_ID","og_type":"article","og_title":"User Story Relationships: Epics, Dependencies, Traces","og_description":"Master user story relationships with practical techniques for hierarchy, dependencies, and traceability diagrams. Improve Agile planning and delivery with real-world modeling guidance.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"6 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/","name":"User Story Relationships: Epics, Dependencies, Traces","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:36:00+00:00","description":"Master user story relationships with practical techniques for hierarchy, dependencies, and traceability diagrams. Improve Agile planning and delivery with real-world modeling guidance.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/user-story-relationships-epics-dependencies-traceability\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"Visualizing and Modeling User Stories","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-write-effective-user-stories\/visualizing-and-modeling-user-stories\/"},{"@type":"ListItem","position":4,"name":"Story Relationships: Epics, Dependencies, and Traces"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1111","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1111\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1109"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1111"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}