Improvement: Define a FFI approach

[aschemmel-tech]

Important

Make sure to link this issue with the PR for your improvement.

FFI (Freedom From Interference) needs to be guaranteed if mixed criticality components are used. E.g. a Logging library may not have any (Functional) Safety Requirement to fulfill, but it might be used by an ASIL B component.
As we usually have no safety mechanism to guarantee that the lib interferes with its users memory (like it is available for seperate processes via MPU memory protection) there needs to be another measure for this.
This measure is currently not defined. For example this could be ASIL B like development quality or doing unit testing including memory overwrite checks.

We may even consider to add a stakeholder requirement for this.