Relationships

Last modified on July 20th, 2022.


What is a Relationship?

A shortened definition of a relationship, as described in the Lifecycle Modeling Language (LML) Specification 1.2:
A relationship connects entities to each other. ... In LML, all relations shall be defined in both directions and shall have unique names with the same verb. ... Each relationship and its inverse shall have unique names. Relationship names shall also be unique across the whole schema. The relationships enable an English reading of the way entities connect.
We applied this LML definition of an relationship to the bi-directional connections, which can be made between two entities in Innoslate. For example, the standard parent-child relationship (used by all LML entities) is 'decomposed by' and its inverse is 'decomposes.' The relationships available in Innoslate mirror those defined in Table 3-3. Summary Table of LML Relationships (recreated below) of the LML Relationships Specification 1.2:
ActionArtifactAsset (Resource)Characteristic (Measure)Connection (Conduit, Logical)CostDecisionInput/OutputLocation (Orbital, Physical, Virtual)RiskStatement (Requirement)Time
Actiondecomposed by * related to *references(consumes) performed by (produced by) (seizes)specified by-incursenables results ingenerates receiveslocated atcauses mitigates resolves(satisfies) traced from (verifies)occurs
Artifactreferenced bydecomposed by * related to *referenced byreferenced by specified bydefines protocol for referenced byincurs referenced byenables referenced by results inreferenced bylocated atcauses mitigates referenced by resolvesreferenced by (satisfies) source of traced from (verifies)occurs
Asset (Resource)(consumed by) performs (produced by) (seized by)referencesdecomposed by * orbited by * related to *specified byconnected byincursenables made responds to results in-located atcauses mitigates resolves(satisfies) traced from (verifies)occurs
Characteristic (Measure)specifiesreferences specifiesspecifiesdecomposed by * related to * specified by *specifiesincurs specifiesenables results in specifiesspecifieslocated at specifiescauses mitigates resolves specifies(satisfies) specifies traced from (verifies)occurs specifies
Connection (Conduit, Logical)-defined protocol by referencesconnects tospecified bydecomposed by * joined by * related to *incursenables results intransferslocated atcauses mitigates resolves(satisfies) traced from (verifies)occurs
Costincurred byincurred by referencesincurred byincurred by specified byincurred bydecomposed by * related to *enables incurred by results inincurred bylocated atcauses incurred by mitigates resolvesincurred by (satisfies) traced from (verifies)occurs
Decisionenabled by result ofenabled by references result ofenabled by made by responded by result ofenabled by result of specified byenabled by result ofenabled by incurs result ofdecomposed by * related to *enabled by result oflocated atcauses enabled by mitigated by result of resolvesalternative enabled by traced from result ofdate resolved by decision due occurs
Input/Outputgenerated by received byreferences-specified bytransferred byincursenables results indecomposed by * related to *located atcauses mitigates resolves(satisfies) traced from (verifies)occurs
Location (Orbital, Physical, Virtual)locateslocateslocateslocates specified bylocateslocateslocateslocatesdecomposed by * related to *locates mitigateslocates (satisfies) traced from (verifies)occurs
Riskcaused by mitigated by resolved bycaused by mitigated by references resolved bycaused by mitigated by resolved bycaused by mitigated by resolved by specified bycaused by mitigated by resolved bycaused by incurs mitigated by resolved bycaused by enables mitigated by results in resolved bycaused by mitigated by resolved bylocated at mitigated bycaused by * decomposed by * related to * resolved by *caused by mitigated by resolved byoccurs mitigated by
Statement (Requirement)(satisfied by) traced to (verified by)references (satisfied by) sourced by traced to (verified by)(satisfied by) traced to (verified by)(satisfied by) specified by traced to (verified by)(satisfied by) traced to (verified by)incurs (satisfied by) traced to (verified by)alternative of enables traced to results in(satisfied by) traced to (verified by)located at (satisfied by) traced to (verified by)causes mitigates resolvesdecomposed by * traced to * related to *occurs (satisfied by) (verified by)
Timeoccurred byoccurred byoccurred byoccurred by specified byoccurred byoccurred bydate resolves decided by occurred byoccurred byoccurred byoccurred by mitigatesoccurred by (satisfies) (verifies)decomposed by * related to *
Please Note: LML does not claim to solve everyone’s total data capture needs, therefore we have included the capability to extend the default database schema in Innoslate via Innoslate's Schema Editor feature.

Relationships

Last modified on July 20th, 2022. 


What is a Relationship?

A shortened definition of a relationship, as described in the Lifecycle Modeling Language (LML) Specification 1.2:

