Reference

LML Relationships (schema)

46 relationship pairs. Every relationship has an inverse: “A decomposed by B” also means “B decomposes A”.

Relationship	Inverse	Description
alternative	alternative of	Names a Statement that is one of the options for this Decision. Choice marks the option that was selected.
caused by	causes	Names the entity that gives rise to this Risk or Issue.
connected by	connects to	Names a Connection attached to this Asset.
consumed by	consumes	Names an Action that uses up some of this Resource. What it uses is not given back when the Action ends.
copied by	copies	Names a Requirement that was made as a copy of this one, for example to reuse it in another document.
date resolved by	date resolves	Names the Time at which this Decision was made and closed.
decision due	decided by	Names the Time by which this Decision has to be made.
decomposed by	decomposes	Names a child of this entity in its hierarchy: a part, a subfunction or a lower-level item.
defined protocol by	defines protocol for	Names the Artifact, such as a standard or interface document, that defines the protocol this Conduit uses.
derived by	derives	Names a Requirement that was developed from this one, usually at a lower level of the design.
enabled by	enables	Names an entity that makes this Decision possible or necessary, such as an analysis, a cost or a finding.
equation of	equation for	Names an Equation that calculates or constrains values of this entity.
extend	extended by	Names the base Action or Asset that this one optionally adds behavior to (a use-case «extend»).
fetches	fetched by	Names the state that this Transition leads to (in a state machine).
generates	generated by	Names an item that this Action or state produces.
has dependent	depends on	Names the Action or Dependency that waits for this one.
has variable	variable of	Names a Characteristic that is a variable in this Equation.
included by	include	Names an Action that always uses this one as a part (a use-case «include»).
incurred by	incurs	Names an entity that gives rise to this Cost.
instantiates	instantiated by	Names the definition that this entity is an instance or usage of, such as the block that types a part or the interface that types a port.
joins	joined by	Names the Connection that this Connection ends at. Bidirectional says whether items can flow both ways across the joint.
locates	located at	Names an entity that is at this Location.
made	made by	Names a Decision that this Asset makes or made.
mitigated by	mitigates	Names an entity that reduces the likelihood or effect of this Risk or Issue.
occurs	occurred by	Names the Time at which, or during which, this entity happens or exists.
orbits	orbited by	Names the Asset that this Asset orbits.
performs	performed by	Names an Action that this Asset carries out.
produces	produced by	Names a Resource that this Action creates more of when it finishes.
pushes	pushed by	Names a Transition that leaves this state (in a state machine).
receives	received by	Names an item that this Action or state takes in. Trigger marks an item the Action has to wait for before it can start.
references	referenced by	Names an Artifact that this entity cites as a source or for further detail.
refines	refined by	Names the Requirement that this one makes more precise.
related to	relates	Names a peer entity that this one is associated with. Context can explain how.
represented in	represents	Names an Asset that stands for this one in another view, such as an actor that stands for a person or system.
resolved by	resolves	Names an entity that removes or closes this Risk or Issue.
responds to	responded by	Names a Decision that this Asset acts on.
result of	results in	Names an entity that led to this Decision.
satisfied by	satisfies	Names an entity in the design that fulfills this Requirement.
scheduled by	schedules	Names the Time, such as a sprint or phase, within which this Task is planned.
seizes	seized by	Names a Resource that this Action holds while it runs and gives back when it ends.
source of	sourced by	Names an entity that comes from this Artifact, such as a Statement or Requirement taken from a document.
specified by	specifies	Names a Characteristic that describes this entity in more detail.
traced from	traced to	Names the Statement or Requirement that this entity answers to, for example the need behind a function.
tracked by	tracks	Names the Time, such as a Kanban board column, that shows this Task.
transferred by	transfers	Names the Conduit or Connection that carries this item.
verified by	verifies	Names an entity, usually a Test Case, that shows whether this Requirement is met.

Full documentation: Schema and Extensions › Relations and targets