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

Request to Implement OCL Constraint – Validation of Failure Modes per Function

medini_1073797666

Hello,

I'd like to request the implementation of the following OCL constraint to be applied to the HARA table:

Constraint Objective:

Ensure that each function defined in the HARA includes at least one instance of each of the following failure modes:

Loss

Not

Degraded

Unexpected

Untimely

Thank you in advance for your support.

Best regards,

Hiba

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1063548292

Hi Hiba!

I kind of forgot that navigation via mediniGetOpposites() works only with the "reference" profile property.

So in this case the user_function defined at HaEv is a derived property ... sooorry for that!

So I had to use All Instances j'ai décidé to go for HazardAnalysisModel, that maybe better for performance .. not really sure, can also use HazardousEvent.allInstances()

I also noticed that you placed the code into the HazardousEvent as a target Class while I assumed sysml::SysMLActivity

Another point I think one should also take care about following case :

The function is not part of any HARA -> hEvents is empty -> causing false flags

Overall A simple modifications of my previous OCL code :

Source:

inv EnsureAllFailureModesUsedOncePerFunction :
 --define required malfunctions
let requiredModes : Set(String) = Set{'loss', 'not', 'degraded', 'unexpected', 'intempestive'}
in

-- collect all Hazardous events tthat are linked with current function ( sysml:SysMLActivity)
let hEvents : Set(hazard::HazardousEvent) = hazard::HazardAnalysisModel.allInstances().hazardElements
	->selectByKind(hazard::HazardousEvent)
	->select(he:hazard::HazardousEvent|he.getProfilePropertyValue('user_function')->includes(self))->asSet()
	->asSet() 
in

--get malufnciton names from Hazradous event
	let foundMfs : Set(String) = hEvents.malfunctions
		->selectByKind(safetyModel::Malfunction)
		->collect(m | m.name.trim().toLower())
		->asSet()
	in
 -- preare a list of missing fialure names
	let MessageArg1 : Set(String) = requiredModes
		--using matches with wildacrds, uncommment to enable 
		--->reject(req | foundMfs->exists(curr|curr.matches('.*'+req+'.*'))) 
		--using str = str
		->reject(req | foundMfs->exists(curr|curr = req)) 
in
 -- funciton ust have some hevents associated and the 'seen' sequence ( MEssageArg1) has to be empty to return false
 MessageArg1->isEmpty() or hEvents->isEmpty()

and result in ESL example:

Marian

All comments

medini_1073797666

On this table we need to ensure that each function has the 5 failure modes used at least once.
for FP1 for example only one failure mode is used, so we need to get a warning on that function saying that all other four failure mode are not used for that function

we tried to add this validation rule but it doesn't seem to work.

medini_1063548292

Hi Hiba,

Interesting touch I did not know that yo can "save" the package prefix ("hazard::")

I laso did not know that within the dyn constrain you don't neef to use i.user_function resp i.getProfilePropertyValue('user_function')

now to what spotted

line 2 :
I am surprised that there was no error as the variables expects String while you collect SysMLActivity.
I would maybe shorten the query

let functions:Set(sysml::SysMLActivity) = HazardousEvent.allInstances().function
->selectByKind(sysml::SysMLActivity)
->asSet()

not sure if the list of mfnames will be exact (string = string ) or just some further string th adjustment shiuld be done(.trim().toLower()) and maybe use matches() or other method to test if the mf name contains the required text

You can also use some let MessageArg1:OclAny= .. to debug/report a bit on what mfs from required list are missing

just to confirm the list of malfunctions shall be present in a single HARA or in any HARA? The approach you choose will be yield different results when executed oa a project as a scope or other hierarchy ( package/GHARA)

Marian

medini_1063548292

Hi iIba,

Question,Have you considered to use sysml::SysMLActivity as a target class for a constraint? Seems like it should be that as the validations wil report problematic functions

And

check if the function is part of HARA event
let hEvents: Set(hazard::HazrdousEvent)=self.mediniGetOpposites('user_function')
->selectByKind(hara::HazardousEvent)->asSet()
in
scan malfunctions of found HazarduosEvent
let foundmfs:Set(String)= hEvnts.malfunctions
->selectByKind(safetyModel::Malfunction).name->asSet()
in
condition and store the list of HE entered malfunctions against expect names
let MessageArg1:Set(String)=requiredModes
->reject(reqName|foundmfs.name.trim().toLower()->including(reqName))
check if missing Names stored inside of MessageArg1 is empty, if nt it will be passed to the message as arg {1}
MessageArg1->isEmpty()

