Feature Requirements#
Coverage: 100.0% (55 of 55 items OK)
[OK] TRLC Assumedsystemreq Communication.ASR_ErrorHandling
(C++) exceptions shall not be used for error handling. The best way to deal with errors is to try to resolve those component internally. If not possible the caller of the function shall be notified of the error. For (error) returns there is a specific library to be used in S-CORE, it is the score::Result library which is part of the Base Libraries feature.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:17:27
[OK] TRLC Assumedsystemreq Communication.ASR_InterProcessCommunication
The platform shall support inter-process communication.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:27:27
[OK] TRLC Assumedsystemreq Communication.ASR_IntraProcessCommunication
The platform shall support intra-process communication.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:34:27
[OK] TRLC Assumedsystemreq Communication.ASR_ExtensibleExternalCommunication
The platform shall support external communication via well established protocols e.g. Zenoh, DDS, SOME/IP.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:41:27
[OK] TRLC Assumedsystemreq Communication.ASR_SafeCommunication
The platform shall support safe communication in terms of ISO 26262. I.e. it shall provide mechanisms to avoid communication errors defined by the ISO 26262.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:48:27
[OK] TRLC Assumedsystemreq Communication.ASR_SecureCommunication
The information exchanged between applications shall be protected against unauthorized access and manipulation. The platform shall provide mechanisms to ensure confidentiality, integrity, and authenticity of the exchanged information.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:55:27
[OK] TRLC Assumedsystemreq Communication.ASR_SupportForTimeBasedArchitectures
The platform shall support a deterministic, time-based application execution model that triggers logic based on predefined schedules or polling intervals.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:62:27
[OK] TRLC Assumedsystemreq Communication.ASR_SupportForDataDrivenArchitecture
The platform shall support an event-driven, high-throughput application architecture where execution is triggered by data changes.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:69:27
[OK] TRLC Assumedsystemreq Communication.ASR_SupportForRequestDrivenArchitecture
The platform shall support a request-driven application architecture that processes requests on-demand.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:76:27
[OK] TRLC Assumedsystemreq Communication.ASR_ProgrammingLanguagesForApplicationDevelopment
The platform shall support implementation of applications in the following programming languages up to the highest ASIL level as defined in automotive_safety: C++, Rust.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:84:27
[OK] TRLC Assumedsystemreq Communication.ASR_TracingOfCommunication
The platform shall support the tracing of communication events for internal and external communication systems.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:91:27
[OK] TRLC Assumedsystemreq Communication.ASR_AvailabilityOfCommunicationPartners
The platform shall provide a mechanism to detect the availability of communication partners for internal and external communication systems and provide the required information to communicate with them.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:98:27
[OK] TRLC Assumedsystemreq Communication.ASR_StablePublicApi
The platform shall provide a stable API for the communication middleware.
Source: score/mw/com/dependability/assumed_system/assumed_system_requirements.trlc:105:27
[OK] TRLC Featreq Communication.FEAT_SupportForTimeBasedArchitecture
The communication framework shall provide API to support a time-based architecture.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:17:18
[OK] TRLC Featreq Communication.FEAT_SupportForDataDrivenArchitecture
The communication framework shall provide API to support a data-driven architecture.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:24:18
[OK] TRLC Featreq Communication.FEAT_SupportForRequestDrivenArchitecture
The communication framework shall provide API to support a request-driven architecture.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:31:18
[OK] TRLC Featreq Communication.FEAT_CommunicationInterfaces
The communication framework shall support communication interfaces composed of any number of the following elements: Events, Methods, Fields, Signals.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:38:18
[OK] TRLC Featreq Communication.FEAT_EventTypeStructure
An event-type shall be a named element of a communication interface with an associated data type.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:45:18
[OK] TRLC Featreq Communication.FEAT_EventAccess
An event-type shall allow its producer to assign a value and its consumers to either subscribe to value-changed events or poll unseen, cached events.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:52:18
[OK] TRLC Featreq Communication.FEAT_MethodStructure
A method shall be defined by a name, a specified application routine with a given set of parameters, and a return type.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:59:18
[OK] TRLC Featreq Communication.FEAT_MethodInvocation
When a communication partner calls a method with the required parameters, the method shall invoke its application routine with those parameters, return the result to the caller, and support both synchronous and asynchronous invocation.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:66:18
[OK] TRLC Featreq Communication.FEAT_FieldTypeStructure
A field shall be defined by a name, a data type, and dedicated getter and setter methods.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:73:18
[OK] TRLC Featreq Communication.FEAT_FieldAccess
A field shall allow its producer to assign a value, and shall allow its consumers to subscribe to value-changed notifications, poll unseen cached values, or retrieve and update the value via its getter and setter methods.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:80:18
[OK] TRLC Featreq Communication.FEAT_SignalStructure
A signal shall be a named element of a communication interface that does not transport data.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:87:18
[OK] TRLC Featreq Communication.FEAT_SignalAccess
A signal is sent by a service-provider, and it shall be supported, that a service-consumer can wait for its reception and also check/poll if the signal was received or subscribe to update notifications.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:94:18
[OK] TRLC Featreq Communication.FEAT_ProducerConsumerPattern
Communication shall be cached based on the producer-consumer pattern.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:101:18
[OK] TRLC Featreq Communication.FEAT_ServiceInstance
The communication framework shall support offering multiple service instances for the same interface.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:108:18
[OK] TRLC Featreq Communication.FEAT_ServiceInstanceNames
A service instance shall be offered and discoverable under one unique name.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:115:18
[OK] TRLC Featreq Communication.FEAT_ServiceLocationTransparency
The interface to access service instances shall be agnostic to the binding used to communicate with the service.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:122:18
[OK] TRLC Featreq Communication.FEAT_StatelessCommunication
The communication framework shall support stateless communication.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:129:18
[OK] TRLC Featreq Communication.FEAT_ServiceInstanceGranularity
The communication framework shall support multiple service instances per software architecture element.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:136:18
[OK] TRLC Featreq Communication.FEAT_ServiceDiscovery
The communication framework shall provide service discovery that considers version compatibility to find available services during runtime.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:143:18
[OK] TRLC Featreq Communication.FEAT_SafeCommunication
The communication framework shall support safe communication involving communication partners on the same or multiple criticality levels.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:150:18
[OK] TRLC Featreq Communication.FEAT_DataCorruption
Consumers with lower criticality shall not be able to corrupt data consumed by partners with higher criticality.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:157:18
[OK] TRLC Featreq Communication.FEAT_DataReordering
Consumers with lower criticality shall not be able to modify the order of data consumed by partners with higher criticality.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:164:18
[OK] TRLC Featreq Communication.FEAT_DataRepetition
Consumers with lower criticality shall not be able to duplicate data consumed by other communication partners with higher criticality.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:171:18
[OK] TRLC Featreq Communication.FEAT_DataLoss
Consumers with lower criticality shall not be able to drop data before it is consumed by partners with higher criticality.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:178:18
[OK] TRLC Featreq Communication.FEAT_ZeroCopy
The communication framework shall enable Zero-Copy communication without copying to-be-transferred data.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:185:18
[OK] TRLC Featreq Communication.FEAT_SupportForMultipleProgrammingLanguages
The communication framework shall provide a public API for each supported programming language of S-CORE.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:192:18
[OK] TRLC Featreq Communication.FEAT_SupportForProgrammingLanguageIdioms
Each public API shall support the idioms of the programming language it is written in.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:199:18
[OK] TRLC Featreq Communication.FEAT_UseProgrammingLanguageInfrastructure
Each public API shall use core infrastructure of its programming language and its accompanying standard libraries.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:206:18
[OK] TRLC Featreq Communication.FEAT_FullyMockablePublicAPI
The public API shall be fully mockable.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:214:18
[OK] TRLC Featreq Communication.FEAT_FakeBinding
The communication framework shall provide a fake binding.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:221:18
[OK] TRLC Featreq Communication.FEAT_MultiBindingSupport
The communication framework shall support multiple bindings.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:228:18
[OK] TRLC Featreq Communication.FEAT_BindingAgnosticPublicAPI
The public API of the communication framework shall be binding-agnostic.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:235:18
[OK] TRLC Featreq Communication.FEAT_MultiBindingDeploymentConfiguration
The association between a service instance and its binding shall be specified in the deployment configuration.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:242:18
[OK] TRLC Featreq Communication.FEAT_DeploymentConfigurationAtRuntime
Deployment configuration shall be read from an integrity-checked configuration file at runtime.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:249:18
[OK] TRLC Featreq Communication.FEAT_SupportForTracing
The communication framework shall provide infrastructure to enable binding-agnostic, zero-copy, read-only tracing of communication.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:256:18
[OK] TRLC Featreq Communication.FEAT_AccessControlListPerServiceInstance
The communication framework shall support an Access Control List per service instance.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:263:18
[OK] TRLC Featreq Communication.FEAT_AccessControlListForProducer
The communication framework shall support an Access Control List for the communication partner offering a service instance (producer).
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:270:18
[OK] TRLC Featreq Communication.FEAT_AccessControlListForConsumer
The communication framework shall support an Access Control List for the communication partner consuming a service instance.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:277:18
[OK] TRLC Featreq Communication.FEAT_CommunicationASILLevel
The communication framework shall support safe communication up to ASIL-B.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:284:18
[OK] TRLC Featreq Communication.FEAT_CommunicationPartnerCrashRecovery
The communication framework shall support crash recovery and allow a communication partner to rejoin an earlier initialized communication after an application termination.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:291:18
[OK] TRLC Featreq Communication.FEAT_CommunicationAcrossOSBoundaries
The communication framework shall support technologies which allow communication across operating system boundaries.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:298:18
[OK] TRLC Featreq Communication.FEAT_ErrorHandling
(C++) exceptions shall not be used for error handling. The best way to deal with errors is to try to resolve those component internally. If not possible the caller of the function shall be notified of the error. For (error) returns there is a specific library to be used in S-CORE, it is the Score::Result library which is part of the Base Libraries feature.
Source: score/mw/com/dependability/requirements/feature_requirements/feature_requirements_ipc.trlc:305:18