Relationships

Last modified on January 31st, 2017.


What is a Relationship?

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

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 also shall 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.1:

  Action Artifact Asset
(Resource)
Characteristic
(Measure)
Connection
(Conduit, Logical)
Cost Decision Input/Output Location
(Orbital, Physical, Virtual)
Risk Statement
(Requirement)
Time
Action decomposed by *
related to *
references (consumes)
performed by
(produced by)
(seizes)
specified by - incurs enables
results in
generates
receives
located at causes
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Artifact referenced by decomposed by *
related to *
referenced by referenced by
specified by
defines protocol for
referenced by
incurs
referenced by
enables
referenced by
results in
referenced by located at causes
mitigates
referenced by
resolves
referenced by
(satisfies)
source of
traced from
(verifies)
occurs
Asset
(Resource)
(consumed by)
performs
(produced by)
(seized by)
references decomposed by *
orbited by *
related to *
specified by connected by incurs enables
made
responds to
results in
- located at causes
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Characteristic
(Measure)
specifies references
specifies
specifies decomposed by *
related to *
specified by *
specifies incurs
specifies
enables
results in
specifies
specifies located at
specifies
causes
mitigates
resolves
specifies
(satisfies)
specifies
traced from
(verifies)
occurs
specifies
Connection
(Conduit, Logical)
- defined protocol by
references
connects to specified by decomposed by *
joined by *
related to *
incurs enables
results in
transfers located at causes
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Cost incurred by incurred by
references
incurred by incurred by
specified by
incurred by decomposed by *
related to *
enables
incurred by
results in
incurred by located at causes
incurred by
mitigates
resolves
incurred by
(satisfies)
traced from
(verifies)
occurs
Decision enabled 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 at causes
enabled by
mitigated by
result of
resolves
alternative
enabled by
traced from
result of
date resolved by
decision due
occurs
Input/Output generated by
received by
references - specified by transferred by incurs enables
results in
decomposed by *
related to *
located at causes
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Location
(Orbital, Physical, Virtual)
locates locates locates locates
specified by
locates locates locates locates decomposed by *
related to *
locates
mitigates
locates
(satisfies)
traced from
(verifies)
occurs
Risk caused 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)
Time occurred by occurred by occurred by occurred by
specified by
occurred by occurred by date resolves
decided by
occurred by
occurred by occurred by occurred by
mitigates
occurred by
(satisfies)
(verifies)
decomposed by *
related to *

 

Please Note:

Relationships

Last modified on January 31st, 2017. 


What is a Relationship?

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

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 also shall 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.1:

  Action Artifact Asset
(Resource)
Characteristic
(Measure)
Connection
(Conduit, Logical)
Cost Decision Input/Output Location
(Orbital, Physical, Virtual)
Risk Statement
(Requirement)
Time
Action decomposed by *
related to *
references (consumes)
performed by
(produced by)
(seizes)
specified by incurs enables
results in
generates
receives
located at causes
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Artifact referenced by decomposed by *
related to *
referenced by referenced by
specified by
defines protocol for
referenced by
incurs
referenced by
enables
referenced by
results in
referenced by located at causes
mitigates
referenced by
resolves
referenced by
(satisfies)
source of
traced from
(verifies)
occurs
Asset
(Resource)
(consumed by)
performs
(produced by)
(seized by)
references decomposed by *
orbited by *
related to *
specified by connected by incurs enables
made
responds to
results in
located at causes
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Characteristic
(Measure)
specifies references
specifies
specifies decomposed by *
related to *
specified by *
specifies incurs
specifies
enables
results in
specifies
specifies located at
specifies
causes
mitigates
resolves
specifies
(satisfies)
specifies
traced from
(verifies)
occurs
specifies
Connection
(Conduit, Logical)
defined protocol by
references
connects to specified by decomposed by *
joined by *
related to *
incurs enables
results in
transfers located at causes
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Cost incurred by incurred by
references
incurred by incurred by
specified by
incurred by decomposed by *
related to *
enables
incurred by
results in
incurred by located at causes
incurred by
mitigates
resolves
incurred by
(satisfies)
traced from
(verifies)
occurs
Decision enabled 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 at causes
enabled by
mitigated by
result of
resolves
alternative
enabled by
traced from
result of
date resolved by
decision due
occurs
Input/Output generated by
received by
references specified by transferred by incurs enables
results in
decomposed by *
related to *
located at causes
mitigates
resolves
(satisfies)
traced from
(verifies)
occurs
Location
(Orbital, Physical, Virtual)
locates locates locates locates
specified by
locates locates locates locates decomposed by *
related to *
locates
mitigates
locates
(satisfies)
traced from
(verifies)
occurs
Risk caused 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)
Time occurred by occurred by occurred by occurred by
specified by
occurred by occurred by date resolves
decided by
occurred by
occurred by occurred by occurred 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.