{"id":1621,"date":"2026-02-25T10:43:55","date_gmt":"2026-02-25T10:43:55","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/"},"modified":"2026-02-25T10:43:55","modified_gmt":"2026-02-25T10:43:55","slug":"sysml-documentation-report-generation","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/","title":{"rendered":"Adapting SysML Models for Documentation and Reports"},"content":{"rendered":"<p>Many engineers start by exporting SysML diagrams as images and pasting them into Word documents. It&#8217;s quick, familiar, and feels like progress. But this approach often results in disconnected, poorly explained visuals that fail to convey the system\u2019s intent to stakeholders.<\/p>\n<p>Over 20 years in systems engineering taught me this truth: a diagram is not documentation. It\u2019s evidence. The real value lies in transforming your model into a living document\u2014a report that tells a story, not just shows a picture.<\/p>\n<p>This chapter walks you through the systematic process of adapting SysML models for real-world documentation. You\u2019ll learn how to generate structured reports, annotate diagrams effectively, and communicate SysML diagrams to non-technical audiences without sacrificing technical accuracy.<\/p>\n<p>By the end, you\u2019ll know how to turn your SysML model from a tool for design into a trusted artifact for decision-making\u2014exactly what modern engineering demands.<\/p>\n<h2>Why Raw Diagrams Aren\u2019t Enough<\/h2>\n<p>Too often, a SysML model is treated as a final deliverable\u2014just a set of diagrams slapped into a PDF.<\/p>\n<p>But if someone outside your team opens that report, the first question they\u2019ll ask is: *What does this mean?* Without context, the model is meaningless.<\/p>\n<p>Think of it like showing a map with no legend. The roads are there, but no one knows what the symbols mean.<\/p>\n<p>That\u2019s why effective SysML documentation must do three things:<\/p>\n<ul>\n<li>Explain the purpose of each diagram<\/li>\n<li>Connect diagrams through narrative context<\/li>\n<li>Present information in a format suited to the audience<\/li>\n<\/ul>\n<p>For example, a subsystem engineer needs detail. A project manager needs clarity. An executive needs strategy.<\/p>\n<h2>Step-by-Step: From Model to Report<\/h2>\n<p>Here\u2019s how to turn a SysML model into a structured, shareable report\u2014step by step.<\/p>\n<h3>1. Define Your Audience and Objective<\/h3>\n<p>Before writing a single word, ask: *Who will read this, and what do they need to know?*<\/p>\n<p>Use this simple framework:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Audience<\/th>\n<th>Focus<\/th>\n<th>Recommended Detail Level<\/th>\n<\/tr>\n<tr>\n<td>System Designer<\/td>\n<td>Component structure, interfaces, allocations<\/td>\n<td>High<\/td>\n<\/tr>\n<tr>\n<td>Project Manager<\/td>\n<td>Scope, dependencies, key functions<\/td>\n<td>Moderate<\/td>\n<\/tr>\n<tr>\n<td>Executive<\/td>\n<td>Objectives, risks, key outcomes<\/td>\n<td>High-level<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Design the report to serve that need\u2014not to showcase how many diagrams you made.<\/p>\n<h3>2. Use Automated Report Generation Tools<\/h3>\n<p>Manual copying is error-prone and time-consuming. Instead, use your modeling tool\u2019s built-in report engine\u2014such as Visual Paradigm\u2019s report generator.<\/p>\n<p>These tools can:<\/p>\n<ul>\n<li>Auto-generate tables of contents<\/li>\n<li>Include model elements with links<\/li>\n<li>Insert diagrams with captions and references<\/li>\n<li>Export in PDF, Word, or HTML<\/li>\n<\/ul>\n<p>Set up a template once, and you\u2019ll reuse it for future reports. This is what I call the \u201creport factory\u201d approach.<\/p>\n<h3>3. Annotate Diagrams with Purpose<\/h3>\n<p>A diagram without explanation is a puzzle with missing pieces.<\/p>\n<p>Always add a short paragraph before each diagram. Answer these questions:<\/p>\n<ul>\n<li>What does this diagram represent?<\/li>\n<li>Why is it important?<\/li>\n<li>How does it relate to the system\u2019s goals?<\/li>\n<\/ul>\n<p>For example, in a Block Definition Diagram showing a smart home hub:<\/p>\n<p><em>This diagram defines the core components of the smart home central controller. The Hub block is the central coordinator, responsible for receiving inputs from sensors and relaying commands to actuators. Its internal structure shows dependencies on a security module and a network interface, highlighting its role as a trust boundary.<\/em><\/p>\n<p>Now, the reader knows not just what the components are\u2014but why they matter.<\/p>\n<h3>4. Integrate Traceability and Requirements<\/h3>\n<p>Stakeholders care about *why* a system behaves a certain way. That\u2019s where requirements come in.<\/p>\n<p>Include a traceability matrix in your report that links:<\/p>\n<ul>\n<li>Each requirement to the model element it satisfies<\/li>\n<li>Each diagram to the specific requirement it supports<\/li>\n<li>Every change to its justification<\/li>\n<\/ul>\n<p>This isn\u2019t just for compliance. It proves your model reflects real design intent.<\/p>\n<h3>5. Use Consistent Formatting and Visual Language<\/h3>\n<p>Consistency builds trust. Use the same font, heading hierarchy, and caption style across all diagrams.<\/p>\n<p>Consider this rule of thumb:<\/p>\n<ul>\n<li>Label diagrams with sequential numbers: <em>Figure 1: Block Definition Diagram<\/em><\/li>\n<li>Reference them in the text: <em>As shown in Figure 1, the Hub manages&#8230;<\/em><\/li>\n<li>Use color codes only if they serve a purpose\u2014e.g., red for safety-critical components<\/li>\n<\/ul>\n<p>Remember: clarity beats decoration.<\/p>\n<h2>Best Practices for Communicating SysML Diagrams<\/h2>\n<p>Even the best report fails if the diagrams themselves are hard to read.<\/p>\n<p>Here\u2019s what works in real projects:<\/p>\n<ul>\n<li><strong>Limit diagram complexity<\/strong>: Break large diagrams into sub-diagrams with clear scope.<\/li>\n<li><strong>Use consistent naming<\/strong>: Avoid acronyms without explanation. Use \u201cSmart Home Hub\u201d instead of \u201cSH-01\u201d.<\/li>\n<li><strong>Highlight key elements<\/strong>: Use bold borders or color to emphasize critical components.<\/li>\n<li><strong>Explain notation<\/strong>: If using special symbols (like the &lt;&lt;allocate&gt;&gt; stereotype), define them in a legend.<\/li>\n<\/ul>\n<p>When I reviewed a report from a junior engineer, the first thing I noticed was a flow diagram with 20+ nodes. It looked like a spiderweb. I asked: \u201cWhat\u2019s the main path?\u201d<\/p>\n<p>He responded: \u201cThe one from sensor input to actuation.\u201d<\/p>\n<p>That\u2019s when I told him: \u201cThen make that the focus. The rest is noise.\u201d<\/p>\n<p>That\u2019s the power of simplifying to communicate.<\/p>\n<h2>Common Pitfalls in SysML Documentation<\/h2>\n<p>Even experienced modelers fall into traps. Watch out for these:<\/p>\n<ul>\n<li><strong>Over-documenting<\/strong>: Adding every detail, even when it doesn\u2019t serve the reader.<\/li>\n<li><strong>Assuming familiarity<\/strong>: Presuming the audience knows SysML terms like \u201callocation\u201d or \u201cinternal block diagram\u201d.<\/li>\n<li><strong>Using raw exports<\/strong>: Copying diagrams from the model without cleanup or annotation.<\/li>\n<li><strong>Ignoring versioning<\/strong>: Presenting a model from three months ago without noting changes.<\/li>\n<\/ul>\n<p>If your report doesn\u2019t answer: \u201cWhy should I care?\u201d \u2014 it\u2019s not working.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I generate a SysML report with Visual Paradigm?<\/h3>\n<p>Go to <strong>Report &gt; Generate Report<\/strong>. Choose a template (e.g., \u201cStandard SysML Report\u201d), select the model elements you want to include, and export to PDF or Word. The tool automatically adds a table of contents and formats diagrams with captions.<\/p>\n<h3>What should I include in a SysML documentation report?<\/h3>\n<p>A complete SysML report should include: an executive summary, a list of key diagrams with explanations, a traceability matrix, a description of system architecture and behavior, and a section on assumptions and risks. Keep the narrative concise and focused on purpose.<\/p>\n<h3>How can I simplify complex SysML diagrams for non-technical stakeholders?<\/h3>\n<p>Use high-level abstractions. For example, replace a detailed Internal Block Diagram with a simplified block hierarchy showing only the main components. Add a one-sentence explanation per diagram. Use analogies\u2014e.g., \u201cThe central hub works like a brain for the home.\u201d<\/p>\n<h3>Should I include the entire SysML model in the report?<\/h3>\n<p>No. Only include what serves the report\u2019s purpose. A model is an input, not the output. Focus on the most relevant diagrams, explanations, and traceability data. Save the full model for the development team.<\/p>\n<h3>How do I ensure consistency across multiple reports?<\/h3>\n<p>Create a reusable report template with consistent formatting, headings, and caption styles. Use the same naming conventions for blocks, ports, and requirements. Store this template in your organization\u2019s shared model repository.<\/p>\n<h2>Conclusion<\/h2>\n<p>SysML documentation is not a chore\u2014it\u2019s a critical phase of model-based systems engineering. When done well, it turns abstract models into actionable insights.<\/p>\n<p>Remember: your diagrams are not the end. They are the foundation for a report that communicates design intent, ensures traceability, and supports decision-making.<\/p>\n<p>Start small. Pick one model element. Turn it into one clear diagram with a short explanation. Then expand. With time, your reports will be trusted, referenced, and respected\u2014exactly as they should be.<\/p>\n<p>And that\u2019s the real power of SysML documentation: turning complexity into clarity.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Many engineers start by exporting SysML diagrams as images and pasting them into Word documents. It&#8217;s quick, familiar, and feels like progress. But this approach often results in disconnected, poorly explained visuals that fail to convey the system\u2019s intent to stakeholders. Over 20 years in systems engineering taught me this truth: a diagram is not [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1617,"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-1621","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>SysML Documentation: Turn Models into Reports<\/title>\n<meta name=\"description\" content=\"Transform SysML models into clear, professional documentation and reports. Learn best practices for SysML report generation and communicating SysML diagrams to stakeholders.\" \/>\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\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SysML Documentation: Turn Models into Reports\" \/>\n<meta property=\"og:description\" content=\"Transform SysML models into clear, professional documentation and reports. Learn best practices for SysML report generation and communicating SysML diagrams to stakeholders.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/\",\"name\":\"SysML Documentation: Turn Models into Reports\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:43:55+00:00\",\"description\":\"Transform SysML models into clear, professional documentation and reports. Learn best practices for SysML report generation and communicating SysML diagrams to stakeholders.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SysML Essentials for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Practical Application and Real-World Scenarios\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Adapting SysML Models for Documentation and Reports\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"SysML Documentation: Turn Models into Reports","description":"Transform SysML models into clear, professional documentation and reports. Learn best practices for SysML report generation and communicating SysML diagrams to stakeholders.","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\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/","og_locale":"de_DE","og_type":"article","og_title":"SysML Documentation: Turn Models into Reports","og_description":"Transform SysML models into clear, professional documentation and reports. Learn best practices for SysML report generation and communicating SysML diagrams to stakeholders.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/","name":"SysML Documentation: Turn Models into Reports","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:43:55+00:00","description":"Transform SysML models into clear, professional documentation and reports. Learn best practices for SysML report generation and communicating SysML diagrams to stakeholders.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/sysml-documentation-report-generation\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"SysML Essentials for Beginners","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Practical Application and Real-World Scenarios","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-examples\/"},{"@type":"ListItem","position":4,"name":"Adapting SysML Models for Documentation and Reports"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1621","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1621\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1617"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1621"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1621"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}