[aadl-modeling]: Undetected Error Probability

[David K]

Thank you for your answer. I tried to implement it into my model but the
outcome doesn't change at all. The OSATE editor indicates no errors so I
don't know why.
As reference for the implementation I used Figure 37 in this essay:
https://resources.sei.cmu.edu/asset_files/TechnicalReport/2016_005_001_464390.pdf
The very basic model I created for this purpose is in the attachment as
well as the resulting fault tree. Is there any reason why the error
probability of the "BTCU_Error_Root"-device the doesn't change?





Am Mo., 9. Juli 2018 um 15:47 Uhr schrieb Peter Feiler <phf at sei.cmu.edu>:

> EMV2 has branching transitions. This allows you to model an error event
> triggering a transition. This transition then takes one of several branches
> according to a fixed probability, e.g., your 90%.
>
> One branch goes to a state that gets propagated – the other to a state
> that does not get propagated.
>
>
>
> This capability is handy for modeling error events occurring with a given
> probability that result in persistent or transient error states with a
> specified fixed distribution.
>
>
>
> Peter
>
>
>
> *From:* aadl-modeling-bounces+phf=sei.cmu.edu at lists.sei.cmu.edu [mailto:
> aadl-modeling-bounces+phf=sei.cmu.edu at lists.sei.cmu.edu] *On Behalf Of *David
> K
> *Sent:* Friday, July 6, 2018 5:14 AM
> *To:* AADL Modeling <aadl-modeling at lists.sei.cmu.edu>
> *Subject:* [aadl-modeling]: Undetected Error Probability
>
>
>
> Good morning,
>
>
>
> I have a short question about detected and undetected errors in a FTA:
>
> The occurrencedistribution attribute of the EMV2-Annex displays the
> detected errors in a FTA if I understand it correctly. Now I additionally
> want to model the probability of undetected erors, e.g. an error has a
> probability of 1e-6 but is forwarded only in 90% of the cases. Is there any
> possibility for this. I searched in several documents for it but just found
> the possibility that an error isn't forwarded at all.
>
>
>
>
>
> Greetings
>
> David
>
-------------- next part --------------
HTML attachment scrubbed and removed
-------------- next part --------------
package modeling_file
public

	
	device BTCU_Error_Root
		features
			p_out	:	out event port;
			
			
		annex EMV2{**
			use types	emv2_errortype_definition, ErrorLibrary;
			use behavior ErrorLibrary::PermanentTransientFailure; 
			

			
			component error behavior
				transitions
					t0	:	Operational-[Failure]->(FailedTransient with 0.5, FailedPermanent with others);	
			end component;
			
			properties
				emv2::occurrencedistribution => [ probabilityValue => 0.05e-6 ;] applies to Failure;				
		**};
	end BTCU_Error_Root;
	
	
	device IO
					
		annex EMV2{**
			use types	emv2_errortype_definition, ErrorLibrary;
			use behavior ErrorLibrary::FailStop; 
			
			component error behavior
				events
					Reset	:	recover event;
				transitions
					t0	:	Operational-[Failure]->FailStop;
					t1	:	FailStop-[Reset]->Operational;		
			end component;
			
			properties
				emv2::occurrencedistribution => [ probabilityValue => 0.05e-6 ;] applies to Failure;				
		**};
	end IO;
	
	
	
	
	system BTCU

	end BTCU;

	
	system implementation BTCU.i
		subcomponents
			BTCU_Error_Root	:	device BTCU_Error_Root;
			IO				:	device IO;

			
		annex EMV2{**
			use types	emv2_errortype_definition, ErrorLibrary;
			use behavior ErrorLibrary::FailStop; 
			
			
			composite error behavior
			states
				[BTCU_Error_Root.FailedTransient]-> FailStop;
				[IO.FailStop]-> FailStop;
			end composite;					
		**};	
	end BTCU.i;


end modeling_file;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example.png
Type: image/png
Size: 527158 bytes
Desc: not available
URL: <http://lists.sei.cmu.edu/pipermail/aadl-modeling/attachments/20180710/b9d6ce4e/attachment.png>