The message can looks like

{0} has missing HARA malfunctions:{1}

If it does not matter if malfunctions and functions are in many HARAs then the 1 & 2 can be combined into one
let foundmfs:Set(String)=self.mediniGetOpposites('user_function')
->selectByKind(hara::HazardousEvent)->asSet().malfunctions
->selectByKind(safetyModel::Malfunction).name->asSet()

Marian

medini_1073797666

Hello,

Thanks for your response !

I followed your recommendations and updated the code, but it still displays the entire list instead of only those with fewer than 5 failure modes.

inv
EnsureAllFailureModesUsedOncePerFunction :

let requiredModes : Set(String) = Set{'loss', 'not', 'degraded', 'unexpected', 'intempestive'} in

let hEvents : Set(hazard::HazardousEvent) = self.mediniGetOpposites('user_function')

->selectByKind(hazard::HazardousEvent)->asSet() in

let foundMfs : Set(String) =
hEvents.malfunctions

->selectByKind(safetyModel::Malfunction)

->collect(m | m.name.trim().toLower())

->asSet() in

let MessageArg1 : Set(String) =
requiredModes

->reject(req | foundMfs->includes(req)) in

MessageArg1->isEmpty()

Thank you !

Hiba

medini_1063548292

Hi Hiba!

I kind of forgot that navigation via mediniGetOpposites() works only with the "reference" profile property.

So in this case the user_function defined at HaEv is a derived property ... sooorry for that!

So I had to use All Instances j'ai décidé to go for HazardAnalysisModel, that maybe better for performance .. not really sure, can also use HazardousEvent.allInstances()

I also noticed that you placed the code into the HazardousEvent as a target Class while I assumed sysml::SysMLActivity

Another point I think one should also take care about following case :

The function is not part of any HARA -> hEvents is empty -> causing false flags

Overall A simple modifications of my previous OCL code :

Source:

inv EnsureAllFailureModesUsedOncePerFunction :
 --define required malfunctions
let requiredModes : Set(String) = Set{'loss', 'not', 'degraded', 'unexpected', 'intempestive'}
in

-- collect all Hazardous events tthat are linked with current function ( sysml:SysMLActivity)
let hEvents : Set(hazard::HazardousEvent) = hazard::HazardAnalysisModel.allInstances().hazardElements
	->selectByKind(hazard::HazardousEvent)
	->select(he:hazard::HazardousEvent|he.getProfilePropertyValue('user_function')->includes(self))->asSet()
	->asSet() 
in

--get malufnciton names from Hazradous event
	let foundMfs : Set(String) = hEvents.malfunctions
		->selectByKind(safetyModel::Malfunction)
		->collect(m | m.name.trim().toLower())
		->asSet()
	in
 -- preare a list of missing fialure names
	let MessageArg1 : Set(String) = requiredModes
		--using matches with wildacrds, uncommment to enable 
		--->reject(req | foundMfs->exists(curr|curr.matches('.*'+req+'.*'))) 
		--using str = str
		->reject(req | foundMfs->exists(curr|curr = req)) 
in
 -- funciton ust have some hevents associated and the 'seen' sequence ( MEssageArg1) has to be empty to return false
 MessageArg1->isEmpty() or hEvents->isEmpty()

and result in ESL example:

Marian

medini_1073797666

Hello Marian,

Thank you for the support!

The code is still not working as expected on my end.

For the function FP3, as you can see, not all the failure modes are present, yet I don’t get any warning or message indicating that some are missing.

Could you please check on your side?

Best regards,

Hiba

medini_1063548292

Hi Hiba,

couple of points.

since the rule is now configured on the Function make sure your Validation scope includes the packages with functions. So if you run Validation on the HARA package you will not get any valid results while when executed on the project you should see the violations (I tested this on the ESL)
Having validation rule to "Live" will effectively trigger the rule whenever any changes are done to a Function object not to the HARA event
Could you copy this rule into an ESL example and try to validate the ESL project whether you will be able to arrive to same results as I did?

Marian

medini_1073797666

Hello Marian,

On the ESL project it's actually working, but not on the template I'm working on.

Can we set a meeting ?

Thank you!

Regards,

Hiba

medini_1063548292

Hi Hiba,

Just to inform others that we resolved the problem. The constraint was correct but there was different problem preventing it from working in your particular project.

Can you mark this article as answered ?

Merci,

Marian