A relationship connects entities to each other. …

In LML, all relations shall be defined in both directions and shall have unique names with the same verb. … Each relationship and its inverse shall have unique names. Relationship names shall also be unique across the whole schema.

The relationships enable an English reading of the way entities connect.

We applied this LML definition of an relationship to the bi-directional connections, which can be made between two entities in Innoslate. For example, the standard parent-child relationship (used by all LML entities) is ‘decomposed by’ and its inverse is ‘decomposes.’

The relationships available in Innoslate mirror those defined in Table 3-3. Summary Table of LML Relationships (recreated below) of the LML Relationships Specification 1.2:

ActionArtifactAsset
(Resource)
Characteristic
(Measure)
Connection
(Conduit, Logical)
CostDecisionInput/OutputLocation
(Orbital, Physical, Virtual)
RiskStatement
(Requirement)
Time
Actiondecomposed by *
related to *
references(consumes)
performed by
(produced by)
(seizes)
specified byincursenables
results in
generates
receives
located atcauses
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Artifactreferenced bydecomposed by *
related to *
referenced byreferenced by
specified by
defines protocol for
referenced by
incurs
referenced by
enables
referenced by
results in
referenced bylocated atcauses
mitigates
referenced by
resolves
referenced by
(satisfies)
source of
traced from
(verifies)
occurs
Asset
(Resource)
(consumed by)
performs
(produced by)
(seized by)
referencesdecomposed by *
orbited by *
related to *
specified byconnected byincursenables
made
responds to
results in
located atcauses
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Characteristic
(Measure)
specifiesreferences
specifies
specifiesdecomposed by *
related to *
specified by *
specifiesincurs
specifies
enables
results in
specifies
specifieslocated at
specifies
causes
mitigates
resolves
specifies
(satisfies)
specifies
traced from
(verifies)
occurs
specifies
Connection
(Conduit, Logical)
defined protocol by
references
connects tospecified bydecomposed by *
joined by *
related to *
incursenables
results in
transferslocated atcauses
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Costincurred byincurred by
references
incurred byincurred by
specified by
incurred bydecomposed by *
related to *
enables
incurred by
results in
incurred bylocated atcauses
incurred by
mitigates
resolves
incurred by
(satisfies)
traced from
(verifies)
occurs
Decisionenabled by
result of
enabled by
references
result of
enabled by
made by
responded by
result of
enabled by
result of
specified by
enabled by
result of
enabled by
incurs
result of
decomposed by *
related to *
enabled by
result of
located atcauses
enabled by
mitigated by
result of
resolves
alternative
enabled by
traced from
result of
date resolved by
decision due
occurs
Input/Outputgenerated by
received by
referencesspecified bytransferred byincursenables
results in
decomposed by *
related to *
located atcauses
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Location
(Orbital, Physical, Virtual)
locateslocateslocateslocates
specified by
locateslocateslocateslocatesdecomposed by *
related to *
locates
mitigates
locates
(satisfies)
traced from
(verifies)
occurs
Riskcaused by
mitigated by
resolved by
caused by
mitigated by
references
resolved by
caused by
mitigated by
resolved by
caused by
mitigated by
resolved by
specified by
caused by
mitigated by
resolved by
caused by
incurs
mitigated by
resolved by
caused by
enables
mitigated by
results in
resolved by
caused by
mitigated by
resolved by
located at
mitigated by
caused by *
decomposed by *
related to *
resolved by *
caused by
mitigated by
resolved by
occurs
mitigated by
Statement
(Requirement)
(satisfied by)
traced to
(verified by)
references
(satisfied by)
sourced by
traced to
(verified by)
(satisfied by)
traced to
(verified by)
(satisfied by)
specified by
traced to
(verified by)
(satisfied by)
traced to
(verified by)
incurs
(satisfied by)
traced to
(verified by)
alternative of
enables
traced to
results in
(satisfied by)
traced to
(verified by)
located at
(satisfied by)
traced to
(verified by)
causes
mitigates
resolves
decomposed by *
traced to *
related to *
occurs
(satisfied by)
(verified by)
Timeoccurred byoccurred byoccurred byoccurred by
specified by
occurred byoccurred bydate resolves
decided by
occurred by
occurred byoccurred byoccurred by
mitigates
occurred by
(satisfies)
(verifies)
decomposed by *
related to *

Please Note: LML does not claim to solve everyone’s total data capture needs, therefore we have included the capability to extend the default database schema in Innoslate via Innoslate’s Schema Editor feature.