Getting a Set of traces from different sources

Question

Hi,

I'm trying to create a "Verification" column in an FHA, to gather there all the means we use to show compliance with a certain failure condition (hazard).

Currently, I'm trying to show in that column a mix of elements coming from:

- Static checklist (CMAs);

- Events (FTAs); and

- Safety requirements (Verification Procedures WIs that I linked from Polarion adding a custom mapping file, so in Medini is a requirement but in Polarion is another thing).

The thing is I'm able to see it properly in Medini, but not when reporting using M2Doc... Something similar happens with requirements (I've already started a ticket in reporting forum about that, but this one is probably related).

I have the current script for that user_verification profile:

self.hazard.mediniGetOpposites('user_failure_condition')
->union(self.malfunctions.mediniGetTracedElements(safetygoals::SafetyRequirement, 'FMET VP'))
->union(self.hazard.mediniGetOpposites('represents')->selectByType(FTA::Event)->select(e:FTA::Event | not e.model.oclIsUndefined()))->asOrderedSet()

[First line for CMAs, second one for testing verification procedures, and the last one for FTAs].

Do you know if there is a chance to improve this script and have a proper outcome in M2Doc?

Many thanks.

Best regards,

Samuel

medini_1059007410 · Answer

Hi Samuel,

Again, great that you found a working solution yourself. Right approach when wanting to access different properties for the different types within the reference column.

Interesting solution with the eClass() - I would have used "{ m:if method.oclIsKindOf(FTA::Event) }" instead. That's just a detail.

Happy Reporting,

Nils

medini_1064234643 · Answer

Not sure if the profile script is the best one, but I figure out how to use it to show the proper outcomes in the M2Doc reporting (I know it's not strictly related to the script discussion forum but still think could be useful for someone else):

{ m:if sc.user_verification <> '' }
{ m:for method | sc.user_verification }
{ m:let method_type = method.eClass().name }
{ m:if method_type = 'Event' }
...
{ m:elseif method_type = 'StaticChecklistItem' }
...
{ m:elseif method_type = 'SafetyRequirement' }
...
{ m:endif }{ m:endlet }{ m:endfor }{ m:endif }

The first 'if' filters if there is an empty field to avoid getting an error (see M2Doc getting errors from "empty" fields topic). Since I have different object types and each one has different attributes I cannot do a general statement to show what I want for all of them, so I create an 'if - elseif' statement to personalize the output.