# 📚 SysML Profile for Universal Hex (UHX) This document describes how a **SysML Profile** can be developed to integrate the four pillars of the **Universal Hex (UHX)** framework into SysML-based modeling environments. UHX consists of: - **UHT** – Universal Hex Taxonomy (trait identity) - **UHR** – Universal Hex Relationships (semantic links) - **UHS** – Universal Hex States (behavior and transitions) - **SDR** – Self-Describing Requirements (semantic specifications) Each of these can be mapped to SysML constructs using stereotypes, tagged values, and traceable relationships. --- ## 📊 Overview Table |UHX Pillar|SysML Element|Mapping Strategy| |---|---|---| |**UHT**|Block, Part, Actor|Apply `<<UHT_Element>>` stereotype with tags| |**UHR**|Connector, Dependency, Association|Apply `<<UHR_Link>>` stereotype to relationships| |**UHS**|StateMachine, Transition|Apply `<<UHX_Transition>>` to transitions, annotate states with UHT| |**SDR**|Requirement, ConstraintBlock|Define `<<SDR>>` stereotype with traits, links, and parameter tags| --- ## 🌟 UHT in SysML ### Stereotype: `<<UHT_Element>>` ```sysml + uhtCode: String // 32-bit hex code + activeTraits: Integer[] // Optional: list of bit indexes + semanticLayer: Enum {Physical, Functional, Abstract, Social} ``` Use this on: - Blocks - Actors - Components - Use Cases --- ## 🔗 UHR in SysML ### Stereotype: `<<UHR_Link>>` ```sysml + uhrCode: String // 8-bit hex (e.g. C1) + traits: String[] // Optional: list of relational traits + label: String // Human-readable name (e.g. Feeds →) + trigger: String // Optional trigger condition ``` Apply to: - Connectors - ControlFlows - Dependencies Enables structured, explainable linkage between system parts. --- ## ⏱️ UHS in SysML ### States Annotate each `State` element with: ```sysml + uhtCode: String ``` ### Transitions Apply `<<UHX_Transition>>` stereotype: ```sysml + trigger: String + causeLink: String // UHR code + deltaTraits: Integer[] // Optional ``` Allows UHT-coded state machines with causal transitions. --- ## 🔨 SDRs in SysML ### Stereotype: `<<SDR>>` ```sysml + mustHaveTraits: Integer[] + mustNotHaveTraits: Integer[] + requiredLinks: String[] // UHR codes + parameters: Map<String, Range> + references: URI[] ``` Apply to: - `Requirement` - `ConstraintBlock` This supports traceability and validation against components or state models. --- ## 🔎 Validation & Analysis - Use **trait matching logic** to validate `<<UHT_Element>>` against `<<SDR>>` - Check UHR link conformity for architecture coverage - Run state transition checks for behavior requirements Tools can implement validators that: - Decode UHT/UHR codes - Compare trait deltas - Trace from SDR to model blocks --- ## 🎯 Use Cases - Model-based design with explainable semantic structure - Safety-critical behavior validation using UHS - Interface control compliance with UHR - Semantically compressed requirement reuse via SDR --- ## 🔄 Summary |Layer|Stereotype|Purpose| |---|---|---| |UHT|`<<UHT_Element>>`|Identity and semantic traits| |UHR|`<<UHR_Link>>`|Relationship typing and causality| |UHS|`<<UHX_Transition>>`|State transitions with trait logic| |SDR|`<<SDR>>`|Declarative, testable requirements| This profile bridges formal SysML modeling with trait-based semantic reasoning.