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

What is the easiest way to debug OCL in Medini?

medini_1060067341

Hello,

Are there any features that make debugging OCL easier in Medini?

For example, whenever I have to specify a Dynamic Constraint, I have to open up the Settings menu for my project and then write my OCL rules there.

If I want to check the attributes from a meta-class, I have to close everything down, use the "What is This?" option for that meta-class and then go back into the Project Settings again to continue writing my OCL rule.

Are there any plugins or any specific editors that makes the whole process of debugging OCL rules easier in Medini? Are there any ways to test my inv rules somewhere else in a more efficient way, and then, once I see they are working, I can simply create a new dynamic constraint and paste the inv rule into it?

Thanks,

Lucas

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hi Lucas,

the OCL console is s"selection sensitive", so you really have to select the "self" object in the model browser first.

The OCL console checks for the selection and if it is an EMF object, it is assigned to "self".

Jan

All comments

medini_1059007410

Hi Lucas,

For looking up metamodel classes and navigating the model I would recommend to open medini twice (with different workspaces, be aware: uses two licenses). Apart from that I don't know another shortcut, maybe Eckhardt or Jan?

Cheers,

Nils

medini_1024169437

Well, there is this "interactive OCL console", one option:

be careful, it doe snot evaluate like medini, it is the pure MDT OCL engine, not our extended version.

Second option (not known widely) is that the "Execute" way of executing scripts can also handle OCL scripts. So just name the file not foo.js but foo.ocl and execute it via the menu. The OCl is evaluated in a read-only transaction.

Regards

Jan

medini_1060067341

Hello Jan,

I've tried using the Interactive OCL console in the past but couldn't really do it.

For example, right now, if I try to do something like:

context security::Vulnerability:

inv: self.id.matches('V001')

I get an error saying "No context element is selected". So how do I go about setting the right context in the OCL Console?

If I try to create an ocl file and execute it, then I get an error message that says: "Cannot evaluate script. inv: misplaced construct(s)".

What am I doing wrong here?

Thanks,

Lucas

medini_1024169437

Hi Lucas,

the OCL console is s"selection sensitive", so you really have to select the "self" object in the model browser first.

The OCL console checks for the selection and if it is an EMF object, it is assigned to "self".

Jan

medini_1060067341

Oh... I see. Now I got it to work. Thanks!!!

medini_1063548292

Hi Jan,

I was
looking for a best article to add my observation..

One thing
you said

"be
careful, it does not evaluate like medini, it is the pure MDT OCL engine, not
our extended version."

What did
you mean by that? The fact the metamodel packages used in profile
property & Dynamic Constraints are not available?

I would
like to prove the opposite. The interactive console actually handles all
available emf packages present in the environment in the application.

The only difference
is the package name . For example couple of cases where the package names differs
or are overlapping:

Package	Package name	Profile Prop.	Dyn. Constraint	OCL console	Example	Note
Project model	‘projectmodel’	Yes	Yes	No	projectmodel::PJResource
Project model	‘pjm’	Yes	Yes	Yes	pjm::PJResource
Trace model	‘traceability’	Yes	Yes	No	traceability::Trace
Trace model	‘tracemodel’	Yes	Yes	Yes	tracemodel::Trace
Checklist	‘checklist’	Yes	Yes	No	checklist::ChecklistItem
Checklist	‘de::ikv::analyze::checklist’	Yes	Yes	Yes	de::ikv::analyze::checklist::ChecklistItem
Safety Goals & Requirements	‘safetygoals’	Yes	Yes	No	safetygoals::SafetyGoal
Safety Goals & Requirements	‘safegoals’	Yes	Yes	Yes	safegoals::SafetyGoal
Attack Tree	‘attacktree’	Yes	Yes	No	attacktree::AttackPathModel
Attack Tree	‘at’	Yes	Yes	Yes	at::AttackPathModel
FTA analysis	‘FTA’	Yes	Yes	No	FTA::TransferGate
FTA analysis	‘fta’	Yes	Yes	Yes	fta::TransferGate
Safety Model	‘safetyModel’	Yes	Yes	No	safetyModel::Hazard
Safety Model	‘safety’	Yes	Yes	Yes	safety::Hazard
Hazard analysis model	‘hazop’	Yes	Yes	No	hazop::GuideWord
Hazard analysis model	‘hazopmodel’	Yes	Yes	Yes	hazopmodel::GuideWord
Goal Model	‘goal’	Yes	Yes	No	goal::GoalRelation
Goal Model	‘goalmodel’	Yes	Yes	Yes	goalmodel::GoalRelation
Failure rate & catalog	‘failureratecatalogs’	Yes	Yes	Yes	failureratecatalogs::FRVariable	Not available in DYN Constraints target class list box
SysML Table model	‘table’	Yes	Yes	Yes	table::SysMLTableRow	Not available in DYN Constraints target class list box
Table Layot model	‘layout’	Yes	Yes	Yes	layout::ColumnState	Not available in DYN Constraints target class list box
Cyber Security	‘cybersecurity’	Yes	Yes	Yes	cybersecurity::SecurityAttribute	Not available in DYN Constraints target class list box

And more …

PS : Valid
for 2024R1+ … I think that sample applies for mdoc .. Maybe it could be good to
include this in a Metamodel Guide or Help ?

Happy OCL
debugging!

Marian

medini_1024169437

Hi Marian, this is very good observations, thanks for sharing! I will definitely share this and add it to the documentation.

Btw. my statement about "not like medini" might be indeed obsolete: in the early days our profile mechanism was not 100% EMF like to other EMF based tools like the OCL COnsole or BIRT based reports could not "see" them. We have changed that and I assume that this is the reason why you for example cann access user_ properties correctly even in non-medini tooling.

Happy using OCL indeed

Jan