{"id":790,"date":"2026-02-25T10:24:56","date_gmt":"2026-02-25T10:24:56","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/"},"modified":"2026-02-25T10:24:56","modified_gmt":"2026-02-25T10:24:56","slug":"dfd-vs-uml-strengths","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/","title":{"rendered":"Core Strengths and Limitations of Each Approach"},"content":{"rendered":"

When I began my career, I assumed every system needed both DFDs and UML diagrams\u2014like a dual engine. But experience taught me the truth: not every problem needs two models<\/strong>. DFDs and UML serve different purposes. One focuses on data transformation across processes; the other on object behavior and relationships.<\/p>\n

DFD excels when the core challenge is understanding how data flows through a system\u2014especially in batch processing, compliance reporting, or audit trails. UML shines when systems depend on complex object interactions, state changes, or real-time behavior.<\/p>\n

But the real insight? Choosing between them isn\u2019t about preference\u2014it\u2019s about context<\/strong>. A financial system may need DFD for transaction lineage, while an e-commerce platform demands UML to model session states and cart logic. This chapter dissects their strengths and limits, based on real projects\u2014no theoretical fluff.<\/p>\n

By the end, you\u2019ll know when to trust DFD\u2019s simplicity and when UML\u2019s power becomes unavoidable. You\u2019ll also recognize when over-modeling with UML leads to confusion\u2014something I\u2019ve seen derail multiple projects.<\/p>\n

Expressive Power: What Each Notation Handles Well<\/h2>\n

Each notation has its domain of excellence.<\/p>\n

    \n
  • DFD strength<\/strong>: Visualizing data transformation across processes. Ideal for tracking how a customer\u2019s order moves from input to invoice, passing through validation, pricing, and shipping.<\/li>\n
  • UML strength<\/strong>: Modeling object behavior, relationships, and lifecycle. Perfect for systems where objects like ShoppingCart<\/code>, UserSession<\/code>, or PaymentProcessor<\/code> interact in complex ways.<\/li>\n<\/ul>\n

    One project involved a claims processing system. The business team couldn\u2019t understand UML sequence diagrams with 12 actors and 30 messages. We replaced it with a Level 1 DFD: the data flow from claim submission to approval was clear, traceable, and validated in days.<\/p>\n

    Conversely, when a healthcare software team tried to model a patient\u2019s clinical journey with a single DFD, the model became a tangled mess of data flows. Only when we switched to UML state machines and activity diagrams did we capture the real-time decision points, timeouts, and transitions between care stages.<\/p>\n

    When Data Flow Wins: DFD\u2019s Expressive Advantage<\/h3>\n

    DFD\u2019s power lies in end-to-end data lineage<\/strong>. It answers: Where does this data come from? Where does it go? What transforms it?<\/em><\/p>\n

      \n
    • Regulatory compliance (SOX, HIPAA): DFDs show exactly how patient or financial data passes through systems.<\/li>\n
    • Legacy systems: DFDs reveal data movement patterns that UML often obscures.<\/li>\n
    • Batch processes: A nightly report generation process is best modeled as a DFD process transforming input data into output.<\/li>\n<\/ul>\n

      In a banking modernization project, we used DFD Level 0 to map the core transaction flow from ATM input to ledger update. The clarity was immediate\u2014developers and auditors agreed on the path.<\/p>\n

      When Object Behavior Wins: UML\u2019s Expressive Advantage<\/h3>\n

      UML\u2019s strength is in modeling object collaboration<\/strong>. It answers: Who is responsible? What do objects do when they interact? How does state change over time?<\/em><\/p>\n

        \n
      • Real-time systems: UML statecharts and timing diagrams capture transitions and timeouts.<\/li>\n
      • Microservices orchestration: Sequence diagrams show how services call each other.<\/li>\n
      • Business logic with decision trees: Activity diagrams model complex workflows.<\/li>\n<\/ul>\n

        When a retail client modeled their cart system with DFD, they had 12 processes and 7 data stores. It was hard to track if a user\u2019s cart was \u201cactive\u201d or \u201cexpired.\u201d UML class and sequence diagrams clarified object ownership, state transitions, and expiry logic in one diagram.<\/p>\n

        Scalability and Practical Limits<\/h2>\n

        Both notations have natural limits. Understanding them prevents over-engineering.<\/p>\n\n\n\n\n\n\n\n
        Factor<\/th>\nDFD<\/th>\nUML<\/th>\n<\/tr>\n<\/thead>\n
        Scalability Threshold<\/strong><\/td>\nMore than 15\u201320 processes and 10 data stores become hard to manage visually.<\/td>\nMore than 50+ classes or 10+ sequence diagrams overwhelm most teams.<\/td>\n<\/tr>\n
        Common Failure Point<\/strong><\/td>\nProcesses become abstract or invisible. Users lose sight of data transformation.<\/td>\nSequence diagrams become overly detailed, losing focus on intent.<\/td>\n<\/tr>\n
        Real Project Example<\/strong><\/td>\nInsurance claims: DFD failed at Level 2 with 18 subprocesses.<\/td>\nE-commerce: UML sequence diagrams with 60+ messages confused business stakeholders.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

        On a healthcare system, we attempted to model a patient\u2019s entire journey through 22 DFD processes. The result was a 4-meter-wide printout no one could read. We stepped back, segmented the process, and used UML for the high-complexity parts.<\/p>\n

        Another team used UML activity diagrams to model a 200-step approval workflow. It became unreadable. We simplified it into three DFD processes: Initiate Request<\/code>, Route for Approval<\/code>, and Finalize<\/code>. The business loved it.<\/p>\n

        When DFD Fails: The Limits of Data Flow Diagrams<\/h3>\n

        DFD excels at data movement but struggles with:<\/p>\n

          \n
        • State changes<\/strong>: DFD doesn\u2019t model object state. A Payment<\/code> object being \u201cpending,\u201d \u201capproved,\u201d or \u201cfailed\u201d isn\u2019t captured.<\/li>\n
        • Behavioral logic<\/strong>: Conditional rules, exceptions, retries, and timeouts are implicit, not explicit.<\/li>\n
        • Object identity<\/strong>: Two data flows with the same name may represent different objects\u2014DFD doesn\u2019t distinguish.<\/li>\n<\/ul>\n

          When I worked on a payment gateway, DFD couldn\u2019t show that a transaction could be \u201cretried three times\u201d before failing. That required UML state machines.<\/p>\n

          When UML Fails: The Pitfalls of Over-Modeling<\/h3>\n

          UML has its own limitations:<\/p>\n

            \n
          • Cognitive overload<\/strong>: A single sequence diagram with more than 15 messages loses its value for non-technical stakeholders.<\/li>\n
          • Too many abstractions<\/strong>: Classes like OrderProcessorService<\/code> or PaymentValidationEngine<\/code> can hide real behaviors.<\/li>\n
          • Not for high-level structure<\/strong>: UML is poor at showing system boundaries and data exchange patterns.<\/li>\n<\/ul>\n

            Once, a team insisted on UML class diagrams for a simple form submission. The model had 47 classes\u2014none of which were used in code. It was a modeling artifact, not a design aid.<\/p>\n

            when UML modeling fails<\/strong> most often when it\u2019s used to replace clarity with complexity. The goal is not to fit every detail into a diagram, but to show intent.<\/p>\n

            Cognitive Load and Learning Curve<\/h2>\n

            Learning DFD is fast\u2014most analysts grasp Level 0 in a day. UML takes weeks.<\/p>\n

            But learning isn\u2019t just about time. It\u2019s about cost.<\/p>\n

              \n
            • DFD<\/strong>: Simple symbols, no inheritance, no polymorphism. Easy to teach to business analysts and auditors.<\/li>\n
            • UML<\/strong>: Requires understanding of class relationships, multiplicity, interfaces, and lifelines. Misuse is common.<\/li>\n<\/ul>\n

              One team spent two weeks training new hires on UML. They still confused association<\/code> with aggregation<\/code>. We switched to DFD for initial modeling, then introduced UML only where needed.<\/p>\n

              Even experienced developers struggle with UML notation limitations: the ambiguity in association vs dependency, or when to use composition over aggregation. These aren\u2019t teaching issues\u2014they\u2019re design flaws in the notation.<\/p>\n

              Tool Ecosystem and Maintenance<\/h2>\n

              Tooling affects not just modeling, but maintenance.<\/p>\n

              But tool maturity isn\u2019t the only factor.<\/p>\n

              On a government project, we used Visual Paradigm to maintain both DFD and UML models. The key was layering<\/strong>: DFD for data flow, UML for object behavior. We linked them using traceability matrices.<\/p>\n

              When tools don\u2019t support cross-model navigation\u2014like when a DFD process references a UML class\u2014the model becomes siloed. That\u2019s when maintenance breaks down.<\/p>\n

              My advice: use one tool that supports both<\/strong>. Don\u2019t mix incompatible tools. A single workspace keeps models synchronized.<\/p>\n

              Frequently Asked Questions<\/h2>\n

              When should I use DFD instead of UML?<\/h3>\n

              Choose DFD when the primary goal is understanding data transformation, especially in compliance, batch processing, or legacy systems. Use it to answer: \u201cWhere does this data come from and where does it go?\u201d<\/p>\n

              When does UML become too complex?<\/h3>\n

              UML modeling fails when diagrams exceed 15 messages (sequence), 50 classes (class diagram), or 10 state transitions (statechart). When stakeholders can\u2019t follow it, you\u2019ve crossed the line.<\/p>\n

              Can I use both in the same project?<\/h3>\n

              Absolutely. Use DFD for high-level data flow (e.g., context diagram), and UML for detailed design (e.g., sequence diagrams). The key is consistency: map DFD processes to UML use cases, data stores to classes, and flows to messages.<\/p>\n

              What if my team doesn\u2019t understand UML?<\/h3>\n

              Start with DFD. Use it to model the core flow. Then, only introduce UML where object behavior matters\u2014like session management or payment processing. Simplify. Communicate. Iterate.<\/p>\n

              Is DFD still relevant in modern software?<\/h3>\n

              Yes. In microservices, DFDs help visualize data flow between services. In compliance, they provide audit trails. DFD isn\u2019t outdated\u2014it\u2019s underused.<\/p>\n

              How do I decide between DFD and UML early in a project?<\/h3>\n

              Ask: Is the problem about data movement or object behavior? If data flow is central, use DFD. If object collaboration and state matter, use UML. If unsure, start with DFD\u2014it\u2019s simpler and faster to validate.<\/p>\n","protected":false},"excerpt":{"rendered":"

              When I began my career, I assumed every system needed both DFDs and UML diagrams\u2014like a dual engine. But experience taught me the truth: not every problem needs two models. DFDs and UML serve different purposes. One focuses on data transformation across processes; the other on object behavior and relationships. DFD excels when the core […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":787,"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-790","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nDFD vs UML Strengths: Practical Comparison<\/title>\n<meta name=\"description\" content=\"Compare DFD vs UML strengths: when data flow clarity wins, when object modeling excels. Real-world advice for choosing the right notation for your system design.\" \/>\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\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DFD vs UML Strengths: Practical Comparison\" \/>\n<meta property=\"og:description\" content=\"Compare DFD vs UML strengths: when data flow clarity wins, when object modeling excels. Real-world advice for choosing the right notation for your system design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/\",\"name\":\"DFD vs UML Strengths: Practical Comparison\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:24:56+00:00\",\"description\":\"Compare DFD vs UML strengths: when data flow clarity wins, when object modeling excels. Real-world advice for choosing the right notation for your system design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data Flow Diagrams vs. UML: When to Use Each\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Understanding the Methodologies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Core Strengths and Limitations of Each Approach\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DFD vs UML Strengths: Practical Comparison","description":"Compare DFD vs UML strengths: when data flow clarity wins, when object modeling excels. Real-world advice for choosing the right notation for your system design.","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\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/","og_locale":"pt_PT","og_type":"article","og_title":"DFD vs UML Strengths: Practical Comparison","og_description":"Compare DFD vs UML strengths: when data flow clarity wins, when object modeling excels. Real-world advice for choosing the right notation for your system design.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/","name":"DFD vs UML Strengths: Practical Comparison","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:24:56+00:00","description":"Compare DFD vs UML strengths: when data flow clarity wins, when object modeling excels. Real-world advice for choosing the right notation for your system design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/dfd-vs-uml-strengths\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"Data Flow Diagrams vs. UML: When to Use Each","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/"},{"@type":"ListItem","position":3,"name":"Understanding the Methodologies","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/dfd-vs-uml-when-to-use-each\/understanding-the-methodologies\/"},{"@type":"ListItem","position":4,"name":"Core Strengths and Limitations of Each Approach"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/790","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/790\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/787"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=790"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=790"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}