LML
LML language coverage
Holarch's LML projects support LML 1.x models and are based on the LML 2.0 specification, published openly by the Lifecycle Modeling Organization. This page lists each part of the specification and how far Holarch supports it.
What the levels mean
- Supported: the element is in Holarch's default schema with the meaning the specification gives it, and the pages, diagrams, checks and exports that use it read and write it.
- Partial: supported, with the limits named in the row.
- Not yet: not available.
LML defines no conformance test suite, so "supported" here means that the element is present with the meaning the specification states.
Jump to: LML 1.x models · Classes, relationships and attributes · Diagrams · Execution · Appendices · Known gaps
LML 1.x models
LML 2.0 support is an addition. Every class, relationship, attribute and value that LML 1.x models use stays in Holarch with its meaning, and projects made before the LML 2.0 additions open, display, check and export as they did. Where LML 2.0 moved or added something, Holarch keeps the earlier form next to the new one:
- Start and Percent Complete on Action stay, although LML 2.0 moved them to Task. Tasks inherit them.
- The Verification Requirement type of Requirement (a label) stays next to the new Verification Requirement class.
- Task priority labels High, Medium and Low stay next to the new Priority attribute.
- Handling Strategy on Risk stays in projects that have it; projects created since use Mitigation Status, with the same values.
- Test cases that verify requirements directly count in the verification matrix as before; test cases traced from a Verification Requirement count too.
A project created before the LML 2.0 additions keeps its schema. Schema → Add New Built-ins… adds the new classes, relationships and attributes to it without changing anything that is there.
Classes, relationships and attributes
| Area | Level | Elements | Limits |
|---|---|---|---|
| Entity classes | Supported | All 24 classes of the core: Action, Task, Test Case, Artifact, Asset, Resource, Characteristic, Measure, Connection, Conduit, Dependency, Logical, Cost, Decision, Input/Output, Location, Orbital, Physical, Virtual, Risk, Statement, Requirement, Verification Requirement, Time. From the SysML appendix: Equation and Port. From the structured-artifacts appendix: Heading. | Holarch adds Issue and Transition, which the specification allows as extensions. |
| Relationships | Supported | Every relationship pair of the core in both directions, including evaluates / evaluated by (Test Case and Asset), contains / contained by and originates / originated by from the structured-artifacts appendix, decomposition of Logical connections and transfers on any Connection; the SysML appendix relationships. | None known. |
| Attributes on relationships | Supported | Context, amount, trigger, origin, multiplicity, bidirectional, dependency, choice and responsibility. | None known. |
| Class attributes | Supported | The attributes of every class, including the LML 2.0 additions: Verification Requirement (verification method, acceptance criteria, evidence, rationale), Test Case event conditions and event constraints, Task planned start and priority, Risk mitigation status and trend, Decision status Open and Closed, Time end, Physical units. | None known. |
| Data types | Supported | All 18: Big Text, Boolean, Computable, DateTime, Duration, Enumeration, Equation, File, GeoPoint, HTML, Multiplicity, Multiselect, Number (including distributions), Percent, Quality, Text, URI, User/Team. | None known. |
| Types, inheritance and extensions | Supported | Types as labels, inherited attributes and relationships, and project schema extensions. | None known. |
Diagrams
| Diagram | Level | Limits |
|---|---|---|
| Action Diagram | Supported | Sequence, parallel with SYNC, OR, LOOP and EXIT; inputs and outputs; resources. |
| Asset Diagram | Supported | Conduit capacity and latency can be shown on the lines (Show Capacity and Latency), as on the Interface Control Diagram. |
| Spider Diagram | Supported | None known. |
| Interface Control Diagram | Supported | None known. |
| Class, Hierarchy, Timeline, Risk Matrix and State Machine diagrams | Supported | None known. |
| Fault tree | Supported | Risks, hazards and failure modes as events with AND, OR, voting and inhibit gates; the top-event probability from each risk's probability, minimal cut sets and importance. Static gates only. |
| Entity-relationship-attribute (ERAA) view | Supported | The Class diagram's Relationship Attributes view lists each relationship's attributes and the characteristics that specify it. |
| SysML 1.x diagrams from the SysML appendix | Supported | All nine diagram types, drawn from the LML model. |
Execution
Supported. The Simulator runs Action diagrams as the specification describes: an action starts when control has reached it, its trigger inputs have arrived and its resources are available; consumes, produces and seizes change resource levels; conduit latency and capacity delay transfers; durations can be distributions; OR, LOOP and SYNC behave as specified; discrete-event and Monte Carlo runs total cost and time.
Appendices
- SysML mapping: supported, with XMI import and export.
- DoDAF and UAF: DoDAF products are supported; UAF views are offered over Holarch's diagrams.
- Structured artifacts: supported. Documents are built from any class; the Heading class makes a section that contains items of any class, which keep their own numbers, and originates / originated by links a requirement to the artifact it came from.
- REST API: Holarch has its own public API and MCP endpoint rather than the appendix's example API.
Known gaps
None known. Optional diagram details that Holarch does not draw are named in the tables above.
The Lifecycle Modeling Language specification is published by the Lifecycle Modeling Organization at lifecyclemodeling.org. What’s new lists each change to Holarch's LML support.