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; } } }

Show value of aprofile variable of traced requirements

medini_1026949627

Hi all,

In a safety mechanism collection I have used the OCL script to list the traced requirements:

self.oclAsType(safetyModel::Measure).mediniGetTracedElements(ecore::EObject)->select(e | e.oclIsKindOf(safetygoals::SafetyRequirement))

In a separate column I want to show the test status which is imported as attribute from DOORS:

The test status is what I want to add to the SM Collection. However, I struggle with modifying the OCL script to show the attribute.

Has anyone an idea?

Kind regards

Günter

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

I think you can use the same OCL statement and then use "collect" on it like:

self.oclAsType(safetyModel::Measure).mediniGetTracedElements(ecore::EObject)->select(e | e.oclIsKindOf(safetygoals::SafetyRequirement))->collect(e | e.oclAsType(safetygoals::SafetyRequirement).state)

Jan

medini_1026949627

Hi Jan,

this works well for 'state'. However, for my user variable "user_test_status" I didn't get it working.

self.oclAsType(safetyModel::Measure).mediniGetTracedElements(ecore::EObject)->select(e | e.oclIsKindOf(safetygoals::SafetyRequirement))->collect(e | e.oclAsType(safetygoals::SafetyRequirement).user_test_status)

Is there a difference between Requiremetns and DOORS Requirements?

Kind regards

Günter

medini_1023909254

Hello Günter,

are you actually using the import/update of requirements from "Classic" DOORS or do you you DOORS NG with import/export resp push/pull of requirements between medini and DOORS NG?

DOORS Requirement in medini is only used for the first case (and the model itself is a DOORS Requirements Model). For the second case (and also for all other requirements systems like PTC, JAMA ...) the standard Requirement is used in medini and the model is a "Safety Goals/Requirements Model". So make sure, you have defined your profile property for the right kind of Requirement and adjust also the types in the oclIsKindOf(...) resp. oclAsType(...) statements as needed.

Best regards,

Eckhardt

medini_1024169437

Hi Günter,

indeed, DOORS imported requirements have a separate meta class for historical reasons.

If you have added the attribute to that class, the last statement (cast and attribute access) will not work.

Maybe this modification will do the trick:

self.oclAsType(safetyModel::Measure).mediniGetTracedElements(ecore::EObject)->select(e | e.oclIsKindOf(safetygoals::SafetyRequirement))->collect(e | e.oclAsType(doorsrequirements::DoorsRequirement).user_test_status)

Happy Scripting

Jan

medini_1026949627

Hi Jan,

no error message but also no value is shown.

@Eckhard: We are using DOORS 9.6

Kind regards

Günter

medini_1023909254

Hi Günter,

in that case, can you try:

self.mediniGetTracedElements(doorsrequirements::DoorsRequirement).oclAsType(doorsrequirements::DoorsRequirement).user_test_status

which should work as long as you have a trace between the safety mechanism and a DOORS requirement

Best regards,
Eckhardt

medini_1024169437

Strangely, both scripts work for me.

Jan

medini_1026949627

Hi Eckhard,

hi Jan,

both scripts are working well! Thank you for your support. Jan, your script worked also yesterday, but I had a safety mechanism displayed with a trace to a Doors requirement without test result. My mistake.

Kind regards