EMV2 Annex -- AS5506/5 document preparation

[jjhugues]

This issue tracks the preparation of the AS5506/5 document. This document will gather all annexes in one document.

This particular issue tracks the progress in preparing the chapter on the EMV2 annex.

The EMV2 annex has been updated in AS5506/5 to address 15 errata:

• issue Or operator with XOR semantics #6 "Or operator with XOR semantics" has a proposition made to have a true or and xor operator to reduce the semantics gap. The original EMV2 had or operator with the semantics of xor;
• issue new operators to deal with sets of condition elements #7 introduces all( {set of conditions}) and all -'k' {set of conditions}) operators to complement k ormore and k orless ones;
• issue no restriction on how many initial states #8 details that there can be only one initial state.
• issue Semantics of "orless" and "ormore" definition #13 refines the semantics of ormore and orless
• issue Alternative transitions semantics #16 corrects the interpretation of "alternative transition condition"
• issue Explicit EMV2 metamodel is lacking #34 details the metamodel names that are reserved
• issue Allow properties with EMV2 subclause #42 allows properties with EMV2 subclause,
• issue Reference to MIL-STD882 inconsistent #44 updates the document to reference MIL-STD882E,
• issue Missing legality rule on fixed_probability #46 details legality rules for fixed_probability values
• issue Missing legality rule for ormore and orless #47 add missing legality rules for ormore and orless
• issue Definition of DetectionMechanism property #48 corrects the definition of DetectionMechanism property
• issue Inconsistent rules for error_detection_effect #49 defines the rules for error_detection_effect
• issue Error model subclauses are allowed in feature group types #50 forbids EMV2 subclauses in feature groups,
• issue Clarify restrictions on steady state #51 details the restrictions on steady states,
• issue Naming rule E.8 (N42) is redundant #52 addresses redundancy in the definition of legality rule E.8 (N42)

The following errata are still open for discussion. The urgency is usually unclear at this stage

• issue "orless" and logical negation operation #14 "orless" and logical negation operation
• issue "orless", logical negation and FTA #15 "orless", logical negation and FTA
• issue allow EMV2 specific property associations for core model elements  #31 "allow EMV2 specific property associations for core model elements" misses a minimal working example to go further

The following 12 errata are deferred for future revisions of EMV2. They correspond to errata that would impact the language and cause

• issue cannot reference port array elements in error propagation #12 that limits reference of port array elements in error propagation
• issue equivalent of a priority AND in FTA #17 that discussion priority AND mechanism
• issue Homogeneity of references to AADL core objects #20 that discusses naming references to AADL core objects
• issue Cannot declare states in component error behavior #29 that forbids declaration of states in component error behavior
• issue Cannot associate properties with product error types #30 that limits property association with product error types
• issue Be clear about event vs. state based interpretation #32 that points to ambiguity between state vs. event interpretation of error propagation
• issue Error propagation syntax could be improved #35 that points to limits in syntax
• issue Semantics of propagation with fan-in #36 that discusses semantics of propagation with fan-in
• issue EMV2 property associations inconsistent with core AADL #37 that points to inconsistencies in EMV2 property associations
• issue User defined propagation paths only reference user defined propagation points #40 that points to limits in user-defined propagation paths
• issue Name for error type library #39 that discusses names for error type library
• issue Paths with user-defined propagation points #43 that paths with user-defined propagation points

In addition, the document has been updated to match the latest SAE template.
All models and property sets are available in the git repository at https://github.com/saeaadl/emv2

The document is now ready for review.