Feature Requirements

Coverage: 76.9% (10 of 13 items OK)

[MISSING] TRLC Assumedsystemreq MessagePassing.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 Mitigation MessagePassing.SafeState

The Safe State of the system shall be *safe-silent*

---

Traces to:

• missing reference to Component Requirements

---

Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:29:21

[MISSING] TRLC Featreq MessagePassing.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

[OK] TRLC Featreq MessagePassing.ServerInterface

The message passing component shall provide a server interface that registers connection handlers and processes incoming requests.

---

Traces to:

• MessagePassing.OSProvidedSenderIdentity

• MessagePassing.UnforgableSenderIdentity

• MessagePassing.ServerCallbacksAreSequential

• MessagePassing.IServerStartListeningAPI

• MessagePassing.IServerStopListeningAPI

• MessagePassing.IServerConnectionNotifyAPI

• MessagePassing.ServerConnectionRefusal

• MessagePassing.ServerIConnectionHandlerDispatch

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:22:18

[OK] TRLC Featreq MessagePassing.OSIndependentAPI

The message passing component shall provide an OS-independent API for OS-native IPC mechanisms.

---

Traces to:

• MessagePassing.SafetyCertifiedTransportMechanismUnderQNX

• MessagePassing.TransportMechanismOnLinux

• MessagePassing.ClientConnectionMaintainsStateMachine

• MessagePassing.ClientFactoryCreateAPI

• MessagePassing.ServerFactoryCreateAPI

• MessagePassing.IClientConnectionGetStateAPI

• MessagePassing.ClientConnectionStateCallbackInvocation

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:29:18

[OK] TRLC Featreq MessagePassing.SafetyCertifiedTransportMechanism

The implementation under QNX shall use a safety-certified transport mechanism.

---

Traces to:

• MessagePassing.SafetyCertifiedTransportMechanismUnderQNX

• MessagePassing.TransportMechanismOnLinux

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:36:18

[OK] TRLC Featreq MessagePassing.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:

• MessagePassing.MessageOrderPreservationPerConnection

• MessagePassing.SingleServerInstancePerServiceIdentifier

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:43:18

[OK] TRLC Featreq MessagePassing.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:

• MessagePassing.SynchronousSendBlocksUntilServerReceives

• MessagePassing.IClientConnectionSendAPI

• MessagePassing.ClientConnectionSendFailsWhenStopped

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:57:18

[OK] TRLC Featreq MessagePassing.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:

• MessagePassing.ServerProcessesSinglePendingRequest

• MessagePassing.SendWaitReplyBlocksUntilServerReply

• MessagePassing.IClientConnectionSendWaitReplyAPI

• MessagePassing.IServerConnectionReplyAPI

• MessagePassing.ClientConnectionSendWaitReplyFailsWhenStopped

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:64:18

[OK] TRLC Featreq MessagePassing.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:

• MessagePassing.AsynchronousSendReturnsAfterLocalAcceptance

• MessagePassing.IClientConnectionSendWithCallbackAPI

• MessagePassing.ClientConnectionSendWithCallbackFailsWhenStopped

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:71:18

[OK] TRLC Featreq MessagePassing.SingletonFreeImplementation

The Message Passing library design shall not use any singletons.

---

Traces to:

• MessagePassing.ClientConnectionSharedResourceEngineInjection

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:78:18

[OK] TRLC Featreq MessagePassing.AllowsBoundedMonotonicMemoryAllocation

The Message Passing library design shall allow bounded monotonic memory allocation.

---

Traces to:

• MessagePassing.ServerPreallocatesConnectionObjects

• MessagePassing.ServerRingBufferQueueSizeConfigurable

• MessagePassing.ClientConnectionSendQueuePreallocation

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:86:18

[OK] TRLC Featreq MessagePassing.AllowsResourceMockInjectionForTesting

The Message Passing library design shall allow resource mock injection for testing.

---

Traces to:

• MessagePassing.ClientConnectionMockInjectionForTesting

---

Source: score/message_passing/dependability/requirements/feature_requirements.trlc:93:18