{"id":1221,"date":"2026-02-25T10:37:36","date_gmt":"2026-02-25T10:37:36","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/"},"modified":"2026-02-25T10:37:36","modified_gmt":"2026-02-25T10:37:36","slug":"integrating-journey-bpmn-with-other-models","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/","title":{"rendered":"Integrating BPMN Journey Models with Other Diagrams"},"content":{"rendered":"<p>When a BPMN model feels disconnected from the systems it governs, I know the real work hasn\u2019t started\u2014only the surface has been scratched. I\u2019ve seen teams build elegant journey diagrams that stall at the interface between experience and execution. The missing thread? Integration with the systems that actually deliver the service.<\/p>\n<p>Most practitioners stop once they\u2019ve mapped the customer path. They\u2019ve captured touchpoints, emotions, and handoffs\u2014but what happens behind the scenes when a request arrives? Who owns the data? How do services interact? The answer isn\u2019t in the journey diagram. It\u2019s in the alignment between your BPMN model and other technical artifacts.<\/p>\n<p>This chapter isn\u2019t about choosing between models. It\u2019s about understanding how each contributes to the whole. You\u2019ll learn to bridge the gap between customer experience and system implementation\u2014using BPMN as the central thread that connects strategy, process, data, and architecture.<\/p>\n<h2>Why Integration Matters: Beyond the Siloed Diagram<\/h2>\n<p>Customer journey BPMN models are powerful\u2014but they\u2019re only one layer of a broader ecosystem. Without integration, they risk becoming artifacts that sit in a folder, admired but unused.<\/p>\n<p>Consider this: a customer clicks \u201cForgot Password.\u201d The BPMN shows a flow from request to email delivery. But who validates the email? What data is accessed? What happens if the user doesn\u2019t exist? These questions live in the database, not in the journey map.<\/p>\n<p>Effective integration ensures that every step in the customer journey is traceable to the underlying systems, data entities, and service boundaries. It turns a descriptive model into a living blueprint for execution.<\/p>\n<h2>Connecting BPMN Journeys to UML<\/h2>\n<p>UML (Unified Modeling Language) offers structure and semantics that BPMN alone can\u2019t provide. When modeling complex journeys\u2014like medical onboarding, enterprise software provisioning, or multi-step financial authorization\u2014UML class and sequence diagrams add clarity.<\/p>\n<p>Here\u2019s how to connect:<\/p>\n<ul>\n<li><strong>Map BPMN activities to UML operations<\/strong>: A \u201cVerify Identity\u201d step in BPMN can be linked to a method like <code>verifyUser(String id)<\/code> in a UML class diagram.<\/li>\n<li><strong>Align BPMN gateways with UML decision nodes<\/strong>: Use UML state machines to define when a journey moves from \u201cPending Verification\u201d to \u201cVerified\u201d or \u201cRejected.\u201d<\/li>\n<li><strong>Use UML collaborations to define service responsibilities<\/strong>: A \u201cProcess Payment\u201d flow can reference a UML component like <code>PaymentProcessor<\/code> with defined interfaces.<\/li>\n<\/ul>\n<p>Example: In a healthcare onboarding journey, the BPMN step \u201cCollect Patient Data\u201d maps to a UML class <code>PatientRecord<\/code> with attributes like <code>SSN<\/code>, <code>DOB<\/code>, and <code>EmergencyContact<\/code>. The <code>validate()<\/code> method in that class is triggered by the BPMN activity.<\/p>\n<h3>Practical Workflow: From BPMN to UML<\/h3>\n<p>Start with your BPMN journey model. For each major process step:<\/p>\n<ol>\n<li>Identify the object or service involved (e.g., \u201cCustomer Account\u201d).<\/li>\n<li>Define its data attributes and behaviors in a UML class diagram.<\/li>\n<li>Create a UML sequence diagram showing how the journey step interacts with that object.<\/li>\n<li>Link the BPMN activity to the UML operation via a shared identifier.<\/li>\n<\/ol>\n<p>This creates a traceable chain: customer action \u2192 BPMN step \u2192 UML method \u2192 system execution.<\/p>\n<h2>Linking Processes to Data Models<\/h2>\n<p>Every customer journey relies on data. But data isn\u2019t static\u2014it\u2019s transformed, validated, and stored across systems. ERD (Entity-Relationship Diagram) models reveal the structure behind the scenes.<\/p>\n<p>Integrating BPMN with ERD means mapping journey steps to data entities and their relationships. This isn\u2019t about copying entities into BPMN\u2014it\u2019s about anchoring where data is created, updated, or read.<\/p>\n<p>For example, in a purchase journey:<\/p>\n<ul>\n<li><strong>\u201cInitiate Checkout\u201d<\/strong> \u2192 creates a <code>Cart<\/code> entity.<\/li>\n<li><strong>\u201cApply Discount\u201d<\/strong> \u2192 queries <code>DiscountCode<\/code> and updates <code>Order<\/code>.<\/li>\n<li><strong>\u201cConfirm Payment\u201d<\/strong> \u2192 updates <code>PaymentStatus<\/code> in <code>Order<\/code> and creates <code>Transaction<\/code> record.<\/li>\n<\/ul>\n<p>These mapping rules ensure that when a journey step references \u201ccustomer data,\u201d it\u2019s clear which entity and attribute are involved.<\/p>\n<h3>Mapping Table: Journey Step to ERD Entity<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Journey Step<\/th>\n<th>ERD Entity<\/th>\n<th>Key Attributes<\/th>\n<th>Interaction Type<\/th>\n<\/tr>\n<tr>\n<td>Verify Email Address<\/td>\n<td>Customer<\/td>\n<td>Email, VerifiedStatus<\/td>\n<td>Read\/Update<\/td>\n<\/tr>\n<tr>\n<td>Submit Order<\/td>\n<td>Order<\/td>\n<td>OrderID, Total, CreatedAt<\/td>\n<td>Create<\/td>\n<\/tr>\n<tr>\n<td>Process Refund<\/td>\n<td>Refund<\/td>\n<td>RefundID, Amount, Status<\/td>\n<td>Create\/Update<\/td>\n<\/tr>\n<tr>\n<td>Update Profile<\/td>\n<td>Customer<\/td>\n<td>Address, PhoneNumber<\/td>\n<td>Update<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use consistent naming between BPMN and ERD\u2014for example, \u201cCustomer\u201d in both, not \u201cUser\u201d in BPMN and \u201cCustomer\u201d in ERD. This reduces confusion and strengthens traceability.<\/p>\n<h2>End-to-End Modeling from CX to Systems<\/h2>\n<p>True end-to-end modeling means starting with a customer\u2019s perception and ending with system-level behavior. It requires aligning BPMN with architectural views such as:<\/p>\n<ul>\n<li><strong>Application Architecture<\/strong>: Which application handles the step? (e.g., CRM, ERP, Portal)<\/li>\n<li><strong>Service Architecture<\/strong>: Is the step handled by a microservice, API, or internal workflow?<\/li>\n<li><strong>Data Architecture<\/strong>: Where is data stored? How is it secured and backed up?<\/li>\n<\/ul>\n<p>Here\u2019s a real example: a bank\u2019s \u201cOpen New Account\u201d journey.<\/p>\n<ul>\n<li><strong>BPMN Step<\/strong>: \u201cSubmit Application\u201d \u2192 triggers a message to the <code>AccountService<\/code>.<\/li>\n<li><strong>UML<\/strong>: <code>AccountService.createAccount()<\/code> accepts a <code>CustomerApplication<\/code> object.<\/li>\n<li><strong>ERD<\/strong>: A new <code>Account<\/code> record is created with <code>AccountNumber<\/code>, <code>Type<\/code>, <code>Status<\/code>.<\/li>\n<li><strong>Architecture<\/strong>: The <code>AccountService<\/code> is a RESTful microservice deployed on AWS Lambda.<\/li>\n<\/ul>\n<p>This integrated view ensures that when stakeholders ask, \u201cWhy does it take 48 hours to open an account?\u201d, the answer isn\u2019t just \u201cthe process is slow\u201d\u2014it\u2019s \u201cthe system queues requests, verifies identity via an external API, and creates the account only after compliance review.\u201d<\/p>\n<h3>Best Practices for Integration<\/h3>\n<ul>\n<li><strong>Use shared identifiers<\/strong>: Give BPMN activities, UML classes, and ERD entities the same unique ID (e.g., \u201cACCT-001\u201d) to enable traceability.<\/li>\n<li><strong>Document assumptions<\/strong>: Note in BPMN annotations why a step is handled by a specific service or data source.<\/li>\n<li><strong>Start with high-impact journeys<\/strong>: Prioritize integration for processes that directly affect customer satisfaction, such as support, onboarding, or renewal.<\/li>\n<li><strong>Use a model repository<\/strong>: Store BPMN, UML, ERD, and architecture diagrams in a single system (e.g., Visual Paradigm) for centralized access and navigation.<\/li>\n<\/ul>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Many teams fail at integration not for lack of effort, but because they treat models as isolated artifacts. Here are the traps\u2014and how to avoid them:<\/p>\n<ul>\n<li><strong>Overloading BPMN diagrams<\/strong>: Adding UML or ERD elements to BPMN makes it unreadable. Instead, use references or annotations to point to external models.<\/li>\n<li><strong>Inconsistent naming<\/strong>: \u201cCustomer\u201d in BPMN vs \u201cUser\u201d in ERD causes confusion. Agree on a shared vocabulary early.<\/li>\n<li><strong>Missing ownership<\/strong>: Without a clear owner for each system or data model, integration breaks down. Assign responsibility to a team or person.<\/li>\n<li><strong>Ignoring change management<\/strong>: When a system evolves, the journey model must too. Use versioning and audit trails.<\/li>\n<\/ul>\n<h2>Conclusion<\/h2>\n<p>Integrating BPMN journey models with UML, ERD, and architecture views isn\u2019t a technical luxury\u2014it\u2019s a requirement for delivering seamless customer experiences at scale. It transforms a journey from a narrative into a measurable, executable, and maintainable blueprint.<\/p>\n<p>When you integrate these models, you\u2019re not just improving documentation\u2014you\u2019re building trust across CX, product, and IT teams. The result? A system where customer impact is visible at every level, from the first click to the final database update.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I link a BPMN model to a UML class diagram?<\/h3>\n<p>Assign a unique ID to each BPMN activity and map it to a corresponding UML method. Use a shared naming convention (e.g., \u201cVerifyIdentity\u201d) and add a note in BPMN referencing the UML class and method.<\/p>\n<h3>Can BPMN be connected to an ERD without making diagrams too complex?<\/h3>\n<p>Absolutely. Use annotations or references. For example, in the BPMN step \u201cCreate Order,\u201d add a note: \u201cSee ERD: Order entity, attributes: OrderID, Total.\u201d This keeps the diagram clean while enabling traceability.<\/p>\n<h3>Is it necessary to integrate all models for every journey?<\/h3>\n<p>No. Start with high-impact or complex journeys\u2014like onboarding, support, or payment. For simple journeys, a clean BPMN may suffice. Save integration for processes where system behavior directly affects customer experience.<\/p>\n<h3>What tools support linking BPMN with UML and ERD?<\/h3>\n<p>Visual Paradigm support multi-model integration. Use their built-in linking features, shared repositories, and traceability matrices to connect diagrams across domains.<\/p>\n<h3>How do I ensure consistency between BPMN and data models?<\/h3>\n<p>Define a shared glossary with consistent terms (e.g., \u201cCustomer\u201d not \u201cUser\u201d). Use unique identifiers across models and conduct regular cross-checks with stakeholders from CX, data, and IT teams.<\/p>\n<h3>How do I handle changes in the system after integration?<\/h3>\n<p>Implement a change governance process. When a data model or service changes, update the linked BPMN model and notify relevant teams. Use versioning and audit logs to track modifications.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a BPMN model fe [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1218,"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-1221","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Integrating Journey BPMN with Other Models<\/title>\n<meta name=\"description\" content=\"Learn how to integrate BPMN journey models with UML, ERD, and architecture views for end-to-end modeling from CX to systems. Practical guidance for connecting customer experience to implementation.\" \/>\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\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Integrating Journey BPMN with Other Models\" \/>\n<meta property=\"og:description\" content=\"Learn how to integrate BPMN journey models with UML, ERD, and architecture views for end-to-end modeling from CX to systems. Practical guidance for connecting customer experience to implementation.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/\" \/>\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=\"7 \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\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/\",\"name\":\"Integrating Journey BPMN with Other Models\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-02-25T10:37:36+00:00\",\"description\":\"Learn how to integrate BPMN journey models with UML, ERD, and architecture views for end-to-end modeling from CX to systems. Practical guidance for connecting customer experience to implementation.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Governance, Standards, and Advanced Topics\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Integrating BPMN Journey Models with Other Diagrams\"}]},{\"@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":"Integrating Journey BPMN with Other Models","description":"Learn how to integrate BPMN journey models with UML, ERD, and architecture views for end-to-end modeling from CX to systems. Practical guidance for connecting customer experience to implementation.","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\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/","og_locale":"zh_TW","og_type":"article","og_title":"Integrating Journey BPMN with Other Models","og_description":"Learn how to integrate BPMN journey models with UML, ERD, and architecture views for end-to-end modeling from CX to systems. Practical guidance for connecting customer experience to implementation.","og_url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/","og_site_name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"7 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/","name":"Integrating Journey BPMN with Other Models","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-02-25T10:37:36+00:00","description":"Learn how to integrate BPMN journey models with UML, ERD, and architecture views for end-to-end modeling from CX to systems. Practical guidance for connecting customer experience to implementation.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/integrating-journey-bpmn-with-other-models\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/tw\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"Governance, Standards, and Advanced Topics","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/"},{"@type":"ListItem","position":4,"name":"Integrating BPMN Journey Models with Other Diagrams"}]},{"@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\/1221","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\/1221\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1218"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=1221"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=1221"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}