Feature Requirements#
Coverage: 60.9% (14 of 23 items OK)
[MISSING] TRLC Assumedsystemreq MessagePassing.ClientServerCommunicationModel
The system shall provide a mechanism for two application processes to communicate as a client and a server across process boundaries: a server process accepts connections addressed to a named service, and a client process initiates a connection to that named service.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:22:27
[MISSING] TRLC Assumedsystemreq MessagePassing.PointToPointConnectionTopology
Each connection the system establishes between a client and a server shall connect exactly one client endpoint to exactly one server endpoint for the connection’s entire lifetime.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:29:27
[MISSING] TRLC Assumedsystemreq MessagePassing.RequestReplyInteractionCapability
The system shall support a request-reply interaction, in which a request sent to a server yields a corresponding reply from that server as part of the same interaction.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:36:27
[MISSING] TRLC Assumedsystemreq MessagePassing.OneWayMessageDeliveryCapability
The system shall support delivering a message from either end of a connection to the other without the sender waiting for or expecting a reply.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:43:27
[MISSING] TRLC Assumedsystemreq MessagePassing.RuntimeFailureDetectability
The system shall provide the communicating application with the means to determine, during operation, that a communication attempt has failed rather than succeeded.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:50:27
[MISSING] TRLC Assumedsystemreq MessagePassing.IntegrationMisconfigurationDetectability
The system shall provide the means to detect, when a client and a server first attempt to communicate, that they have been configured with incompatible communication parameters.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:57:27
[MISSING] TRLC Assumedsystemreq MessagePassing.PlatformAbstraction
The system shall provide its client-server communication API in a form usable across more than one host operating system, to support development, evaluation, and testing convenience, and deployment in non-safety (QM) contexts on platforms other than the certified safety target.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:64:27
[MISSING] TRLC Assumedsystemreq MessagePassing.QnxAsilBQualifiedImplementation
On QNX, the system’s certified safety target platform, the common client-server API, its shared abstraction code, and the underlying transport implementation shall be capable of ASIL B qualification.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:71:27
[MISSING] TRLC Assumedsystemreq MessagePassing.PeerIdentityInformationForAccessControl
The system shall provide the server with information identifying the connecting client, sufficient to support the integrator’s own authentication and/or access-control decisions.
Traces to:
missing reference to Component Requirements
Source: score/message_passing/dependability/assumed_system/assumed_system_requirements.trlc:78:27
[OK] TRLC Featreq MessagePassing.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
[OK] TRLC Featreq MessagePassing.ClientInterface
The message passing component shall provide a client interface that establishes and maintains a connection to a server, exposing its lifecycle state, the reason for its termination, and a callback invoked on every state change.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:29:18
[OK] TRLC Featreq MessagePassing.OSIndependentAPI
The message passing component shall provide an OS-independent API for OS-native IPC mechanisms.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:36:18
[OK] TRLC Featreq MessagePassing.QMImplementationOnNonQnxOS
The message passing component shall provide a QM-quality implementation of its API on host operating systems other than QNX, to support development, evaluation, testing, and QM deployment off the ASIL B certified target.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:43:18
[OK] TRLC Featreq MessagePassing.SafetyCertifiedTransportMechanism
The implementation under QNX shall use a safety-certified transport mechanism.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:50: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:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:57:18
[OK] TRLC Featreq MessagePassing.SynchronousUnidirectionalCommunication
The communication shall support client-initiated one-way message sending (Send) on a given connection, where the send call is allowed to hand the message directly to the underlying OS transport call, which may block the calling thread, depending on client configuration and whether a reply is currently pending on the same connection.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:64: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:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:72:18
[OK] TRLC Featreq MessagePassing.AsynchronousUnidirectionalCommunication
The communication shall support client-initiated one-way message sending (Send) on a given connection, where the send call enqueues the message for asynchronous delivery by the background transport and returns after local acceptance, whenever client configuration or a reply currently pending on the same connection requires it. No guarantee is provided that an enqueued message is delivered to or processed by the receiver.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:79:18
[OK] TRLC Featreq MessagePassing.AsynchronousServerNotification
The message passing component shall allow a server to send a one-way notification message to a connected client (Notify), unconditionally asynchronously: the call returns after the message has been accepted by the local message passing layer, without blocking on the client’s receipt or processing of the notification.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:86:18
[OK] TRLC Featreq MessagePassing.SingletonFreeImplementation
The Message Passing library design shall not use any singletons.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:93:18
[OK] TRLC Featreq MessagePassing.AllowsBoundedMonotonicMemoryAllocation
The Message Passing library design shall allow bounded monotonic memory allocation.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:101:18
[OK] TRLC Featreq MessagePassing.AllowsResourceMockInjectionForTesting
The Message Passing library design shall allow resource mock injection for testing.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:108:18
[OK] TRLC Featreq MessagePassing.ClientIdentificationForAccessControl
The message passing component shall provide the server-side application with the OS-provided identity of the client of each Server Connection, to support server-side client identification and access control decisions.
Traces to:
Source: score/message_passing/dependability/requirements/feature_requirements.trlc:115:18