{"id":1608,"date":"2026-02-25T10:43:50","date_gmt":"2026-02-25T10:43:50","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/"},"modified":"2026-02-25T10:43:50","modified_gmt":"2026-02-25T10:43:50","slug":"sysml-state-machine-diagram-reactive-systems","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/","title":{"rendered":"State Machine Diagrams: Modeling Reactive Systems"},"content":{"rendered":"<p>In a recent project involving a medical device control system, a single unmodeled transition led to a critical state where the device remained in a \u201cwaiting for calibration\u201d state indefinitely\u2014causing operational delays and regulatory scrutiny. This wasn\u2019t due to poor code or hardware flaws. It was a modeling gap. I\u2019ve seen this pattern repeat across multiple industries: teams fail to capture the full lifecycle of reactive behavior through formal modeling. That\u2019s where the SysML state machine diagram becomes indispensable.<\/p>\n<p>The SysML state machine diagram provides a structured way to model dynamic behavior by defining states, transitions, triggers, and actions. It\u2019s not just about flow\u2014it\u2019s about control logic, state persistence, and event-driven responses. Whether you&#8217;re modeling a smart thermostat, a robotic arm, or a software state engine, getting this right prevents silent failures and ensures traceability from design to execution.<\/p>\n<p>This chapter walks you through building state machine diagrams with real precision. You\u2019ll learn how to define states, model transitions with triggers and guards, and apply best practices to avoid common modeling pitfalls. By the end, you\u2019ll be able to model reactive systems that are not only correct but also maintainable and testable.<\/p>\n<h2>Understanding State Machine Diagrams in SysML<\/h2>\n<p>State machine diagrams are part of the behavioral modeling family in SysML. They describe how an object or system changes over time in response to events. Unlike activity diagrams, which focus on workflow and control flow, state machine diagrams emphasize the states an object can be in and the transitions that cause changes between them.<\/p>\n<p>Each state represents a condition during the lifetime of a system or object\u2014such as \u201cIdle,\u201d \u201cRunning,\u201d or \u201cError.\u201d Transitions occur when specific events trigger a shift from one state to another. These events can be external (e.g., user input) or internal (e.g., timer expiration).<\/p>\n<p>Key elements in a SysML state machine diagram include:<\/p>\n<ul>\n<li><strong>Initial state<\/strong> (a filled circle) \u2013 marks the starting point of the diagram.<\/li>\n<li><strong>States<\/strong> (rounded rectangles) \u2013 represent conditions or modes.<\/li>\n<li><strong>Transitions<\/strong> (arrows with labels) \u2013 show movement from one state to another.<\/li>\n<li><strong>Triggers<\/strong> (event that causes a transition) \u2013 often labeled on the transition.<\/li>\n<li><strong>Guards<\/strong> (conditions in square brackets) \u2013 must be true for the transition to occur.<\/li>\n<li><strong>Actions<\/strong> (in parentheses) \u2013 actions performed during transition or state entry\/exit.<\/li>\n<\/ul>\n<p>These elements work together to form a precise, executable representation of system behavior.<\/p>\n<h2>Key Elements and Their Roles<\/h2>\n<h3>States and State Hierarchy<\/h3>\n<p>States define the condition of a system at a moment in time. They are not just labels\u2014they represent a set of invariant conditions and behaviors. For example, in a vending machine, \u201cWaiting for Selection\u201d and \u201cDispensing Item\u201d are distinct states where different actions are allowed.<\/p>\n<p>States can be hierarchical. You can define sub-states within a composite state. For instance, a \u201cRunning\u201d state might include sub-states like \u201cIdle,\u201d \u201cActive,\u201d and \u201cPausing.\u201d This allows for more granular control and avoids duplication in transition logic.<\/p>\n<p>When modeling, avoid over-abstracting. A state should be stable and meaningful\u2014too many states make the diagram hard to manage. Ask: \u201cCan this state be reached through a single, clear event? Is it distinguishable from adjacent states?\u201d<\/p>\n<h3>Transitions and Triggers<\/h3>\n<p>A <strong>state transition SysML<\/strong> describes the change from one state to another. Transitions are triggered by events\u2014either external (e.g., \u201cButton Pressed\u201d) or internal (e.g., \u201cTimer Expired\u201d). The event is the trigger.<\/p>\n<p>Not every event causes a transition. Only if the guard condition is satisfied will the transition fire. For example:<\/p>\n<pre><code>Transition: From \"Idle\" to \"Running\"\nTrigger: \"Start Button Pressed\"\nGuard: [System Power On = true]\nAction: [Start Motor]<\/code><\/pre>\n<p>This ensures that the system doesn\u2019t start when power is off\u2014preventing dangerous behavior.<\/p>\n<p>Use triggers to capture real-world stimuli. If you&#8217;re modeling a security system, triggers could be \u201cMotion Detected,\u201d \u201cAlarm Armed,\u201d or \u201cUser Authentication Success.\u201d<\/p>\n<h3>Guard Conditions: The Decision Gate<\/h3>\n<p>Guards are logical expressions that determine whether a transition can occur. They must evaluate to true for the transition to proceed.<\/p>\n<p>Common guard patterns:<\/p>\n<ul>\n<li><code>[Battery Level &gt; 20%]<\/code> \u2013 only allow certain transitions if battery is sufficient.<\/li>\n<li><code>[Not (Error Flag = true)]<\/code> \u2013 avoid transitioning into a state if an error exists.<\/li>\n<li><code>[Time Since Last Check &gt; 10s]<\/code> \u2013 model periodic checks.<\/li>\n<\/ul>\n<p>Guards should be crisp and unambiguous. Avoid vague conditions like \u201cif it\u2019s okay\u201d\u2014instead, use measurable, traceable expressions.<\/p>\n<h3>Actions and State Entry\/Exit<\/h3>\n<p>Actions are executable behaviors performed during a transition or when entering\/leaving a state. For example:<\/p>\n<ul>\n<li><em>On entry to \u201cError State\u201d:<\/em> Log error code and send alert to supervisor.<\/li>\n<li><em>During transition to \u201cShutdown\u201d:<\/em> Close all I\/O ports and save configuration.<\/li>\n<\/ul>\n<p>Use parentheses to denote actions. They help make behavior explicit and testable. Never assume actions happen\u2014model them.<\/p>\n<h2>Building a SysML State Example: Smart Thermostat<\/h2>\n<p>Let\u2019s apply this to a real example: modeling a smart thermostat.<\/p>\n<p>The thermostat has three core states:<\/p>\n<ul>\n<li><strong>Heating<\/strong> \u2013 heating element is on.<\/li>\n<li><strong>Cooling<\/strong> \u2013 cooling system is active.<\/li>\n<li><strong>Idle<\/strong> \u2013 no heating or cooling.<\/li>\n<\/ul>\n<p>Here\u2019s how the transitions work:<\/p>\n<table>\n<tbody>\n<tr>\n<th>From<\/th>\n<th>To<\/th>\n<th>Trigger<\/th>\n<th>Guard<\/th>\n<th>Action<\/th>\n<\/tr>\n<tr>\n<td>Idle<\/td>\n<td>Heating<\/td>\n<td>Temperature Below Setpoint<\/td>\n<td>[Heating Mode Active]<\/td>\n<td>Turn on heater<\/td>\n<\/tr>\n<tr>\n<td>Idle<\/td>\n<td>Cooling<\/td>\n<td>Temperature Above Setpoint<\/td>\n<td>[Cooling Mode Active]<\/td>\n<td>Turn on AC<\/td>\n<\/tr>\n<tr>\n<td>Heating<\/td>\n<td>Idle<\/td>\n<td>Temperature Reached Setpoint<\/td>\n<td>[Heater On]<\/td>\n<td>Turn off heater<\/td>\n<\/tr>\n<tr>\n<td>Cooling<\/td>\n<td>Idle<\/td>\n<td>Temperature Reached Setpoint<\/td>\n<td>[AC On]<\/td>\n<td>Turn off AC<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This <strong>SysML state example<\/strong> captures the core control logic. It\u2019s clear, testable, and aligns with real-world behavior.<\/p>\n<h2>Design and Modeling Best Practices<\/h2>\n<p>Modeling state machines is more than drawing boxes and arrows. It\u2019s about precision, clarity, and maintainability.<\/p>\n<p>Here\u2019s a checklist to follow:<\/p>\n<ol>\n<li><strong>Define clear, mutually exclusive states.<\/strong> Avoid overlapping behaviors.<\/li>\n<li><strong>Use triggers consistently.<\/strong> Label each transition with exactly one trigger.<\/li>\n<li><strong>Minimize deep nesting.<\/strong> More than three levels of sub-states can become hard to manage.<\/li>\n<li><strong>Use guards to prevent invalid transitions.<\/strong> They act as safety checks.<\/li>\n<li><strong>Model entry\/exit actions explicitly.<\/strong> Don\u2019t rely on implicit behavior.<\/li>\n<li><strong>Test with realistic scenarios.<\/strong> Simulate edge cases like power loss, invalid inputs, or simultaneous triggers.<\/li>\n<\/ol>\n<p>Remember: a well-modeled state machine is not just correct\u2014it\u2019s readable and reusable. If a colleague can\u2019t understand your diagram in 30 seconds, reconsider your naming or structure.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>The most frequent issues in state machine diagrams stem from poor design or incomplete modeling.<\/p>\n<ul>\n<li><strong>Missing transitions<\/strong>: A state might have no exit path. Always ensure each non-final state has at least one outgoing transition.<\/li>\n<li><strong>Redundant transitions<\/strong>: Two transitions with the same trigger and guard are often a sign of poor design. Consolidate them.<\/li>\n<li><strong>Unreachable states<\/strong>: If no transition leads to a state, it serves no purpose. Review the logic to remove or fix.<\/li>\n<li><strong>Overuse of guards<\/strong>: Too many guards make the diagram cluttered. Refactor complex logic into compound states or external decision points.<\/li>\n<li><strong>Confusing state names<\/strong>: \u201cState1,\u201d \u201cNewState,\u201d and \u201cTemporary\u201d are not helpful. Use descriptive names like \u201cWaiting for User Input\u201d or \u201cSystem Calibrating.\u201d<\/li>\n<\/ul>\n<p>When in doubt, ask: \u201cCan this be tested?\u201d If not, it\u2019s not modeled well enough.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What is the purpose of a SysML state machine diagram?<\/h3>\n<p>To model the dynamic behavior of a system based on events and state changes. It captures how an object or system responds to triggers, transitions between states, and what actions are performed.<\/p>\n<h3>How do I differentiate between a state and an activity in SysML?<\/h3>\n<p>A <strong>state<\/strong> represents a condition or mode (e.g., \u201cIdle,\u201d \u201cError\u201d). An <strong>activity<\/strong> represents a sequence of actions or steps. Use state machine diagrams for control logic involving persistence and conditions; use activity diagrams for workflow and process flow.<\/p>\n<h3>Can a state have multiple incoming transitions?<\/h3>\n<p>Yes. A state can have multiple incoming transitions, especially in complex systems. However, ensure each transition has a distinct trigger or guard condition to avoid ambiguity. Use orthogonal regions if the system has parallel states.<\/p>\n<h3>What\u2019s the difference between a trigger and a guard in a transition?<\/h3>\n<p>The <strong>trigger<\/strong> is the event that may initiate a transition. The <strong>guard<\/strong> is a condition that must be true for the transition to actually occur. A trigger alone doesn\u2019t guarantee the transition\u2014only when the guard evaluates to true does it fire.<\/p>\n<h3>How do I model a state that can be entered in multiple ways?<\/h3>\n<p>Use multiple incoming transitions to the same state, each with different triggers and potentially different guards. Define entry actions to handle logic that should occur regardless of entry path.<\/p>\n<h3>Can I model parallel states in a SysML state machine diagram?<\/h3>\n<p>Yes. Use orthogonal regions to model parallel state machines. For example, a system could be in \u201cCooling\u201d and \u201cMonitoring Temperature\u201d simultaneously. Each region is a separate state machine but shares the same object.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In a recent project involving a medical device control system, a single unmodeled transition led to a critical state where the device remained in a \u201cwaiting for calibration\u201d state indefinitely\u2014causing operational delays and regulatory scrutiny. This wasn\u2019t due to poor code or hardware flaws. It was a modeling gap. I\u2019ve seen this pattern repeat across [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1601,"menu_order":6,"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-1608","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 State Machine Diagram: Reactive Systems Modeling<\/title>\n<meta name=\"description\" content=\"Learn how to model reactive systems with SysML state machine diagrams. Understand states, transitions, triggers, and guard conditions for robust system control logic.\" \/>\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-diagrams\/sysml-state-machine-diagram-reactive-systems\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SysML State Machine Diagram: Reactive Systems Modeling\" \/>\n<meta property=\"og:description\" content=\"Learn how to model reactive systems with SysML state machine diagrams. Understand states, transitions, triggers, and guard conditions for robust system control logic.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/\" \/>\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=\"7\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-diagrams\/sysml-state-machine-diagram-reactive-systems\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/\",\"name\":\"SysML State Machine Diagram: Reactive Systems Modeling\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:43:50+00:00\",\"description\":\"Learn how to model reactive systems with SysML state machine diagrams. Understand states, transitions, triggers, and guard conditions for robust system control logic.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/#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 Fundamentals in SysML\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"State Machine Diagrams: Modeling Reactive Systems\"}]},{\"@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 State Machine Diagram: Reactive Systems Modeling","description":"Learn how to model reactive systems with SysML state machine diagrams. Understand states, transitions, triggers, and guard conditions for robust system control logic.","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-diagrams\/sysml-state-machine-diagram-reactive-systems\/","og_locale":"de_DE","og_type":"article","og_title":"SysML State Machine Diagram: Reactive Systems Modeling","og_description":"Learn how to model reactive systems with SysML state machine diagrams. Understand states, transitions, triggers, and guard conditions for robust system control logic.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"7\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/","name":"SysML State Machine Diagram: Reactive Systems Modeling","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:43:50+00:00","description":"Learn how to model reactive systems with SysML state machine diagrams. Understand states, transitions, triggers, and guard conditions for robust system control logic.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/sysml-state-machine-diagram-reactive-systems\/#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 Fundamentals in SysML","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/sysml-essentials-for-beginners\/sysml-diagrams\/"},{"@type":"ListItem","position":4,"name":"State Machine Diagrams: Modeling Reactive Systems"}]},{"@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\/1608","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\/1608\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1601"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1608"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1608"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}