Feature Requirements#
Coverage: 8.3% (1 of 12 items OK)
[MISSING] TRLC Assumedsystemreq MessagePassingSEooC.SystemMessagingProtocol
The system shall provide a mechanism for inter-process communication via a client-server messaging protocol.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:22:27
[MISSING] TRLC Featreq MessagePassingSEooC.OSIndependentAPI
The message passing component shall provide an OS-independent API for OS-native IPC mechanisms.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:29:18
[MISSING] TRLC Featreq MessagePassingSEooC.SafetyCertifiedTransportMechanism
The implementation under QNX shall use a safety-certified transport mechanism.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:36:18
[MISSING] TRLC Featreq MessagePassingSEooC.PointToPointConnections
The message passing component shall support only point-to-point (1:1) connections between communication endpoints. N:M connections are explicitly excluded.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:43:18
[MISSING] TRLC Featreq MessagePassingSEooC.SmallDataLowLatencyCommunication
The message passing component shall provide low-latency communication for small data between dedicated endpoints.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:50:18
[MISSING] TRLC Featreq MessagePassingSEooC.SynchronousUnidirectionalCommunication
The communication shall support synchronous unidirectional message sending on a given connection. The send call blocks until the message has been transferred to the receiving side and a suitable handler has been identified.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:57:18
[MISSING] TRLC Featreq MessagePassingSEooC.SynchronousBidirectionalCommunication
The communication shall support synchronous bidirectional request-response communication on a given connection. The send call blocks until a reply from the receiver has been received (SendWaitReply).
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:64:18
[MISSING] TRLC Featreq MessagePassingSEooC.AsynchronousUnidirectionalCommunication
The communication shall support asynchronous unidirectional message sending, where the send call returns after the local message passing layer has accepted the message. No guarantee is provided that the message is delivered to or processed by the receiver.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:71:18
[MISSING] TRLC Featreq MessagePassingSEooC.SingletonFreeImplementation
The Message Passing library design shall not use any singletons.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:78:18
[MISSING] TRLC Featreq MessagePassingSEooC.AllowsBoundedMonotonicMemoryAllocation
The Message Passing library design shall allow bounded monotonic memory allocation.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:86:18
[MISSING] TRLC Featreq MessagePassingSEooC.AllowsResourceMockInjectionForTesting
The Message Passing library design shall allow resource mock injection for testing.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:93:18
[OK] TRLC Featreq MessagePassingSEooC.ServerInterface
The message passing component shall provide a server interface that registers connection handlers and processes incoming requests.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:22:18