Abstract: A computer-implemented method for maintaining a function of a local entity upon connection disruption to a backend in a communication system including a backend and a plurality of local entities. The backend provides backend information for the function. The method includes reception of local behavior models from a plurality of local entities by the backend, wherein the local behavior models provide the function in the local entities if particular backend information is not available; creation of a behavior model based on the received local behavior models; and transmission of the behavior model to a local entity of the plurality of the local entities by the backend.

Abstract: A computer-implemented method for preventing loss of function in a local instance when there is a disturbance of a connection to a backend in a communication system that has a local instance having a local agent and a backend acting in part as a global agent, an agent designating a unit that is designed to achieve defined goals through autonomous behavior. The method includes, when there is a connection to the backend, the providing of the function by the global agent, which receives backend information from the backend during the providing of the function, and, if a connection to the backend is disturbed, the providing of the function by the local agent.

Abstract: A method for communicating data requests to one or more data sources. The method includes receiving a data request, with which data of one or more data types are requested, from an application, and checking the availability of one or more data sources that are able to provide the one or more requested data types. The method further comprises: if at least one of the one or more data sources is available, sending a request to the available data source for the requested associated data type that the data source can provide; and, if no data source is available for at least one of the requested data types, sending a request for this data type to a placeholder module.

Abstract: A method for testing a, in particular safety-relevant, technical system, in particular encompassing software. The system is represented by a model encompassing at least two or more components. An assumption of a respective component regarding the safety-relevant system, and a guarantee of a respective component to the safety-relevant technical system, are specified by a safety contract. Executable program code is generated based on at least one assumption and based on at least one guarantee. The safety-relevant technical system is tested by executing the program code.

Abstract: A method for communicating data requests to one or more data sources. The method includes receiving a data request, with which data of one or more data types are requested, from an application, and checking the availability of one or more data sources that are able to provide the one or more requested data types. The method further comprises: if at least one of the one or more data sources is available, sending a request to the available data source for the requested associated data type that the data source can provide; and, if no data source is available for at least one of the requested data types, sending a request for this data type to a placeholder module.

Abstract: A computer-implemented method for testing an, in particular, safety-relevant, technical system, in particular including software and/or hardware components. The method includes the following steps: providing a model of the technical system; providing a set of requirements to the technical system; converting a particular requirement into at least one formal expression of at least one formal logic, the formal logic being selected from a logic set, which includes at least two formal logics, based on properties of the requirements; checking whether a particular requirement has been met by the model, the checking taking place by carrying out at least one program solver for a particular formal expression.

Abstract: A method for testing a, in particular safety-relevant, technical system, in particular encompassing software. The system is represented by a model encompassing at least two or more components. An assumption of a respective component regarding the safety-relevant system, and a guarantee of a respective component to the safety-relevant technical system, are specified by a safety contract. Executable program code is generated based on at least one assumption and based on at least one guarantee. The safety-relevant technical system is tested by executing the program code.

Abstract: A method for agreeing to a collaboration between a first system and a second system. The method includes: assumptions of the first system with respect to the second system, and guarantees of the first system to the second system, are transmitted by the first system, assumptions of the second system with respect to the first system, and guarantees of the second system to the first system, are transmitted by the second system, if reciprocal assumptions and guarantees correspond to one another, a digital safety contract is concluded between the first system and the second system, and the safety contract is documented in a transaction database.