nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Dynamic Constraints with OCL

medini_1065298040

Hello dear forum members,

I'm new to medini analyze and I'm trying to write a constraint in OCL for the FMEDA, that checks whether there is a mismatch between the boxes that indicate if a component is safety related and the corresponding documents of the project. The mismatch is marked in orange as seen in the picture below.

The problem already starts with the constraint target class, because I'm not sure which one to use. Is there any documentation about the target classes? Or maybe someone alreay has a solution for what I'm trying so solve?

Thank's for helping. Regards Yannik

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Hi Yannik, there is a metamodel guide for example here: https://medini.freshdesk.com/support/discussions/topics/1000086548

I also suggest to run medini in debug mode and use the Attribute View to check objects and attributes at runtime. You find appropriate articles here as well.

I assume the class is the DCComponentEntry class

Happy Scripting

Jan

medini_1023909254

Hi Yannik,

just two additional points:

Are you referring with "...the corresponding documents of the project" to the architecture model from which the Worksheet is derived or something different?
Are you just using "simple" Worksheets or do you do the analyses using variants and/or multiple safety goals with Individual Metrics activated? For the simple case it is probably rather straight-forward, for the other cases the validation rule may become quite complex. BTW, Why do you want to have a validation rule - is the orange highlighting in the Workkseeht not sufficient for you?

Best regards,

Eckhardt

medini_1065298040

Hi Jan and Eckhardt,

thank you for your responses. I'm sorry for my late answer, I was a little bit off topic the last weeks.

To your questions Eckhardt, yes I'm reffering to the architecture model and I'm only using simple worksheets, no variants and no multiple safety goals. The thing is that our FMEDA's are quite big, so a constraint which is returning all the orange marked safety boxes would be helpful. Is there a flag that is set which indicates whether a safety related box in the FMEDA is marked orange or not? I think checking this flag would already be the soultion.

Best regards Yannik

medini_1023909254

Hi Yannik,

so in that case the following constraint should be sufficient:

Here is for your convenience also the OCL:

inv:
if self.element.oclIsKindOf(sysml::SysMLPart)
then
 self.safetyRelated = self.element.oclAsType(sysml::SysMLPart).safetyRelated
else
if self.element.oclIsKindOf(sysml::SysMLPortUsage)
then
 self.safetyRelated = self.element.oclAsType(sysml::SysMLPortUsage).safetyRelated
else
 true
endif endif

And one final remark - on the Coversheet of the DC Worksheet you should select the Metrics at Level Leaves. This makes the worksheet a little more compact and avoids a potential risk of counting failure rates twice.

Best regards,

Eckhardt

medini_1065298040

Hi Eckhardt,

thank you very much for your approach, that's exaclty the the solution I was looking for.

Regards Yannik

medini_1065298040

Hello guys,

I have another question regarding some flags I want to check in OCL. This would be the following cells in the FMEDA sheet:

- failure effect description

- failure kind

- SM prevents FM from violation of Safety Goals

- Self test measure

As also seen in the picture below.

I tried to find the corresponding flags in debug mode, but I couldn't find them.

Best regards Yannik

medini_1023909254

Hello Yannik,

what exactly do you want to check for these entries? ... Note, an OCL Validation rule is a logical expression which checks whether some condition is always validating to true. Also with the exception of "SM prevents FM from violation of Safety Goals" the other fields are all defined by you as a profile property, so I can not say much about them. So you need to give some more explanation on them too

Eckhardt

medini_1065298040

Hi Eckhardt,

as an example for what I want to do, if the safety related flag is set, check whether there is something specified in these boxes and return true if there is something and false if not.

I know that I can do this with the ->notEmpty() function. I checked this for other cells where I know how to access them, there it works. But for checking the named cells I need to know how to access them.

Regards Yannik

medini_1023909254

Hello Yannik,

the names for the user-defined properties can be found also in the debug mode (they all start with user_) - but you may also see the name in the profiling definition itself as shown in the example below:

Depending on how/where you use them the access may be direct using dot-notation (E.g. self.user_comment) or you may use the general approach using a function - i.e. self.getProfilePropertyValue('user_comment') which delivers a sequence of elements referenced by the property.

Eckhardt