Supported SysML v2 Language

Holarch supports SysML v2 projects based on the OMGObject Management Group The standards body that maintains UML, SysML, UAF and XMI. SysML v2 specification. It implements a subset of the language; this page lists what works today and what is not yet available.

Language

• Packages, nested packages, imports (also recursive and filtered), aliases, visibility, short names, doc and comments.
• Definitions and usages of parts, attributes, items, ports, connections, interfaces, flows, actions, states, requirements, constraints, calculations, use cases, analysis and verification cases, views, enumerations, occurrences and allocations.
• Typing, specialization, subsetting, redefinition, conjugated ports, feature chains and multiplicities.
• Values with units (1650 [kg]), quantity kinds and unit checks, expressions and calculations, evaluated by the model.
• Successions, control nodes, guards, accept and send, loops; states with entry, do and exit actions, transitions and parallel regions.
• Requirements with subject, require constraint, satisfy and verify; use cases with actors and include.
• Metadata, including Holarch's own HolarchMetadata (TBDTo Be Determined A requirement value or detail that is not known yet. Holarch tracks TBDs with an owner and a due date. and TBRTo Be Reviewed A requirement value that is filled in but still needs to be confirmed.) and HolarchFrameworks packages.

In Holarch

• The Editor with checks, completion, go to definition and rename; the Browser; the read-only Standard Library.
• General, Interconnection, Action Flow, State Transition, Sequence and Grid views, the Requirement, Use Case, Parametric and Package views, and a 2D Geometry View (Views in SysML v2 Projects).
• Holarch's analysis diagrams (Spider, Hierarchy, Tree, IDEF0Integration Definition for Function Modeling A function-modeling method: each box is a function, with inputs, controls, outputs and mechanisms on fixed sides., ICOMInputs, Controls, Outputs, Mechanisms The four kinds of arrows on an IDEF0 box, each entering or leaving on its own side., FFBDFunctional Flow Block Diagram A diagram of functions in the order they run, with branches, loops and parallel paths.) and Functional Analysis (Analysis Diagrams and Functional Analysis in SysML v2 Projects).
• The lifecycle pages on the model: Requirements, Quality, TBD/TBR, Suspect Links, Approvals, RVTMRequirements Verification Traceability Matrix A table of each requirement with how it is verified, the tests that verify it and their latest result., Verification Cases, Traceability Matrix, Model Checks, Interfaces, Budgets & TPMsTechnical Performance Measure A key technical parameter, such as mass or power, tracked over time against its target and threshold., Trade Studies, Risk & Decisions, Plan & Deliver, DoDAFDepartment of Defense Architecture Framework The US DoD framework for describing architectures as a set of viewpoints and products, such as OV-1 and SV-1. and UAFUnified Architecture Framework An OMG architecture framework that organizes views in a grid of viewpoints and aspects. It covers DoDAF and NATO needs..
• Simulating action flows: Discrete Event runs, Monte Carlo studies and Check Against Requirement (Simulate Action Flows).
• Documents, whiteboards and presentations that read the model; Word, Excel, CSV and picture exports.
• Import and export of .sysml files and SysML v2 JSON (Import and Export SysML v2 Files).
• The API and MCP: reading the model, proposals checked before review, and the read-only Systems Modeling API (The API and MCP in SysML v2 Projects).
• Converted copies, from LMLLifecycle Modeling Language An open modeling language with a small set of classes and relationships that covers a system's whole lifecycle. Holarch models are LML models. to SysML v2 and back, with a report of what does not convert (Converting Projects).

Not yet

• Pulling from and pushing to a SysML v2 model repository.
• Writing to Holarch through the Systems Modeling API; it reads the current model only.
• Running state machines; actions run only in the Simulator, as action flows.
• Variants and configurations (the text is kept as written), individuals, snapshots and time slices.
• User-defined keywords and language extensions; models written only in KerML. .kerml files are not read.
• 3D geometry; exchanging view layouts with other tools.
• Editing the standard library; it is read-only.