Autonomous systems are gaining momentum in various application domains, such as autonomous vehicles, autonomous transport robotics and self-adaptation in smart homes. Product liability regulations impose high standards on manufacturers of such systems with respect to dependability (safety, security and privacy). Today's conventional engineering methods are not adequate for providing guarantees with respect to dependability requirements in a costefficient manner, e.g. road tests in the automotive industry sum up millions of miles before a system can be considered sufficiently safe. System engineers will no longer be able to test and respectively formally verify autonomous systems during development time in order to guarantee the dependability requirements in advance. In this vision paper, we introduce a new holistic software systems engineering approach for autonomous systems, which integrates development time methods as well as operation time techniques. With this approach, we aim to give the users a transparent view of the confidence level of the autonomous system under use with respect to the dependability requirements. We present already obtained results and point out research goals to be addressed in the future.

No abstract

No abstract

Die Systems-of-Systems (SoS) bilden eine neue Klasse von Softwaresystemen, deren Ziel es ist, ehemals isolierte Systeme miteinander zu vernetzen und dadurch dem Anwender einen größeren Nutzen zu bieten, als die teilnehmenden Einzelsysteme es vermögen. Die Integration, der unabhängig entwickelten Systeme, zu einem solchen SoS birgt allerdings Risiken. Hierbei ist ein zentraler Faktor die Frage der Gültigkeit systemweiter Korrektheitsbedingungen (sog. Constraints) in einem SoS nach der Integration der Einzelsysteme. Denn die Gültigkeit SoS-weiter Constraints bei der Bewertung von Einzelsystemen in einer modellierten Systemumgebung garantiert nicht hinreichend die Gültigkeit dieser Constraints in einem integrierten SoS. Grund dafür ist der höhere Abstraktionsgrad der modellierten Systemumgebung gegenüber dem SoS. In diesem Papier wird ein Ansatz vorgestellt, welcher es zur Entwicklungszeit eines SoS erlaubt, sowohl die einzelnen Teilsysteme als auch das daraus resultierende SoS zu verifizieren und dadurch unerwartetes Verhalten anhand von Constraint-Verletzungen zu identifizieren. Als Grundlage für dieses Verfahren wird der Modellchecker UPPAAL eingesetzt.

Increasing complexity of today's software systems is one of the major challenges software engineers have to face. This is aggravated by the fact that formerly isolated systems have to be interconnected to more complex systems, called System-of-Systems (SoS). Those systems are in charge to provide more functionality to the user than all of their independent sub-systems could do. Reducing the complexity of such systems is one goal of the software engineering paradigm called component-based software engineering (CBSE). CBSE enables the developers to treat individual sub-systems as components which interact via interfaces with a simulated environment. Thus those components can be developed and implemented independently from other components. After the implementation a system integrator is able to interconnect the components to a SoS. Despite this much-used approach it is possible to show that constraints, which are valid in an isolated sub-system, are broken after this system is integrated into a SoS. To emphasize this issue we developed a technique based on interconnected timed automata for modelling sub-systems and System-of-Systems in the model checking tool UPPAAL. The presented modelling technique allows it to verify the correctness of single sub-systems as well as the resulting SoS. Additionally we developed a tool which abstracts the complicated timed automata to an easy to read component based language with the goal to help system integrators building and verifying complex SoS.