{"id":4673,"date":"2026-01-20T10:17:59","date_gmt":"2026-01-20T02:17:59","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/"},"modified":"2026-01-20T11:35:43","modified_gmt":"2026-01-20T03:35:43","slug":"prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/","title":{"rendered":"Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements"},"content":{"rendered":"

Section: Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements<\/strong><\/h3>\n

Effective communication with the AI co-pilot is essential to producing a model that is both structurally sound and strategically relevant. Prompt engineering<\/strong> is the practice of crafting natural language descriptions that allow the AI to accurately identify architectural entities, relationships, and viewpoints<\/strong>. Rather than starting with a blank canvas, architects can describe a business scenario in plain English, and the AI translates these high-level requirements into a compliant ArchiMate diagram.<\/p>\n

Best Practices for Effective AI Prompts<\/strong><\/h4>\n
    \n
  1. Leverage Official Viewpoints:<\/strong> Always specify the intended ArchiMate viewpoint<\/strong> from the menu or within the prompt to ensure the AI uses the correct subset of elements for your audience.<\/li>\n
  2. Use Specific Element Terminology:<\/strong> When describing components, use ArchiMate keywords such as “Business Actor,” “Application Component,” or “Node”<\/strong> followed by the specific organizational name to help the AI apply the correct notation.<\/li>\n
  3. Define Inter-Layer Relationships:<\/strong> Explicitly state how different elements interact using verbs like “realizes,” “serves,” “hosts,” or “triggers”<\/strong> to establish end-to-end traceability.<\/li>\n
  4. Adopt an Iterative Refinement Approach:<\/strong> If the initial generation is missing a component, use conversational refinement<\/strong> to adjust the model (e.g., “Add a flow relationship between Application A and B”<\/em>) rather than starting over.<\/li>\n
  5. Specify Audience and Tone:<\/strong> You can define the desired tone (e.g., technical for engineers or formal for executives<\/strong>) to ensure the generated explanation accompanying the diagram is appropriately tailored.<\/li>\n<\/ol>\n
    \n

    Practical Examples of AI Prompts<\/strong><\/h3>\n

    The following examples demonstrate how to apply these best practices to translate high-level requirements into ArchiMate models across various domains:<\/p>\n

      \n
    • Retail Digital Transformation:<\/strong>\n
        \n
      • Prompt:<\/strong> “Generate an ArchiMate diagram for a retail company\u2019s shift to e-commerce, including business processes for order fulfillment, application services like inventory management, and technology nodes for cloud hosting”<\/em>.<\/li>\n
      • Result:<\/strong> A Layered Viewpoint<\/strong> model that traces the impact of the new cloud hosting strategy on customer-facing business services.<\/li>\n<\/ul>\n<\/li>\n
      • Telecom Infrastructure Rollout:<\/strong>\n
          \n
        • Prompt:<\/strong> “Telecom 5G Network Rollout Architecture”<\/em>.<\/li>\n
        • Result:<\/strong> A Technology Layer<\/strong> diagram showing how infrastructure elements (cell towers) and network services work together to deliver 5G connectivity.<\/li>\n<\/ul>\n<\/li>\n
        • Cloud Migration Strategy:<\/strong>\n
            \n
          • Prompt:<\/strong> “Create a Technology Usage viewpoint for migrating a banking app to AWS, comparing re-hosting vs. re-platforming options”<\/em>.<\/li>\n
          • Result:<\/strong> A model visualizing dependencies on virtual machines<\/strong>, allowing project managers to perform “what-if” analysis for downtime risks.<\/li>\n<\/ul>\n<\/li>\n
          • Specific Element Construction:<\/strong>\n
              \n
            • Prompt:<\/strong> “Create a Business Layer diagram with a \u2018Business Actor\u2019 named \u2018Client\u2019 who uses a \u2018Business Service\u2019 named \u2018Insurance Quoting\u2019”<\/em>.<\/li>\n
            • Result:<\/strong> A precise Organization viewpoint<\/strong> that clearly maps specific actors to the services they consume.<\/li>\n<\/ul>\n<\/li>\n
            • Iterative Refinement of Relationships:<\/strong>\n
                \n
              • Prompt (Refinement):<\/strong> “Add a serving relationship from Application Service to Business Process”<\/em> or “Analyze gaps in this implementation viewpoint”<\/em>.<\/li>\n
              • Result:<\/strong> The AI instantly refactors the visual model<\/strong> to reflect new insights while maintaining strict compliance with ArchiMate syntax.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n","protected":false},"featured_media":0,"parent":4659,"menu_order":2,"comment_status":"open","ping_status":"closed","template":"","meta":{"_yoast_wpseo_title":"","_yoast_wpseo_metadesc":"","_eb_attr":"","neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":""},"doc_tag":[],"class_list":["post-4673","docs","type-docs","status-publish","hentry"],"yoast_head":"\nPrompt Engineering for ArchiMate: Best Practices for High-Level Requirements - Visual Paradigm Guides Spanish<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements - Visual Paradigm Guides Spanish\" \/>\n<meta property=\"og:description\" content=\"Section: Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements Effective communication with the AI co-pilot is essential to producing a model that is both structurally sound and strategically relevant. Prompt engineering is the practice of crafting natural language descriptions that allow the AI to accurately identify architectural entities, relationships, and viewpoints. Rather than starting with a blank canvas, architects can describe a business scenario in plain English, and the AI translates these high-level requirements into a compliant ArchiMate diagram. Best Practices for Effective AI Prompts Leverage Official Viewpoints: Always specify the intended ArchiMate viewpoint from the menu or within the prompt to ensure the AI uses the correct subset of elements for your audience. Use Specific Element Terminology: When describing components, use ArchiMate keywords such as “Business Actor,” “Application Component,” or “Node” followed by the specific organizational name to help the AI apply the correct notation. Define Inter-Layer Relationships: Explicitly state how different elements interact using verbs like “realizes,” “serves,” “hosts,” or “triggers” to establish end-to-end traceability. Adopt an Iterative Refinement Approach: If the initial generation is missing a component, use conversational refinement to adjust the model (e.g., “Add a flow relationship between Application A and B”) rather than starting over. Specify Audience and Tone: You can define the desired tone (e.g., technical for engineers or formal for executives) to ensure the generated explanation accompanying the diagram is appropriately tailored. Practical Examples of AI Prompts The following examples demonstrate how to apply these best practices to translate high-level requirements into ArchiMate models across various domains: Retail Digital Transformation: Prompt: “Generate an ArchiMate diagram for a retail company\u2019s shift to e-commerce, including business processes for order fulfillment, application services like inventory management, and technology nodes for cloud hosting”. Result: A Layered Viewpoint model that traces the impact of the new cloud hosting strategy on customer-facing business services. Telecom Infrastructure Rollout: Prompt: “Telecom 5G Network Rollout Architecture”. Result: A Technology Layer diagram showing how infrastructure elements (cell towers) and network services work together to deliver 5G connectivity. Cloud Migration Strategy: Prompt: “Create a Technology Usage viewpoint for migrating a banking app to AWS, comparing re-hosting vs. re-platforming options”. Result: A model visualizing dependencies on virtual machines, allowing project managers to perform “what-if” analysis for downtime risks. Specific Element Construction: Prompt: “Create a Business Layer diagram with a \u2018Business Actor\u2019 named \u2018Client\u2019 who uses a \u2018Business Service\u2019 named \u2018Insurance Quoting\u2019”. Result: A precise Organization viewpoint that clearly maps specific actors to the services they consume. Iterative Refinement of Relationships: Prompt (Refinement): “Add a serving relationship from Application Service to Business Process” or “Analyze gaps in this implementation viewpoint”. Result: The AI instantly refactors the visual model to reflect new insights while maintaining strict compliance with ArchiMate syntax.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Spanish\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-20T03:35:43+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"2 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/\",\"name\":\"Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements - Visual Paradigm Guides Spanish\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-01-20T02:17:59+00:00\",\"dateModified\":\"2026-01-20T03:35:43+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ArchiMate Explained: A Guide to AI-Powered Enterprise Architecture\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Part III: AI-Powered ArchiMate Modeling\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Chapter 5: Instant Diagram Generation with AI\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Guides Spanish\",\"description\":\"Smart guides for an AI-driven world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements - Visual Paradigm Guides Spanish","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:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/","og_locale":"es_ES","og_type":"article","og_title":"Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements - Visual Paradigm Guides Spanish","og_description":"Section: Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements Effective communication with the AI co-pilot is essential to producing a model that is both structurally sound and strategically relevant. Prompt engineering is the practice of crafting natural language descriptions that allow the AI to accurately identify architectural entities, relationships, and viewpoints. Rather than starting with a blank canvas, architects can describe a business scenario in plain English, and the AI translates these high-level requirements into a compliant ArchiMate diagram. Best Practices for Effective AI Prompts Leverage Official Viewpoints: Always specify the intended ArchiMate viewpoint from the menu or within the prompt to ensure the AI uses the correct subset of elements for your audience. Use Specific Element Terminology: When describing components, use ArchiMate keywords such as “Business Actor,” “Application Component,” or “Node” followed by the specific organizational name to help the AI apply the correct notation. Define Inter-Layer Relationships: Explicitly state how different elements interact using verbs like “realizes,” “serves,” “hosts,” or “triggers” to establish end-to-end traceability. Adopt an Iterative Refinement Approach: If the initial generation is missing a component, use conversational refinement to adjust the model (e.g., “Add a flow relationship between Application A and B”) rather than starting over. Specify Audience and Tone: You can define the desired tone (e.g., technical for engineers or formal for executives) to ensure the generated explanation accompanying the diagram is appropriately tailored. Practical Examples of AI Prompts The following examples demonstrate how to apply these best practices to translate high-level requirements into ArchiMate models across various domains: Retail Digital Transformation: Prompt: “Generate an ArchiMate diagram for a retail company\u2019s shift to e-commerce, including business processes for order fulfillment, application services like inventory management, and technology nodes for cloud hosting”. Result: A Layered Viewpoint model that traces the impact of the new cloud hosting strategy on customer-facing business services. Telecom Infrastructure Rollout: Prompt: “Telecom 5G Network Rollout Architecture”. Result: A Technology Layer diagram showing how infrastructure elements (cell towers) and network services work together to deliver 5G connectivity. Cloud Migration Strategy: Prompt: “Create a Technology Usage viewpoint for migrating a banking app to AWS, comparing re-hosting vs. re-platforming options”. Result: A model visualizing dependencies on virtual machines, allowing project managers to perform “what-if” analysis for downtime risks. Specific Element Construction: Prompt: “Create a Business Layer diagram with a \u2018Business Actor\u2019 named \u2018Client\u2019 who uses a \u2018Business Service\u2019 named \u2018Insurance Quoting\u2019”. Result: A precise Organization viewpoint that clearly maps specific actors to the services they consume. Iterative Refinement of Relationships: Prompt (Refinement): “Add a serving relationship from Application Service to Business Process” or “Analyze gaps in this implementation viewpoint”. Result: The AI instantly refactors the visual model to reflect new insights while maintaining strict compliance with ArchiMate syntax.","og_url":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/","og_site_name":"Visual Paradigm Guides Spanish","article_modified_time":"2026-01-20T03:35:43+00:00","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"2 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/","url":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/","name":"Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements - Visual Paradigm Guides Spanish","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/#website"},"datePublished":"2026-01-20T02:17:59+00:00","dateModified":"2026-01-20T03:35:43+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/prompt-engineering-for-archimate-best-practices-for-high-level-requirements-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"ArchiMate Explained: A Guide to AI-Powered Enterprise Architecture","item":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/"},{"@type":"ListItem","position":3,"name":"Part III: AI-Powered ArchiMate Modeling","item":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/"},{"@type":"ListItem","position":4,"name":"Chapter 5: Instant Diagram Generation with AI","item":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/"},{"@type":"ListItem","position":5,"name":"Prompt Engineering for ArchiMate: Best Practices for High-Level Requirements"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/es\/#website","url":"https:\/\/guides.visual-paradigm.com\/es\/","name":"Visual Paradigm Guides Spanish","description":"Smart guides for an AI-driven world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4673","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/comments?post=4673"}],"version-history":[{"count":1,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4673\/revisions"}],"predecessor-version":[{"id":4840,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4673\/revisions\/4840"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4659"}],"next":[{"title":"Hands-on: Generating a Multi-Layer Model from a Single Topic","link":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/hands-on-generating-a-multi-layer-model-from-a-single-topic\/","href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4681"}],"prev":[{"title":"How the AI Interprets Context and Intent","link":"https:\/\/guides.visual-paradigm.com\/es\/docs\/archimate-explained-a-guide-to-ai-powered-enterprise-architecture\/part-iii-ai-powered-archimate-modeling\/chapter-5-instant-diagram-generation-with-ai\/how-the-ai-interprets-context-and-intent\/","href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4668"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=4673"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=4673"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}