[cdemirsoy]

Link RootCauseReturnsWrongFreeSampleCount to CompReq CalculationOfFreeSampleCount

• Link mw_com_fta.RootCauseReturnsWrongFreeSampleCount to the existing CompReq CalculationOfFreeSampleCount (SCR-21803116) via derived_from, instead of adding a Mitigation
• Add AssigningNullptrToSamplePtrIncrementsFreeSampleCount in proxy_event_test.cpp, the only part of the requirement that had no test
• Add lobster-tracing: Communication.CalculationOfFreeSampleCount to the new test and to the existing SamplePtrLimitsAreEnforced, so all parts of the requirement trace to the CompReq

The root cause will stay [PARTIAL] until mw::com has a component(...) target in dependable_element.components

[crimson11]

Clarify with Jochen:

I would name the file mitigations.tlrc!
Naming it safetymeasures.tlrc makes no sense to me! Also AoUs and component-rey may be "safety measures" and they are each in their own file - named accordingly!

[cdemirsoy]

Omitting this solution for now.

[crimson11]

So - is this just an arbitrary sample? Because for this root cause I would NOT come up with a mitigation, but with a component req. instead, which can be tested....
I.e. "mitigations" are the "last resort", when we don't have a comp.req. which we can test and we also do not have an AoU, which can handle the issue.

[cdemirsoy]

Alright, I will follow this way.