F_CM: no arbitration made between USBKey and NavigationParameters

AdaCore / RESSAC_Use_Case

A Collaborative Development Assurance Lab

6 stars 12 forks source link

F_CM: no arbitration made between USBKey and NavigationParameters #4

Open AnthonyLeonardoGracio opened 7 years ago

AnthonyLeonardoGracio commented 7 years ago

Document: UseCaseDevelopment/Layer1_MMS/RESSAC_muXAV_SystemRQ_MMS_SW_Incr1.doc Commit: 74aa074

Dans la spec de F_CM il est dit que F_CM gère les incohérences entre les données venant de GS et celles venant d'AV, mais je ne comprends pas comment c'est possible puisqu'il transfère à F_MM à la fois USBKey et NavigationParameters.

ledinot commented 7 years ago

Yes, F_MM is in charge of this priority management, not F_CM. Move the sentence "When the two channels are active.....CP prevails over GS" from 6.9.4 to 6.6.4.