{"id":1136,"date":"2026-02-25T10:36:43","date_gmt":"2026-02-25T10:36:43","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/"},"modified":"2026-02-25T10:36:43","modified_gmt":"2026-02-25T10:36:43","slug":"dfd-symbols-data-flow-diagram-notation","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/","title":{"rendered":"The Language of DFDs: Symbols, Conventions, and Standards"},"content":{"rendered":"

One of the most common early missteps I see in novice modelers is not recognizing that a broken DFD isn\u2019t always a flaw in logic\u2014it\u2019s often a failure to speak the language consistently. A single misused symbol or inconsistent flow direction can create confusion, even if the underlying process is correct. This happens because DFDs are not just diagrams\u2014they\u2019re a formal language. The moment you deviate from agreed-upon DFD symbols, the model loses its precision and becomes a barrier to communication.<\/p>\n

For over two decades, I\u2019ve worked with teams across banking, healthcare, and government sectors where misunderstandings between business analysts, developers, and stakeholders stemmed not from poor ideas, but from poor notation. The fix? Commit to a consistent, well-documented set of DFD symbols and conventions from day one. This chapter gives you the exact tools to do that\u2014grounded in real-world experience, aligned with Gane & Sarson and Yourdon standards, and designed to make your diagrams both accurate and maintainable.<\/p>\n

Core DFD Symbols: The Building Blocks<\/h2>\n

Every DFD begins with four foundational elements: processes, data stores, external entities, and data flows. These are not arbitrary symbols\u2014they are standardized representations of system behavior and data movement.<\/p>\n

Process: The Engine of Transformation<\/h3>\n

Processes represent actions that transform input data into output. They are always represented as rounded rectangles\u2014never circles or squares. The key is that every process must have at least one input and one output flow.<\/p>\n

Why this matters: I once reviewed a DFD where a process had no inputs. The developer claimed it \u201cgenerated data from nothing.\u201d That\u2019s not a process\u2014it\u2019s a contradiction in logic. Even in a hypothetical system, the data must come from somewhere. The process symbol enforces this rule.<\/p>\n

Labeling should be in imperative verb form: \u201cCalculate total,\u201d \u201cValidate user input,\u201d \u201cGenerate report.\u201d This ensures consistency and avoids ambiguity.<\/p>\n

Data Store: The Persistent Memory<\/h3>\n

The data store symbol\u2014two parallel horizontal lines with a rectangle above\u2014represents a collection of data that persists over time. It is not a database in the technical sense, but a logical holding area for data.<\/p>\n

The data store symbol meaning<\/strong> is critical: it signifies data that is not transient. If data moves through a process and disappears, it\u2019s not stored. If it remains available across multiple transactions, it\u2019s stored.<\/p>\n

Common mistake: Drawing data stores as databases. The symbol is abstract. Use it for \u201cCustomer Records,\u201d \u201cInvoice Log,\u201d or \u201cPending Approvals\u201d\u2014not \u201cMySQL Table Orders.\u201d This preserves model integrity.<\/p>\n

External Entity: The Source and Sink<\/h3>\n

External entities (also called actors) are represented by small, square boxes with a label. They represent stakeholders or systems outside the scope of the current DFD.<\/p>\n

They are not processes. They cannot act on data\u2014they only send or receive. A user clicking a button is not a process; the action of submitting data is.<\/p>\n

If your system receives data from a third-party API, the API is an external entity. If a report is emailed to a manager, the manager is an external entity.<\/p>\n

Data Flow: The Path of Movement<\/h3>\n

Data flows are arrows showing the direction of data movement. The arrowhead is always pointed at the destination.<\/p>\n

Every flow must connect a source (process, data store, or external entity) to a destination (process, data store, or external entity). Arrows should never loop back to their source without a clear operational reason.<\/p>\n

Flow labels are critical. Not just \u201cdata,\u201d but \u201ccustomer order details,\u201d \u201cpayment confirmation,\u201d or \u201cuser login request.\u201d Vague labels lead to ambiguity and inconsistent interpretation across teams.<\/p>\n

DFD Conventions: The Unwritten Rules<\/h2>\n

While the symbols are standardized, the way they are applied is governed by a set of conventions. These are not rigid rules, but best practices that ensure clarity and consistency.<\/p>\n

    \n
  • Left-to-right flow<\/strong>: It\u2019s best practice to design flows from left to right. This aligns with how most people read\u2014top to bottom, left to right. Avoid diagonal or circular data flows unless absolutely necessary.<\/li>\n
  • Use of arrows<\/strong>: Arrows should not cross each other. When unavoidable, break the flow into segments or reorganize the layout to maintain readability.<\/li>\n
  • Process numbering<\/strong>: In higher-level DFDs, use numbers (e.g., 1.1, 2.3) to maintain traceability when decomposing. This is especially useful for auditing or version control.<\/li>\n
  • Consistent labeling<\/strong>: Use the same term for the same data across all levels. If \u201cOrder Details\u201d is used in Level 1, don\u2019t call it \u201cOrder Items\u201d in Level 2. This ensures consistency and avoids confusion.<\/li>\n<\/ul>\n

    Why DFD Conventions Matter<\/h3>\n

    When I worked on a financial system audit, we found that three different analysts used different terms for the same data element\u2014\u201cInvoice,\u201d \u201cBill,\u201d and \u201cStatement.\u201d The data flow diagram notation wasn\u2019t wrong, but the inconsistency caused major delays during integration. Had they followed a consistent labeling convention from the start, the entire project would\u2019ve been more efficient.<\/p>\n

    These conventions are not about aesthetics. They are about minimizing ambiguity. A DFD is not just a diagram\u2014it\u2019s a contract between developers, analysts, and stakeholders.<\/p>\n

    Comparing Notation Standards: Gane & Sarson vs. Yourdon<\/h2>\n

    Two major standards govern DFD notation: Gane & Sarson and Yourdon. They are functionally equivalent but differ in visual style.<\/p>\n\n\n\n\n\n\n\n
    Element<\/th>\nGane & Sarson<\/th>\nYourdon<\/th>\n<\/tr>\n
    Process<\/td>\nRounded rectangle with process number<\/td>\nCircle with process name<\/td>\n<\/tr>\n
    Data Store<\/td>\nTwo parallel lines with box above<\/td>\nTwo parallel lines with label inside<\/td>\n<\/tr>\n
    External Entity<\/td>\nSmall rectangle<\/td>\nSmall rectangle with a label<\/td>\n<\/tr>\n
    Data Flow<\/td>\nArrow with label<\/td>\nArrow with label<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Both standards are valid. The key is consistency. If your team uses Gane & Sarson, stick with it across all diagrams. Don\u2019t mix styles within the same model.<\/p>\n

    My advice: Choose one standard and document it in your team\u2019s modeling guide. This prevents confusion and ensures all new members can contribute accurately from day one.<\/p>\n

    Data Flow Diagram Notation in Practice<\/h2>\n

    Let\u2019s walk through a real-world example: a university registration system.<\/p>\n

    Level 0 (Context Diagram)<\/strong>: The external entities are \u201cStudent\u201d and \u201cRegistrar System.\u201d The process is \u201cRegister Student.\u201d Data flows: \u201cRegistration Form\u201d (from student to process), \u201cEnrolled Course List\u201d (from process to registrar).<\/p>\n

    Level 1<\/strong>: Break down \u201cRegister Student\u201d into sub-processes:<\/p>\n

      \n
    • \u201cValidate Student Eligibility\u201d \u2013 input: \u201cStudent Record,\u201d output: \u201cEligibility Status\u201d<\/li>\n
    • \u201cCheck Course Availability\u201d \u2013 input: \u201cCourse List,\u201d output: \u201cAvailable Courses\u201d<\/li>\n
    • \u201cEnroll Student in Course\u201d \u2013 input: \u201cAvailable Courses,\u201d output: \u201cEnrollment Confirmation\u201d<\/li>\n<\/ul>\n

      Notice how each process has at least one input and one output. The data flow \u201cEligibility Status\u201d is not arbitrary\u2014it\u2019s a specific data object defined in the data dictionary.<\/p>\n

      This example illustrates how DFD symbols and conventions work together to enforce logic. You can\u2019t have a process that consumes data but produces nothing. That violates the principle of data balance.<\/p>\n

      Common Pitfalls and How to Avoid Them<\/h2>\n

      Even experienced modelers make these mistakes. Here\u2019s how to avoid them:<\/p>\n

        \n
      1. Creating processes with no inputs<\/strong>: Every process must have at least one input. If a process seems to generate data from nothing, re-evaluate: is there a data store or external entity providing the base data?<\/li>\n
      2. Confusing data stores with data flows<\/strong>: A data store holds data over time. A flow is movement. If data is being transferred, it\u2019s a flow. If it\u2019s being preserved, it\u2019s a store.<\/li>\n
      3. Using the same label for different data objects<\/strong>: \u201cInvoice\u201d might mean a document in one context and a number in another. Use precise, unambiguous labels.<\/li>\n
      4. Overloading processes with too many flows<\/strong>: If a process has more than 5\u20136 flows, it\u2019s likely too complex. Decompose it into smaller, focused processes.<\/li>\n<\/ol>\n

        Remember: clarity isn\u2019t just about looking good. It\u2019s about being interpretable by people who didn\u2019t build the model.<\/p>\n

        Frequently Asked Questions<\/h2>\n

        What is the correct symbol for a data store in DFD notation?<\/h3>\n

        The data store symbol is two horizontal parallel lines with a rectangle or label above. It represents a persistent collection of data. The symbol is consistent across both Gane & Sarson and Yourdon conventions.<\/p>\n

        Can data flows connect to external entities only?<\/h3>\n

        No. Data flows can originate from or terminate at a process, data store, or external entity. A flow from process to data store means data is being written. A flow from data store to process means data is being read.<\/p>\n

        How do I choose between Gane & Sarson and Yourdon conventions?<\/h3>\n

        Choose based on your organization\u2019s standard. Gane & Sarson is more common in business analysis. Yourdon is often used in academic settings. Pick one and apply it consistently.<\/p>\n

        Why is the data store symbol meaning so important to understand?<\/h3>\n

        Because it defines data persistence. If you think a data store is just a database, you\u2019ll incorrectly model transient data as stored. Understanding the data store symbol meaning<\/strong> ensures you represent data correctly across time.<\/p>\n

        Do DFDs require a data dictionary?<\/h3>\n

        Yes. A data dictionary defines every data flow, data store, and process. It\u2019s essential for DFD consistency, especially during balancing and decomposition.<\/p>\n

        What\u2019s the difference between a process and an external entity?<\/h3>\n

        A process performs work on data. An external entity sends or receives data but does not process it. For example, a \u201cStudent\u201d is an external entity; \u201cValidate ID\u201d is a process.<\/p>\n","protected":false},"excerpt":{"rendered":"

        One of the most common early missteps I see in novice modelers is not recognizing that a broken DFD isn\u2019t always a flaw in logic\u2014it\u2019s often a failure to speak the language consistently. A single misused symbol or inconsistent flow direction can create confusion, even if the underlying process is correct. This happens because DFDs […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1132,"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-1136","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nDFD Symbols: Mastering Data Flow Diagram Notation<\/title>\n<meta name=\"description\" content=\"Learn the essential DFD symbols, conventions, and standards for accurate data flow diagram notation. Master process, data store, and flow representation using Gane & Sarson and Yourdon methods.\" \/>\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\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/\" \/>\n<meta property=\"og:locale\" content=\"vi_VN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DFD Symbols: Mastering Data Flow Diagram Notation\" \/>\n<meta property=\"og:description\" content=\"Learn the essential DFD symbols, conventions, and standards for accurate data flow diagram notation. Master process, data store, and flow representation using Gane & Sarson and Yourdon methods.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u01af\u1edbc t\u00ednh th\u1eddi gian \u0111\u1ecdc\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 ph\u00fat\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/\",\"name\":\"DFD Symbols: Mastering Data Flow Diagram Notation\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#website\"},\"datePublished\":\"2026-02-25T10:36:43+00:00\",\"description\":\"Learn the essential DFD symbols, conventions, and standards for accurate data flow diagram notation. Master process, data store, and flow representation using Gane & Sarson and Yourdon methods.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/#breadcrumb\"},\"inLanguage\":\"vi\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/vn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering Data Flow Diagram Levels and Balancing\",\"item\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Core Concepts and Foundations\",\"item\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"The Language of DFDs: Symbols, Conventions, and Standards\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/vn\/\",\"name\":\"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/vn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"vi\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#organization\",\"name\":\"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t\",\"url\":\"https:\/\/skills.visual-paradigm.com\/vn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"vi\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/vn\/wp-content\/uploads\/sites\/11\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/vn\/wp-content\/uploads\/sites\/11\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DFD Symbols: Mastering Data Flow Diagram Notation","description":"Learn the essential DFD symbols, conventions, and standards for accurate data flow diagram notation. Master process, data store, and flow representation using Gane & Sarson and Yourdon methods.","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\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/","og_locale":"vi_VN","og_type":"article","og_title":"DFD Symbols: Mastering Data Flow Diagram Notation","og_description":"Learn the essential DFD symbols, conventions, and standards for accurate data flow diagram notation. Master process, data store, and flow representation using Gane & Sarson and Yourdon methods.","og_url":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/","og_site_name":"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t","twitter_card":"summary_large_image","twitter_misc":{"\u01af\u1edbc t\u00ednh th\u1eddi gian \u0111\u1ecdc":"8 ph\u00fat"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/","url":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/","name":"DFD Symbols: Mastering Data Flow Diagram Notation","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/vn\/#website"},"datePublished":"2026-02-25T10:36:43+00:00","description":"Learn the essential DFD symbols, conventions, and standards for accurate data flow diagram notation. Master process, data store, and flow representation using Gane & Sarson and Yourdon methods.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/#breadcrumb"},"inLanguage":"vi","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/dfd-symbols-data-flow-diagram-notation\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/vn\/"},{"@type":"ListItem","position":2,"name":"Mastering Data Flow Diagram Levels and Balancing","item":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/"},{"@type":"ListItem","position":3,"name":"Core Concepts and Foundations","item":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/core-concepts-and-foundations\/"},{"@type":"ListItem","position":4,"name":"The Language of DFDs: Symbols, Conventions, and Standards"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/vn\/#website","url":"https:\/\/skills.visual-paradigm.com\/vn\/","name":"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/vn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/vn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"vi"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/vn\/#organization","name":"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t","url":"https:\/\/skills.visual-paradigm.com\/vn\/","logo":{"@type":"ImageObject","inLanguage":"vi","@id":"https:\/\/skills.visual-paradigm.com\/vn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/vn\/wp-content\/uploads\/sites\/11\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/vn\/wp-content\/uploads\/sites\/11\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/vn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/docs\/1136","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/docs\/1136\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/docs\/1132"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/media?parent=1136"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/doc_tag?post=1136"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}