{"id":352,"date":"2026-02-25T10:16:39","date_gmt":"2026-02-25T10:16:39","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/"},"modified":"2026-02-25T10:16:39","modified_gmt":"2026-02-25T10:16:39","slug":"why-bpmn-has-multiple-diagram-types","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/","title":{"rendered":"Why BPMN Has Multiple Diagram Types"},"content":{"rendered":"

When I first encountered BPMN, I assumed one diagram would cover everything. That expectation lasted until I tried to explain a multi-party order process to a vendor, a finance team, and a developer \u2014 all at once. The result? Confusion, misalignment, and wasted time.<\/p>\n

That moment taught me a hard truth: no single diagram can serve every purpose. Not even close.<\/p>\n

Why does BPMN define multiple diagram types instead of one unified view? Because different people need different levels of detail, different perspectives, and different ways of seeing the same process.<\/p>\n

The purpose of BPMN diagram types is not to complicate modeling. It\u2019s to make it purposeful. Each diagram type answers a specific question: Who does what? How do they interact? What messages are exchanged? What\u2019s the big picture?<\/p>\n

As someone who\u2019s guided over 50 process transformation initiatives, I\u2019ve seen teams struggle not because they didn\u2019t know BPMN, but because they used the wrong diagram for the wrong audience. The real power of BPMN lies in choosing the right view at the right time.<\/p>\n

In this chapter, you\u2019ll learn why BPMN has multiple diagram types \u2014 not as a technical redundancy, but as a strategic design choice. We\u2019ll explore the four core types, when to use each, and how they work together to deliver clarity across organizations.<\/p>\n

The Core Reason: Stakeholders Demand Different Views<\/h2>\n

Let\u2019s start with a simple truth: people don\u2019t think in process flows.<\/p>\n

Executives think in outcomes and dependencies. Developers think in interfaces and triggers. Operations teams think in handoffs and delays. A customer service agent cares about the next step \u2014 not the one after that.<\/p>\n

That\u2019s why BPMN has multiple diagram types. Each one maps to a distinct stakeholder perspective.<\/p>\n

Imagine a loan approval process. To a business analyst, the internal steps matter most. To a bank\u2019s IT team, the API calls and system handoffs are critical. To a partner bank, only the message exchanges matter.<\/p>\n

One diagram can\u2019t satisfy all three. That\u2019s the core of BPMN\u2019s design philosophy: align the diagram type with the audience\u2019s intent<\/strong>.<\/p>\n

When you use the right diagram type, you\u2019re not just drawing shapes \u2014 you\u2019re speaking the right language to the right person.<\/p>\n

BPMN Views and Perspectives: The Foundation of Clarity<\/h3>\n

Think of BPMN diagram types as different lenses. Each one focuses on a specific aspect of a process.<\/p>\n

For example, a process diagram zooms in on internal logic \u2014 the sequence of activities within one organization. A collaboration diagram shows how multiple parties interact. A choreography diagram defines the expected message order between participants, regardless of internal structure. A conversation diagram summarizes all this into high-level communication topics.<\/p>\n

These aren\u2019t arbitrary categories. They\u2019re rooted in real-world modeling needs.<\/p>\n

When I worked on a cross-border procurement project, we used a collaboration diagram to clarify responsibilities between procurement, legal, and supplier teams. The same process, modeled in a single pool, would have buried those boundaries under layers of internal steps.<\/p>\n

So, the purpose of BPMN diagram types is to reduce ambiguity by matching the view to the question being asked<\/strong>.<\/p>\n

The Four Core BPMN Diagram Types: A Conceptual Overview<\/h2>\n

Let\u2019s break down the four main diagram types at a high level. You don\u2019t need to memorize every symbol yet \u2014 just understand what each one is for.<\/p>\n

1. Process Diagram: The Internal Workflow Blueprint<\/h3>\n

This is the most common type. It models a single participant\u2019s internal process \u2014 a private process, as BPMN calls it.<\/p>\n

Think of it as a script for one actor: start, do this, make a decision, do that, end. It includes events, activities, gateways, and sequence flows \u2014 all within one pool.<\/p>\n

Use this when you\u2019re documenting how a team performs a task, or when preparing a model for automation.<\/p>\n

2. Collaboration Diagram: The Interaction Map<\/h3>\n

This diagram shows how multiple participants work together. It uses pools to represent each participant and message flows to show communication.<\/p>\n

It\u2019s ideal for cross-functional or cross-organizational workflows. You\u2019ll see it often in B2B processes, shared services, or departmental handoffs.<\/p>\n

Unlike a process diagram, it doesn\u2019t show internal steps \u2014 only who sends what to whom.<\/p>\n

3. Choreography Diagram: The Message Sequence Contract<\/h3>\n

This is where things get interesting. A choreography diagram defines the expected message exchange order between participants \u2014 without revealing their internal logic.<\/p>\n

It\u2019s like a contract: \u201cYou send this, then I send that, then you respond.\u201d It\u2019s used in service contracts, API specifications, or when partners need to agree on behavior without sharing internal design.<\/p>\n

It\u2019s especially powerful when you\u2019re not in control of the other participant\u2019s process.<\/p>\n

4. Conversation Diagram: The Big-Picture Communication Map<\/h3>\n

This is the executive view. It groups related message exchanges into conversation nodes \u2014 high-level summaries of who talks to whom about what.<\/p>\n

Use this to present an overview of complex systems to stakeholders who don\u2019t need the details. It\u2019s perfect for value chain mapping, enterprise architecture, or onboarding new teams.<\/p>\n

It\u2019s not about what happens \u2014 it\u2019s about what\u2019s being discussed.<\/p>\n

Why One Diagram Isn\u2019t Enough: The Trade-Offs of Clutter and Confusion<\/h2>\n

Let\u2019s be honest: modeling a process with just one diagram is tempting. It feels simpler. But it\u2019s a trap.<\/p>\n

When you try to show internal logic, external interactions, and message sequences in one diagram, you create visual noise. The result? Readers can\u2019t tell what\u2019s important.<\/p>\n

Here\u2019s a real example: a hospital\u2019s patient admission process. If you try to show the nurse\u2019s steps, the lab\u2019s work, the billing system\u2019s triggers, and the patient\u2019s notifications in one diagram, you\u2019ll end up with a spaghetti-like mess.<\/p>\n

Instead, use a process diagram for the nurse\u2019s workflow. A collaboration diagram to show how the lab and nurse exchange test results. A choreography diagram to define the expected message order between systems. And a conversation diagram to show the key communication topics: \u201ctest request,\u201d \u201cresults sent,\u201d \u201cbilling initiated.\u201d<\/p>\n

Each diagram answers a different question. Together, they form a complete picture.<\/p>\n

That\u2019s the power of having multiple diagram types. It\u2019s not about having more work \u2014 it\u2019s about doing the right work, for the right person.<\/p>\n

When to Use Each Diagram Type: A Decision Guide<\/h3>\n

Here\u2019s a simple decision tree to help you choose the right type:<\/p>\n

    \n
  • Use a Process Diagram<\/strong> when documenting internal steps, preparing for automation, or analyzing a single team\u2019s workflow.<\/li>\n
  • Use a Collaboration Diagram<\/strong> when clarifying interactions between departments, partners, or systems \u2014 especially when responsibilities are shared.<\/li>\n
  • Use a Choreography Diagram<\/strong> when defining message contracts, specifying external behavior, or working with systems you don\u2019t control.<\/li>\n
  • Use a Conversation Diagram<\/strong> when presenting an overview to executives, mapping a value chain, or summarizing complex communication patterns.<\/li>\n<\/ul>\n

    Remember: the goal isn\u2019t to model everything. It\u2019s to model what matters \u2014 to the right person.<\/p>\n

    How These Types Work Together: A Unified Modeling Approach<\/h2>\n

    One of the most common misconceptions is that these diagram types are separate. They\u2019re not. They\u2019re parts of a single, coherent model.<\/p>\n

    Think of them as layers: a process diagram is the foundation. A collaboration diagram adds the interaction layer. A choreography diagram defines the contract. A conversation diagram pulls it all together.<\/p>\n

    For example, in a claims handling process:<\/p>\n

      \n
    • The process diagram<\/strong> shows how an adjuster reviews a claim.<\/li>\n
    • The collaboration diagram<\/strong> shows how the adjuster, the insurer, and the repair shop exchange messages.<\/li>\n
    • The choreography diagram<\/strong> defines the expected message sequence: \u201cclaim submitted,\u201d \u201cadjustment requested,\u201d \u201crepair quote received,\u201d etc.<\/li>\n
    • The conversation diagram<\/strong> groups these into topics: \u201cClaim Initiation,\u201d \u201cAdjustment Review,\u201d \u201cRepair Coordination.\u201d<\/li>\n<\/ul>\n

      This layered approach ensures clarity at every level. It also makes the model easier to maintain \u2014 changes in one diagram can be traced and reflected in others.<\/p>\n

      Practical Tips for Using Multiple Diagram Types<\/h2>\n

      Here\u2019s what I\u2019ve learned from real-world modeling:<\/p>\n

        \n
      1. Start with the audience.<\/strong> Ask: Who will read this? What do they need to know?<\/li>\n
      2. Don\u2019t over-model.<\/strong> If a conversation diagram answers the question, don\u2019t create a collaboration diagram just because you can.<\/li>\n
      3. Use consistent naming.<\/strong> Participant names, message types, and interface names should match across diagrams.<\/li>\n
      4. Link diagrams where possible.<\/strong> In tools like Visual Paradigm, you can link a choreography task to a process step \u2014 creating traceability.<\/li>\n
      5. Review with stakeholders.<\/strong> Show each diagram to its intended audience. If they don\u2019t understand it, simplify or change the type.<\/li>\n<\/ol>\n

        These aren\u2019t rules. They\u2019re guidelines from experience. The real test is whether the diagram reduces confusion \u2014 not whether it looks complex or \u201ccomplete.\u201d<\/p>\n

        Frequently Asked Questions<\/h2>\n

        What is the purpose of BPMN diagram types?<\/h3>\n

        The purpose is to align modeling with stakeholder needs. Each diagram type serves a specific audience and answers a distinct question \u2014 whether it\u2019s internal logic, external interaction, message contracts, or high-level communication.<\/p>\n

        When should I use a BPMN process diagram vs a collaboration diagram?<\/h3>\n

        Use a process diagram when modeling internal steps within one organization. Use a collaboration diagram when showing how multiple parties interact \u2014 especially when responsibilities are distributed across pools.<\/p>\n

        Can I use more than one diagram type for the same process?<\/h3>\n

        Yes, and you should. A single business scenario can be modeled across multiple diagram types to serve different audiences. For example, a loan approval process can be shown as a process diagram (for operations), a collaboration diagram (for IT), and a conversation diagram (for executives).<\/p>\n

        How do BPMN views and perspectives differ?<\/h3>\n

        BPMN views refer to the different diagram types (process, collaboration, choreography, conversation). Perspectives refer to the mindset of the reader \u2014 e.g., operational, technical, strategic. The right diagram type helps you deliver the right perspective to the right person.<\/p>\n

        What\u2019s the difference between a choreography and a collaboration diagram?<\/h3>\n

        A collaboration diagram shows internal steps within each participant\u2019s process, plus message flows between them. A choreography diagram focuses only on the sequence of message exchanges, without revealing internal logic. It\u2019s a contract, not a blueprint.<\/p>\n

        Why does BPMN have multiple diagram types instead of one unified view?<\/h3>\n

        Because one size doesn\u2019t fit all. A unified view would either be too detailed for some audiences or too vague for others. Multiple diagram types allow you to tailor the level of abstraction, reduce clutter, and improve communication \u2014 which is the core goal of process modeling.<\/p>\n","protected":false},"excerpt":{"rendered":"

        When I first encountered BPMN, I assumed one diagram would cover everything. That expectation lasted until I tried to explain a multi-party order process to a vendor, a finance team, and a developer \u2014 all at once. The result? Confusion, misalignment, and wasted time. That moment taught me a hard truth: no single diagram can […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":351,"menu_order":0,"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-352","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nWhy BPMN Has Multiple Diagram Types<\/title>\n<meta name=\"description\" content=\"Discover the real reason why BPMN has multiple diagram types \u2014 to align with stakeholder needs, reduce complexity, and improve clarity. Learn how each type serves a unique purpose in process modeling.\" \/>\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\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why BPMN Has Multiple Diagram Types\" \/>\n<meta property=\"og:description\" content=\"Discover the real reason why BPMN has multiple diagram types \u2014 to align with stakeholder needs, reduce complexity, and improve clarity. Learn how each type serves a unique purpose in process modeling.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/\",\"name\":\"Why BPMN Has Multiple Diagram Types\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:16:39+00:00\",\"description\":\"Discover the real reason why BPMN has multiple diagram types \u2014 to align with stakeholder needs, reduce complexity, and improve clarity. Learn how each type serves a unique purpose in process modeling.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"BPMN Diagram Types Explained\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Understanding BPMN Diagram Types\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Why BPMN Has Multiple Diagram Types\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Why BPMN Has Multiple Diagram Types","description":"Discover the real reason why BPMN has multiple diagram types \u2014 to align with stakeholder needs, reduce complexity, and improve clarity. Learn how each type serves a unique purpose in process modeling.","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\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/","og_locale":"fr_FR","og_type":"article","og_title":"Why BPMN Has Multiple Diagram Types","og_description":"Discover the real reason why BPMN has multiple diagram types \u2014 to align with stakeholder needs, reduce complexity, and improve clarity. Learn how each type serves a unique purpose in process modeling.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/","name":"Why BPMN Has Multiple Diagram Types","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:16:39+00:00","description":"Discover the real reason why BPMN has multiple diagram types \u2014 to align with stakeholder needs, reduce complexity, and improve clarity. Learn how each type serves a unique purpose in process modeling.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/why-bpmn-has-multiple-diagram-types\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"BPMN Diagram Types Explained","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/"},{"@type":"ListItem","position":3,"name":"Understanding BPMN Diagram Types","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-diagram-types-explained\/bpmn-diagram-types-overview\/"},{"@type":"ListItem","position":4,"name":"Why BPMN Has Multiple Diagram Types"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/352","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/352\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/351"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=352"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=352"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}