A common use case of "derived" aka "scripted" profile properties is to navigate references and traces in the project and to show traced or referenced elements in table columns. If you have done that or read some of my articles, you know that this is quite simple and easily done with OCL or Java Script for example by doing:
-- OCL
self.nameOfReference
As the title already names it, that is <?WORD FLAGGED?> easy if you have a reference from and object A to an object B. Each name has a reference and you just use it in the script to navigate. However, there are many references in the medini metamodel that are "uni-directional" so A references B but that does not imply that you can easily navigate from B to A.
An example: a failure mode has references to one or more safety mechanism, one for SPF another for LF. These references are typically utilized by FMEDA/DC worksheets.
A nice use case now is to see all failure modes that are addressed by a safety mechanism also in the SM collection. To accomplish that, the script has to utilize the so called "cross reference" and use the "mediniGetOpposites" operation.
To sow that I have prepared a derived property at Safety Mechanisms:
The script can be done in OCL or JS, they mostly look the same:
or as snippet for copy / paste:
self.mediniGetOpposites('spfSafetyMechanisms')The trick is to "navigate" the spfSafetyMechanism reference (which is defined for Failure Modes) reverse and by doing so "finding all failure modes that reference the safety mechanism".
The result looks like this:
You can extend this and script another column for "mpfSafetyMechanisms".
Happy Scripting
Jan
