Safety Manual

Communication Safety Manual		status: draft security: NO safety: ASIL_B
realizes: wp__module_safety_manual
doc__communication_safety_manual		Generic Document

Introduction/Scope

This safety manual covers the communication module.

Assumed Platform Safety Requirements

For the communication module the following safety related stakeholder requirements are assumed to define the top level functionality (purpose) of the communication module. I.e. from these all the feature and component requirements implemented are derived.

<List here all the stakeholder requirements, with safety not equal to QM, the module’s components requirements are derived from.>

Attention

This section is currently missing.

Assumptions of Use

Assumptions on the Environment

Generally the assumption of the project platform SEooC is that it is integrated in a safe system, i.e. the POSIX OS it runs on is qualified and also the HW related failures are taken into account by the system integrator, if not otherwise stated in the module’s safety concept.

<List here all the OS calls the project platform expects to be safe.>

Attention

This section is currently missing.

List of AoUs expected from the environment the platform / module runs on:

No needs passed the filters

Assumptions on the User

As there is no assumption on which specific OS and HW is used, the integration testing of the stakeholder and feature requirements is expected to be performed by the user of the platform SEooC. Tests covering all stakeholder and feature requirements performed on a reference platform (tbd link to reference platform specification), reviewed and passed are included in the platform SEooC safety case.

Additionally the components of the platform may have additional specific assumptions how they are used. These are part of every module documentation: <link to add>. Assumptions from components to their users can be fulfilled in two ways:

1. There are assumption which need to be fulfilled by all SW components, e.g. “every user of an IPC mechanism needs to make sure that he provides correct data (including appropriate ASIL level)” - in this case the AoU is marked as “platform”.

2. There are assumption which can be fulfilled by a safety mechanism realized by some other project platform component and are therefore not relevant for an user who uses the whole platform. But those are relevant if you chose to use the module SEooC stand-alone - in this case the AoU is marked as “module”. An example would be the “JSON read” which requires “The user shall provide a string as input which is not corrupted due to HW or QM SW errors.” - which is covered when using together with safe project platform persistency feature.

List of AoUs on the user of the platform features or the module of this safety manual:

Title	ID	Status
aragen not safe	aou_req__communication__27	valid
Check for nullptr on Allocate()	aou_req__communication__14	valid
Checking for possible message overflow	aou_req__communication__8	valid
Config on a safe filesystem	aou_req__communication__10	valid
Correctly configured ASIL Level	aou_req__communication__4	valid
Correctly configured events/fields per service type	aou_req__communication__34	valid
Correctly configured maximum number of maximum elements per subscriber	aou_req__communication__3	valid
Correctly Configured Maximum Number of Subscribers	aou_req__communication__2	valid
Different user for ASIL and QM processes	aou_req__communication__9	valid
Event or Field reception via GenericProxy needs specific care	aou_req__communication__32	valid
Event Subscription active while holding SamplePtr	aou_req__communication__19	valid
LoLa Memory only accessed through LoLa	aou_req__communication__24	valid
LoLa specific QNX Messaging End-Points only accessed through LoLa	aou_req__communication__26	valid
Monotonic Semi-Dynamic Memory Allocation	aou_req__communication__1	valid
No APIs from Implementation Namespace	aou_req__communication__6	valid
No Copy-Send() while holding AllocateePtr.	aou_req__communication__16	valid
No guarantee in availability of services	aou_req__communication__12	valid
No guarantee on execution time	aou_req__communication__29	valid
No guarantees for notifications	aou_req__communication__7	valid
No notification on termination of producer	aou_req__communication__13	valid
No shared memory allocation in namespace lola	aou_req__communication__25	valid
No static context support	aou_req__communication__11	valid
Non-Terminating callbacks	aou_req__communication__20	valid
None reentrant methods per event instance	aou_req__communication__17	valid
One producer only one AllocateePtr	aou_req__communication__15	valid
Only LoLa supported types	aou_req__communication__5	valid
Quality of data is dependent on producer	aou_req__communication__22	valid
Same compiler settings for provider and consumer side	aou_req__communication__31	valid
Skeleton alive while its AllocateePtr being used	aou_req__communication__18	valid
unsupported data-types	aou_req__communication__28	valid
Usage of configuration "oversubscription"	aou_req__communication__30	valid
Valid callbacks while proxy alive	aou_req__communication__21	valid
Validity of pointer on LoLa pointer	aou_req__communication__23	valid

Safety concept of the SEooC

<Describe here the safety concept incl. which faults are taken care of, reactions of the implemented functions under anomalous operating conditions … if this is not already documented sufficiently in the feature documentation “safety impact” section of all the features the module is used in.>

Attention

This section is currently missing.

Safety Anomalies

Anomalies (bugs in ASIL SW, detected by testing or by users, which could not be fixed) known before release are documented in the platform/module release notes <add link to release note>.

Attention

This section is currently missing.

References

User Manual

<other links>