Converting Projects

A project keeps its type. To work on an 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. model in SysML v2, or on a SysML v2 model with the LML pages, make a converted copy. The original project stays unchanged.

Make a copy

• On Manage Projects, click ⋯ on the project's row.
• Choose Make a SysML v2 Copy… (LML project) or Make an LML Copy… (SysML v2 project).
• Read the report: what converts, with counts, and what does not, with the reason. Download Report (CSV) saves it with each item.
• Enter a name and click Create Copy. The copy opens; its document Conversion report lists every item that did not convert.

LML to SysML v2

• Assets become part definitions; each decomposition becomes a part usage in the parent's definition, and the top assets become parts in package System. Ports become ports; characteristics of an asset become attributes.
• Conduits become connections, or interfaces when both ends are ports.
• Requirements become requirement usages (number as short name, text as documentation); status and verification methods stay with them. Satisfied by becomes satisfy.
• Test cases become verification cases with a verify objective, in a package per test suite; their result stays with them.
• Actions become action usages with successions: SYNC and parallel blocks become fork and join, OR becomes decide and merge, LOOP becomes a loop action. When every branch label of an OR is a Boolean expression over model values (such as speed > 3), the labels become guards; otherwise they become doc comments on the successions, and the branches stay a free choice. Branch probabilities stay with the successions for the Simulator. Received and generated input/outputs become item parameters, with flows between neighboring actions. Performed by becomes perform in the part definition; use cases get their actors.
• State characteristics and transitions become a state definition that the asset exhibits. Equations become constraint definitions with their variables; the expression is kept as a comment.
• Risks, decisions, tasks, costs, schedules, issues, documents and whiteboards are copied and stay linked to the converted elements.

SysML v2 to LML

• Each part usage becomes an Asset, with the parts, ports and attributes of its definition (and of the definitions it specializes) copied in; redefinitions replace what they redefine.
• Connections and interfaces become conduits between those assets; requirements, verification cases, satisfy, verify, perform, item parameters, states and transitions map back as above.
• Successions become action flows; a decision's guards (or the doc comments of its successions) become the OR branch labels, with their probabilities. A succession graph that is not a sequence of parallel, decision and loop blocks is put in order, and the report says where.

Not converted, and listed in the report: diagram layouts (views and diagrams are drawn fresh), history, baselines, change requests, and the elements one language has no place for, such as LML measures and resources or SysML enumerations, calculations and analysis cases.