{"id":1412,"date":"2026-02-25T10:40:57","date_gmt":"2026-02-25T10:40:57","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/"},"modified":"2026-02-25T10:40:57","modified_gmt":"2026-02-25T10:40:57","slug":"uml-banking-system-secure-transaction-modeling","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/","title":{"rendered":"Case Study #3 \u2013 Banking Transaction and Security Platform"},"content":{"rendered":"

When designing a banking platform, the line between \u201cworking\u201d and \u201csecure\u201d often hinges on how clearly you model risk and state transitions. Too many developers start with a class diagram full of accounts and transactions, only to realize later that the sequence of authentication checks, transaction validation, and fraud detection logic wasn\u2019t captured at all.<\/p>\n

I\u2019ve seen this pattern repeat across financial institutions: a system built from the bottom up without modeling the guardrails that prevent fraud, overdraws, or unauthorized access. The mistake isn\u2019t in the code\u2014it\u2019s in skipping the behavioral clarity that UML provides.<\/p>\n

This chapter focuses on how to use decision tables and state modeling\u2014not just as academic exercises\u2014but as tools to define real transaction logic in a banking UML system. We\u2019ll walk through how to model authentication states, transaction eligibility, and risk thresholds using decision tables, ensuring your secure UML architecture reflects operational realities.<\/p>\n

Why Decision Tables Are Essential in Banking UML Modeling<\/h2>\n

Decision tables are not just for business analysts. In a banking UML system, they translate complex rules into a clear, visual format that developers, auditors, and QA teams can all validate.<\/p>\n

Consider a transaction approval rule: A transaction is allowed only if the account is active, the balance exceeds the amount, and the user is authenticated via MFA.<\/p>\n

Without a decision table, this becomes a tangled chain of if-else statements scattered across code. With a decision table, you define the full decision logic up front.<\/p>\n

Structure of a Decision Table for Transaction Approval<\/h3>\n

Here\u2019s how to break it down:<\/p>\n\n\n\n\n\n\n\n
Rule #<\/th>\nAccount Active?<\/th>\nBalance \u2265 Amount?<\/th>\nMFA Verified?<\/th>\nAction<\/th>\n<\/tr>\n
1<\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nApprove<\/td>\n<\/tr>\n
2<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nChallenge (MFA)<\/td>\n<\/tr>\n
3<\/td>\nYes<\/td>\nNo<\/td>\nAny<\/td>\nDecline (Insufficient Funds)<\/td>\n<\/tr>\n
4<\/td>\nNo<\/td>\nAny<\/td>\nAny<\/td>\nDecline (Inactive Account)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The real power of this approach is that it becomes a living specification. Every stakeholder\u2014from developers to compliance officers\u2014can align on what \u201capproved\u201d means.<\/p>\n

Modeling Authentication States with UML State Diagrams<\/h2>\n

Authentication isn\u2019t a single step. It\u2019s a lifecycle. In any secure UML architecture, you must model the progression of a user\u2019s session.<\/p>\n

Think of it this way: a user logs in via username and password \u2014 that\u2019s the first state. Then they must complete MFA \u2014 a transition. Once verified, they enter an authenticated state. But if they\u2019re inactive for 15 minutes, they\u2019re automatically logged out.<\/p>\n

Here\u2019s how to model that in a UML state diagram:<\/p>\n

    \n
  • Initial State:<\/strong> Unauthenticated<\/li>\n
  • Transition 1:<\/strong> Enter credentials \u2192 Authenticated (with 2FA)<\/li>\n
  • Transition 2:<\/strong> Idle for 15 min \u2192 Timeout \u2192 Return to Unauthenticated<\/li>\n
  • Exception:<\/strong> Failed 2FA attempts \u2192 Lockout state (after 5 attempts)<\/li>\n<\/ul>\n

    This visual state flow prevents over-engineering. You can\u2019t miss a guard condition or fail to handle a timeout.<\/p>\n

    Why This Matters in Real Banking Systems<\/h3>\n

    One bank I consulted with had a critical flaw: the 2FA verification was checked at the wrong point in the transaction flow. The system would approve the transaction before verifying MFA, leading to multiple unauthorized transfers.<\/p>\n

    After introducing a state diagram and integrating it with the transaction sequence diagram, the team caught the flaw in the design phase\u2014saving weeks of debugging.<\/p>\n

    Integrating Decision Tables into UML Sequence Diagrams<\/h2>\n

    Decision tables aren\u2019t standalone. They feed into the behavioral models that drive execution.<\/p>\n

    Use a sequence diagram to show the flow from login \u2192 MFA check \u2192 transaction request \u2192 decision table evaluation \u2192 response.<\/p>\n

    Here\u2019s a simplified sequence example:<\/p>\n

      \n
    1. User sends transaction request<\/li>\n
    2. System checks user\u2019s authentication state<\/li>\n
    3. If not authenticated, redirect to login<\/li>\n
    4. If authenticated, apply decision table rules<\/li>\n
    5. Based on result, approve, decline, or challenge<\/li>\n
    6. Send confirmation to user<\/li>\n<\/ol>\n

      The decision table becomes the gatekeeper\u2014no more hidden logic in conditionals.<\/p>\n

      Best Practices for Secure UML Architecture in Banking Systems<\/h2>\n

      Building a secure UML architecture isn\u2019t about adding more diagrams. It\u2019s about choosing the right ones and using them with intent.<\/p>\n

      Here\u2019s what I\u2019ve seen work consistently across multiple financial platforms:<\/p>\n

        \n
      1. Start with use cases.<\/strong> Define \u201cProcess Transaction,\u201d \u201cEnforce MFA,\u201d \u201cDetect Fraud\u201d to capture functional needs.<\/li>\n
      2. Use decision tables for business rules.<\/strong> Especially those involving thresholds, eligibility, and risk levels.<\/li>\n
      3. Model authentication states explicitly.<\/strong> A state diagram prevents forgetting session timeouts or lockout logic.<\/li>\n
      4. Link decision tables to sequence diagrams.<\/strong> Make it clear when and how business rules are applied.<\/li>\n
      5. Validate with stakeholders.<\/strong> Have compliance and security teams review decision tables\u2014this prevents legal exposure down the line.<\/li>\n<\/ol>\n

        These steps aren\u2019t just best practices. They\u2019re survival mechanisms in an industry where a single flawed rule can cost millions.<\/p>\n

        Common Pitfalls in Banking UML Modeling<\/h2>\n

        Even with the best intentions, teams fall into traps that undermine both clarity and security.<\/p>\n

          \n
        • Overloading class diagrams.<\/strong> Too many attributes and operations in an Account class make it hard to spot violations.<\/li>\n
        • Ignoring state transitions.<\/strong> A user is either logged in or not\u2014no in-between. But real systems need to handle \u201cpending MFA,\u201d \u201clocked,\u201d or \u201csuspended\u201d states.<\/li>\n
        • Using decision tables only for simple logic.<\/strong> They work best for rules with 3+ conditions. Don\u2019t create one for \u201cif balance > 0, allow transaction\u201d\u2014that\u2019s better as code.<\/li>\n
        • Isolating diagrams.<\/strong> A sequence diagram without a decision table is a promise that may not be kept.<\/li>\n<\/ul>\n

          These are not mistakes in UML syntax. They\u2019re failures in modeling intent.<\/p>\n

          Frequently Asked Questions<\/h2>\n

          Why should I use decision tables instead of code for rules?<\/h3>\n

          Because decision tables separate business logic from execution. You can test them independently, validate them with auditors, and even hand them off to a business analyst for review. Code changes are far more brittle, and errors get buried in nested conditionals.<\/p>\n

          Can I generate code directly from a decision table in Visual Paradigm?<\/h3>\n

          Yes. Visual Paradigm supports code generation from decision tables into Java, C#, or Python. The generated logic includes guard conditions and decision outcomes, making it easy to integrate into your transaction service layer.<\/p>\n

          How do I model fraud detection in a UML banking system?<\/h3>\n

          Use a combination of state diagrams (for user session states) and decision tables (for transaction rules). Add a \u201cfraud risk assessment\u201d state after transaction submission. The decision table can evaluate velocity, location, and amount. If risk score exceeds threshold, trigger a manual review.<\/p>\n

          Is it necessary to model every authentication state?<\/h3>\n

          Yes. Missing states like \u201clocked,\u201d \u201csuspended,\u201d or \u201cMFA challenge pending\u201d leads to security gaps. A state diagram ensures no state is forgotten, especially in high-stakes systems.<\/p>\n

          How often should I update decision tables in a banking UML system?<\/h3>\n

          At least quarterly, or whenever business rules change. Use version control for your models\u2014Visual Paradigm integrates with Git. This way, any change is traceable and auditable.<\/p>\n

          Can decision tables be used in microservices architecture?<\/h3>\n

          Absolutely. In a transactional microservice, the decision table can be embedded in the service itself or shared via API contract. Use a decision engine (like Drools) to execute the logic. This keeps the business rules decoupled from the service implementation.<\/p>\n","protected":false},"excerpt":{"rendered":"

          When designing a ban […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1409,"menu_order":2,"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-1412","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nUML Banking System: Secure Transaction Modeling<\/title>\n<meta name=\"description\" content=\"Master secure UML banking system design with real-world decision tables, authentication states, and architecture patterns. Learn how to model transaction workflows effectively using proven banking UML modeling and secure UML architecture techniques.\" \/>\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\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"UML Banking System: Secure Transaction Modeling\" \/>\n<meta property=\"og:description\" content=\"Master secure UML banking system design with real-world decision tables, authentication states, and architecture patterns. Learn how to model transaction workflows effectively using proven banking UML modeling and secure UML architecture techniques.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9810\u4f30\u95b1\u8b80\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 \u5206\u9418\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/\",\"name\":\"UML Banking System: Secure Transaction Modeling\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-02-25T10:40:57+00:00\",\"description\":\"Master secure UML banking system design with real-world decision tables, authentication states, and architecture patterns. Learn how to model transaction workflows effectively using proven banking UML modeling and secure UML architecture techniques.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Real-World UML: Case Studies in Software Design\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Real-World UML Case Studies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Case Study #3 \u2013 Banking Transaction and Security Platform\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-TW\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-TW\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"UML Banking System: Secure Transaction Modeling","description":"Master secure UML banking system design with real-world decision tables, authentication states, and architecture patterns. Learn how to model transaction workflows effectively using proven banking UML modeling and secure UML architecture techniques.","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\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/","og_locale":"zh_TW","og_type":"article","og_title":"UML Banking System: Secure Transaction Modeling","og_description":"Master secure UML banking system design with real-world decision tables, authentication states, and architecture patterns. Learn how to model transaction workflows effectively using proven banking UML modeling and secure UML architecture techniques.","og_url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/","og_site_name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"6 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/","name":"UML Banking System: Secure Transaction Modeling","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-02-25T10:40:57+00:00","description":"Master secure UML banking system design with real-world decision tables, authentication states, and architecture patterns. Learn how to model transaction workflows effectively using proven banking UML modeling and secure UML architecture techniques.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-banking-system-secure-transaction-modeling\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/tw\/"},{"@type":"ListItem","position":2,"name":"Real-World UML: Case Studies in Software Design","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/"},{"@type":"ListItem","position":3,"name":"Real-World UML Case Studies","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/"},{"@type":"ListItem","position":4,"name":"Case Study #3 \u2013 Banking Transaction and Security Platform"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website","url":"https:\/\/skills.visual-paradigm.com\/tw\/","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-TW"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/tw\/","logo":{"@type":"ImageObject","inLanguage":"zh-TW","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1412","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1412\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1409"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=1412"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=1412"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}