Properties not applied to error source

[brlarson]

I get these error reports: Property EMV2::Hazards does not apply to inf Devices.aadl /isolette-ksu/aadl/packages line: 19 /isolette-ksu/aadl/packages/Devices.aadl Xtext Check (fast) Property EMV2::Likelihood does not apply to inf Devices.aadl /isolette-ksu/aadl/packages line: 28 /isolette-ksu/aadl/packages/Devices.aadl Xtext Check (fast) Property EMV2::Severity does not apply to inf Devices.aadl /isolette-ksu/aadl/packages line: 27 /isolette-ksu/aadl/packages/Devices.aadl Xtext Check (fast)

for EMV2 annex subclause:

annex EMV2 {\ use types ErrorLibrary; use behavior KSU_Isolette::FailStop; error propagations internal_failure: out propagation {ItemOmission,ItemCommission}; flows --model error in detection and reporting inf: error source internal_failure{ItemOmission}; end propagations; component error behavior detections --in "failed" state put value on port internal_failure failed -[ ]-> internal_failure!; end component; properties --set occurrence of detection failure EMV2::OccurrenceDistribution => Iso_Properties::DetectionRegulatorFailureRate applies to inf;
--set failure rate for regulator EMV2::OccurrenceDistribution => Iso_Properties::RegulatorFailureRate applies to fail;
EMV2::hazards => ( [ crossreference => "REMH A.5.1.4"; failure => "regulator failure not detected"; phases => ("all"); environment => "infant intensive care"; description => "failed, but not detected"; comment => "effect unknown"; ]) applies to inf; EMV2::Severity => ARP4761::Minor applies to inf; EMV2::Likelihood => ARP4761::ExtremelyRemote applies to inf;
**};

[juli1]

Dear Brian,

Is it possible to provide a complete model to reproduce the bug? Please use gist.github.com to send the models. Thanks.

[brlarson]

see Gist topic:

ErrorModel issue #68: example isolette AADL model

Sample files to show issue with properties of error sources. These source texts, combined into OSATE project(s) will generate 6 error markers: 3x in Devices.aadl to error source "inf", 3x in Regulate.aadl to error source "ifso", All applying EMV2 properties. The BLESS pre-declared packages and property set are included, that would be loaded into Plugin_Resources when the BLESS plugin is installed.

[brlarson]

Julien,

I also am having a similar problem with the BLESS proof tool not finding BLESS::Assertion properties of ports. The symptom is that long-running proof-tactic scripts cause an erroneous proof-exception complaining that an out event port has no Assertion.

I suspect something's a kilter with property associations in the new UML2 Ecore model. When the anomalous behavior is that nothing happens, it's hard to give an example.

[reteprelief]

Works.