{"id":1623,"date":"2026-02-25T10:43:56","date_gmt":"2026-02-25T10:43:56","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/"},"modified":"2026-02-25T10:43:56","modified_gmt":"2026-02-25T10:43:56","slug":"thinking-like-a-systems-modeler-sysml","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/","title":{"rendered":"Thinking Like a Systems Modeler"},"content":{"rendered":"<p>You know you&#8217;re thinking like a systems modeler when your team stops arguing about semantics and starts aligning on the model. Not because someone explained it perfectly\u2014but because the model itself revealed the disconnect.<\/p>\n<p>That shift happens when abstraction becomes second nature, not a task. When you see a block not as a box, but as a boundary between concerns. When behavior isn\u2019t just a flowchart\u2014it\u2019s a promise about how the system responds under uncertainty.<\/p>\n<p>Over 20 years in engineering, I\u2019ve watched teams move from static documentation to dynamic models. The difference? Not tools. It\u2019s mindset. This chapter is your bridge from \u201cI know what SysML is\u201d to \u201cI use it to think.\u201d<\/p>\n<p>You\u2019ll learn how to break down complexity, define boundaries with purpose, and design systems that evolve\u2014not collapse\u2014under change. This isn\u2019t theory. It\u2019s what happens when model-based thinking becomes instinct.<\/p>\n<h2>Abstraction: The Core of Systems Thinking<\/h2>\n<p>Abstraction isn\u2019t simplification. It\u2019s focus.<\/p>\n<p>When you model a smart thermostat, you don\u2019t begin with a wiring diagram. You start with a purpose: maintain indoor comfort. That\u2019s abstraction. From there, you define what matters\u2014temperature, time, user preferences\u2014while hiding irrelevant details like capacitor tolerances.<\/p>\n<p>Systems thinking means asking: What is the system *for*? Who are its stakeholders? What are the boundaries?<\/p>\n<p>Ask yourself: If I were to hand this model to a new engineer next week, would they understand the intent without a meeting?<\/p>\n<p>That\u2019s the goal of abstraction. Not to hide information\u2014but to make the right information visible at the right time.<\/p>\n<h3>Levels of Abstraction in SysML<\/h3>\n<p>Modeling at different levels of abstraction helps manage complexity. Here\u2019s how it works in practice:<\/p>\n<ul>\n<li><strong>Level 1: Context<\/strong> \u2013 Show the system in its environment. Use a Use Case Diagram or a simple boundary box.<\/li>\n<li><strong>Level 2: Structure<\/strong> \u2013 Define components and relationships with Block Definition Diagrams (BDD).<\/li>\n<li><strong>Level 3: Behavior<\/strong> \u2013 Capture workflows and state changes with Activity and State Machine Diagrams.<\/li>\n<li><strong>Level 4: Details<\/strong> \u2013 Use Internal Block Diagrams (IBD) and detailed parametric constraints for implementation.<\/li>\n<\/ul>\n<p>Each layer serves a purpose. Don\u2019t jump to Level 4. You\u2019ll drown in details before you\u2019ve validated intent.<\/p>\n<p>One project I led started with a single question: \u201cWhat does the customer actually care about?\u201d The answer\u2014\u201creliability and ease of use\u201d\u2014shaped our entire model. Everything else followed.<\/p>\n<h2>Modularity: Designing for Change<\/h2>\n<p>Modularity isn\u2019t just about components. It\u2019s about control.<\/p>\n<p>A modular system means you can update one part\u2014say, the temperature sensing module\u2014without rewriting the entire thermostat logic. That\u2019s not a feature. It\u2019s a necessity in complex systems.<\/p>\n<p>With SysML, you enforce modularity through blocks and interfaces. Each block becomes a self-contained unit with well-defined ports, inputs, and outputs.<\/p>\n<p>Here\u2019s a real example: In a medical device model, we broke the system into \u201cUser Interface,\u201d \u201cSensor Processor,\u201d and \u201cCommunication Module.\u201d Each had its own diagram. When requirements changed, only the affected module was revised\u2014no ripple across the entire model.<\/p>\n<p>That\u2019s the power of modularity: change is localized, risk is contained, and testing is focused.<\/p>\n<h3>How to Build a Modular SysML Model<\/h3>\n<p>Follow these steps to avoid over-integration and premature coupling:<\/p>\n<ol>\n<li>Define the system\u2019s purpose and key external interfaces.<\/li>\n<li>Break the system into logical subsystems using BDD.<\/li>\n<li>Assign responsibilities to each block (e.g., \u201cControls data transmission\u201d).<\/li>\n<li>Use interfaces to define how blocks interact\u2014never internal logic.<\/li>\n<li>Validate each module\u2019s behavior independently using Activity or Sequence Diagrams.<\/li>\n<\/ol>\n<p>Don\u2019t try to model the whole system in one diagram. That\u2019s a red flag. It means you\u2019re modeling a process, not a system.<\/p>\n<h2>Traceability: Linking Intent to Implementation<\/h2>\n<p>Traceability isn\u2019t a feature. It\u2019s the backbone of trust in your model.<\/p>\n<p>If you can\u2019t show how a requirement connects to a design decision, you can\u2019t prove compliance. Worse, you can\u2019t justify a change.<\/p>\n<p>With SysML, traceability is built into the language. Use the Requirements Diagram to define and link requirements to model elements.<\/p>\n<p>Every time you add a block, component, or action, ask: What requirement does this satisfy? If you can\u2019t answer\u2014stop. You\u2019re modeling without purpose.<\/p>\n<p>I\u2019ve seen projects fail not from poor design, but from missing traceability. A requirement was changed, but the model wasn\u2019t. The system worked\u2014until it didn\u2019t.<\/p>\n<p>Here\u2019s a simple check: For every requirement, is there at least one model element (a block, action, constraint) that fulfills it? If not, you\u2019ve created a gap.<\/p>\n<h3>Traceability Checklist<\/h3>\n<p>Use this to audit your model:<\/p>\n<ul>\n<li>Every requirement must be linked to at least one system element.<\/li>\n<li>Every model element must be linked to a requirement or a justification.<\/li>\n<li>Use allocation (e.g., \u201cFunction \u2192 Block\u201d) to show how behavior maps to structure.<\/li>\n<li>Review traceability after every significant change.<\/li>\n<\/ul>\n<p>Traceability is not a one-time task. It\u2019s a continuous practice.<\/p>\n<h2>Model-Based Mindset: The Real Skill<\/h2>\n<p>What separates beginners from experts? It\u2019s not syntax. It\u2019s mindset.<\/p>\n<p>You don\u2019t \u201cdraw a diagram\u201d in MBSE. You \u201cexpress intent.\u201d A model is not a picture. It\u2019s a formal statement of how you expect the system to work.<\/p>\n<p>When I say \u201cmodel-based mindset,\u201d I mean: You trust the model more than the meeting notes. You question assumptions by asking: \u201cDoes this model capture the real behavior?\u201d<\/p>\n<p>Let\u2019s be clear: No model is perfect. But a well-structured one gives you a shared language, reduces ambiguity, and makes reasoning about trade-offs possible.<\/p>\n<p>Systems modeling skills aren\u2019t learned overnight. They grow from practice\u2014reflection\u2014iteration.<\/p>\n<h3>Model-Based Mindset vs. Documentation Mindset<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Aspect<\/th>\n<th>Documentation Mindset<\/th>\n<th>Model-Based Mindset<\/th>\n<\/tr>\n<tr>\n<td>Focus<\/td>\n<td>Describing what exists<\/td>\n<td>Defining what should be<\/td>\n<\/tr>\n<tr>\n<td>Change Handling<\/td>\n<td>Update after the fact<\/td>\n<td>Model first, document later<\/td>\n<\/tr>\n<tr>\n<td>Traceability<\/td>\n<td>Manual cross-references<\/td>\n<td>Automated, bidirectional links<\/td>\n<\/tr>\n<tr>\n<td>Collaboration<\/td>\n<td>Text-heavy reviews<\/td>\n<td>Shared visual language<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Choose the model-based mindset. It\u2019s not faster at first. But it\u2019s *right*\u2014and it scales.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even experienced modelers make mistakes. Here are the most common\u2014and how to fix them:<\/p>\n<ul>\n<li><strong>Over-modeling<\/strong>: Adding every possible detail. Fix: Ask, \u201cIs this necessary for the current level of abstraction?\u201d<\/li>\n<li><strong>Untied behavior<\/strong>: Activity diagrams that don\u2019t map to blocks. Fix: Use allocation to link actions to system components.<\/li>\n<li><strong>Missing interfaces<\/strong>: Blocks connected by lines, but no defined ports. Fix: Always define ports and their roles.<\/li>\n<li><strong>Untraceable requirements<\/strong>: Requirements listed but not linked. Fix: Use ReqIF or model traceability tools.<\/li>\n<\/ul>\n<p>These aren\u2019t bugs. They\u2019re symptoms of a weak systems mindset.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if I\u2019m thinking like a systems modeler?<\/h3>\n<p>When you prioritize structure and intent over syntax. When your model helps you answer \u201cWhat if?\u201d before implementation. When you use it to challenge assumptions, not just document them.<\/p>\n<h3>Can I use SysML without a modeling tool?<\/h3>\n<p>Technically yes, but inefficiently. Manual diagrams are error-prone and hard to trace. <\/p>\n<h3>What\u2019s the biggest mistake beginners make?<\/h3>\n<p>Trying to model everything at once. Start with the core purpose. Define key blocks. Trace a single requirement. Build from there. Abstraction is not a sprint\u2014it\u2019s a process.<\/p>\n<h3>How do I convince my team to use SysML?<\/h3>\n<p>Start small. Pick a real problem\u2014like a recurring bug or requirement gap. Show how a model reveals the root cause faster than emails or meetings. Prove value before scaling.<\/p>\n<h3>Is systems thinking only for engineers?<\/h3>\n<p>No. It\u2019s vital for product managers, testers, and even business analysts. The ability to see systems, not just parts, is a competitive advantage in any complex domain.<\/p>\n<h3>How often should I review my model?<\/h3>\n<p>With every change. After a requirement update, a design decision, or a test failure. Use traceability to assess impact. A well-structured model should make this easy.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>You know you&#8217;re thinking like a systems modeler when your team stops arguing about semantics and starts aligning on the model. Not because someone explained it perfectly\u2014but because the model itself revealed the disconnect. That shift happens when abstraction becomes second nature, not a task. When you see a block not as a box, but [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1622,"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-1623","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>Thinking Like a Systems Modeler with SysML<\/title>\n<meta name=\"description\" content=\"Learn to adopt a model-based mindset with Systems Thinking in SysML. Master systems modeling skills through structured, traceable, and modular design practices for real-world engineering success.\" \/>\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-best-practices\/thinking-like-a-systems-modeler-sysml\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Thinking Like a Systems Modeler with SysML\" \/>\n<meta property=\"og:description\" content=\"Learn to adopt a model-based mindset with Systems Thinking in SysML. Master systems modeling skills through structured, traceable, and modular design practices for real-world engineering success.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/\" \/>\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-best-practices\/thinking-like-a-systems-modeler-sysml\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/\",\"name\":\"Thinking Like a Systems Modeler with SysML\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:43:56+00:00\",\"description\":\"Learn to adopt a model-based mindset with Systems Thinking in SysML. Master systems modeling skills through structured, traceable, and modular design practices for real-world engineering success.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/#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\":\"Modeling Mindset and Professional Practice\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Thinking Like a Systems Modeler\"}]},{\"@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":"Thinking Like a Systems Modeler with SysML","description":"Learn to adopt a model-based mindset with Systems Thinking in SysML. Master systems modeling skills through structured, traceable, and modular design practices for real-world engineering success.","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-best-practices\/thinking-like-a-systems-modeler-sysml\/","og_locale":"de_DE","og_type":"article","og_title":"Thinking Like a Systems Modeler with SysML","og_description":"Learn to adopt a model-based mindset with Systems Thinking in SysML. Master systems modeling skills through structured, traceable, and modular design practices for real-world engineering success.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/","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-best-practices\/thinking-like-a-systems-modeler-sysml\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/","name":"Thinking Like a Systems Modeler with SysML","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:43:56+00:00","description":"Learn to adopt a model-based mindset with Systems Thinking in SysML. Master systems modeling skills through structured, traceable, and modular design practices for real-world engineering success.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/thinking-like-a-systems-modeler-sysml\/#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":"Modeling Mindset and Professional Practice","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-best-practices\/"},{"@type":"ListItem","position":4,"name":"Thinking Like a Systems Modeler"}]},{"@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\/1623","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\/1623\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1622"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1623"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1623"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}