Saved in:
| Main Authors: | , , , , , , |
|---|---|
| Format: | Preprint |
| Published: |
2024
|
| Subjects: | |
| Online Access: | https://arxiv.org/abs/2404.12035 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| _version_ | 1866929318792265728 |
|---|---|
| author | Baumeister, Jan Finkbeiner, Bernd Kohn, Florian Löhr, Florian Manfredi, Guido Schirmer, Sebastian Torens, Christoph |
| author_facet | Baumeister, Jan Finkbeiner, Bernd Kohn, Florian Löhr, Florian Manfredi, Guido Schirmer, Sebastian Torens, Christoph |
| contents | This paper reports on the integration of runtime monitoring into fully-electric aircraft designed by Volocopter, a German aircraft manufacturer of electric multi-rotor helicopters. The runtime monitor recognizes hazardous situations and system faults. Since the correct operation of the monitor is critical for the safety of the aircraft, the development of the monitor must follow strict aeronautical standards. This includes the integration of the monitor into different development environments, such as log-file analysis, hardware/software-in-the-loop testing, and test flights. We have used the stream-based monitoring framework RTLola to generate monitors for a range of requirements. In this paper, we present representative monitoring specifications and our lessons learned from integrating the generated monitors. Our main finding is that the specification and the integration need to be decoupled, because the specification remains stable throughout the development process, whereas the different development stages require a separate integration of the monitor into each environment. We achieve this decoupling with a novel abstraction layer in the monitoring framework that adapts the monitor to each environment without affecting the core component generated from the specification. The decoupling of the integration has also allowed us to react quickly to the frequent changes in the hardware and software environment of the monitor due to the fast-paced development of the aircraft in a startup company. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2404_12035 |
| institution | arXiv |
| publishDate | 2024 |
| record_format | arxiv |
| spellingShingle | Monitoring Unmanned Aircraft: Specification, Integration, and Lessons-learned Baumeister, Jan Finkbeiner, Bernd Kohn, Florian Löhr, Florian Manfredi, Guido Schirmer, Sebastian Torens, Christoph Software Engineering Logic in Computer Science F.3.1; J.2 This paper reports on the integration of runtime monitoring into fully-electric aircraft designed by Volocopter, a German aircraft manufacturer of electric multi-rotor helicopters. The runtime monitor recognizes hazardous situations and system faults. Since the correct operation of the monitor is critical for the safety of the aircraft, the development of the monitor must follow strict aeronautical standards. This includes the integration of the monitor into different development environments, such as log-file analysis, hardware/software-in-the-loop testing, and test flights. We have used the stream-based monitoring framework RTLola to generate monitors for a range of requirements. In this paper, we present representative monitoring specifications and our lessons learned from integrating the generated monitors. Our main finding is that the specification and the integration need to be decoupled, because the specification remains stable throughout the development process, whereas the different development stages require a separate integration of the monitor into each environment. We achieve this decoupling with a novel abstraction layer in the monitoring framework that adapts the monitor to each environment without affecting the core component generated from the specification. The decoupling of the integration has also allowed us to react quickly to the frequent changes in the hardware and software environment of the monitor due to the fast-paced development of the aircraft in a startup company. |
| title | Monitoring Unmanned Aircraft: Specification, Integration, and Lessons-learned |
| topic | Software Engineering Logic in Computer Science F.3.1; J.2 |
| url | https://arxiv.org/abs/2404.12035 |